Intro In this post, I want to show you how to set up Azure Migrate with VMware vSphere. I will go through the entire process of discovering, testing, and migrating virtual servers from my home lab environment into Azure. It will be a long post with many pictures, but I don’t feel splitting it into a series makes sense. I have used the Microsoft documentation as a guideline for this blog post.

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.

Intro Lately, I have been looking at Azure dashboards to provide a quick overview of services running in Azure. In this post, I want to show you how to create a dashboard showing the state of virtual machines, S2S VPN connections, and network peerings. Azure Resource Graph Explorer (RGE) The base for the dashboards in this post is RGE. I will create some queries to generate the data I want to show on my dashboard.

Intro Building on my last article on integrating Azure DevOps into Microsoft Teams, I want to show you how to incorporate dashboards and kanban boards. The integrations can be helpful when co-workers might not be inside Azure DevOps every day but are using Teams. Some of the integration can also provide co-workers/users the ability to create bug reports without having them inside your Azure DevOps environment. This article will add two dashboards and one kanban board into a Microsoft Teams channel.

Intro I want to show how to add Azure DevOps into Microsoft Teams in this post. I will show how to add the App to Teams and integrate it with the DevOps pipeline. The integration will display any pipeline actions, and it will also post any approval action into teams. With this integration, you can delegate activities in DevOps to coworkers who are not comfortable with Azure DevOps but are very pleased with Teams.

After being annoyed with WordPress, I decided to try something new. This week I looked at alternatives to WordPress, and going back and forth, I ended up with Hugo and Azure Static Web Apps as the solution. It is a very cheap solution, but also very powerful. I can use VS Code for writing blogs, and when I commit my code to GitHub, it will use a GitHub action to publish the changes to Azure Static Web Apps.

2021 has been a busy year for me, but in a good way. January, I started in a new role as Cloud Solution Specialist with edgemo A/S. It was strange to start the new position with Covid-19 still going strong, but it worked out great with the team I joined. We did meet at the office the first two days, but it was pretty much working from home for quite sometime after that.

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.

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:

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.