After the pandemic beguns Microsoft switched the both big conference Microsoft Build and Microsoft Ignite to virtual only events. The Ignite was two times a year in 2020 and 2021. For 2022 it was long time not clear will it go back to an in-person event or still stay as a virtual event.
The Microsoft Ignite 2022 has start 2 hours ago as an hybrid event delivered from Seattle with 6 Spotlight events around the globe and delivered as before virtually. I’m a little disappointed because a lot of the content is pre-recorded and even great speakers like Donovan Brown don’t hold their sessions live in Seattle but are only shown there virtually as well.
In this article I will share the important announcements from my perspective from the Microsoft Ignite 2022. Most of you know me as an Azure Governance, (Hybrid) Infrastructure and Security guy, so please forgive me for focusing on these things.
In the past, it was quite quiet about new features and announcements in the Azure IaaS space. Yes, sometimes there were new VM sizes with more cores or more RAM, but in general there were no surprising announcements last year. From my point of view, this has changed with MS Inspire, which is currently underway.
Microsoft announced, surprising from my point of view, a new Disk SKU for Azure VMs called Premium SSD v2 Disk. The last announcement in this area was 2019 with the introduction of Ultra Disks.
I know it’s been a little quiet on new blog articles the last few months, but that’s due to other community topics I’m working on. One of my new projects is the Azure Ask my Anything Live format that I will be hosting with my team at Azure Bonn Live on YouTube and Linkedin. I’m excited to announce that we’re kicking off this year with an Azure AMA on Azure Virtual Desktop Best Practices, and we have the pleasure of welcoming Marcel Meurer and Patrick Koehler to this session. Marcel and Patrick are two Azure MVPs and do a lot of work in the AVD community. Marcel is known as the brains behind the WVDAdmin and Project Hydra products, which are services to automate all things Azure Virtual Desktop. Patrick has also been active in the AVD community for many years with great sessions and insights about AVD and is the organizer of AVD TechFest together with Simon Binder.
Azure AMA – Azure Virtual Desktop Best Practices will take place live on Youtube on February 14, 2022. You can register for this event via our Azure Bonn page. Please note that this is a live AMA session and we would love for you to join us live and bring your questions to the session. If you don’t have time this time, please use our Microsoft forms to submit your questions before the session starts. The session will be held in German, but you can also ask your questions in English.
In the last couple of days I try to optimize some Azure environments from security and cost perspective. One customer has a SQL Server Express installed inside an Azure VM. The backup was configured for the hole VM, but there is no need to backup the Datadisk which contains the SQL databases. In this article I will explain how you can reinstall the Azure Backup Windows Workload extension to fix the issue when the service account will not listed on the Azure SQL Server VM. This fix the issue only did you not find the service account in the SQL Server management studio. To add the account in the right way, please refer to the article from Wim Matthysen.
Microsoft has changed the #AzureBastion minimum subnet size from /27 to /26. Installed #Azure Bastion are unaffected, but new deployments require the new subnet size. Please remember this. https://docs.microsoft.com/en-us/azure/bastion/bastion-faq#subnet
When you create an Azure Bastion instance Microsoft creates in the backend an optimized Azure VM that runs all the processes they are needed for Azure Bastion. This Azure VM is called a Instance and had some limitations. In general when you deploy the Azure Bastion Basic SKU Microsoft deploys two instances which supports 20-24 concurrent sessions which means each instance support 10-12 sessions.
The Standard SKU allows you to specify the number of instances called as host scalling.
Please note that when using an Azure Bastion Standard SKU, the AzureBastionSubnet size should be increased to a subnet size of approximately /26 or larger.
up to 50
Max. supported concurrent sessions
up to 500
Azure Portal, Powershell, CLI
Only Azure Portal
Deploy an Azure Bastion Standard SKU
Only the Azure Portal allows to deploy an Azure Bastion Standard SKU with the host scalling feature, because the feature is in public preview.
Over the past few months, I have conducted many customer workshops, designed and implemented Landing Zones, and migrated or placed VMs into Azure. One of the most common customer questions has been about best practices for Azure VMs to maximize performance and efficiency, minimize costs, increase security, and reduce management overhead. This article is based on my real-world experience and recommendations based on several Azure projects.
In the last couple of days I get a lot of question how to move Azure VMs between regions. So I decided to write a blog post about this question. First of all it is really important to understand which topics this article covers and which not.
To understand the article right, keep the follow settings in mind:
This article will cover how to move Azure VMs between global regions with ASR
Global regions mean all the standard available regions
This article doesn´t cover the movement between Azure Global and Azure Germany, Azure Governance or China
For moving Azure VMs from Azure Germany to Azure Global there there is planned to write an additional article
For a general movement of Azure resources (SQL databases, Web Apps and more) a futher post will follow
This article focuses on how to move Azure VMs between Azure global regions using Azure Site Recovery (ASR). Another article will focus on how to move other Azure resources between regions.
To move Azure VMs between different global regions with ASR there are some requirements needed:
Azure subscriptions are allowed to create Azure VMs in the target regions
User rights to create the Azure ressources (Azure VMs, VNETs, NICs, etc.)
Install latest updates on Windows/Linux OS
Check that the VM has Internet access without Proxy or Firewall between VM and Internet
Configure the VNET and Subnet in the target destination before move the VM to a different region
The process to move Azure VMs between different Global regions is straight forward. But don´t forget, all related management tasks to the VM, like Backup, Log analytics Workspace, Start Stop Runbooks will be lost after the migration.
In the past I do a lot of Azure Governance workshops. One part of this workshops are the high availabilty options in Azure. This article descripe the different SLAs for VM workloads in Azure. Often I get an ask about the SLA level and the requirements. In this discussion many people are confused about the difference of Availability Set and Availability Zone and how this compares to the SLA. The new feature about the Proximitiy Placement Groups comes into play to make the confusing complete. This article descripes the differences between these features.
Für Azure VM’s gibt es unterschiedliche Disk Typen mit unterschiedlichen Performancewerten. Dazu zählen Standard HDDs, Standard SSDs und Premium SSDs. Vor wenigen Tagen ganz neu hinzugekommen sind die Ultra SSDs.
In diesem Blog Beitrag gehe ich auf die neuen Ultra SSDs ein. Stelle die Leistungswerte der unterschiedlichen SSDs gegenüber und stelle die Besonderheiten der Ultra SSDs in ihrer jetzigen Form vor.
In unterschiedlichen Szenarien kommt es vor, dass wir Images hochladen aus denen wir AzureVMs bereitstellen. Gerade in den Szenarien wo Citrix on Azure eingesetzt wird, werden häufig vorkonfigurierte Windows 10 VMs auf VMware erstellt, gesyspreped und entsprechend in eine VHD konvertiert.
Bei einem solchen Szenario hatte ich jetzt einen interessanten Fehler der mich etwas beschäftigte. Nachdem die VM erstellt und entsprechend der Anleitung Vorbereitung einer Windows VM zum hochladen in Azure konfiguriert wurde, erhielt ich nach Upload der VHD und generieren eines Image aus der VHD folgende Fehlermeldung:
New-AzureRmImage : Only blobs formatted as VHDs can be imported. ErrorCode: InvalidParameter