Generated on: September 17, 2025 Target period: Within the last 24 hours Processing mode: Details Mode Number of updates: 6 items
Published: September 16, 2025 21:30:32 UTC Link: Generally Available: At-cost data transfer between Azure and an external endpoint
Update ID: 501915 Data source: Azure Updates API
Categories: Launched, Pricing & Offerings, Management
Summary:
What was updated
Azure now offers at-cost data transfer pricing for data moved between Azure and external endpoints over the internet within Europe.
Key changes or new features
Customers and Cloud Solution Provider (CSP) partners in Europe can transfer data between Azure and non-Azure environments at cost, reducing expenses compared to standard data transfer rates. This update supports greater flexibility and cost efficiency for hybrid and multi-cloud scenarios involving data movement across network boundaries.
Target audience affected
Developers and IT professionals managing data integration, hybrid cloud architectures, or multi-cloud deployments in Europe. CSP partners reselling Azure services will also benefit from reduced data transfer costs.
Important notes if any
This at-cost pricing applies specifically to internet-based data transfers between Azure and external endpoints within Europe. It encourages customer choice and supports scenarios where data must flow between Azure and other environments without incurring premium data transfer fees. Users should verify regional applicability and consider this option when architecting data flows to optimize cost.
For more details, visit: https://azure.microsoft.com/updates?id=501915
Details:
The recent Azure update announces the general availability of at-cost data transfer pricing for data moved between Azure and external endpoints over the internet, specifically targeting customers and Cloud Solution Provider (CSP) partners in Europe. This update reflects Microsoft’s commitment to supporting customer choice and cost transparency when transferring data between Azure and non-Azure environments.
Background and Purpose
Traditionally, data egress from Azure to external networks incurs standard bandwidth charges, which can be significant and unpredictable for enterprises managing hybrid or multi-cloud architectures. Customers and CSPs often require frequent data exchanges between Azure and on-premises systems, other cloud providers, or external endpoints. The purpose of this update is to provide a more cost-effective and transparent pricing model—charging only the actual cost incurred by Microsoft for data transfer—thus enabling customers to optimize their network expenditure and improve budgeting accuracy.
Specific Features and Detailed Changes
Technical Mechanisms and Implementation Methods
From a technical standpoint, data transfer pricing is managed at the Azure subscription and billing layer. When data packets exit Azure datacenters to external IP addresses over the internet, the network monitoring and metering systems track the volume of data transferred. The billing system then applies the at-cost rate to these outbound transfers for eligible customers and CSP partners in Europe. There is no change required in user configuration or network setup; the pricing adjustment is transparent and automatic. The data transfer itself continues to use standard Azure networking infrastructure, including Azure Virtual Network (VNet) gateways, Azure Firewall, or load balancers, depending on the customer’s architecture.
Use Cases and Application Scenarios
Important Considerations and Limitations
Integration with Related Azure Services
In summary, the general availability of at-cost data transfer pricing for Azure-to-external internet transfers in Europe offers IT professionals a practical means to reduce network egress expenses, improve cost predictability
Published: September 16, 2025 19:45:51 UTC Link: Retirement: Azure Kubernetes Service on VMware will be retired on March 16, 2026 - Replace with Azure Kubernetes Service on Azure Local
Update ID: 500294 Data source: Azure Updates API
Categories: Retirements
Summary:
What was updated
Azure announced the retirement of Azure Kubernetes Service (AKS) on VMware (preview) effective March 16, 2026.
Key changes or new features
The AKS on VMware preview will no longer be supported after the retirement date. Microsoft recommends transitioning workloads to Azure Kubernetes Service on Azure Local, a fully supported AKS deployment option that provides a consistent Kubernetes experience closer to your on-premises environment.
Target audience affected
Developers and IT professionals currently using or evaluating AKS on VMware for container orchestration in hybrid or on-premises VMware environments.
Important notes if any
Plan your migration to AKS on Azure Local well before March 16, 2026 to avoid service disruption. Azure Local offers enhanced support and integration compared to the preview VMware offering. Review your current AKS on VMware workloads and dependencies to ensure a smooth transition. For more details, visit the official Azure update link.
Details:
The announced retirement of Azure Kubernetes Service (AKS) on VMware, effective March 16, 2026, signals a strategic shift by Microsoft to consolidate Kubernetes container orchestration offerings and streamline support towards Azure Kubernetes Service on Azure Local. AKS on VMware, introduced as a preview, enabled customers to deploy and manage AKS clusters directly on VMware infrastructure within their on-premises or hybrid environments, facilitating containerized application modernization without migrating workloads to the public cloud. The retirement notice advises users to transition to AKS on Azure Local, a fully supported service designed to run AKS clusters on Azure Stack HCI or Azure Stack Edge devices, providing a consistent Kubernetes experience closer to the edge or on-premises with full integration into Azure management and security frameworks.
From a feature perspective, AKS on VMware provided Kubernetes cluster lifecycle management, integrated Azure Active Directory (AAD) authentication, and Azure Monitor integration while running on VMware vSphere environments. Its retirement means these capabilities will no longer receive updates or support after the cutoff date. AKS on Azure Local offers comparable and enhanced features, including seamless integration with Azure Arc for hybrid management, Azure Policy enforcement for governance, and native support for Azure Container Registry and Azure DevOps pipelines. Technically, AKS on Azure Local leverages Azure Stack HCI infrastructure, utilizing Windows Server 2022 and Kubernetes distributions optimized for edge and on-premises scenarios, with automated cluster provisioning, upgrades, and scaling managed via Azure Portal or CLI.
Implementation of the transition involves assessing existing AKS on VMware workloads and migrating containerized applications and configurations to AKS on Azure Local clusters. This may require reconfiguring network settings, storage classes, and identity integration to align with Azure Local’s architecture. Tools such as Azure Migrate and Kubernetes-native utilities (e.g., Velero for backup/restore) can facilitate workload migration. The use cases for AKS on Azure Local encompass edge computing scenarios, disconnected or intermittently connected environments, and organizations requiring data residency or low-latency processing near the data source, while still benefiting from Azure’s cloud management capabilities.
Important considerations include planning the migration timeline well before the retirement date to avoid service disruption, validating compatibility of existing workloads with AKS on Azure Local’s Kubernetes version and supported features, and ensuring that operational teams are trained on the new environment’s management tools and security model. Limitations may arise from differences in underlying infrastructure capabilities between VMware and Azure Stack HCI platforms, such as storage options, networking plugins, or hardware compatibility, which must be evaluated during migration planning.
Integration with related Azure services is a key advantage of AKS on Azure Local. It supports Azure Arc-enabled Kubernetes for unified management across hybrid and multi-cloud environments, Azure Monitor for observability, Azure Policy for compliance enforcement, and Azure Security Center for threat protection. Additionally, it integrates with Azure DevOps and GitHub Actions for CI/CD pipelines, enabling streamlined DevOps workflows. This integration enhances operational efficiency and governance compared to the AKS on VMware preview, which had limited Azure service connectivity.
In summary, the retirement of AKS on VMware by March 16, 2026, requires IT professionals to proactively plan and execute migration to AKS on Azure Local to maintain supported Kubernetes container orchestration capabilities on-premises or at the edge. AKS on Azure Local offers a robust, fully supported platform with deeper Azure ecosystem integration, optimized for hybrid and edge scenarios, ensuring continuity, enhanced security, and management consistency within Azure’s cloud-native framework.
Published: September 16, 2025 17:45:04 UTC Link: Generally Available: Azure File Sync in Poland Central and Spain Central
Update ID: 503421 Data source: Azure Updates API
Categories: Launched, Compute, Storage, Cloud Services, Storage Accounts, Features
Summary:
What was updated
Azure File Sync is now generally available in the Poland Central and Spain Central regions.
Key changes or new features
This update extends Azure File Sync’s regional availability, enabling seamless synchronization and tiering of data between on-premises Windows Servers and Azure Files in these new locations. Organizations can now leverage hybrid cloud scenarios with improved data locality, reduced latency, and compliance benefits by keeping data closer to end users in Poland and Spain.
Target audience affected
Developers and IT professionals managing file server infrastructure, hybrid cloud storage solutions, and data migration projects in Poland, Spain, or nearby regions will benefit from this update. It is particularly relevant for those looking to optimize on-premises file server performance while integrating with Azure Files for backup, disaster recovery, or cloud tiering.
Important notes if any
Ensure your environment meets Azure File Sync prerequisites and consider network bandwidth and latency when deploying in these new regions. This regional expansion supports compliance with data residency requirements and can improve performance for local users accessing synchronized files. For detailed deployment guidance, refer to Azure File Sync documentation.
Details:
The recent general availability of Azure File Sync in the Poland Central and Spain Central regions extends Microsoft’s hybrid cloud storage capabilities by enabling organizations in these geographies to seamlessly synchronize and tier data between on-premises Windows Servers and Azure Files. Azure File Sync is designed to simplify data migration, enhance data availability, and optimize storage costs by combining the performance and compatibility of local file servers with the scalability and durability of Azure cloud storage.
Background and Purpose of the Update
Azure File Sync was introduced to address challenges faced by enterprises managing large volumes of file data across distributed environments. Traditionally, organizations rely on on-premises file servers for low-latency access but face limitations in scalability, backup complexity, and disaster recovery. Azure Files provides cloud-based SMB/NFS file shares with high durability but may introduce latency for local users. Azure File Sync bridges this gap by enabling a hybrid approach: local file servers cache frequently accessed data while less-used files are tiered to Azure Files, providing a unified namespace and centralized management. The expansion to Poland Central and Spain Central regions reflects Microsoft’s commitment to regional data residency, compliance, and performance optimization for customers in these areas.
Specific Features and Detailed Changes
With this update, customers can now deploy Azure File Sync endpoints and sync groups in Poland Central and Spain Central, benefiting from local Azure infrastructure. Key features include:
Technical Mechanisms and Implementation Methods
Azure File Sync operates by installing an agent on Windows Server (2012 R2, 2016, 2019, or later) that communicates with the Azure File Sync service. The service manages sync groups, which link one or more server endpoints to an Azure File share. The agent monitors file changes locally and synchronizes them to the cloud asynchronously. Cloud tiering uses a file attribute called the “hydration state” to determine whether a file is cached locally or tiered in the cloud. When a user accesses a tiered file, the agent transparently downloads the file on-demand. The sync engine uses a change journal and a cloud change log to track and reconcile changes, supporting conflict resolution and ensuring data consistency.
Use Cases and Application Scenarios
Important Considerations and Limitations
Published: September 16, 2025 17:45:04 UTC Link: Public Preview: Azure HBv5-series VMs
Update ID: 503129 Data source: Azure Updates API
Categories: In preview, Compute, Linux Virtual Machines, Virtual Machines, Windows Virtual Machines, Services
Summary:
What was updated
Azure announced the public preview availability of HBv5-series virtual machines (VMs) in the South Central US region.
Key changes or new features
HBv5 VMs are designed for high-performance computing (HPC) workloads that require high memory bandwidth. They feature AMD EPYC 7003-series processors with up to 120 vCPUs, large memory capacity, and support for RDMA over InfiniBand for low-latency, high-throughput networking. These VMs are optimized for applications such as computational fluid dynamics, automotive and aerospace simulations, weather modeling, and other memory bandwidth-intensive HPC scenarios.
Target audience affected
Developers and IT professionals working on HPC workloads, scientific simulations, engineering applications, and other compute- and memory-intensive tasks will benefit from these new VM options.
Important notes if any
The HBv5-series VMs are currently in public preview and available only in the South Central US region. Users should consider preview limitations and regional availability when planning deployments. Integration with Azure HPC networking features like RDMA is a key advantage for scaling HPC applications efficiently.
Details:
The Azure HBv5-series virtual machines (VMs) have entered public preview in the South Central US region, targeting high-performance computing (HPC) workloads that demand exceptional memory bandwidth and computational power. This update introduces a new VM SKU optimized specifically for memory bandwidth-intensive applications such as computational fluid dynamics (CFD), automotive and aerospace simulations, and weather modeling, expanding Azure’s HPC capabilities.
Background and Purpose
Azure’s HPC offerings continuously evolve to meet the growing computational and memory bandwidth requirements of scientific and engineering workloads. The HBv5-series VMs build upon the previous HB-series by incorporating the latest AMD EPYC 7003 “Milan” processors, which provide a significant increase in memory bandwidth and core count. The purpose of this update is to enable customers running memory-bound HPC applications to achieve better performance and scalability on Azure’s cloud infrastructure, reducing time-to-solution and improving cost efficiency.
Specific Features and Detailed Changes
Technical Mechanisms and Implementation Methods
The HBv5-series VMs utilize AMD’s latest EPYC “Milan” processors, which implement the Zen 3 microarchitecture. This architecture improves instructions per cycle (IPC) and memory subsystem efficiency, delivering higher memory bandwidth per core. Azure pairs these CPUs with RDMA-capable InfiniBand networking, enabling low-latency, high-bandwidth inter-node communication essential for distributed HPC workloads using MPI or similar frameworks. The VMs are deployed on Azure’s HPC-optimized infrastructure, ensuring dedicated hardware resources and isolation for predictable performance.
Use Cases and Application Scenarios
Important Considerations and Limitations
Integration with Related Azure Services
Published: September 16, 2025 17:30:21 UTC Link: Generally Available: AKS Automatic
Update ID: 503235 Data source: Azure Updates API
Categories: Launched, Compute, Containers, Azure Kubernetes Service (AKS), Features
Summary:
What was updated
Azure Kubernetes Service (AKS) Automatic is now generally available, providing enhanced automation for cluster management.
Key changes or new features
AKS Automatic simplifies Kubernetes operations by automating cluster lifecycle management tasks such as provisioning, scaling, patching, and upgrades. It reduces the operational overhead by handling infrastructure tuning and security updates automatically. This helps teams focus more on application development rather than cluster maintenance. The service also improves reliability and security by proactively managing risks and ensuring clusters are up-to-date with best practices.
Target audience affected
Developers and IT professionals managing Kubernetes workloads on Azure, especially those seeking to reduce complexity and operational burden in AKS cluster management.
Important notes if any
Teams adopting AKS Automatic should review their existing cluster configurations to align with automated management policies. While automation reduces manual intervention, monitoring and governance remain critical to ensure compliance and performance. This update is part of Azure’s ongoing efforts to streamline Kubernetes adoption and operational excellence.
For more details, visit: https://azure.microsoft.com/updates?id=503235
Details:
The Azure Kubernetes Service (AKS) Automatic Update feature has reached general availability, addressing the operational complexity and maintenance overhead commonly associated with managing Kubernetes clusters. This update is designed to streamline cluster management by automating the patching and upgrading of AKS nodes and control plane components, thereby enhancing security, reliability, and operational efficiency for IT teams.
Background and Purpose
Kubernetes, while powerful for orchestrating containerized applications, presents challenges in cluster lifecycle management, including frequent updates to address security vulnerabilities, bug fixes, and feature enhancements. Manual updates are time-consuming and error-prone, often requiring downtime or complex coordination. The AKS Automatic Update feature aims to reduce this operational burden by enabling automated, controlled, and seamless updates to AKS clusters, allowing teams to focus more on application development rather than infrastructure maintenance.
Specific Features and Detailed Changes
Technical Mechanisms and Implementation Methods
The Automatic Update feature integrates with AKS’s existing cluster management APIs and Azure Resource Manager (ARM) to schedule and execute updates. It leverages Kubernetes’ native rolling update mechanisms to drain and update nodes without impacting running workloads significantly. The control plane updates are managed by Azure as a managed service, ensuring minimal downtime. Users configure update policies via Azure CLI, Azure Portal, or ARM templates, specifying parameters such as maintenance windows, version constraints, and node pool selection. The system monitors cluster health during updates, with rollback capabilities if issues are detected.
Use Cases and Application Scenarios
Important Considerations and Limitations
Integration with Related Azure Services
In summary, the general availability of AKS Automatic Update significantly simplifies Kubernetes cluster maintenance by automating patching and upgrades within controlled parameters, improving security posture and operational efficiency while integrating seamlessly with Azure’s ecosystem of monitoring, governance, and DevOps tools. This enables IT professionals to
Published: September 16, 2025 14:30:41 UTC Link: Generally Available: Azure Container Storage v2.0.0 now with NVMe performance boost, open source, and no service fees
Update ID: 502853 Data source: Azure Updates API
Categories: Launched, Containers, Compute, Azure Container Storage, Azure Kubernetes Service (AKS), Features
Summary:
What was updated
Azure Container Storage (ACStor) has reached general availability with version 2.0.0.
Key changes or new features
ACStor v2.0.0 introduces a significant performance boost by leveraging local NVMe storage, delivering up to 7× higher IOPS and 4× lower latency compared to the previous version 1.3.1. This makes it the fastest storage option for Azure Kubernetes Service (AKS). Additionally, the solution is now open source and offered with no service fees, reducing cost and increasing transparency for users.
Target audience affected
Developers and IT professionals working with containerized applications on Azure Kubernetes Service will benefit from improved storage performance and cost efficiency. DevOps teams managing AKS clusters can leverage faster persistent storage for stateful workloads.
Important notes if any
The update emphasizes local NVMe storage integration, so workloads requiring high IOPS and low latency will see the most benefit. Being open source allows for community contributions and customization. No service fees mean organizations can optimize costs when scaling container storage in AKS environments.
For more details, visit: https://azure.microsoft.com/updates?id=502853
Details:
Azure Container Storage (ACStor) v2.0.0 has reached general availability, introducing significant performance improvements, an open-source model, and the removal of service fees, positioning it as a high-performance, cost-effective storage solution for Azure Kubernetes Service (AKS) workloads. This update addresses the growing demand for low-latency, high-throughput storage in containerized environments by leveraging local NVMe storage technology.
Background and Purpose
The update aims to enhance the storage performance and cost-efficiency for containerized applications running on AKS. Previous versions of ACStor provided persistent storage but were limited by traditional storage media and incurred service fees. As containerized workloads increasingly require faster I/O to support stateful applications such as databases, caching layers, and real-time analytics, ACStor v2.0.0 introduces NVMe-based local storage to meet these demands while simplifying cost structures through open-source availability and zero service fees.
Specific Features and Detailed Changes
Technical Mechanisms and Implementation
ACStor v2.0.0 leverages local NVMe SSDs attached to AKS nodes to provide ultra-low latency and high throughput storage. It implements a CSI driver that exposes these NVMe devices as persistent volumes to Kubernetes pods. The local NVMe storage is managed by ACStor’s control plane, which handles volume provisioning, lifecycle management, and data persistence. By using local storage rather than network-attached storage, ACStor minimizes I/O path length, reducing latency and increasing IOPS. The open-source nature allows users to inspect and modify the storage controller and CSI driver components.
Use Cases and Application Scenarios
Important Considerations and Limitations
Integration with Related Azure Services
ACStor v2.0.0 integrates tightly with
This report was automatically generated - 2025-09-17 03:03:16 UTC