Azure Update - 1st August 2025

Key insights

• TLS 1.0 and 1.1 Retirement: Azure will stop supporting TLS 1.0 and TLS 1.1 for all services after August 31, 2025. Only more secure versions like TLS 1.2 or later will be allowed.

• Mandatory Upgrade to TLS 1.2 or Later: All connections to Azure, including services like Application Gateway and Storage, must use TLS 1.2 or newer for better security and compliance with modern standards.

• Action Required for Customers: Customers need to update their systems to support TLS 1.2. This includes checking SSL profiles, updating software, and making sure all connections meet the new requirements before the deadline.

• New Azure Features Available: Recent general availability releases include live resizing for Premium SSD v2, updated policies for SAS tokens, and auto-provisioning in Kubernetes Service (AKS).

• Preview Updates: New features in preview include support for AZNFS 3.0 with FUSE for BlobNFS and Kafka triggers on Azure Functions consumption plan, showing ongoing improvements across services.

• AI and Fabric Enhancements: Azure has added new fine-tuning options in AI services and visual SQL audit log setups within Microsoft Fabric, giving users more control over data management and analytics.

Introduction: Major Security Shift for Azure Users

Azure’s latest update, as highlighted in John Savill’s MVP YouTube video from August 1, 2025, brings a significant security change to the forefront. The central focus is the final enforcement of the retirement of TLS 1.0 and TLS 1.1 support across all Azure services. With a firm deadline set for August 31, 2025, this move aims to improve both security and compliance for organizations relying on Microsoft’s cloud platform.

This policy shift means that after the deadline, all connections to Azure services—including critical components like Application Gateway—must use TLS 1.2 or later. The update is part of a broader ongoing effort to ensure stronger encryption and better protection against evolving cyber threats. Let’s break down the implications, challenges, and additional updates highlighted in the video.

End of Support for Legacy TLS Protocols

The retirement of TLS 1.0 and TLS 1.1 has been anticipated for some time, but Microsoft extended the deadline to allow customers more time to adapt. Now, with the final date approaching, it is essential for organizations to verify their systems and ensure compliance.

TLS 1.0 and 1.1 are considered outdated due to vulnerabilities that could be exploited by attackers. By enforcing TLS 1.2 or newer, Azure aligns itself with industry standards and regulatory requirements, reducing the risk of data breaches. However, this transition may pose challenges for organizations still operating legacy applications or devices that do not support modern encryption protocols.

Mandatory Upgrades: What Customers Must Do

With the new requirement, all Azure services—including Application Gateway, Storage, and others—will only accept connections using TLS 1.2 or above. This means customers must review their entire technology stack, from frontend interfaces to backend integrations, to confirm compatibility.

Updating TLS policies, configuring SSL profiles, and upgrading client or server software might be necessary steps. The tradeoff here is balancing the cost and effort of these upgrades against the improved security and compliance. Some organizations may face challenges if they have dependencies on older libraries or systems, requiring careful planning and testing to prevent disruptions.

Additional Azure Enhancements and Previews

Beyond the security update, John Savill’s video covers several noteworthy Azure advancements. For instance, features such as live resizing for Premium SSD v2 and Ultra NVMe Disks are now generally available, offering greater flexibility for storage management. Enhanced policies for Shared Access Signature (SAS) tokens in Azure Storage add another layer of security and governance.

Meanwhile, preview releases like AZNFS 3.0 for BlobNFS with FUSE support and Kafka trigger integration for Azure Functions illustrate Microsoft’s commitment to continuous improvement. These updates enable users to optimize workloads and adopt new capabilities, but they also bring decisions about when and how to implement new features versus maintaining stability in production environments.

Azure AI, Data Services, and Retirement Notices

The update also spotlights advancements in Azure AI, including enhanced fine-tuning options and new visual SQL audit log configurations within Microsoft Fabric. These enhancements can help organizations extract more value from data while maintaining robust oversight.

On the other hand, the retirement of the Azure Dedicated HSM (Hardware Security Module) service marks the end of an era for some customers. Transitioning away from retired services can require significant migration planning and may involve tradeoffs between cost, complexity, and desired security posture.

Conclusion: Preparing for the August 31 Deadline

In summary, the most urgent action for Azure customers is to ensure all connections use TLS 1.2 or newer before August 31, 2025. This update aligns Azure with best practices for encryption and data security, but it demands proactive attention to avoid service disruptions.

While the security upgrade is paramount, users are also encouraged to explore the latest Azure features and previews to further optimize their cloud environments. By staying informed and adaptable, organizations can navigate both the challenges and opportunities presented by Microsoft’s evolving cloud platform.

Keywords

Azure Update August 2025 Azure latest features 2025 Microsoft Azure news Cloud computing updates Azure service improvements August 2025 Azure security updates Azure performance enhancements