Public Preview for Azure Migrate ASP.NET Assessments & Business Case for Windows Containers
Today we're excited to announce the public preview of ASP.NET Assessments and the Business Case features for Windows Containers on Azure Kubernetes Services (AKS) and App Service via Azure Migrate. These new features add on top of the existing functionality of discovering and migrating .NET web apps. Azure Migrate aims to be a one-stop shop for all migrations to Azure, providing capabilities to discover, assess and right size your workloads and migrate them at-scale. With these new features, Azure Migrate provides the following for ASP.NET web apps: Cloud readiness for AKS, App Service A recommended configuration of Node SKUs and Node count (or App Service plan) The yearly cost savings by running these apps on Azure.
Containers in AKS cannot access Azure resources (Failed to resolve URL)
I have an API server (Python Flask) hosted on AKS. When the service starts, it: Access Azure key-vault to get storage account connection string use the connection string to perform CRUD jobs on Azure storage account > PS. The whole system consists of `ingress(clusterIP & loadbalancer)`, `service (clusterIP)`, and my `flask API` Then I deploy it to AKS, which works fine (except that the CPU usage is usually > 100%). Two days later, I noticed that the server started restarting over and over again. The error message looks like this: `azure.core.exceptions.ServiceRequestError: <urllib3.connection.HTTPSConnection object at 0x7fc1f5e0c550>: Failed to resolve 'MY_KEY_VAULT.vault.azure.net' ([Errno -3] Temporary failure in name resolution)` At first, I thought it was caused by key vault, so I put the connection string directly in my code. And same thing happened again, `Failed to resolve 'MY_STORAGE_ACCOUNT.blob.core.windows.net' ([Errno -3] Temporary failure in name resolution` After my first deployment, I did nothing to my AKS resources. Below is basic info about my AKS: One possible root cause is that I set auto upgrade to `enable`. Please give me some suggestions for debugging, thanks! [Update -1] I deploy same container to another node pool. Things works fine ...Azure September: Announced end of life
For those who missed the last announces of Azure end of life, please find a small recap: Azure AI Intelligence The Azure AI Document Intelligence API v2.0 will be retired on August 31, 2026. You are simply encouraged to migrate to the same API but in version 3.1 which obviously offers more features than the previous one. Azure AI Video Indexer Due to the withdrawal of Azure Media Services, announced during the month of July, Microsoft has decided to remove all dependencies related to Azure Media from Azure AI Video Indexer, starting January 15, 2024. Azure FarmBeats The Azure FarmBeats project will be retired on September 30, 2023. For those who are not familiar with Azure FarmBeats, it is a solution that allows you to aggregate agricultural datasets from different providers. Instead, Microsoft offers Azure Data Manager for Agriculture, which is actually an enhanced version of the Azure FarmBeats project. Azure HPC Azure FXT Edge Filer which is a caching appliance for HPC computing tasks will be retired on December 31, 2026. However, no information on a possible service which will replace it. Azure Kubernetes Service The AKS product team has decided to remove Azure Monitor for AKS-Engine on September 14, 2026. You are therefore encouraged to use Azure Monitor for Containers functionality instead. We continue with another decommission on AKS which concerns the HTTP application routing add-on module, which will be deleted on March 3, 2025. Please note that this module is no longer supported since version 1.22 of K8S. Instead, you are encouraged to use the Web Application routing add-on. Azure Sphere The Classic version of Azure Sphere CLI will be decommissioned on September 30, 2024. No worries here for its replacement which is none other than Azure Sphere CLI. Azure Database for MariaDB End of life of Azure Database for MariaDB which will be retired on September 19, 2025. Microsoft therefore suggests that you use Azure Database for MySQL instead which offers more features. Azure Monitor The removal of the Data Collector API that manages custom log ingestion into Azure Monitor logs will be done on September 14, 2026. Before this date, you will need to migrate to the rules-based log ingestion API which provides all the functionality of the Data Collector API, plus some new features. On September 30, 2026 the "Classic" URL Ping Tests configured on Application Insights will be deleted, in favor of the "Standard" tests. Azure Storage The product team announced for September 13, 2024 the removal of the old Azure Storage Python client libraries, but also the Azure Storage Ruby client libraries, as well as the old Azure Storage Go client libraries. Instead you will have to use the new libraries. Azure Maps The product team announces that the Azure Maps Data V1/V2 APIs will be retired on September 16, 2024. Instead, Azure Maps has deployed Data Registry APIs that provide enhanced data security. Azure Maps Render V1 APIs will be retired on September 17, 2026. You are therefore encouraged to migrate or deploy Azure Maps Render V2 APIs, which provide improved data quality and performance compared to the previous version. The Azure Maps Gen1 pricing tier will no longer exist from September 15, 2026. You will therefore need to upgrade to the Azure Maps Gen2 pricing tier which offers simplified pricing and better flexibility.Azure decommissioning - December 2023
Hi there I know that 2023 is over, but if you missed them, here are the decommissions announced by the Azure teams during the month of December: 1). 5G & Space Azure Object Anchors The service will be withdrawn on May 20, 2024. So for those like me, who don't know this service, it allows you to create 3D content objects through virtual points on physical objects. Azure Spatial Anchors Same punishment for the Azure Spatial Anchors service which will be withdrawn on November 20, 2024. Just like the previous one, I didn't know it, and it allows developers to generate mixed reality applications. -- 2). Containers Azure Container Apps On the Azure Container Apps side, the product team has decided to remove the plane 2023-04-01-preview control API from March 6, 2024. You simply need to switch to the latest stable version of the API i.e. 2023-05-01 Azure Kubernetes Service On the AKS side, the Pod Security Policy functionality which was in preview, will be removed as of August 1, 2024. Instead, Microsoft encourages you to use the Pod security admission controller functionality or the Azure policy service. -- 3). Management and Governance Azure Automation On August 31, 2024, change tracking and inventory with the Log Analytics agent will be removed. Instead you are encouraged to migrate to change tracking and inventory in Azure Monitoring Agent. The removal of the Update Management features, as well as the Log Analytics agent as of August 31, 2024. Azure Update Manager is the perfect replacement for Update Management, in fact I'm going to take a look at it because I might have some needed on one of my projects. Azure Monitor The removal of custom alerts from Container insights recommended alerts on May 31, 2024, instead of March 14, 2026. You are therefore encouraged to use the Prometheus rules instead. -- 4). Network VPN Gateway The withdrawal of the Standard and High Performance SKUs for the VPN gateway service on September 30, 2025. You will therefore need to consider using another SKU before this date to avoid any impact on your infrastructure. See you soon đTransforming Enterprise AKS: Multi-Tenancy at Scale with Agentic AI and Semantic Kernel
In this post, Iâll show how you can deploy an AI Agent on Azure Kubernetes Service (AKS) using a multi-tenant approach that maximizes both security and cost efficiency. By isolating each tenantâs agent instance within the cluster and ensuring that every agent has access only to its designated Azure Blob Storage container, cross-tenant data leakage risks are eliminated. This model allows you to allocate compute and storage resources per tenant, optimizing usage and spending while maintaining strong data segregation and operational flexibilityâkey requirements for scalable, enterprise-grade AI applications.
WAC Azure Extension vs Local Installation - Feature Set checklist
Hi All Is there any article that has a comprehensive side by side of the features that are available via the WAC Extension in Azure (Arc specifically) vs downloading and installing WAC locally I was trying to follow Thomas Mauer's guide to deploy an AKS cluster locally. I wanted to achieve this from Azure, but the AKS blade/option is not present via this extension. Is there a method to connect to the local WAC from Azure, similar to the way the extension is presented? I am aware that I could deploy WAC locally, configure AKS on it, then join that on its own to Azure. My use-case on this is that I have a bunch of bare-metal that has a lot of compute power that would make for excellent local clusters or dev environments.
