Skip to content

Commit 1255146

Browse files
Merge pull request #281281 from davidsmatlak/ds-mg-updates-20240718
Fixes typo and product name
2 parents 2a40b1f + 7310e1b commit 1255146

9 files changed

+22
-22
lines changed

articles/governance/management-groups/create-management-group-azure-cli.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -28,14 +28,14 @@ directory. You receive a notification when the process is complete. For more inf
2828
locally. To find the version, run `az --version`. If you need to install or upgrade, see
2929
[Install Azure CLI](/cli/azure/install-azure-cli).
3030

31-
- Any Azure AD user in the tenant can create a management group without the management group write
31+
- Any Microsoft Entra ID user in the tenant can create a management group without the management group write
3232
permission assigned to that user if
3333
[hierarchy protection](./how-to/protect-resource-hierarchy.md#setting---require-authorization)
3434
isn't enabled. This new management group becomes a child of the Root Management Group or the
3535
[default management group](./how-to/protect-resource-hierarchy.md#setting---default-management-group)
3636
and the creator is given an "Owner" role assignment. Management group service allows this ability
3737
so that role assignments aren't needed at the root level. No users have access to the Root
38-
Management Group when it's created. To avoid the hurdle of finding the Azure AD Global Admins to
38+
Management Group when it's created. To avoid the hurdle of finding the Microsoft Entra ID Global Admins to
3939
start using management groups, we allow the creation of the initial management groups at the root
4040
level.
4141

articles/governance/management-groups/create-management-group-dotnet.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -28,14 +28,14 @@ directory. You receive a notification when the process is complete. For more inf
2828
[Azure management libraries for .NET authentication](/dotnet/azure/sdk/authentication#mgmt-auth).
2929
Skip the step to install the .NET Core packages as we'll do that in the next steps.
3030

31-
- Any Azure AD user in the tenant can create a management group without the management group write
31+
- Any Microsoft Entra ID user in the tenant can create a management group without the management group write
3232
permission assigned to that user if
3333
[hierarchy protection](./how-to/protect-resource-hierarchy.md#setting---require-authorization)
3434
isn't enabled. This new management group becomes a child of the Root Management Group or the
3535
[default management group](./how-to/protect-resource-hierarchy.md#setting---default-management-group)
3636
and the creator is given an "Owner" role assignment. Management group service allows this ability
3737
so that role assignments aren't needed at the root level. No users have access to the Root
38-
Management Group when it's created. To avoid the hurdle of finding the Azure AD Global Admins to
38+
Management Group when it's created. To avoid the hurdle of finding the Microsoft Entra ID Global Admins to
3939
start using management groups, we allow the creation of the initial management groups at the root
4040
level.
4141

articles/governance/management-groups/create-management-group-go.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -29,14 +29,14 @@ directory. You receive a notification when the process is complete. For more inf
2929
[Azure management libraries for .NET authentication](/dotnet/azure/sdk/authentication#mgmt-auth).
3030
Skip the step to install the .NET Core packages as we'll do that in the next steps.
3131

32-
- Any Azure AD user in the tenant can create a management group without the management group write
32+
- Any Microsoft Entra ID user in the tenant can create a management group without the management group write
3333
permission assigned to that user if
3434
[hierarchy protection](./how-to/protect-resource-hierarchy.md#setting---require-authorization)
3535
isn't enabled. This new management group becomes a child of the Root Management Group or the
3636
[default management group](./how-to/protect-resource-hierarchy.md#setting---default-management-group)
3737
and the creator is given an "Owner" role assignment. Management group service allows this ability
3838
so that role assignments aren't needed at the root level. No users have access to the Root
39-
Management Group when it's created. To avoid the hurdle of finding the Azure AD Global Admins to
39+
Management Group when it's created. To avoid the hurdle of finding the Microsoft Entra ID Global Admins to
4040
start using management groups, we allow the creation of the initial management groups at the root
4141
level.
4242

articles/governance/management-groups/create-management-group-javascript.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,14 +26,14 @@ directory. You receive a notification when the process is complete. For more inf
2626
- Before you start, make sure that at least version 12 of [Node.js](https://nodejs.org/) is
2727
installed.
2828

29-
- Any Azure AD user in the tenant can create a management group without the management group write
29+
- Any Microsoft Entra ID user in the tenant can create a management group without the management group write
3030
permission assigned to that user if
3131
[hierarchy protection](./how-to/protect-resource-hierarchy.md#setting---require-authorization)
3232
isn't enabled. This new management group becomes a child of the Root Management Group or the
3333
[default management group](./how-to/protect-resource-hierarchy.md#setting---default-management-group)
3434
and the creator is given an "Owner" role assignment. Management group service allows this ability
3535
so that role assignments aren't needed at the root level. No users have access to the Root
36-
Management Group when it's created. To avoid the hurdle of finding the Azure AD Global Admins to
36+
Management Group when it's created. To avoid the hurdle of finding the Microsoft Entra ID Global Admins to
3737
start using management groups, we allow the creation of the initial management groups at the root
3838
level.
3939

articles/governance/management-groups/create-management-group-portal.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,14 +23,14 @@ directory. You receive a notification when the process is complete. For more inf
2323
- If you don't have an Azure subscription, create a [free](https://azure.microsoft.com/free/)
2424
account before you begin.
2525

26-
- Any Azure AD user in the tenant can create a management group without the management group write
26+
- Any Microsoft Entra ID user in the tenant can create a management group without the management group write
2727
permission assigned to that user if
2828
[hierarchy protection](./how-to/protect-resource-hierarchy.md#setting---require-authorization)
2929
isn't enabled. This new management group becomes a child of the Root Management Group or the
3030
[default management group](./how-to/protect-resource-hierarchy.md#setting---default-management-group)
3131
and the creator is given an "Owner" role assignment. Management group service allows this ability
3232
so that role assignments aren't needed at the root level. No users have access to the Root
33-
Management Group when it's created. To avoid the hurdle of finding the Azure AD Global Admins to
33+
Management Group when it's created. To avoid the hurdle of finding the Microsoft Entra ID Global Admins to
3434
start using management groups, we allow the creation of the initial management groups at the root
3535
level.
3636

articles/governance/management-groups/create-management-group-powershell.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,14 +26,14 @@ directory. You receive a notification when the process is complete. For more inf
2626
- Before you start, make sure that the latest version of Azure PowerShell is installed. See
2727
[Install Azure PowerShell module](/powershell/azure/install-azure-powershell) for detailed information.
2828

29-
- Any Azure AD user in the tenant can create a management group without the management group write
29+
- Any Microsoft Entra ID user in the tenant can create a management group without the management group write
3030
permission assigned to that user if
3131
[hierarchy protection](./how-to/protect-resource-hierarchy.md#setting---require-authorization)
3232
isn't enabled. This new management group becomes a child of the Root Management Group or the
3333
[default management group](./how-to/protect-resource-hierarchy.md#setting---default-management-group)
3434
and the creator is given an "Owner" role assignment. Management group service allows this ability
3535
so that role assignments aren't needed at the root level. No users have access to the Root
36-
Management Group when it's created. To avoid the hurdle of finding the Azure AD Global Admins to
36+
Management Group when it's created. To avoid the hurdle of finding the Microsoft Entra ID Global Admins to
3737
start using management groups, we allow the creation of the initial management groups at the root
3838
level.
3939

articles/governance/management-groups/create-management-group-python.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,14 +23,14 @@ directory. You receive a notification when the process is complete. For more inf
2323
- If you don't have an Azure subscription, create a [free](https://azure.microsoft.com/free/)
2424
account before you begin.
2525

26-
- Any Azure AD user in the tenant can create a management group without the management group write
26+
- Any Microsoft Entra ID user in the tenant can create a management group without the management group write
2727
permission assigned to that user if
2828
[hierarchy protection](./how-to/protect-resource-hierarchy.md#setting---require-authorization)
2929
isn't enabled. This new management group becomes a child of the Root Management Group or the
3030
[default management group](./how-to/protect-resource-hierarchy.md#setting---default-management-group)
3131
and the creator is given an "Owner" role assignment. Management group service allows this ability
3232
so that role assignments aren't needed at the root level. No users have access to the Root
33-
Management Group when it's created. To avoid the hurdle of finding the Azure AD Global Admins to
33+
Management Group when it's created. To avoid the hurdle of finding the Microsoft Entra ID Global Admins to
3434
start using management groups, we allow the creation of the initial management groups at the root
3535
level.
3636

articles/governance/management-groups/create-management-group-rest-api.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -28,14 +28,14 @@ directory. You receive a notification when the process is complete. For more inf
2828
[Invoke-RestMethod](/powershell/module/microsoft.powershell.utility/invoke-restmethod) or
2929
[Postman](https://www.postman.com).
3030

31-
- Any Azure AD user in the tenant can create a management group without the management group write
31+
- Any Microsoft Entra ID user in the tenant can create a management group without the management group write
3232
permission assigned to that user if
3333
[hierarchy protection](./how-to/protect-resource-hierarchy.md#setting---require-authorization)
3434
isn't enabled. This new management group becomes a child of the Root Management Group or the
3535
[default management group](./how-to/protect-resource-hierarchy.md#setting---default-management-group)
3636
and the creator is given an "Owner" role assignment. Management group service allows this ability
3737
so that role assignments aren't needed at the root level. No users have access to the Root
38-
Management Group when it's created. To avoid the hurdle of finding the Azure AD Global Admins to
38+
Management Group when it's created. To avoid the hurdle of finding the Microsoft Entra ID Global Admins to
3939
start using management groups, we allow the creation of the initial management groups at the root
4040
level.
4141

articles/governance/management-groups/overview.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -141,7 +141,7 @@ will inherit down the hierarchy like any built-in role. For information about th
141141

142142
[Defining and creating a custom role](../../role-based-access-control/custom-roles.md) doesn't
143143
change with the inclusion of management groups. Use the full path to define the management group
144-
**/providers/Microsoft.Management/managementgroups/{_groupId_}**.
144+
`/providers/Microsoft.Management/managementgroups/{_groupId_}`.
145145

146146
Use the management group's ID and not the management group's display name. This common error happens
147147
since both are custom-defined fields when creating a management group.
@@ -154,11 +154,11 @@ since both are custom-defined fields when creating a management group.
154154
"IsCustom": true,
155155
"Description": "This role provides members understand custom roles.",
156156
"Actions": [
157-
"Microsoft.Management/managementgroups/delete",
158-
"Microsoft.Management/managementgroups/read",
159-
"Microsoft.Management/managementgroup/write",
160-
"Microsoft.Management/managementgroup/subscriptions/delete",
161-
"Microsoft.Management/managementgroup/subscriptions/write",
157+
"Microsoft.Management/managementGroups/delete",
158+
"Microsoft.Management/managementGroups/read",
159+
"Microsoft.Management/managementGroups/write",
160+
"Microsoft.Management/managementGroups/subscriptions/delete",
161+
"Microsoft.Management/managementGroups/subscriptions/write",
162162
"Microsoft.resources/subscriptions/read",
163163
"Microsoft.Authorization/policyAssignments/*",
164164
"Microsoft.Authorization/policyDefinitions/*",

0 commit comments

Comments
 (0)