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/backup/backup-azure-auto-enable-backup.md
+10-11Lines changed: 10 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,13 +1,8 @@
1
1
---
2
2
title: Auto-Enable Backup on VM Creation using Azure Policy
3
3
description: 'An article describing how to use Azure Policy to auto-enable backup for all VMs created in a given scope'
4
-
ms.reviewer: dcurwin
5
-
author: adbalaji
6
-
manager: sivan
7
-
ms.service: backup
8
4
ms.topic: conceptual
9
5
ms.date: 11/08/2019
10
-
ms.author: adbalaji
11
6
---
12
7
13
8
# Auto-Enable Backup on VM Creation using Azure Policy
@@ -18,7 +13,7 @@ Today, Azure Backup provides a built-in policy (using Azure Policy) that can be
18
13
19
14
## Supported Scenarios
20
15
21
-
* The built-in policy is currently supported only for Azure VMs. Users must take care to ensure that the retention policy specified during assignment is a VM retention policy. Refer to [this](https://aka.ms/AA6il6q) document to see all the VM SKUs supported by this policy.
16
+
* The built-in policy is currently supported only for Azure VMs. Users must take care to ensure that the retention policy specified during assignment is a VM retention policy. Refer to [this](https://aka.ms/PolicySupportedSKUs) document to see all the VM SKUs supported by this policy.
22
17
23
18
* The policy can be assigned to a single location and subscription at a time. To enable backup for VMs across locations and subscriptions, multiple instances of the policy assignment need to be created, one for each combination of location and subscription.
24
19
@@ -32,18 +27,22 @@ To assign the policy to the required scope, please follow the below steps:
32
27
33
28
1. Login to the Azure Portal and navigate to the **Policy** Dashboard.
34
29
2. Select **Definitions** in the left menu to get a list of all built-in policies across Azure Resources.
35
-
3. Filter the list for **Category=Backup**. You will see the list filtered down to a single policy named ‘Deploy prerequisites to backup VMs of a location to an existing central Vault in the same location’.
3. Filter the list for **Category=Backup**. You will see the list filtered down to a single policy named 'Configure backup on VMs of a location to an existing central Vault in the same location'.
5. Click on the **Assign** button at the top of the blade. This redirects you to the **Assign Policy** blade.
40
35
6. Under basics, click on the three dots next to the **Scope** field. This opens up a right context blade 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 VMs in a particular resource group.
7. In the **Parameters** tab, choose a location from the drop-down, and select the vault and backup policy to which the VMs in the scope must be associated.
8. Ensure that **Effect** is set to deployIfNotExists.
45
40
9. Navigate to **Review+create** and click **Create**.
46
41
42
+
> [!NOTE]
43
+
>
44
+
> Azure Policy can also be used on existing VMs, using [remediation](https://docs.microsoft.com/azure/governance/policy/how-to/remediate-resources).
45
+
47
46
> [!NOTE]
48
47
>
49
48
> It is recommended that this policy is assigned to not more than 200 VMs. If the policy is assigned for more than 200 VMs, it can result in the backup getting triggered a few hours later than that specified by the schedule.
0 commit comments