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/update-manager/enable-cross-subscription-patching.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,8 +22,8 @@ This article describes how to enable cross-subscription patching either through
22
22
23
23
Open your Azure CLI and enter the following commands:
24
24
25
-
az provider register--namespace "Microsoft.Insights"
26
-
az provider register--namespace "Microsoft.Maintenance"
25
+
az provider register--namespace "Microsoft.Insights"
26
+
az provider register--namespace "Microsoft.Maintenance"
27
27
28
28
# [Using Azure portal](#tab/az-portal)
29
29
@@ -39,8 +39,8 @@ This article describes how to enable cross-subscription patching either through
39
39
- Assign the appropriate roles to your Azure VM and Arc assets to ensure scheduled patching can be managed effectively. The required roles are:
40
40
- Scheduled patching contributor
41
41
- Reader
42
-
- These roles can be granted on the Resource Group or Subscription level if you have resources spread amongst multiple resource groups and want to include them all at once.
43
-
- If you have a smaller scope and plan to manage it with a dedicated admin or group, these two roles can be granted to an user or a security group (SG). If you are envisioning a larger scope with automation in place, grant these roles to the API and Service Principal Name (SPN) you use.
42
+
- These roles can be granted on the Resource Group or Subscription level if you have resources spread among multiple resource groups and want to include them all at once.
43
+
- If you have a smaller scope and plan to manage it with a dedicated admin or group, these two roles can be granted to a user or a security group (SG). If you're envisioning a larger scope with automation in place, grant these roles to the API and Service Principal Name (SPN) you use.
44
44
45
45
3. Scheduling
46
46
@@ -55,7 +55,7 @@ This article describes how to enable cross-subscription patching either through
55
55
# [Using API](#tab/az-patch-cli)
56
56
57
57
- Use the API to programmatically schedule the patching.
58
-
- For schedule patching on VM or Arc assets, locate the assets by using the *resourceId* and *subscription* that they are attached to.
58
+
- For schedule patching on VM or Arc assets, locate the assets by using the *resourceId* and *subscription* that they're attached to.
0 commit comments