Skip to content

Commit 5d9d372

Browse files
committed
edit pass: articles-about-management-groups
1 parent f673456 commit 5d9d372

File tree

3 files changed

+5
-6
lines changed

3 files changed

+5
-6
lines changed

articles/governance/management-groups/how-to/protect-resource-hierarchy.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ these operations are available in the Azure built-in role Hierarchy Settings Adm
3131

3232
## <a name="setting---default-management-group">Setting: Define the default management group
3333

34-
By default, a new subscription that you add in a tenant is added as a member of the root management
34+
By default, a new subscription that you add in a tenant becomes a member of the root management
3535
group. If you assign policy assignments, Azure RBAC, and other governance
3636
constructs to the root management group, they immediately affect these new
3737
subscriptions. For this reason, many organizations don't apply these constructs at the root

articles/governance/management-groups/manage.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,7 @@ You can change the name of the management group by using the Azure portal, Azure
5656

5757
### Change the name in Azure PowerShell
5858

59-
To update the display name, use `Update-AzManagementGroup`. For example, to change a management
59+
To update the display name, use `Update-AzManagementGroup` in Azure PowerShell. For example, to change a management
6060
group's display name from **Contoso IT** to **Contoso Group**, run the following command:
6161

6262
```azurepowershell-interactive

articles/governance/management-groups/overview.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ creating a hierarchy for governance by using management groups.
2929
:::image-end:::
3030

3131
You can create a hierarchy that applies a policy, for example, that limits VM locations to the West US region in the management group called _Corp_. This policy will inherit all the Enterprise Agreement (EA) subscriptions that are descendants of that management group and will apply to all VMs under those subscriptions. The resource or subscription
32-
owner can't alter this security policy, which allows for improved governance.
32+
owner can't alter this security policy, to allow for improved governance.
3333

3434
> [!NOTE]
3535
> Management groups aren't currently supported in cost management features for Microsoft Customer Agreement (MCA) subscriptions.
@@ -67,10 +67,9 @@ you can assign your account as the owner of the root management group.
6767

6868
### Important facts about the root management group
6969

70-
- By default, the root management group's display name is **Tenant root group** and operates itself as a management group. The ID is the same value as the Microsoft Entra tenant ID.
70+
- By default, the root management group's display name is **Tenant root group**, and it operates itself as a management group. The ID is the same value as the Microsoft Entra tenant ID.
7171
- To change the display name, your account must have the Owner or Contributor role on the
72-
root management group. To update
73-
the name of a management group, see
72+
root management group. For more information, see
7473
[Change the name of a management group](manage.md#change-the-name-of-a-management-group).
7574
- The root management group can't be moved or deleted, unlike other management groups.
7675
- All subscriptions and management groups fold up into one root management group within the

0 commit comments

Comments
 (0)