Merge pull request #116436 from tfitzmac/0526deploy

add note for deploy deletions

Author: American-Dipper

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

@@ -0,0 +1,78 @@
+---
+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: 05/27/2020
+---
+# Automatic deletions from deployment history
+
+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.
+
+Starting in June 2020, 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.
+
+> [!NOTE]
+> Deleting a deployment from the history doesn't affect any of the resources that were deployed.
+
+## When deployments are deleted
+
+Deployments are deleted from your deployment history only when you near the limit of 800. Azure Resource Manager deletes a small set of the oldest deployments to clear space for future deployments. Most of your history remains unchanged. The oldest deployments are always deleted first.
+
+:::image type="content" border="false" source="./media/deployment-history-deletions/deployment-history.svg" alt-text="Deletions from deployment history":::
+
+In addition to deployments, you also trigger deletions when you run the [what-if operation](template-deploy-what-if.md) or validate a deployment.
+
+When you give a deployment the same name as one in the history, you reset its place in the history. The deployment moves to the most recent place in the history. You also reset a deployment's place when you [roll back to that deployment](rollback-on-error.md) after an error.
+
+## Opt out of automatic deletions
+
+You can opt out of automatic deletions from the history. **Use this option only when you want to manage the deployment history yourself.** The limit of 800 deployments in the history is still enforced. If you exceed 800 deployments, you'll receive an error and your deployment will fail.
+
+To disable automatic deletions, register the `Microsoft.Resources/DisableDeploymentGrooming` feature flag. When you register the feature flag, you opt out of automatic deletions for the entire Azure subscription. You can't opt out for only a particular resource group.
+
+# [PowerShell](#tab/azure-powershell)
+
+For PowerShell, use [Register-AzProviderFeature](/powershell/module/az.resources/Register-AzProviderFeature).
+
+```azurepowershell-interactive
+Register-AzProviderFeature -ProviderNamespace Microsoft.Resources -FeatureName DisableDeploymentGrooming
+```
+
+To see the current status of your subscription, use:
+
+```azurepowershell-interactive
+Get-AzProviderFeature -ProviderNamespace Microsoft.Resources -FeatureName DisableDeploymentGrooming
+```
+
+# [Azure CLI](#tab/azure-cli)
+
+For Azure CLI, use [az feature register](/cli/azure/feature#az-feature-register).
+
+```azurecli-interactive
+az feature register --namespace Microsoft.Resources --name DisableDeploymentGrooming
+```
+
+To see the current status of your subscription, use:
+
+```azurecli-interactive
+az feature show --namespace Microsoft.Resources --name DisableDeploymentGrooming
+```
+
+# [REST](#tab/rest)
+
+For REST API, use [Features - Register](/rest/api/resources/features/register).
+
+```rest
+POST https://management.azure.com/subscriptions/{subscriptionId}/providers/Microsoft.Features/providers/Microsoft.Resources/features/DisableDeploymentGrooming/register?api-version=2015-12-01
+```
+
+To see the current status of your subscription, use:
+
+```rest
+GET https://management.azure.com/subscriptions/{subscriptionId}/providers/Microsoft.Features/providers/Microsoft.Resources/features/DisableDeploymentGrooming/register?api-version=2015-12-01
+```
+
+---
+
+## Next steps
+
+* To learn about viewing the deployment history, see [View deployment history with Azure Resource Manager](deployment-history.md).

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

@@ -3,11 +3,13 @@ title: Deployment history
 description: Describes how to view Azure Resource Manager deployment operations with the portal, PowerShell, Azure CLI, and REST API.
 tags: top-support-issue
 ms.topic: conceptual
-ms.date: 05/22/2020
+ms.date: 05/26/2020
 ---
 # View deployment history with Azure Resource Manager
 
-Azure Resource Manager enables you to view your deployment history and examine specific operations in past deployments. You can see the resources that were deployed, and get information about any errors.
+Azure Resource Manager enables you to view your deployment history. You can examine specific operations in past deployments and see which resources were deployed. This history contains information about any errors.
+
+The deployment history for a resource group is limited to 800 deployments. As you near the limit, deployments are automatically deleted from the history. For more information, see [Automatic deletions from deployment history](deployment-history-deletions.md).
 
 For help with resolving particular deployment errors, see [Resolve common errors when deploying resources to Azure with Azure Resource Manager](common-deployment-errors.md).
 
@@ -111,7 +113,7 @@ Each deployment can include multiple operations. To see more details about a dep
 
 1. On the summary for a deployment, select **Operation details**.
 
-    ![Select deployment operations](./media/deployment-history/get-operation-details.png)
+    ![Select operation details](./media/deployment-history/get-operation-details.png)
 
 1. You see the details for that step of the deployment. When an error occurs, the details include the error message.
 
@@ -204,6 +206,6 @@ The response includes an error message.
 ## Next steps
 
 * For help with resolving particular deployment errors, see [Resolve common errors when deploying resources to Azure with Azure Resource Manager](common-deployment-errors.md).
-* To learn about using the activity logs to monitor other types of actions, see [View activity logs to manage Azure resources](../management/view-activity-logs.md).
+* To learn about how deployments are managed in the history, see [Automatic deletions from deployment history](deployment-history-deletions.md).
 * To validate your deployment before executing it, see [Deploy a resource group with Azure Resource Manager template](deploy-powershell.md).
 

articles/azure-resource-manager/templates/deployment-quota-exceeded.md

@@ -2,13 +2,16 @@
 title: Deployment quota exceeded
 description: Describes how to resolve the error of having more than 800 deployments in the resource group history.
 ms.topic: troubleshooting
-ms.date: 10/04/2019
+ms.date: 05/26/2020
 ---
 
 # Resolve error when deployment count exceeds 800
 
 Each resource group is limited to 800 deployments in its deployment history. This article describes the error you receive when a deployment fails because it would exceed the allowed 800 deployments. To resolve this error, delete deployments from the resource group history. Deleting a deployment from the history doesn't affect any of the resources that were deployed.
 
+> [!NOTE]
+> Starting in June 2020, Azure Resource Manager automatically deletes deployments from your history as you near the limit. You may still see this error if you've opted out of automatic deletions. For more information, see [Automatic deletions from deployment history](deployment-history-deletions.md).
+
 ## Symptom
 
 During deployment, you receive an error stating that the current deployment will exceed the quota of 800 deployments.