Generated on: August 02, 2025 Target period: Within the last 24 hours Processing mode: Details Mode Number of updates: 3 items
Published: August 01, 2025 18:45:04 UTC Link: Generally Available: Azure File Sync Arc Extension
Update ID: 498452 Data source: Azure Updates API
Categories: Launched, Storage, Azure Files, Features
Summary:
What was updated
Azure File Sync Arc Extension has reached general availability, enabling deployment and management of Azure File Sync on Arc-enabled Windows Servers.
Key changes or new features
The extension allows seamless installation and management of Azure File Sync on Windows Servers connected via Azure Arc. This expands hybrid file synchronization capabilities beyond traditional on-premises environments to include multi-cloud and distributed infrastructure. It simplifies syncing files between on-premises or other cloud servers and Azure Files, leveraging Azure Arc for unified management.
Target audience affected
Developers and IT professionals managing hybrid or multi-cloud environments who require centralized file synchronization and management across diverse Windows Server instances. Organizations using Azure Arc to extend Azure management to on-premises or other cloud servers will benefit from streamlined Azure File Sync deployment.
Important notes if any
General availability means the extension is production-ready with full support from Microsoft. Users should ensure their Windows Servers are Azure Arc-enabled to utilize this feature. This update enhances hybrid cloud scenarios by integrating Azure File Sync with Azure Arc’s management plane, improving operational efficiency and consistency.
For more details, visit: https://azure.microsoft.com/updates?id=498452
Details:
The Azure File Sync Arc Extension has reached general availability, marking a significant enhancement in hybrid file synchronization by enabling Azure File Sync deployment and management directly on Arc-enabled Windows Servers. This update addresses the growing need for unified file services across diverse environments, including on-premises data centers and multi-cloud infrastructures.
Background and Purpose:
Azure File Sync traditionally allows organizations to centralize their file shares in Azure Files while maintaining local access and performance through caching on Windows Servers. However, managing Azure File Sync across distributed and multi-cloud environments posed challenges due to disparate management tools and inconsistent deployment processes. The introduction of the Azure File Sync Arc Extension leverages Azure Arc’s capabilities to extend Azure management to any Windows Server, regardless of location, simplifying deployment, configuration, and monitoring of Azure File Sync in hybrid and multi-cloud scenarios.
Specific Features and Changes:
Technical Mechanisms and Implementation:
The extension operates by installing the Azure File Sync agent as an Arc extension on Windows Servers registered with Azure Arc. Azure Arc acts as a control plane, enabling Azure Resource Manager (ARM) templates and policies to deploy and configure the sync agent consistently. The sync agent then communicates with Azure Files shares, caching frequently accessed files locally and synchronizing changes back to Azure Files. This architecture ensures data consistency, reduces latency for local users, and provides cloud-based backup and disaster recovery capabilities.
Use Cases and Application Scenarios:
Important Considerations and Limitations:
Integration with Related Azure Services:
Published: August 01, 2025 16:00:17 UTC Link: Generally Available: Agentless multi-disk crash consistent backup for Azure VMs
Update ID: 499192 Data source: Azure Updates API
Categories: Launched, Management and governance, Storage, Azure Backup, Compliance, Features, Management
Summary:
What was updated
Azure Backup now offers Generally Available (GA) support for agentless multi-disk crash consistent backups for Azure Virtual Machines.
Key changes or new features
This update enables backup of multiple data disks attached to an Azure VM without requiring the installation of any backup agents inside the VM. The backups are crash consistent, capturing the VM and all attached disks in a consistent state at the time of backup. This simplifies backup management and reduces overhead by eliminating the need for in-guest agents, while supporting complex VM disk configurations.
Target audience affected
Developers and IT professionals responsible for Azure VM backup and disaster recovery, especially those managing multi-disk VMs who want simplified, agentless backup solutions.
Important notes if any
The feature is now GA, indicating production readiness and full support. Crash consistent backups do not guarantee application consistency, so workloads requiring application-consistent backups may still need agent-based solutions or additional configurations. This update improves backup efficiency and management for multi-disk Azure VMs without agent installation.
For more details, visit: https://azure.microsoft.com/updates?id=499192
Details:
The recent Azure Backup update announces the general availability of agentless multi-disk crash consistent backups for Azure Virtual Machines (VMs), enabling IT professionals to perform comprehensive VM backups without installing any backup agents inside the VM. This enhancement addresses the need for simplified, reliable, and scalable backup solutions for multi-disk Azure VMs, particularly in environments where agent installation is impractical or undesired.
Background and Purpose:
Traditionally, Azure VM backups relied on either agent-based or snapshot-based approaches. Agent-based backups require installation and management of backup agents inside each VM, which can increase operational overhead, complicate maintenance, and introduce potential compatibility issues. Snapshot-based backups, while agentless, often focused on single disk or OS disk backups, lacking comprehensive multi-disk consistency. The purpose of this update is to provide a fully agentless backup solution that ensures crash consistency across multiple attached data disks of a VM, simplifying backup management and improving reliability for complex VM configurations.
Specific Features and Detailed Changes:
Technical Mechanisms and Implementation Methods:
The agentless multi-disk crash consistent backup leverages Azure’s underlying snapshot and storage infrastructure. It uses Azure’s native snapshot capabilities to capture the state of all attached managed disks simultaneously. The backup service coordinates the snapshot creation to ensure all disks are captured at the same point in time, preserving crash consistency. This is achieved without requiring any in-guest coordination or quiescing, relying on the VM’s storage stack and Azure platform to maintain consistency. The snapshots are then stored in the Recovery Services vault, enabling restore operations as needed.
Use Cases and Application Scenarios:
Important Considerations and Limitations:
Integration with Related Azure Services:
Published: August 01, 2025 11:15:51 UTC Link: Retirement: Azure Dedicated HSM
Update ID: 499214 Data source: Azure Updates API
Categories: Security, Azure Dedicated HSM, Retirements, Services
Summary:
What was updated
Microsoft announced the planned retirement of the Azure Dedicated HSM service, which will be replaced by the newer Azure Cloud HSM service.
Key changes or new features
Azure Dedicated HSM will no longer be available after the retirement date. Customers are encouraged to transition to Azure Cloud HSM, which offers enhanced capabilities, improved scalability, and integration with Azure Key Vault for streamlined key management.
Target audience affected
This update primarily affects developers, IT professionals, and security teams currently using Azure Dedicated HSM for hardware security module (HSM)-based key management and cryptographic operations.
Important notes if any
Microsoft will continue to provide full support for existing Azure Dedicated HSM customers until July 31, 2028, allowing ample time for migration. Customers should plan their transition strategy to Azure Cloud HSM to benefit from the latest features and ensure continued compliance and security. No immediate action is required, but early migration is recommended to avoid service disruption post-retirement.
For detailed migration guidance and timelines, refer to the official Azure update link.
Details:
Microsoft has announced the planned retirement of the Azure Dedicated Hardware Security Module (HSM) service, with full support continuing until July 31, 2028, after which customers are encouraged to transition to the Azure Cloud HSM service. This update reflects Microsoft’s strategic move to consolidate and enhance its cryptographic key management offerings by leveraging the more scalable, flexible, and fully managed Azure Cloud HSM platform.
Background and Purpose:
Azure Dedicated HSM has historically provided customers with dedicated, single-tenant hardware security modules that allow organizations to generate, store, and manage cryptographic keys within FIPS 140-2 Level 3 validated HSMs. However, as cloud-native architectures evolve, there is a growing demand for more scalable, multi-tenant, and fully managed HSM services that integrate seamlessly with broader Azure security and identity frameworks. Azure Cloud HSM addresses these needs by offering a fully managed, elastic, and highly available HSM service that supports industry-standard APIs and integrates with Azure Key Vault.
Specific Features and Changes:
The retirement of Azure Dedicated HSM means no new Dedicated HSM instances will be provisioned, and existing customers must plan migration to Azure Cloud HSM before the end-of-support date. Azure Cloud HSM provides:
Technical Mechanisms and Implementation:
Azure Cloud HSM operates as a multi-tenant service built on FIPS 140-2 Level 3 validated HSMs hosted in Azure data centers. It abstracts hardware management complexities by automating provisioning, patching, and failover. Customers interact with Cloud HSM via standard cryptographic APIs, enabling seamless migration from Dedicated HSM with minimal application changes. Migration typically involves exporting keys from Dedicated HSM (where allowed by key export policies) and importing them into Cloud HSM or re-creating keys and certificates within the new environment.
Use Cases and Application Scenarios:
Both services are designed for scenarios requiring stringent cryptographic key protection, such as:
With the transition to Azure Cloud HSM, customers gain enhanced scalability and integration, making it suitable for modern cloud-native applications requiring flexible cryptographic services.
Important Considerations and Limitations:
Integration with Related Azure Services:
Azure Cloud HSM integrates tightly with Azure Key Vault Managed HSM pools, enabling centralized key management, role-based access control (RBAC), and logging via Azure Monitor and Azure Security Center. It also complements Azure Confidential Computing by securing keys used in Trusted Execution Environments (TEEs). Additionally, Cloud HSM supports integration with Azure Active Directory for authentication and authorization, enhancing security posture and operational efficiency.
In summary, the retirement of Azure
This report was automatically generated - 2025-08-02 03:01:52 UTC