April 5, 2023
Welcome to the seventh edition of the Azure World Newsletter in 2023.
Hello again, my friends from around the world. I’m so happy you continue to subscribe and read this bi-weekly newsletter on Azure. I enjoy sitting down each week to research and write this, and hopefully, you will continue to find value in it. Feel free to invite your co-workers or others to subscribe if you think they would find it helpful.
The unsubscribe link is at the bottom if you want to stop receiving these emails.
ONE.
Recently, a new service went into general availability called Azure Virtual Network Manager or AVNM. This service continues along the trend of central management of resources. AVNM enables you to manage and scale your virtual networks in Azure centrally.
AVNM allows you to create a mesh or secure hub-and-spoke network in one operation instead of provisioning the individual resources and peer them yourself.
When creating your Azure Virtual Network Manager, you will be asked to define the scope. You can set AVNM to a management group scope and manage the virtual networks across several subscriptions.
It also allows you to group virtual networks into network groups. You can select and add networks to the group using static membership. Or use Azure Policy to add networks to the group using dynamic membership.
- Key benefits:
- Centrally manage connectivity and security policies globally across regions and subscriptions.
- Enable direct connectivity between spokes in a hub-and-spoke configuration without the complexity of managing a mesh network.
- Highly scalable and highly available service with redundancy and replication across the globe.
- Ability to create network security rules that override network security group rules.
- Low latency and high bandwidth between resources in different virtual networks using virtual network peering.
- Roll out network changes through a specific region sequence and chosen frequency.
More info:
What is Azure Virtual Network Manager? | Microsoft Learn
TWO.
When creating Cosmos DB databases, you typically provision and pay for the resource using a metric called Request Units or RU. This, however, forces you to predict in advance how many RUs are needed in advance including how many request units each query costs and how many simultaneous queries will need to be running.
There was a benefit to this, in that the RU was an abstraction from the system resources such as CPU, IOPS, and memory required to run the database.
Now, Azure is introducing Cosmos DB for MongoDB vCore.
As the name implies, instead of having to define request units, you now provision a MongoDB server by CPU, IOPS, and RAM.
There is a similar dynamic on the Azure SQL Database side. You can provision a server based on tiers or provision it based on vCores.
Cosmos DB for MongoDB vCore is currently in preview mode.
More info:
Introduction/Overview – Azure Cosmos DB for MongoDB vCore | Microsoft Learn
AZURE PLATFORM UPDATES.
The following updates to the Azure platform were announced in the last two weeks:
- Azure Virtual Network Manager (AVNM), now in GA
- Azure Cosmos DB for MongoDB vCore, in preview
- Azure Monitor Alerts now support duplicating alert rules, now in GA
- Azure Premium SSD v2 Disk Storage in East US 2, North Europe and West US 2, now in GA
- Larger SKUs for App Service Environment v3, now in GA
- Mount Azure Files and ephemeral storage in Azure Container Apps, in GA
- Azure Image Builder Portal Functionality now available
Much of this news at this time is about service retirements. These announcements mention services that will no longer exist and by what date.
- AKS will stop support for Windows Server 2019 on March 1, 2026
- Batch Service in select regions will be retired on 31 March 2026
- Docker container runtime retirement for Windows node pools effective May 1, 2023
- Batch custom image pools using VHD or managed images will be retired on 31 March 2026
- ExpressRoute Public Peering will be retired on March 31, 2024
- SQL Server connector’s V1 actions and triggers will be retired on 31 March 2024
- Azure CDN Standard from Akamai is being retired, and services will end on 31 October 2023
- On 28 March 2025, Azure Database for PostgreSQL Single Server will be retired, and you’ll need to migrate to Azure Database for PostgreSQL Flexible Server by that date
- The “managed” IoT Edge solution on Azure Stack Edge will be retired on 31 March 2024
- Implement disaster recovery strategies for your Azure App Service web apps by 31 March 2025
Be sure and check out the Azure Updates page if any of these affect you.
https://azure.microsoft.com/en-us/updates/
COMING UP FOR ME.
I’ve decided to re-record the AZ-104 course from top to bottom completely. The first 10 hours of that 16-hour course have already been re-done, and I’m continuing to update videos every day. If you’re in the course, you’ll already see the new content as I upload it as I complete it. If you’re not, why not? Get your Azure Administrator certification in 2023 with the absolute latest and best-selling course on the topic: http://sjd.ca/az104
My ChatGPT course continues to sell, and the field continues to evolve rapidly. I’ve already updated the course to talk about the new GPT-4 release, as well as the rollout of the new Bing. You can see videos in the course about both. I’ll continue to update and revise as the field changes. http://sjd.ca/chatgpt
WHERE TO FIND ME.
And that’s it for issue 4.07. Thanks for reading this far. Talk to you again in two weeks.
What is your favorite platform to be on? Perhaps we can connect there.
Facebook Page: https://www.facebook.com/getcloudskills/
LinkedIn: https://www.linkedin.com/in/scottjduffy/
Instagram: https://www.instagram.com/getcloudskills.ca/
Twitter: https://twitter.com/scottjduffy
Udemy: https://www.udemy.com/user/scottduffy2/
LinkedIn Learning: https://www.lynda.com/Scott-Duffy/1993589682-1.html


