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.
Dealing with “Your Azure credentials have not been set up or have expired” Error Message in a Azure Template Visual Studio Project
Keeping things simple is an idea I like to promote at all times, particularly in the world of IT. Adopting this mantra can lead to fewer headaches and, as a recent example involving Azure Template deployments within Visual Studio demonstrates, a much faster resolution to your particular problem.
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.
When working with Azure templates for the first time, there's always a risk of misconfiguring a setting. All fine when testing, until you realise you have been charged an unexpected amount on your credit card. In this post, I provide an example of this in practice when working with Stream Analytic Job resources.
It's essential to understand the precise behaviour your Azure templates will have when deployed, to avoid any unexpected issues or even data loss that could occur. This week's post will explore an example of why this is so important, involving Azure App Service application settings.