# Azure product updates - 2026-08-12 **4 new update(s)** — first seen in this run. The last 7 day(s) are rescanned every time so late or backdated announcements are not missed. Grouped by Azure product category. Source: [Azure Updates](https://azure.microsoft.com/en-us/updates) ## Summary by category | Category | Updates | GA | Preview | Top products | | --- | ---: | ---: | ---: | --- | | [Networking](#networking) | 2 | 1 | 1 | Azure Front Door | | [Compute](#compute) | 1 | - | 1 | App Service | | [Hybrid + multicloud](#hybrid-multicloud) | 1 | - | - | Microsoft Sentinel | ## Networking ### [Generally Available: Batch rule updates for Azure Front Door](https://azure.microsoft.com/en-us/updates?id=569246) **Status:** Launched | **Published:** 2026-08-12 | **Products:** Azure Front Door | **Tags:** Features Azure Front Door Standard and Premium now generally support batch rule updates, allowing multiple rule changes to be applied atomically for safer and more predictable Infrastructure-as-Code deployments. - Batch rule updates enable adding, updating, deleting, or reordering multiple rules in a rule set as a single coordinated operation. - This feature improves deployment safety by preventing partial rule states, rule-order conflicts, and rollback complexity, especially in large or complex rule sets. - Batch mode must be explicitly enabled when creating a new rule set; existing rule sets continue using classic rule management by default for backward compatibility. - Batch operations have size limits (up to 100 rules per set with caching rules counting as two) and require careful batching when many caching-enabled rules exist to avoid exceeding quotas during updates. Documentation: [Batch Rule Updates for Rule Sets - Azure Front Door](https://learn.microsoft.com/en-us/azure/frontdoor/rule-set-batch) ### [Public Preview: Azure Front Door mutual TLS](https://azure.microsoft.com/en-us/updates?id=569251) **Status:** In preview | **Published:** 2026-08-12 | **Products:** Azure Front Door | **Tags:** Feature Azure Front Door now supports mutual TLS (mTLS) in public preview, enabling client certificate authentication to enhance security for applications and APIs by validating client identities before requests reach the origin. - Supports four client certificate validation modes: require and validate, require without validation, validate when presented, and pass through to origin. - Validates client certificates issued by both public and private certificate authorities, with trusted CA chains uploaded to Azure Key Vault. - Includes comprehensive validation checks such as certificate validity period, Extended Key Usage, SAN/CN matching, and revocation status via OCSP. - mTLS enhances security for sensitive scenarios like B2B, IoT, financial services, and enterprise networks, but disables caching on routes where enabled. Documentation: [Mutual TLS authentication (Preview) - Azure Front Door](https://learn.microsoft.com/en-us/azure/frontdoor/mutual-tls) ## Compute ### [Public Preview: Markdown for Agents in Azure App Service](https://azure.microsoft.com/en-us/updates?id=568979) **Status:** In preview | **Published:** 2026-08-12 | **Products:** App Service | **Tags:** Feature Azure App Service now supports automatic conversion of HTML responses to Markdown for AI agents, simplifying content consumption without code changes. - Enables AI agents and tools to receive cleaner Markdown content instead of raw HTML. - Automatically converts app's HTML responses to Markdown upon client request. - Available in public preview for Azure App Service apps. - Improves integration with AI by reducing noise from scripts, styles, and HTML markup. Documentation: [Announcing public preview: Markdown for Agents in Azure App Service | Microsoft Community Hub](https://techcommunity.microsoft.com/blog/appsonazureblog/announcing-public-preview-markdown-for-agents-in-azure-app-service/4537023) ## Hybrid + multicloud ### [Retirement: Containerized data connector agent for the Microsoft Sentinel solution for SAP applications](https://azure.microsoft.com/en-us/updates?id=568457) **Status:** Retirement | **Published:** 2026-08-12 | **Products:** Microsoft Sentinel | **Tags:** Retirements, Security Microsoft Sentinel is retiring the containerized data connector agent for SAP applications on September 14, 2026, requiring customers to migrate to the agentless data connector which offers simplified deployment and reduced maintenance. - The containerized SAP agent will be permanently disabled on September 14, 2026, stopping SAP log collection through it. - The agentless data connector is generally available and supports side-by-side migration with no gap in log coverage. - Agentless connector offers zero footprint on SAP NetWeaver, less maintenance, and a future-proof architecture based on SAP Integration Suite and SAP Cloud Connector. - Existing analytics rules, workbooks, and playbooks remain functional with the agentless connector, ensuring continuity for customers. Documentation: [Containerized Agent to Agentless Connector migration guide](https://learn.microsoft.com/en-us/azure/sentinel/sap/sap-agent-migrate) --- _Generated automatically on 2026-08-12 23:46 UTC._