Merge pull request #224901 from timwarner-msft/timwarner-mgremove

Remove outdated information

Author: prmerger-automator[bot]

articles/governance/management-groups/overview.md

@@ -1,7 +1,7 @@
 ---
 title: Organize your resources with management groups - Azure Governance
 description: Learn about the management groups, how their permissions work, and how to use them.
-ms.date: 01/03/2023
+ms.date: 01/24/2023
 ms.topic: overview
 author: timwarner-msft
 ms.author: timwarner
@@ -107,35 +107,6 @@ access and policies that other customers within the directory can't bypass. Anyt
 root will apply to the entire hierarchy, which includes all management groups, subscriptions,
 resource groups, and resources within that Azure AD tenant.
 
-## Trouble seeing all subscriptions
-
-A few directories that started using management groups early in the preview before June 25, 2018
-could see an issue where not all the subscriptions were within the hierarchy. The process to have
-all subscriptions in the hierarchy was put in place after a role or policy assignment was done on
-the root management group in the directory.
-
-### How to resolve the issue
-
-There are two options you can do to resolve this issue.
-
-- Remove all role and policy assignments from the root management group
-  - By removing any policy and role assignments from the root management group, the service
-    backfills all subscriptions into the hierarchy the next overnight cycle. This process is so
-    there's no accidental access given or policy assignment to all of the tenants subscriptions.
-  - The best way to do this process without impacting your services is to apply the role or policy
-    assignments one level below the root management group. Then you can remove all assignments from
-    the root scope.
-- Call the API directly to start the backfill process
-  - Any customer in the directory can call the _TenantBackfillStatusRequest_ or
-    _StartTenantBackfillRequest_ APIs. When the StartTenantBackfillRequest API is called, it kicks
-    off the initial setup process of moving all the subscriptions into the hierarchy. This process
-    also starts the enforcement of all new subscription to be a child of the root management group.
-    This process can be done without changing any assignments on the root level. By calling the API,
-    you're saying it's okay that any policy or access assignment on the root can be applied to all
-    subscriptions.
-
-If you have questions on this backfill process, contact: `[email protected]`
-
 ## Management group access
 
 Azure management groups support