This guide explains how to join an Azure virtual machine to Azure Active Directory (Azure AD). Please note that this process has several prerequisites that must be met before configuration which are described in the guide itself.
In this guide, I show the path from installation to deployment: I install the needed Bicep software, I prepare my Azure login using Azure CLI, and then I run a single server Bicep setup so you can see the process end-to-end.
This guide explains how to enable and use Windows Admin Center in Microsoft Azure to manage several Windows Server VMs by installing the extension and connecting using a webbased interface.
In this post I will show you how to deploy ARM templates directly from a public URL, how to create a Deploy to Azure button, and why converting Bicep to ARM JSON is the easy part.
In Azure we can link tags onto different resources, resource groups and subscriptions. We can use resource tagging for various reasons. With Azure Policy we can automate this process even further, linking different resources automatically based on what we want to achieve. For example, giving every resource in a specific resource group a tag.
Cost management is very important when leveraging cloud services. Unexpected costs of cloud services can really disallow us from using any more services, and knowing from week to week what happens can help us with this. To partly address this issue for Azure Consumption costs, I have made a Logic App that sends us the actual consumption on weekly level. This because Logic Apps gives us much more customization options as the default built-in "Subscribe" feature.
Sometimes you just want to trigger an Entra Connect sync quickly, without opening an RDP session to the Entra Connect server itself. For that reason I made a small PowerShell script that runs the sync remotely from a management server. It keeps the action simple: connect to the Entra Connect server, start a delta sync, show the result, and catch errors if something goes wrong.
When you reinstall your admin workstation or setup a fresh workstation, there are always a couple of PowerShell modules and tools must be installed install directly. These modules save a lot of time and make managing Azure and Microsoft 365 environments much easier but you always have to remember them correctly to actually install them.
Dynamic Groups are really great for automating certain things. They are basically like groups like we know them for several years but they always required some sort of manual action or assignment. Dynamic Groups will help us eliminating this. I will give some examples how I implemented certain actions in production. I will also share the rules syntaxes which can be used directly into your environment and can be changed to your likings.