Merge pull request #279586 from mumian/0627-history-groom

ARM deployment history auto grooming at the tenant and the mg scope

Author: rmca14

articles/azure-resource-manager/bicep/overview.md

@@ -82,7 +82,7 @@ Bicep provides the following advantages:
 
   You can also create Bicep files in Visual Studio with the [Bicep extension for Visual Studio](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.visualstudiobicep).
 
-- **Repeatable results**: Repeatedly deploy your infrastructure throughout the development lifecycle and have confidence your resources are deployed in a consistent manner. Bicep files are idempotent, which means you can deploy the same file many times and get the same resource types in the same state. You can develop one file that represents the desired state, rather than developing lots of separate files to represent updates. For example, the following file creates a storage account. If you deploy this template and the storage account with the specified properties already exists , no changes are made.
+- **Repeatable results**: Repeatedly deploy your infrastructure throughout the development lifecycle and have confidence your resources are deployed in a consistent manner. Bicep files are idempotent, which means you can deploy the same file many times and get the same resource types in the same state. You can develop one file that represents the desired state, rather than developing lots of separate files to represent updates. For example, the following file creates a storage account. If you deploy this template and the storage account with the specified properties already exists, no changes are made.
 
   # [Bicep](#tab/bicep)
 
@@ -173,6 +173,8 @@ Bicep automatically manages dependencies between resources. You can avoid settin
 
 The structure of the Bicep file is more flexible than the JSON template. You can declare parameters, variables, and outputs anywhere in the file. In JSON, you have to declare all parameters, variables, and outputs within the corresponding sections of the template.
 
+[!INCLUDE [Request ARM template support](../../../includes/template-support.md)]
+
 ## Next steps
 
 Get started with the [Quickstart](./quickstart-create-bicep-use-visual-studio-code.md).

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: 03/20/2024
+ms.date: 08/28/2024
 ms.custom: devx-track-azurecli, devx-track-arm-template
 ---
 
@@ -12,8 +12,6 @@ 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.
 
-**Automatic deletions are supported for resource group and subscription deployments. Currently, deployments in the history for [management group](deploy-to-management-group.md) and [tenant](deploy-to-tenant.md) deployments aren't automatically deleted.**
-
 > [!NOTE]
 > Deleting a deployment from the history doesn't affect any of the resources that were deployed.
 
@@ -58,7 +56,9 @@ If the current user doesn't have the required permissions, automatic deletion is
 
 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. To reenable automatic deletions, unregister the feature flag.
+To disable automatic deletions at the tenant or the management group scope, open a support ticket. For the instructions, see [Request support](./overview.md#get-support).
+
+To disable automatic deletions at the subscription scope, 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. To reenable automatic deletions, unregister the feature flag.
 
 # [PowerShell](#tab/azure-powershell)
 

articles/azure-resource-manager/templates/overview.md

@@ -27,7 +27,7 @@ If you're trying to decide between using ARM templates and one of the other infr
 
 * **Declarative syntax**: ARM templates allow you to create and deploy an entire Azure infrastructure declaratively. For example, you can deploy not only virtual machines, but also the network infrastructure, storage systems, and any other resources you may need.
 
-* **Repeatable results**: Repeatedly deploy your infrastructure throughout the development lifecycle and have confidence your resources are deployed in a consistent manner. Templates are idempotent, which means you can deploy the same template many times and get the same resource types in the same state. You can develop one template that represents the desired state, rather than developing lots of separate templates to represent updates. For example, the following file creates a storage account. If you deploy this template and the storage account with the specified properties already exists , no changes is made.
+* **Repeatable results**: Repeatedly deploy your infrastructure throughout the development lifecycle and have confidence your resources are deployed in a consistent manner. Templates are idempotent, which means you can deploy the same template many times and get the same resource types in the same state. You can develop one template that represents the desired state, rather than developing lots of separate templates to represent updates. For example, the following file creates a storage account. If you deploy this template and the storage account with the specified properties already exists, no changes are made.
 
 ```json
 {
@@ -168,6 +168,8 @@ After creating your template, you may wish to share it with other users in your
 
 This approach means you can safely share templates that meet your organization's standards.
 
+[!INCLUDE [Request ARM template support](../../../includes/template-support.md)]
+
 ## Next steps
 
 * For a step-by-step tutorial that guides you through the process of creating a template, see [Tutorial: Create and deploy your first ARM template](template-tutorial-create-first-template.md).

includes/media/template-support/request-arm-template-support.png

@@ -0,0 +1,20 @@
+---
+
+ms.service: bicep, arm-templates
+ms.topic: include
+ms.date: 08/28/2024
+
+---
+
+## Get support
+
+Here are the steps for opening a support ticket for Azure Resource Manager (ARM) template related issues:
+
+1. Open the [Azure portal](https://portal.azure.com).
+1. Select the **Support + Troubleshooting** icon from the upper right corner.
+1. In **Briefly describe the issue**, enter **ARM template**, and then select **Go**.
+1. In **Which service are you having an issue with?**, select **Portal** under **Monitoring & Management**, and then select **Next**.
+1. Select a subscription, and then select **Next**.
+1. Select **Issue with ARM templates**, and then select **Next**.
+
+   :::image type="content" source="./media/template-support/request-arm-template-support.png" alt-text="Screenshot of requesting ARM template support." border="false":::