Merge pull request #300500 from MicrosoftDocs/main

5/28/2025 AM Publish

Author: Taojunshen

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

@@ -2,65 +2,76 @@
 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/27/2025
 ms.custom: devx-track-azurecli, devx-track-arm-template
 ---
 
 # 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.
-
-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.
+When you deploy resources to Azure, the deployment details are recorded in the deployment history at the scope where the deployment occurs. Each scope—whether it's a [resource group](./deploy-to-resource-group.md), [subscription](./deploy-to-subscription.md), [management group](./deploy-to-management-group.md), [tenant](./deploy-to-tenant.md)—can store up to **800 deployments** in its history. Once this limit is reached, Azure **automatically deletes the oldest deployments** to make space for new ones. This automatic cleanup process was implemented on **August 6, 2020**.
 
 > [!NOTE]
 > Deleting a deployment from the history doesn't affect any of the resources that were deployed.
 
-## When deployments are deleted
+## Overview of automatic deployment history deletions
 
 Deployments are deleted from your history when you exceed 700 deployments. Azure Resource Manager deletes deployments until the history is down to 600. The oldest deployments are always deleted first.
 
 :::image type="content" border="false" source="./media/deployment-history-deletions/deployment-history.png" alt-text="Diagram of deployment history deletion.":::
 
 > [!IMPORTANT]
