You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/replication.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ services: azure-netapp-files
5
5
author: b-ahibbard
6
6
ms.service: azure-netapp-files
7
7
ms.topic: concept-article
8
-
ms.date: 07/14/2025
8
+
ms.date: 11/25/2025
9
9
ms.author: anfdocs
10
10
ms.custom: references_regions
11
11
---
@@ -33,7 +33,7 @@ Azure [availability zones](../reliability/availability-zones-overview.md) ar
33
33
To learn more about availability zones in Azure NetApp Files, see [Reliability in Azure NetApp Files](../reliability/reliability-netapp-files.md).
34
34
35
35
> [!IMPORTANT]
36
-
> We don't recommend that you use availability zones with Terraform-managed volumes. If you do, you must[add the zone property to your volume](manage-availability-zone-volume-placement.md#populate-availability-zone-for-terraform-managed-volumes).
36
+
> If you manage volumes with Terraform,[add the zone property to your volume](manage-availability-zone-volume-placement.md#populate-availability-zone-for-terraform-managed-volumes).
Copy file name to clipboardExpand all lines: articles/backup/backup-azure-manage-windows-server.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -195,8 +195,8 @@ Use **Export jobs** to create a spreadsheet containing all Jobs menu information
195
195
196
196
To export the jobs information to a spreadsheet, select **Export jobs**. The service creates a spreadsheet using the name of the vault and date, but you can change the name.
197
197
198
-
>[!Note]
199
-
>Azure Backup currently doesn't support exporting jobs with a filter applied, triggerring this operation fails for SQL and SAP HANA workload types. Alternatively, enable a Log Analytics workspace and [export workload-specific jobs](backup-azure-monitoring-use-azuremonitor.md#queries-specific-to-recovery-services-vault-workloads).
198
+
>[!NOTE]
199
+
>Azure Backup currently doesn't support exporting jobs with a filter applied. Triggering this operation fails for SQL and SAP HANA workload types. Alternatively, enable a Log Analytics workspace and [export workload-specific jobs](backup-azure-monitoring-use-azuremonitor.md#queries-specific-to-recovery-services-vault-workloads).
title: Audit and enforce backup for Managed Disks using Azure Policy
3
-
description: 'An article describing how to use Azure Policy to audit and enforce backup for all Disks created in a given scope'
3
+
description: Learn how to use Azure Policy to audit and enforce backups for Azure Managed Disks to ensure compliance and protect business-critical data.
4
4
ms.topic: how-to
5
-
ms.date: 12/03/2024
5
+
ms.date: 11/25/2025
6
6
ms.service: azure-backup
7
7
author: AbhishekMallick-MS
8
8
ms.author: v-mallicka
9
9
# Customer intent: As a Backup Admin, I want to configure Azure Policies to enforce backup for Managed Disks, so that I can ensure compliance and protect business-critical data across my organization's resources.
10
10
---
11
11
12
-
# Audit and enforce backup for Managed Disks using Azure Policy
12
+
# Audit and enforce backup for Azure Managed Disks using Azure Policy
13
13
14
-
One of the key responsibilities of a Backup or Compliance Admin in an organization is to ensure that all business-critical machines are backed up with the appropriate retention.
14
+
This article describes how Azure Backup uses built-in [Azure Policy](../governance/policy/overview.md) definitions to automate auditing and enforce backup configurations for Azure Managed Disks. These built-in policies ensure compliance with your organization’s retention requirements for business-critical machines.
15
15
16
-
Today, Azure Backup provides various built-in policies (using [Azure Policy](../governance/policy/overview.md)) to help you automatically ensure that your Azure Managed Disks are configured for backup. Depending on how your backup teams and resources are organized, you can use any one of the below policies:
16
+
As a Backup and Compliance admin, choose the policy that best fits your team’s structure and resource organization to automatically configure backups for Azure Managed Disks.
17
+
18
+
## Azure Policy types for Azure Managed Disk backup
19
+
20
+
The following table lists the various policy types that allow you to manage Azure Managed Disk instances backups automatically:
21
+
22
+
| Policy type | Description |
23
+
| --- | --- |
24
+
|[Policy 1](#policy-1---azure-backup-should-be-enabled-for-managed-disks)| Identify Azure Managed Disks that don't have backup enabled. |
25
+
|[Policy 2](#policy-2---configure-backup-for-azure-disks-managed-disks-with-a-given-tag-to-an-existing-backup-vault-in-the-same-region)| Configures backup for Azure Managed Disks with a given tag to an existing backup vault in the same region. |
26
+
|[Policy 3](#policy-3---configure-backup-for-azure-disks-managed-disks-without-a-given-tag-to-an-existing-backup-vault-in-the-same-region)| Configures backup for Azure Managed Disks without a given tag to an existing backup vault in the same region. |
17
27
18
28
## Policy 1 - Azure Backup should be enabled for Managed Disks
19
29
20
-
Use an [audit-only](../governance/policy/concepts/effects.md#audit) policy to identify disks which don't have backup enabled. However, this policy doesn't automatically configure backups for these disks. It is useful when you're only looking to evaluate the overall compliance of the disks but not looking to take action immediately.
30
+
Use an [audit-only](../governance/policy/concepts/effects.md#audit) policy to identify disks, which don't have backup enabled. However, this policy doesn't automatically configure backups for these disks. It's useful when you're only looking to evaluate the overall compliance of the disks but not looking to take action immediately.
21
31
22
32
## Policy 2 - Configure backup for Azure Disks (Managed Disks) with a given tag to an existing backup vault in the same region
23
33
24
-
A central backup team of an organization can use this policy to configure backup to an existing central Backup vault in the same subscription and location as the Managed Disks being governed. You can choose to **include** Disks that contain a certain tag, in the scope of this policy.
34
+
A central backup team of an organization can use this policy to back up Azure Managed Disks to an existing central Backup vault in the same subscription and location. You can choose to **include** Disks that contain a certain tag, in the scope of this policy.
25
35
26
36
## Policy 3 - Configure backup for Azure Disks (Managed Disks) without a given tag to an existing backup vault in the same region
27
37
28
38
This policy works the same as Policy 2 above, with the only difference being that you can use this policy to **exclude** Disks that contain a certain tag, from the scope of this policy.
29
39
30
-
## Supported Scenarios
31
-
32
-
Before you audit and enforce backups for AKS clusters, see the following scenarios supported:
40
+
## Supported and unsupported scenarios for Azure Managed Disk backup using Azure Policy
33
41
34
-
* The built-in policy is currently supported only for Azure Managed Disks. Ensure that the Backup Vault and backup policy specified during assignment is a Disk backup policy.
42
+
Before you audit and enforce backups for Azure Managed Disk, review the following supported and unsupported scenarios:
35
43
36
-
* The Policies 2 and 3 can be assigned to a single location and subscription at a time. To enable backup for Disks across locations and subscriptions, multiple instances of the policy assignment need to be created, one for each combination of location and subscription.
37
44
38
-
* For the Policies 1, 2 and 3, management group scope is currently unsupported.
45
+
| Policy type | Supported | Unsupported |
46
+
| --- | --- | --- |
47
+
| Policy 1, 2, 3 | Supported for Azure Managed Disk only. <br><br> Ensure that the Backup vault and backup policy specified during assignment is a Disk backup policy. | Management group scope is currently unsupported. |
48
+
|Policy 2 and 3 | Can be assigned to a single location and subscription at a time. <br><br> To enable backup for Disks across locations and subscriptions, multiple instances of the policy assignment need to be created, one for each combination of location and subscription. The specified vault and the disks configured for backup can be under different resource groups. ||
39
49
40
-
* For the Policies 2 and 3, the specified vault and the disks configured for backup can be under different resource groups.
50
+
## Assign built-in Azure Policy for Azure Managed Disk backup
41
51
42
-
43
-
## Using the built-in policies
44
-
45
-
The below steps describe the end-to-end process of assigning Policy 2: **Configure backup on Managed Disks with a given tag to an existing backup vault in the same location to a given scope** . Similar instructions are applicable for the other policies. Once assigned, any new Managed Disk created in the scope is automatically configured for backup.
52
+
This section describes the end-to-end process of assigning Policy 2: **Configure backup on Managed Disks with a given tag to an existing backup vault in the same location to a given scope** . Similar instructions apply for the other policies. Once assigned, any new Managed Disk created in the scope is automatically configured for backup.
46
53
47
54
To assign Policy 2, follow these steps:
48
55
@@ -52,21 +59,21 @@ To assign Policy 2, follow these steps:
52
59
53
60
3. Filter the list for **Category=Backup** and select the policy named *Configure backup on Managed Disks with a given tag to an existing backup vault in the same location to a given scope*.
54
61
55
-
:::image type="content" source="./media/backup-managed-disks-policy/policy-dashboard-inline.png" alt-text="Screenshot showing how to filter the list by category on Policy dashboard.":::
62
+
:::image type="content" source="./media/backup-managed-disks-policy/policy-dashboard-inline.png" alt-text="Screenshot shows how to filter the list by category on Policy dashboard.":::
56
63
57
64
4. Select the name of the policy. You're then redirected to the detailed definition for this policy.
58
65
59
-
:::image type="content" source="./media/backup-managed-disks-policy/policy-definition-blade.png" alt-text="Screenshot showing the Policy Definition pane.":::
66
+
:::image type="content" source="./media/backup-managed-disks-policy/policy-definition-blade.png" alt-text="Screenshot shows the Policy Definition pane.":::
60
67
61
68
5. Select the **Assign** button at the top of the pane. This redirects you to the **Assign Policy** pane.
62
69
63
70
6. Under **Basics**, select the three dots next to the **Scope** field. It opens up a right context pane where you can select the subscription for the policy to be applied on. You can also optionally select a resource group, so that the policy is applied only for Disks in a particular resource group.
64
71
65
-
:::image type="content" source="./media/backup-managed-disks-policy/policy-assignment-basics.png" alt-text="Screenshot showing the Policy Assignment Basics tab.":::
72
+
:::image type="content" source="./media/backup-managed-disks-policy/policy-assignment-basics.png" alt-text="Screenshot shows the Policy Assignment Basics tab.":::
66
73
67
74
7. In the **Parameters** tab, choose a location from the drop-down, and select the vault, backup policy to which the Disks in the scope must be associated, and resource group where these disk snapshots are stored. You can also choose to specify a tag name and an array of tag values. A Disk that contains any of the specified values for the given tag is included in the scope of the policy assignment.
68
75
69
-
:::image type="content" source="./media/backup-managed-disks-policy/policy-assignment-parameters.png" alt-text="Screenshot showing the Policy Assignment Parameters pane.":::
76
+
:::image type="content" source="./media/backup-managed-disks-policy/policy-assignment-parameters.png" alt-text="Screenshot shows the Policy Assignment Parameters pane.":::
70
77
71
78
8. Ensure that **Effect** is set to deployIfNotExists.
72
79
@@ -75,8 +82,9 @@ To assign Policy 2, follow these steps:
75
82
> [!NOTE]
76
83
>
77
84
> - Use [remediation](../governance/policy/how-to/remediate-resources.md) to enable policy of existing Managed Disks.
78
-
> - It's recommended that this policy not be assigned to more than 200 Disks at a time. If the policy is assigned to more than 200 Disks, it can result in the backup being triggered a few hours later than that specified by the schedule.
85
+
> - We recommend that you don’t assign this policy to more than 200 disks. Otherwise, backup operation delays by several hours beyond the scheduled time.
86
+
79
87
80
-
## Next step
88
+
## Next steps
81
89
82
90
[Learn more about Azure Policy](../governance/policy/overview.md)
![learn-build-service-prod[bot]](https://avatars.githubusercontent.com/in/237442?v=4&size=40){kind=avatar}
0 commit comments