Skip to content

Commit 1e0067c

Browse files
Fix formatting and wording in prerequisites section
1 parent ce99186 commit 1e0067c

1 file changed

Lines changed: 24 additions & 23 deletions

File tree

articles/update-manager/includes/pre-post-prerequisites.md

Lines changed: 24 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -8,45 +8,46 @@ ms.date: 09/24/2024
88

99
## Prerequisites
1010

11-
1. Ensure that you are using PowerShell **7.4** runbook.
12-
2. Assign permission to managed identities - You can assign permissions to the appropriate [managed identity](../../automation/automation-security-overview.md#managed-identities). The runbook can use either the Automation account system-assigned managed identity or a user-assigned managed identity.
11+
1. Ensure that you're using PowerShell **7.4** runbook.
12+
2. Assign permission to managed identities. You can assign permissions to the appropriate [managed identity](../../automation/automation-security-overview.md#managed-identities). The runbook can use either the Automation account system-assigned managed identity or a user-assigned managed identity.
1313

14-
For the script examples below (Start VM's and Stop VM's), the Virtual Machine Contributor role is required or a Custom Role with these specific permissions:
15-
• Microsoft.Compute/virtualMachines/start/action
16-
• Microsoft.Compute/virtualMachines/deallocate/action
17-
• Microsoft.Compute/virtualMachines/restart/action
18-
• Microsoft.Compute/virtualMachines/powerOff/action
14+
For the script examples below (Start VMs and Stop VMs), the Virtual Machine Contributor role is required or a Custom Role with these specific permissions:
15+
16+
- Microsoft.Compute/virtualMachines/start/action
17+
- Microsoft.Compute/virtualMachines/deallocate/action
18+
- Microsoft.Compute/virtualMachines/restart/action
19+
- Microsoft.Compute/virtualMachines/powerOff/action
1920

2021
You can use either portal or PowerShell cmdlets to assign permissions to each identity:
2122

2223
#### [Using Azure portal](#tab/portal)
2324

24-
Follow the steps in [Assign Azure roles using the Azure portal](../../role-based-access-control/role-assignments-portal.yml) to assign permissions
25+
Follow the steps in [Assign Azure roles using the Azure portal](../../role-based-access-control/role-assignments-portal.yml) to assign permissions
2526

2627
#### [Using Azure PowerShell](#tab/powershell)
2728

28-
Use PowerShell cmdlet [New-AzRoleAssignment](/powershell/module/az.resources/new-azroleassignment) to assign a role to the system-assigned managed identity.
29+
Use PowerShell cmdlet [New-AzRoleAssignment](/powershell/module/az.resources/new-azroleassignment) to assign a role to the system-assigned managed identity.
2930

30-
```powershell
31-
New-AzRoleAssignment `
31+
```powershell
32+
New-AzRoleAssignment `
3233
-ObjectId $SA_PrincipalId `
3334
-ResourceGroupName $resourceGroup `
3435
-RoleDefinitionName "Contributor"
35-
```
36-
37-
Assign a role to a user-assigned managed identity.
36+
```
37+
38+
Assign a role to a user-assigned managed identity.
3839
39-
```powershell
40-
New-AzRoleAssignment `
40+
```powershell
41+
New-AzRoleAssignment `
4142
-ObjectId $UAMI.PrincipalId `
4243
-ResourceGroupName $resourceGroup `
4344
-RoleDefinitionName "Contributor"
44-
```
45-
46-
For the system-assigned managed identity, show `ClientId` and record the value for later use.
47-
48-
```powershell
49-
$UAMI.ClientId
50-
```
45+
```
46+
For the system-assigned managed identity, show `ClientId` and record the value for later use.
47+
48+
```powershell
49+
$UAMI.ClientId
50+
```
51+
---
5152
5253
3. Import the `Az.ResourceGraph` module, ensure the module is updated to ThreadJob with the module version 2.0.3.

0 commit comments

Comments
 (0)