Generated on: April 01, 2026 Target period: Within the last 24 hours Processing mode: Details Mode Number of updates: 8 items
Published: March 31, 2026 20:00:35 UTC Link: Retirement: External Data Import & Data Connections in Azure Machine Learning will be retired on September 30, 2026
Update ID: 557406 Data source: Azure Updates API
Categories: AI + machine learning, Internet of Things, Azure Machine Learning, Retirements
Summary:
What was updated
Azure Machine Learning is retiring the “Import data from external sources” (Preview) feature—including support for S3, Snowflake, and Azure SQL Database—as well as external Data Connections (Preview). These features will be deprecated and no longer available after September 30, 2026.
Key changes or new features
The ability to directly import data from external sources (S3, Snowflake, Azure SQL DB) and manage external Data Connections within Azure Machine Learning will be removed. No replacement features have been announced at this time.
Target audience affected
Developers, data scientists, and IT professionals who use Azure Machine Learning for data ingestion workflows that rely on these external data import and connection capabilities.
For more details, refer to the official Azure Update.
Details:
Azure Update Report: Retirement of External Data Import & Data Connections in Azure Machine Learning (Effective September 30, 2026)
Background and Purpose of the Update
Microsoft Azure is announcing the retirement of the External Data Import (Preview) and External Data Connections (Preview) features in Azure Machine Learning. These features currently allow users to import data from external sources such as Amazon S3, Snowflake, and Azure SQL Database directly into Azure Machine Learning environments. The purpose of this update is to inform users that these preview functionalities will be deprecated and unavailable after September 30, 2026, encouraging customers to plan for migration or alternative solutions.
Specific Features and Detailed Changes
The affected features include:
After September 30, 2026, these features will be removed from Azure Machine Learning. Users will no longer be able to create, manage, or utilize these data import and connection capabilities within the Azure Machine Learning workspace.
Technical Mechanisms and Implementation Methods
Currently, these preview features leverage built-in connectors and authentication mechanisms to establish secure connections to external data sources. Data import workflows typically involve specifying connection parameters, authentication credentials, and data selection queries within the Azure Machine Learning interface. The system then manages the data transfer and integration, making the external data available for model training, evaluation, and deployment tasks.
With the retirement, these mechanisms will cease to function, and any existing pipelines or scripts relying on these features will need to be refactored. Users must adopt alternative data ingestion methods, such as manually importing data into Azure Storage (Blob, Data Lake), or using other Azure data integration services like Azure Data Factory.
Use Cases and Application Scenarios
Typical use cases impacted by this change include:
Organizations leveraging these preview features for streamlined data access and integration in their ML pipelines will need to revise their architectures to accommodate the retirement.
Important Considerations and Limitations
Integration with Related Azure Services
Azure Machine Learning will continue to support data access via Azure-native services such as Azure Blob Storage, Azure Data Lake Storage, and integration with Azure Data Factory for orchestrating data movement. Users are encouraged to utilize these services for future data ingestion and connection needs.
Summary Sentence
The External Data Import and Data Connections (Preview) features in Azure Machine Learning, which enable direct access to external sources like S3, Snowflake, and Azure SQL Database, will be retired on September 30, 2026, requiring users to transition to alternative Azure-supported data integration methods.
Published: March 31, 2026 18:15:10 UTC Link: Generally Available: Azure DevOps March 2026 updates
Update ID: 559660 Data source: Azure Updates API
Categories: Launched, Developer tools, DevOps, Hybrid + multicloud, Azure DevOps, Features
Summary:
What was updated
Azure DevOps received several updates in March 2026, including the public preview of the Remote MCP Server and enhanced security improvements.
For more details, visit the official update: https://azure.microsoft.com/updates?id=559660
Details:
Azure DevOps March 2026 Updates – Technical Explanation
Background and Purpose of the Update
The March 2026 Azure DevOps update introduces significant enhancements aimed at improving integration capabilities and strengthening security posture. The primary focus is on enabling seamless, AI-powered workflows within Azure DevOps environments, while reducing infrastructure overhead and enhancing security for development teams.
Specific Features and Detailed Changes
Technical Mechanisms and Implementation Methods
Use Cases and Application Scenarios
Important Considerations and Limitations
Integration with Related Azure Services
Summary Sentence
The Azure DevOps March 2026 update introduces the Remote MCP Server in public preview, enabling AI-powered integration without local infrastructure, and delivers security improvements to enhance the overall DevOps environment.
Published: March 31, 2026 17:45:46 UTC Link: Public Preview: Azure Event Grid provides new capabilities for smarter, more secure event-driven architectures
Update ID: 559695 Data source: Azure Updates API
Categories: In preview, Features, Microsoft Build
Summary:
What was updated
Azure Event Grid has introduced new capabilities in Public Preview to enhance event-driven architectures, focusing on improved interoperability, security, and management for large-scale distributed systems.
Target audience affected
Developers and IT professionals building or managing event-driven solutions, especially those working with multi-tenant architectures, distributed systems, or requiring advanced event processing and security.
Details:
Azure Update Report
Title: Public Preview: Azure Event Grid provides new capabilities for smarter, more secure event-driven architectures
Link: Azure Update
Background and Purpose of the Update
Azure Event Grid is a managed event routing service designed for building scalable, event-driven architectures. The update introduces new capabilities in Public Preview, targeting improved management of large-scale, distributed systems. The primary purpose is to enhance interoperability and control, particularly in scenarios where organizations operate across multiple Azure tenants.
Specific Features and Detailed Changes
The key feature highlighted in this Public Preview is Cross-Tenant Webhook Delivery. This functionality enables secure event delivery between Azure tenants, addressing a common challenge in multi-tenant cloud architectures. Previously, event delivery was limited within a single tenant, restricting integration across organizational boundaries. With Cross-Tenant Webhook Delivery, Event Grid can now deliver events to endpoints (webhooks) residing in different Azure tenants, broadening the scope of event-driven integrations.
Technical Mechanisms and Implementation Methods
Cross-Tenant Webhook Delivery leverages secure webhook endpoints to facilitate event transmission between tenants. The mechanism likely involves enhanced authentication and authorization protocols to ensure that events are delivered only to trusted endpoints in external tenants. IT professionals can configure Event Grid to specify webhook endpoints in another tenant, enabling secure cross-tenant communication. This feature is designed to maintain the integrity and confidentiality of event data during transit, utilizing Azure’s built-in security controls.
Use Cases and Application Scenarios
Important Considerations and Limitations
Integration with Related Azure Services
Azure Event Grid integrates seamlessly with other Azure services such as Azure Functions, Logic Apps, and Azure Automation. The Cross-Tenant Webhook Delivery feature extends these integrations by enabling event-driven workflows across tenant boundaries. This enhancement allows IT professionals to build more flexible, distributed solutions leveraging Azure’s serverless and automation capabilities.
Summary Sentence
Azure Event Grid’s Public Preview introduces secure Cross-Tenant Webhook Delivery, empowering IT professionals to build interoperable, event-driven architectures across Azure tenants with enhanced control and scalability.
Published: March 31, 2026 17:30:08 UTC Link: Generally Available: User delegation SAS for Azure Tables, Azure Files, and Azure Queues
Update ID: 559535 Data source: Azure Updates API
Categories: Launched, Storage, Databases, Azure Files, Queue Storage, Table Storage, Features, Security
Summary:
What was updated
User delegation Shared Access Signatures (SAS) are now generally available for Azure Tables, Azure Files, and Azure Queues.
Key changes or new features
This update enables the use of user delegation SAS tokens, which are tied to Azure Active Directory (AAD) identities, for Azure Tables, Files, and Queues. User delegation SAS provides enhanced security compared to account-level or service SAS by associating the token with the user’s AAD credentials and permissions. This allows for more granular access control and better auditing capabilities.
Target audience affected
Developers and IT professionals managing access to Azure Tables, Azure Files, and Azure Queues, especially those implementing secure access patterns or integrating with AAD-based authentication.
Important notes if any
User delegation SAS is recommended over account or service SAS for scenarios requiring scoped, time-limited, and user-specific access to storage resources. This feature aligns with security best practices by reducing the risk of credential leakage and improving traceability. Existing applications using account or service SAS can consider migrating to user delegation SAS for improved security.
For more details, refer to the official Azure Update.
Details:
Comprehensive Technical Explanation:
Background and Purpose of the Update:
Previously, Shared Access Signatures (SAS) for Azure Tables, Azure Files, and Azure Queues were typically created using either account SAS or service SAS. These approaches, while functional, exposed risks because the SAS tokens were tied to the storage account keys, which, if compromised, could allow broad access. The purpose of this update is to enhance security by introducing user delegation SAS (UDSAS) for these services, allowing SAS tokens to be tied to an Azure Active Directory (Azure AD) security principal (the delegator), rather than the storage account keys.
Specific Features and Detailed Changes:
This update makes user delegation SAS generally available for Azure Tables, Azure Files, and Azure Queues. With this feature, users can now generate SAS tokens that are scoped to the permissions and lifetime of an Azure AD user or service principal. This is an extension of the User Delegation Key (UDK) model, previously available for Azure Blob storage, now supporting additional storage services.
Technical Mechanisms and Implementation Methods:
User delegation SAS works by authenticating the user or application with Azure AD. Once authenticated, the user requests a user delegation key from the storage service. This key is then used to generate a SAS token. The resulting SAS token is cryptographically bound to the Azure AD identity and the permissions granted to that identity. The SAS token’s validity is limited to the lifetime of the user delegation key and the permissions assigned via Azure RBAC (Role-Based Access Control).
Use Cases and Application Scenarios:
Important Considerations and Limitations:
Integration with Related Azure Services:
User delegation SAS integrates with Azure AD for authentication and RBAC for permission management. It complements existing security models in Azure Storage, enabling secure, delegated access for applications and users. This approach aligns with best practices for identity-based access control across Azure services.
Summary Sentence:
User delegation SAS for Azure Tables, Azure Files, and Azure Queues is now generally available, enabling more secure, Azure AD-based delegated access to these storage services by tying SAS tokens to the permissions and identity of the delegator.
Published: March 31, 2026 17:30:08 UTC Link: Generally Available: Azure Event Grid provides new capabilities for smarter, more secure event-driven architectures
Update ID: 492542 Data source: Azure Updates API
Categories: Launched, Integration, Internet of Things, Event Grid, Features, Microsoft Build
Summary:
What was updated
Azure Event Grid is now generally available with enhanced capabilities for building smarter and more secure event-driven architectures.
Target audience affected
Developers building event-driven or IoT solutions, IT professionals managing distributed systems, and architects designing secure, scalable cloud integrations.
For more details, refer to the official update: Azure Event Grid update
Details:
Azure Update Report
Title: Generally Available: Azure Event Grid provides new capabilities for smarter, more secure event-driven architectures
Link: Azure Update
Background and Purpose of the Update
Azure Event Grid is a core Azure service for building event-driven architectures, enabling reliable event routing and integration across distributed systems. The latest update introduces new features aimed at enhancing the management of large-scale, distributed environments by improving interoperability and control. This update addresses the need for more sophisticated event handling, especially in scenarios where message order and security are critical.
Specific Features and Detailed Changes
The update brings several generally available features, with a key highlight being MQTT Message Ordering. This feature ensures that messages delivered via the MQTT protocol are received in the exact order they were sent, which is essential for consistency in event processing and downstream logic. The update also includes enhancements designed to make Event Grid smarter and more secure, though the detailed scope of these additional features is not specified in the provided content.
Technical Mechanisms and Implementation Methods
Use Cases and Application Scenarios
Important Considerations and Limitations
Integration with Related Azure Services
Azure Event Grid can be integrated with a wide range of Azure services, including Azure IoT Hub, Azure Functions, Logic Apps, and Azure Service Bus. The new MQTT message ordering feature enhances Event Grid’s role as a central event routing hub, enabling more reliable and predictable event-driven workflows across these services. Engineers can leverage Event Grid’s capabilities to build robust, scalable, and secure solutions that respond to events from various sources and trigger actions in downstream Azure services.
Summary Sentence:
Azure Event Grid’s latest update introduces generally available features such as MQTT message ordering, enhancing interoperability, control, and security for large-scale, distributed event-driven architectures, and providing IT professionals with improved mechanisms for reliable and ordered event processing across integrated Azure services.
Published: March 31, 2026 17:15:56 UTC Link: Generally Available: Microsoft Azure now available from new cloud region in Denmark
Update ID: 559406 Data source: Azure Updates API
Categories: Launched, Regions & Datacenters
Summary:
What was updated
Microsoft Azure has launched a new cloud region, Denmark East, which is now generally available.
Key changes or new features
The Denmark East region offers local, secure cloud infrastructure for Danish customers. This enables support for data residency requirements, improved data security, and reduced latency for applications and services. The new region also supports Azure’s portfolio of services, including AI and digital transformation solutions.
Target audience affected
This update primarily impacts developers, IT professionals, and organizations operating in Denmark or with data residency needs in the region. It is also relevant for partners and ISVs building solutions for Danish customers.
Important notes if any
Customers can now deploy Azure resources in Denmark East to meet compliance and regulatory requirements for local data storage. The new region helps organizations optimize performance for end-users in Denmark and supports the adoption of AI and advanced cloud workloads. Review service availability for Denmark East, as not all Azure services may be available immediately.
Data source: Using API data
Link: https://azure.microsoft.com/updates?id=559406
Details:
Background and Purpose of the Update
Microsoft has announced the general availability of its new Azure cloud region in Denmark, named Denmark East. The primary purpose of this update is to accelerate digital transformation and AI innovation for Danish customers by providing local access to Microsoft Azure’s cloud infrastructure. This regional expansion is designed to address requirements for data residency, security, and performance, enabling organizations in Denmark to leverage Azure services while ensuring compliance with local regulations.
Specific Features and Detailed Changes
The Denmark East region offers a full suite of Azure services, delivered from local datacenters. Key features include:
This update introduces Denmark East as a selectable region in the Azure portal, allowing resource deployment and configuration specifically within Denmark.
Technical Mechanisms and Implementation Methods
Azure regions are composed of multiple datacenters, interconnected via Microsoft’s global backbone network. Denmark East is integrated into this architecture, providing redundancy, high availability, and disaster recovery capabilities. When deploying resources, customers can select Denmark East as the target region, ensuring that compute, storage, and networking resources are provisioned locally. Azure’s resource manager and region-specific APIs are updated to support Denmark East, enabling seamless integration with existing automation and deployment pipelines.
Use Cases and Application Scenarios
Important Considerations and Limitations
Integration with Related Azure Services
Denmark East is fully integrated with Azure’s global ecosystem, supporting cross-region networking, hybrid cloud scenarios, and multi-region deployments. Services such as Azure Active Directory, Azure Backup, and Azure Site Recovery can be configured to utilize Denmark East for local operations. Additionally, customers can leverage Azure’s global tools and APIs for monitoring, management, and automation across the new region.
Summary Sentence
Microsoft Azure’s Denmark East region is now generally available, providing Danish customers with secure, local cloud infrastructure to support data residency, low latency, and compliance, thereby enabling accelerated digital transformation and AI innovation.
Published: March 31, 2026 16:45:33 UTC Link: Retirement: Manually registered Azure VPN Clients for Azure Government and Microsoft Azure operated by 21Vianet clouds will be retired on March 31, 2029
Update ID: 557395 Data source: Azure Updates API
Categories: Networking, Security, VPN Gateway, Retirements
Summary:
What was updated
Microsoft announced the retirement of manually registered Azure VPN clients for point-to-site (P2S) connections using Microsoft Entra ID authentication in Azure Government and Microsoft Azure operated by 21Vianet clouds, effective March 31, 2029.
Key changes or new features
After March 31, 2029, manually registered Azure VPN clients will no longer be supported for P2S connections with Entra ID authentication in the specified sovereign clouds. Customers must transition to supported client registration methods before this date to maintain connectivity.
Target audience affected
This update impacts developers and IT professionals managing Azure VPN P2S connections in Azure Government and Microsoft Azure operated by 21Vianet environments, particularly those using manual client registration with Entra ID authentication.
Important notes if any
To avoid service disruption, customers should migrate to the recommended client registration methods before the retirement date. Review your current VPN client registration processes and update them as needed. This change does not affect Azure public cloud environments. For more details and migration guidance, refer to the official Azure Update: https://azure.microsoft.com/updates?id=557395
Details:
Azure Update Technical Report
Title: Retirement: Manually registered Azure VPN Clients for Azure Government and Microsoft Azure operated by 21Vianet clouds will be retired on March 31, 2029
Link: Azure Update
Background and Purpose of the Update
Microsoft has announced that manually registered Azure VPN clients for point-to-site (P2S) connections using Microsoft Entra ID authentication will be retired in Azure Government and Microsoft Azure operated by 21Vianet clouds on March 31, 2029. This update is part of Microsoft’s ongoing efforts to streamline authentication mechanisms and enhance security and manageability within specialized Azure cloud environments.
Specific Features and Detailed Changes
The retirement specifically targets VPN clients that have been manually registered for P2S connections, where Microsoft Entra ID (formerly Azure Active Directory) is used for authentication. After the retirement date, manually registered VPN clients will no longer be supported for these scenarios. The change applies only to Azure Government and Azure operated by 21Vianet, which are distinct from the global Azure cloud.
Technical Mechanisms and Implementation Methods
Currently, manually registered VPN clients require administrators to register each client individually for P2S connections, enabling Microsoft Entra ID authentication. This manual process involves configuring client certificates and registering device information in Azure. The retirement means that this manual registration workflow will be discontinued, and only supported or automated registration methods will be available for P2S VPN connections using Microsoft Entra ID authentication.
Use Cases and Application Scenarios
This update impacts organizations using Azure Government or Azure operated by 21Vianet that rely on manually registered VPN clients for secure remote access to resources via P2S VPN, authenticated through Microsoft Entra ID. Typical scenarios include government agencies or regulated enterprises that require granular control over VPN client registration and authentication.
Important Considerations and Limitations
Integration with Related Azure Services
Point-to-site VPN connections are commonly used with Azure Virtual Network Gateway, enabling secure remote access to Azure resources. Microsoft Entra ID provides identity-based authentication for these connections. The retirement of manual registration will require organizations to integrate with automated or supported client registration workflows, ensuring compatibility with Azure Virtual Network Gateway and Microsoft Entra ID.
Summary Sentence:
Manually registered Azure VPN clients for point-to-site connections using Microsoft Entra ID authentication in Azure Government and Azure operated by 21Vianet will be retired on March 31, 2029, requiring organizations to transition to supported registration methods to maintain secure remote access.
Published: March 31, 2026 16:30:51 UTC Link: Generally Available: Azure Premium SSD v2 Disk is now available in US Gov Arizona
Update ID: 559677 Data source: Azure Updates API
Categories: Launched, Storage, Compute, Azure Disk Storage, Virtual Machines, Features, Services
Summary:
What was updated
Azure Premium SSD v2 Disk is now generally available in the US Gov Arizona region.
Key changes or new features
Premium SSD v2 is a next-generation general-purpose block storage option for Azure virtual machines. It provides sub-millisecond latencies and high performance, making it suitable for a wide range of enterprise workloads. This release extends support to the US Gov Arizona region, which does not have Availability Zones.
Target audience affected
Developers and IT professionals deploying or managing Azure VMs in US Gov Arizona, especially those requiring high-performance, low-latency disk storage for mission-critical applications.
Important notes if any
The US Gov Arizona region does not support Availability Zones, which may impact high-availability configurations. Customers can now leverage Premium SSD v2’s improved performance and flexibility for government workloads in this region. Review your storage architecture to ensure compatibility and optimal use of the new disk type. For more details, refer to the official Azure documentation.
Details:
Background and Purpose of the Update
This update announces the general availability of Azure Premium SSD v2 disk in the US Gov Arizona region. The purpose is to extend the next-generation general-purpose block storage solution to customers operating in this US Government cloud region, which does not support Availability Zones. This enables government and regulated customers in the region to leverage enhanced disk performance for their Azure virtual machines (VMs).
Specific Features and Detailed Changes
Azure Premium SSD v2 disk is a next-generation block storage offering for Azure VMs. Key features highlighted by this update include:
The main change is the regional expansion, making Premium SSD v2 available in US Gov Arizona, which previously did not offer this disk SKU.
Technical Mechanisms and Implementation Methods
Azure Premium SSD v2 disks are provisioned and managed through the Azure Portal, Azure CLI, PowerShell, or ARM templates, similar to other Azure Managed Disks. These disks are attached to Azure VMs as managed disks, providing persistent storage. The sub-millisecond latency is achieved through Azure’s next-generation storage infrastructure, which is optimized for high throughput and low-latency access patterns. The disks are designed to deliver consistent performance, leveraging Azure’s underlying hardware and software enhancements.
Use Cases and Application Scenarios
Premium SSD v2 disks are ideal for:
Important Considerations and Limitations
Integration with Related Azure Services
Premium SSD v2 disks integrate seamlessly with Azure Virtual Machines as managed disks. They can be used with Azure Backup and Azure Site Recovery for data protection and disaster recovery scenarios. The disks are also compatible with Azure Disk Encryption for enhanced security. Integration with Azure Monitor allows for performance and health monitoring of disk resources.
Summary Sentence
Azure Premium SSD v2 disk, now generally available in the US Gov Arizona region, provides sub-millisecond latency and exceptional performance for Azure VMs, enabling government customers to deploy high-performance, general-purpose block storage in a region without Availability Zones.
This report was automatically generated - 2026-04-01 03:04:46 UTC