You can start getting the most mileage out of your Azure resources by working with them together. A great example is the focus of today's blog post, as we review a handy feature involving Azure Key Vault and Azure App Service / Function Apps.
Data Engineering on Azure is not an easy topic to grasp, and the corresponding certification pathway was also arduous. Thankfully, change is afoot, as we now have a brand new exam available to test our knowledge with…
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.
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.