Today, we are looking at the final topic for the MB-400 exam – the Data Export Service - a convenient tool to use when performing simplistic integrations involving Dynamics 365 Online or the Common Data Service. What’s more, it’s dead easy to set up too...
We've dealt with a fair share of Azure Resource Manager (ARM) template errors in the blog previously. So why not take a look at another one, this time involving Linux App Service Plans and a .NET Core web application...
Secure authentication between Azure Logic App and Function Apps has been possible for a while. What's less clear is whether we can automate the setup of this as part of an Azure Resource template deployment. So, that leaves us with only one option - let's find out!
Azure API Management and resource manager templates are not natural bedfellows, as I recently discovered. Although it's possible to get them working alongside each other, there is a bit of trial and error involved. That's why I thought I'd share my recent experiences working with them both.
A common gripe concerning Microsoft Azure App Service is the fact that you must pay an additional cost to deploy a TLS certificate. Fortunately, this concern is now a thing of the past, thanks to the introduction of the App Service Managed Certificate preview feature.
A few weeks ago, I did a post on the process involved when migrating Microsoft Azure Cloud Solutions Provider (CSP) subscriptions across tenants. Having done some actual work relating to this since then (shock horror!), I thought I'd follow up with a new post, sharing some additional thoughts and lessons learned.
Moving Azure subscriptions across multiple tenants is usually a doddle. I say “usually” because, recently, I hit a bit of brick wall when figuring out to move a Cloud Solutions Provider (CSP) subscription, with there being no obvious way of achieving this simple task.
Migrating across from Microsoft Flow to Azure Logic Apps is ridiculously easy. However, there are some critical feature differences that you must make yourself aware of. One difference relates to how triggers actions work, particularly in tandem with an Azure template.
Validating your Azure templates manually can be a challenging task to complete at scale. Fortunately, with the functionality available within Azure Pipelines, this entire process can be fully automated. This post will show you just how easy it is to implement automatic validation an deployment of your Azure templates within a CI process.