Merge pull request #313340 from MicrosoftDocs/repo_sync_working_branch

Taojunshen · web-flow · commit ebddfa96c26f · 2026-03-19T00:36:09.000+08:00
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
diff --git a/articles/application-gateway/mutual-authentication-arm-template.md b/articles/application-gateway/mutual-authentication-arm-template.md
@@ -388,4 +388,4 @@ az deployment group create \
 
 ## Security notice
 
-This solution is classified as **Microsoft Confidential**. Please ensure you follow your organization’s security and data handling best practices when deploying and managing this solution.
+Please ensure you follow your organization’s security and data handling best practices when deploying and managing this solution.
diff --git a/includes/data-explorer-limits.md b/includes/data-explorer-limits.md
@@ -14,6 +14,7 @@ The following table describes the maximum limits for Azure Data Explorer cluster
 | Instances per cluster | 1,000 | 
 | Number of databases in a cluster | 10,000 |
 | Number of follower clusters (data share consumers) per leader cluster (data share producer) | 100 |
+| Recommended maximum extents per cluster | 10,000,000 |
 
 > [!NOTE]
 > You can request higher limits for *Number of databases in a cluster* and *Clusters per region per subscription*. To request an increase, contact [Azure Support](https://azure.microsoft.com/support/legal/faq/).

Original file line number	Diff line number	Diff line change
`@@ -388,4 +388,4 @@ az deployment group create \`
`388`	`388`
`389`	`389`	`## Security notice`
`390`	`390`
`391`		`-This solution is classified as Microsoft Confidential. Please ensure you follow your organization’s security and data handling best practices when deploying and managing this solution.`
	`391`	`+Please ensure you follow your organization’s security and data handling best practices when deploying and managing this solution.`