Credits and sources Microsoft Learnhttps://learn.microsoft.com/en-us/azure/defender-for-cloud/defender-for-cloud-introduction TechTargethttps://www.techtarget.com/searchsecurity/definition/Cloud-Security-Posture-Management-CSPM Intro In this blog series, I want to focus on how Microsoft Defender for Cloud (MDFC) can help secure your Azure environment. MDFC is a collection of Defender products that provides security and visibility into your security posture in Azure. Still, many security features can also cover on-premises and other public clouds. MDFC offers free features and a range of paid features for your cloud workloads.

Credits and sources Microsoft Learnhttps://learn.microsoft.com/en-us/azure/bastion/bastion-overview Intro I want to look closely into the Azure Bastion service in this post. Azure Bastion is a service that provides secure remote access to Azure virtual machines. Bastion supports RDP and SSH for managing the virtual machines, and all traffic will use TLS for security. One of the key benefits of Bastion is that the need for a public IP address on your resources is removed.

Intro In this part of the series, I am creating the AVD session hosts so my users can start using the new Azure environment. A session host is a virtual machine that users can log in to and use their corporate software while having low latency to other resources placed in Azure. The steps I will go through in this post are. Deploy a virtual machine Install the AVD components on the virtual machine.

Intro In this part of the series, I want to ensure that all permissions are given to the correct groups. I could provide access to individual users, but I try to stick to groups as they are easier to manage across an enterprise. I have identified the following permissions I need to grant to user groups. Azure AD Group to add to AVD Application groups Azure AD Group to add to “Virtual Machine User Login” RBAC role for the session hosts Azure AD Group to add to the “Storage File Data SMB Share Contributor” for the profile storage account There are a few steps to get the storage account configured, and I will go through this process in depth.

Intro I have now come to the part where I will start deploying AVD resources in my Azure environment. I am going to split the resources up into three parts. This first part will be the “backend,” meaning AVD workspace, host pool, and application groups. The next part will be on RBAC roles and security groups, and the last part will be on the session hosts. Azure virtual desktop hostpool First, I will create a host pool for AVD as a container for the session hosts.

Intro I want to deploy some network services to my environment in this part of the blog series. I first need to update my peerings to use the VPN gateway. The VPN requires a slight change in both ends of the current peering. I also want to add an Azure Firewall, which means using route tables, and finally, I want to add network security groups to my subnets in the AVD virtual network.

Intro In this part of the blog series, I want to deploy a new virtual network for my Azure Virtual Desktop environment. I also want to create a network peering between the new network and the one I already deployed named vnet-connectivity-001. Azure Virtual Desktop network As I created a virtual network already in the blogs series, I will make a copy of the code for the network and adjust it to fit this new network I am creating.

Intro In this part of the blog series, I want to deploy my VPN connection to my on-premises environment and the log analytics workspace. Azure key vault Before I can start with my VPN connection I need to create an Azure key vault to store my VPN shared secret. The variables file for my key vault is shown below. variable "Location" { type = string default = "WestEurope" } variable "ResourceGroup" { type = string default = "rg-keyvault-001" } The main.

Intro In this part of the blog series, I want to focus on the GitHub Actions I created in the first part and explain what the Action performs. I will also add the vNet resources to my deployments. GitHub Actions explained To explain what is going on in the GitHub Action, I have added comments to each code section.

Name of the action name: rg-connectivity-001 # Controls when the workflow will run on: # Triggers the workflow on changes to the terraform files in the path # Subscriptions/Sub-MVP-Sponsorship/rg-connectivity-001/ # Action will only trigger on the main branch push: paths: - 'Subscriptions/Sub-MVP-Sponsorship/rg-connectivity-001/*.

Intro This blog series will create and maintain Azure resources using GitHub repositories, GitHub Actions, and Terraform. I will use this blog series to build out a new Azure tenant that I have created, and I thought I might share what I was doing along the way. If you have any questions about this blog series, please reach out to me. The design I am working on right now is outlined below.