-> If your resource group is already at the 800 limit, your next deployment fails with an error. The automatic deletion process starts immediately. You can try your deployment again after a short wait.
+> If your scope is already at the 800 limit, your next deployment fails with an error. The automatic deletion process starts immediately. You can try your deployment again after a short wait.
 
 In addition to deployments, you also trigger deletions when you run the [what-if operation](./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.
 
-## Remove locks that block deletions
+## Permissions required for automatic deletions
+
+The deletions are requested under the identity of the user who deployed the template. To delete deployments, the user must have access to the **Microsoft.Resources/deployments/delete** action. If the user doesn't have the required permissions, deployments aren't deleted from the history.
+
+If the current user doesn't have the required permissions, automatic deletion is attempted again during the next deployment.
+
+## Handling resource locks
+
+If you have a [CanNotDelete lock](../management/lock-resources.md) on a resource group or a subscription, the deployments for that scope can't be automatically deleted. To enable automatic cleanup of the deployment history, you need to remove the lock.
 
-If you have a [CanNotDelete lock](../management/lock-resources.md) on a resource group, the deployments for that resource group can't be deleted. You must remove the lock to take advantage of automatic deletions in the deployment history.
+To delete a resource group lock, run the following commands:
 
-To use PowerShell to delete a lock, run the following commands:
+### [PowerShell](#tab/azure-powershell)
 
 ```azurepowershell-interactive
 $lockId = (Get-AzResourceLock -ResourceGroupName lockedRG).LockId
 Remove-AzResourceLock -LockId $lockId
 ```
 
-To use Azure CLI to delete a lock, run the following commands:
+To delete a resource group lock, run the following commands:
+
+### [Azure CLI](#tab/azure-cli)
 
 ```azurecli-interactive
 lockid=$(az lock show --resource-group lockedRG --name deleteLock --output tsv --query id)
 az lock delete --ids $lockid
 ```
 
-## Required permissions
+### [REST](#tab/rest)
 
-The deletions are requested under the identity of the user who deployed the template. To delete deployments, the user must have access to the **Microsoft.Resources/deployments/delete** action. If the user doesn't have the required permissions, deployments aren't deleted from the history.
+```rest
+DELETE https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Authorization/locks/{lockName}?api-version=2016-09-01
+```
 
-If the current user doesn't have the required permissions, automatic deletion is attempted again during the next deployment.
+---
 
-## Opt out of automatic deletions
+## Opting 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.
+You can opt out of automatic deletion to manually manage your deployment history. **Use this option cautiously**, as the **800-deployment limit** remains enforced, and exceeding it causes deployment failures.
 
-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).
+> [!IMPORTANT]
+> Opting out is available only for subscription scopes, as it's controlled by the subscription-level `Microsoft.Resources/DisableDeploymentGrooming` feature flag. You can't opt out for only a particular resource group. For tenant or management group scopes, open a [support ticket](./overview.md#get-support) to disable automatic deletion.
 
-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.
+To disable automatic deletion at the subscription scope (affects all resource groups within it):
 
-# [PowerShell](#tab/azure-powershell)
+### [PowerShell](#tab/azure-powershell)
 
 For PowerShell, use [Register-AzProviderFeature](/powershell/module/az.resources/Register-AzProviderFeature).
 
@@ -76,7 +87,7 @@ Get-AzProviderFeature -ProviderNamespace Microsoft.Resources -FeatureName Disabl
 
 To reenable automatic deletions, use Azure REST API or Azure CLI.
 
-# [Azure CLI](#tab/azure-cli)
+### [Azure CLI](#tab/azure-cli)
 
 For Azure CLI, use [az feature register](/cli/azure/feature#az-feature-register).
 
@@ -96,7 +107,7 @@ To reenable automatic deletions, use [az feature unregister](/cli/azure/feature#
 az feature unregister --namespace Microsoft.Resources --name DisableDeploymentGrooming
 ```
 
-# [REST](#tab/rest)
+### [REST](#tab/rest)
 
 For REST API, use [Features - Register](/rest/api/resources/features/register).
 

articles/backup/azure-data-lake-storage-backup-manage.md

@@ -0,0 +1,70 @@
+---
+title: Manage Vaulted Backup for Azure Data Lake Storage using Azure portal (preview)
+description: Learn how to manage vaulted backup for Azure Data Lake Storage (preview) using Azure portal.
+ms.topic: how-to
+ms.date: 04/16/2025
+author: jyothisuri
+ms.author: jsuri
+---
+
+# Manage vaulted backup for Azure Data Lake Storage using Azure portal (preview)
+
+This article describes how to manage vaulted backup for Azure Data Lake Storage (preview) using Azure portal.
+
+## Monitor an Azure Data Lake Storage backup job (preview)
+
+The Azure Backup service creates a job for a scheduled backup or when you trigger an on-demand backup operation, allowing you to monitor the job progress.
+
+To check the backup job status, follow these steps:
+
+1. In the [Azure portal](), go to the **Backup vault** > **Backup jobs**.
+
+   :::image type="content" source="./media/azure-data-lake-storage-backup-manage/monitor-backup-jobs.png" alt-text="Screenshot shows how to monitor the backup jobs." lightbox="./media/azure-data-lake-storage-backup-manage/monitor-backup-jobs.png":::
+
+1. On the **Backup jobs** pane, select the required time range and apply filters to narrow down the list of jobs.
+
+   The **Backup jobs** dashboard shows the operation and status for the past seven days.
+
+## Modify the Azure Data Lake Storage backup instance (preview)
+
+After the backup configuration, you can update the policy associated with a backup instance. For vaulted backups, you can also modify the selected backup containers.
+
+To modify the backup instance, follow these steps:
+
+1. Go to the **Backup vault**.
+1. On the **Backup Items** tile, select **Azure Data Lake Storage (Preview)** as the **Datasource type**.
+1. On the **Backup instance** pane, select the backup instance for which you want to change the Backup policy, and then select **Edit backup instance**.
+
+   :::image type="content" source="./media/azure-data-lake-storage-backup-manage/edit-backup-instance.png" alt-text="Screenshot shows the option to modify the backup instance." lightbox="./media/azure-data-lake-storage-backup-manage/edit-backup-instance.png":::
+
+1. On the **Edit backup instance** pane, under **Select policy**, select the appropriate policy from the dropdown list to apply it to the storage account blobs.
+
+   :::image type="content" source="./media/azure-data-lake-storage-backup-manage/change-policy.png" alt-text="Screenshot shows how to change the policy for backup." lightbox="./media/azure-data-lake-storage-backup-manage/change-policy.png":::
+
+1. Select **Save**.
+
+## Stop protection for Azure Data Lake Storage (preview)
+
+You can stop the vaulted backup for the storage account as per your requirements.
+
+>[!Caution]
+>When you remove backups, the object replication policy is removed from the source. The stop protection operation dissociates the storage account from the Backup vault and doesn’t disable any configured change feed.
+
+To stop backup for a storage account, follow these steps: 
+
+1. Go to the **Backup vault**.
+1. On the **Backup Items** tile, select **Azure Data Lake Storage (Preview)** as the **Datasource type**. 
+1. On the **Backup instance** pane, select the backup instance for which you want to stop backup from the list.
+1. On the selected backup instance pane, select **Stop Backup**.
+
+   :::image type="content" source="./media/azure-data-lake-storage-backup-manage/stop-backup.png" alt-text="Screenshot shows how to stop protection for Azure Data Lake Storage." lightbox="./media/azure-data-lake-storage-backup-manage/stop-backup.png":::
+
+>[!Note]
+>After the backup is stopped, you can disable other storage data protection capabilities (enabled for configuring backups) from the **data protection** pane of the storage account.
+
+## Next steps
+
+[Troubleshoot Azure Data Lake Storage vaulted backup and restore errors (preview)](azure-data-lake-storage-backup-troubleshoot.md).
+ 
+
+

articles/backup/backup-azure-recovery-services-vault-overview.md

@@ -2,7 +2,7 @@
 title: Overview of Recovery Services vaults
 description: An overview of Recovery Services vaults.
 ms.topic: overview
-ms.date: 01/17/2025
+ms.date: 05/28/2025
 ms.service: azure-backup
 author: jyothisuri
 ms.author: jsuri
@@ -12,7 +12,7 @@ ms.custom: engagement-fy24
 
 This article describes the features of a Recovery Services vault.
 
-A Recovery Services vault is a storage entity in Azure that houses data. The data is typically copies of data, or configuration information for virtual machines (VMs), workloads, servers, or workstations. You can use Recovery Services vaults to hold backup data for various Azure services such as IaaS VMs (Linux or Windows) and SQL Server in Azure VMs. Recovery Services vaults support System Center DPM, Windows Server, Azure Backup Server, and more. Recovery Services vaults make it easy to organize your backup data, while minimizing management overhead. 
+A Recovery Services vault is a storage entity in Azure that houses data. The data is typically copies of data, or configuration information for virtual machines (VMs), workloads, servers, or workstations. You can use Recovery Services vaults to hold backup data for various Azure services such as IaaS VMs (Linux or Windows) and SQL Server in Azure VMs. Recovery Services vaults support System Center DPM, Windows Server, Azure Backup Server, and more. Recovery Services vaults make it easy to organize your backup data, while minimizing management overhead. Learn about the [types of vault supported for backup and restore](/azure/backup/backup-azure-backup-faq#what-are-the-various-vaults-supported-for-backup-and-restore-).
 
 ## Key features
 

articles/backup/backup-vault-overview.md

@@ -2,15 +2,19 @@
 title: Overview of the Backup vaults
 description: An overview of Backup vaults.
 ms.topic: overview
-ms.date: 09/30/2024
+ms.date: 05/28/2025
 ms.custom: references_regions
 ms.service: azure-backup
 author: jyothisuri
 ms.author: jsuri
 ---
 # Backup vaults overview
 
-This article describes the features of a Backup vault. A Backup vault is a storage entity in Azure that houses backup data for certain newer workloads that Azure Backup supports. You can use Backup vaults to hold backup data for various Azure services, such as Azure Blob, Azure Database for PostgreSQL servers and newer workloads that Azure Backup will support. Backup vaults make it easy to organize your backup data, while minimizing management overhead. Backup vaults are based on the Azure Resource Manager model of Azure, which provides features such as:
+This article describes the features of a Backup vault. A Backup vault is a storage entity in Azure that houses backup data for certain newer workloads that Azure Backup supports. You can use Backup vaults to hold backup data for various Azure services, such as Azure Blob, Azure Database for PostgreSQL servers and newer workloads that Azure Backup will support. Backup vaults make it easy to organize your backup data, while minimizing management overhead. Learn about the [types of vault supported for backup and restore](/azure/backup/backup-azure-backup-faq#what-are-the-various-vaults-supported-for-backup-and-restore-).
+
+## Key features
+
+Backup vaults are based on the Azure Resource Manager model of Azure, which provides features such as:
 
 - **Enhanced capabilities to help secure backup data**: With Backup vaults, Azure Backup provides security capabilities to protect cloud backups. The security features ensure you can secure your backups, and safely recover data, even if production and backup servers are compromised. [Learn more](backup-azure-security-feature.md)
 

articles/backup/media/azure-data-lake-storage-backup-manage/change-policy.png

@@ -647,7 +647,9 @@
     - name: Configure backup
       href: azure-data-lake-storage-configure-backup.md
     - name: Restore
-      href: azure-data-lake-storage-restore.md        
+      href: azure-data-lake-storage-restore.md
+    - name: Manage
+      href: azure-data-lake-storage-backup-manage.md          
   - name: Azure Files backup
     items:
     - name: From the Azure portal

articles/backup/media/azure-data-lake-storage-backup-manage/edit-backup-instance.png

@@ -42,7 +42,7 @@ When using the Call Diagnostics Updates Log Schema, always refer to the highest
 
 ### More about log versions and data latency
 
-The call diagnostics updates log schema may require approximately 60 minutes following the end of a call to propogate data, most logs may be available within 40 minutes. 
+The call diagnostics updates log schema may require approximately 60 minutes following the end of a call to propagate data, most logs may be available within 40 minutes. 
 
 After a call ends, an initial version (version 1) of the log is sent to the CallSummaryUpdates and CallDiagnosticUpdates tables. Initial versions may contain `null` values, if more information becomes available updated versions of the logs are created with more complete information. For example, client data can be delayed because of network connectivity issues between the client computer and our servers, or something as simple as a user closing the lid on their laptop post-call before their client data was sent and re-opening it hours (or days) later.