Azure Template Specs

Intro

Azure Template Specs is an option for storing Azure ARM templates inside Azure to ease sharing templates across your organization. Accessing Template Specs is controlled with RBAC assignments, making Template Specs security like most other Azure resources. Template Specs deploys resources in Azure and is compatible with the tools we know already, so PowerShell, Azure CLI, Pipelines, and the Azure Portal.

To deploy from a Template Spec, a user only needs “Reader” permissions to the Template Spec, but permissions to create the resource in Azure are also required.

5 minutes to read
Martin Therkelsen
Read article

Azure DevOps - Deploy a website to Azure

Intro
In this post, I want to show you how to deploy a .Net 6.0 website to Azure using Azure DevOps. I will create a demo website in Visual Studio using the Microsoft provided templates and publish the website to Azure using a pipeline.

Workflow
The flow for the demo website is simple. I update text on the website and commit the code to an Azure DevOps repository. From Azure DevOps, I can use the repository in a pipeline to deploy the code to Azure. The workflow would be a continuous effort for a production website, so deployment can often happen with new ideas getting into production fast and effortlessly.

4 minutes to read
Martin Therkelsen
Read article

Create Azure Function with Azure DevOps Pipelines

Intro
I want to create the Azure resources needed to build Azure Functions in this post. I will guide you through the necessary bicep files to deploy a Storage Account, Application Insights, App Service Plan, and the Azure Function. You will deploy everything with code by the end of this post, including a demo function.

All code can be found on GitHub .

Workflow
As shown below, the workflow is:

  • Creating Storage Account
  • Creating Azure Application Insights
  • Creating Azure App Service Plan
  • Creating Azure Function
  • Deploying demo function to the Function App.

6 minutes to read
Martin Therkelsen
Read article

Using Azure Key Vault from Bicep

Intro
I have previously written a post on how to use Azure Key Vault with GitHub Actions, and this time I want to show you have to use Key Vault with Bicep deployments in Azure. The reason behind using Key Vault is to avoid having any passwords or secrets stored in templates. Using Key Vault, I can reference a secret that the deployment will look up at deployment time and not display in any log files. Another benefit of using Key Vaults is that the person who deploys the resources does not need to know the password for the resource but only the reference to the Key Vault. Deploying resources using Key Vaults dramatically increases the security and, at the same time, eases the deployments.
3 minutes to read
Martin Therkelsen
Read article

Manage route tables and Network Security Groups in Azure with Bicep and Azure DevOps pipelines

Intro
In this blog post, I want to show you how to maintain route tables and network security group (NSG) configurations in Azure using Azure DevOps and pipelines. I have already written a post on the NSG part, but I have updated a few things since then, so I want to show that in this post.

You can find all the files in this post in their full length on my GitHub .

6 minutes to read
Martin Therkelsen
Read article

Getting Azure Function under source control

Intro
In this post, I want to show you how you can easily set up Azure DevOps to control your Azure Function Apps (AF). Out of the box, AF supports editing in the portal or using VS Code / Visual Studio for both editing and updating. While both methods are fine, I prefer to use Azure DevOps for AF instead, enabling source control. Want to know how I do this? Read on, and I will show you. If you prefer to see it on a video instead, you can find it on my YouTube below.
4 minutes to read
Martin Therkelsen
Read article