Merge pull request #227060 from claytonsiemens77/mg-update

What are Azure mangement groups article update

Author: Court72

articles/governance/management-groups/overview.md

@@ -28,12 +28,12 @@ You can build a flexible structure of management groups and subscriptions to org
 into a hierarchy for unified policy and access management. The following diagram shows an example of
 creating a hierarchy for governance using management groups.
 
-:::image type="complex" source="./media/tree.png" alt-text="Diagram of a sample management group hierarchy." border="false":::
+:::image type="complex" source="../media/mg-org.png" alt-text="Diagram of a sample management group hierarchy." border="false":::
    Diagram of a root management group holding both management groups and subscriptions. Some child management groups hold management groups, some hold subscriptions, and some hold both. One of the examples in the sample hierarchy is four levels of management groups with the child level being all subscriptions.
 :::image-end:::
 
 You can create a hierarchy that applies a policy, for example, which limits VM locations to the
-West US region in the management group called "Production". This policy will inherit onto all the Enterprise
+West US region in the management group called "Corp". This policy will inherit onto all the Enterprise
 Agreement (EA) subscriptions that are descendants of that management group and will apply to all VMs
 under those subscriptions. This security policy cannot be altered by the resource or subscription
 owner allowing for improved governance.
@@ -194,15 +194,15 @@ when trying to separate the assignment from its definition.
 
 For example, let's look at a small section of a hierarchy for a visual.
 
-:::image type="complex" source="./media/subtree.png" alt-text="Diagram of a subset of the sample management group hierarchy." border="false":::
-   The diagram focuses on the root management group with child I T and Marketing management groups. The I T management group has a single child management group named Production while the Marketing management group has two Free Trial child subscriptions.
+:::image type="complex" source="../media/mg-org-sub.png" alt-text="Diagram of a subset of the sample management group hierarchy." border="false":::
+   The diagram focuses on the root management group with child Landing zones and Sandbox management groups. The Landing zones management group has two child management groups named Corp and Online while the Sandbox management group has two child subscriptions.
 :::image-end:::
 
-Let's say there's a custom role defined on the Marketing management group. That custom role is then
-assigned on the two free trial subscriptions.
+Let's say there's a custom role defined on the Sandbox management group. That custom role is then
+assigned on the two Sandbox subscriptions.
 
-If we try to move one of those subscriptions to be a child of the Production management group, this
-move would break the path from subscription role assignment to the Marketing management group role
+If we try to move one of those subscriptions to be a child of the Corp management group, this
+move would break the path from subscription role assignment to the Sandbox management group role
 definition. In this scenario, you'll receive an error saying the move isn't allowed since it will
 break this relationship.
 
@@ -211,7 +211,7 @@ There are a couple different options to fix this scenario:
   MG.
 - Add the subscription to the role definition's assignable scope.
 - Change the assignable scope within the role definition. In the above example, you can update the
-  assignable scopes from Marketing to the root management group so that the definition can be reached by
+  assignable scopes from Sandbox to the root management group so that the definition can be reached by
   both branches of the hierarchy.
 - Create another custom role that is defined in the other branch. This new role requires the role
   assignment to be changed on the subscription also.