Cloudninja.nu
Search

Azure Network Security Group rules - Azure DevOps

As you may know, I am a bit fan of automation and source control, and the reason for this is that these tools help me provide a stable IT environment for customers and internal use. The confidence that doing an installation or update and that the deployment is executed exactly as I did the last time is something I appreciate. Using automation doesn’t mean there are no mistakes, but I only have to fix it one time instead of remembering or doing a document each time explaining the change. Source control enables me to see what changes have been made to the environments I work with. It serves as a documentation framework and ensures I don’t change production until I commit the code to my production branch.
Automation Azure Devops Microsoft Automation Azure Azuredevops Devops Microsoft
7 minutes to read
Martin Therkelsen
Read article

GitHub Actions and Azure key vault

We all know that we shouldn’t put any passwords into our code and check them into source control, but many guides (including my own) often reference a password variable or parameter. The parameter option is actually OK, in my opinion, as long as you then reference a secure password from either an Azure DevOps library, GitHub Secret, or using an Azure key vault. In this post, I want to show you how to reference secrets stored in the Azure key vault and use them in a GitHub action and pass the value to a Bicep deployment. I have written a blog series on using GitHub actions and Bicep. If you haven’t read it yet, have a look here .
Automation Azure Devops Microsoft Automation Azure Azuredevops Microsoft
4 minutes to read
Martin Therkelsen
Read article

Getting started with GitHub Actions and Bicep – Part 6

This is the last part of this blog series, and here I want to show you how to use a JSON configuration file and a PowerShell script to deploy the same environment as you have seen in the first five parts of the series. This deployment type will feel familiar to many consultants since PowerShell is widely used among consultants. This deployment method can ease them into a DevOps mindset. Doing it this way enables flexibility around which part of the code to deploy by using if statements in the PowerShell script.
Automation Azure Devops Microsoft Automation Azure Citrixctp Microsoft
6 minutes to read
Martin Therkelsen
Read article

Getting started with GitHub Actions and Bicep - Part 5

In this part of the series, I will create two virtual machines and join them in my on-premises domain. These machines will be Citrix Cloud Connectors that will serve my Citrix environment with a new resource location in Azure. The Cloud Connectors will be deployed in an Azure Availability Set to ensure high availability.

Source code can be found on my GitHub, find it here .

I start with the creation of a new branch for my code, this will be called “VM”.

Automation Azure Devops Microsoft Automation Azure Citrixctp Microsoft
8 minutes to read
Martin Therkelsen
Read article

Getting started with GitHub Actions and Bicep - Part 4

In this part of the blog series, I want to create the VPN connection from Azure to my on-premises lab environment.

As I did in the last part, I will create a new branch in Github for my work. I am doing this to ensure that my main branch is always running without errors. I will call this new branch for “VPN”.

The first step is to create the template file for the Virtual Network Gateway in Azure. I found the documentation for this item here . As with some of the other resources, there are a lot of settings that I can use, but not all of them are needed. I adapted the template for my needs, and it now looks like the code below. I have saved this file as “VirtualNetworkGateway.bicep” and placed it under the same template folder as the virtual network.

Automation Azure Devops Microsoft Automation Azure Citrixctp Microsoft
6 minutes to read
Martin Therkelsen
Read article

Getting started with GitHub Actions and Bicep - Part 3

I want to create my resource groups and my virtual network in this part of the blog series. To create these resources will use a combination of Bicep files, where I split my code into an execution file with parameters and a generic template file. I am doing this to not limit my options for deploying environments. In fact, the last post in this series will be to deploy the same environment but switching the execution code with a PowerShell script.
Automation Azure Devops Microsoft Automation Azure Citrixctp Microsoft
8 minutes to read
Martin Therkelsen
Read article
Newer posts Older posts