update

Author: mumian

articles/azure-resource-manager/templates/deployment-history-deletions.md

@@ -2,7 +2,7 @@
 title: Deployment history deletions
 description: Describes how Azure Resource Manager automatically deletes deployments from the deployment history. Deployments are deleted when the history is close to exceeding the limit of 800.
 ms.topic: conceptual
-ms.date: 04/28/2025
+ms.date: 05/21/2025
 ms.custom: devx-track-azurecli, devx-track-arm-template
 ---
 
@@ -12,6 +12,18 @@ Every time you deploy a template, information about the deployment is written to
 
 Azure Resource Manager automatically deletes deployments from your history as you near the limit. Automatic deletion is a change from past behavior. Previously, you had to manually delete deployments from the deployment history to avoid getting an error. This change was implemented on August 6, 2020.
 
+
+
+
+Every time you deploy a template, information about the deployment is written to the deployment history. Each resource group is limited to 800 deployments in its deployment history.
+
+Azure Resource Manager automatically deletes deployments from your history as you near the limit. **Automatic deployment deletion applies to all scopes: resource group, subscription, and management group.** Automatic deletion is a change from past behavior. Previously, you had to manually delete deployments from the deployment history to avoid getting an error. This change was implemented on August 6, 2020.
+
+
+
+
+
+
 > [!NOTE]
 > Deleting a deployment from the history doesn't affect any of the resources that were deployed.
 

includes/azure-resource-groups-limits.md

@@ -5,6 +5,7 @@ ms.topic: include
 ms.date: 10/25/2024
 ms.author: jgao
 ---
+
 | Resource | Limit |
 | --- | --- |
 | Resources per [resource group](../articles/azure-resource-manager/management/overview.md#resource-groups) | Resources aren't limited by resource group. Instead, they're limited by resource type in a resource group. See next row. |