diff --git a/docs/content/patterns/alz/FAQ.md b/docs/content/patterns/alz/FAQ.md
index b611a4851..66cdca5ae 100644
--- a/docs/content/patterns/alz/FAQ.md
+++ b/docs/content/patterns/alz/FAQ.md
@@ -8,6 +8,10 @@ weight: 80
 >
 > No but you will need to be using Azure Management groups and for now our focus is on the resources frequently deployed as part of Azure Landing Zone deployments.
 
+> ## Can I deploy to Tenant Root Group ?
+> 
+> While it´s recommended to implement the alert policies and initiatives to an ALZ Management Group hierarchy, it is not a technical requirement. However, please avoid Tenant Root Group assignments, to minimize debugging inherited policies at lower-level mangement groups, see [CAF documentation](https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/landing-zone/design-area/resource-org-management-groups). 
+
 > ## Do I need to deploy to each region that I want to monitor?
 >
 > No, deploying to multiple regions is not necessary. The definitions and assignments are scoped to a management group and are not region specific.
diff --git a/docs/content/patterns/alz/deploy/Introduction-to-deploying-the-ALZ-Pattern.md b/docs/content/patterns/alz/deploy/Introduction-to-deploying-the-ALZ-Pattern.md
index fa7f649fe..06f360400 100644
--- a/docs/content/patterns/alz/deploy/Introduction-to-deploying-the-ALZ-Pattern.md
+++ b/docs/content/patterns/alz/deploy/Introduction-to-deploying-the-ALZ-Pattern.md
@@ -35,7 +35,7 @@ Alerts, action groups and alert processing rules are created as follows:
 7. For leveraging the log alerts for Virtual Machines, ensure that VM Insights is enabled for the Virtual Machines to be monitored. For more information on VM Insights deployment, see [here](https://learn.microsoft.com/en-us/azure/azure-monitor/vm/vminsights-enable-overview) . Note only the performance collection of the VM insights solution is required  for the current alerts to deploy.
 
 {{< hint type=note >}}
-While it´s recommended to implement the alert policies and initiatives to an ALZ Management Group hierarchy, it is not a technical requirement. These policies and initiatives can be implemented in existing brownfield scenarios that don´t adhere to the ALZ Management Group hierarchy. For example, in hierarchies where there is a single management group, or where the structure does not align to ALZ. At least one management group is required. In case you haven't implemented management groups, we included guidance on how to get started.
+While it´s recommended to implement the alert policies and initiatives to an ALZ Management Group hierarchy, it is not a technical requirement (avoid Tenant Root Group assignments, to minimize debugging inherited policies at lower-level mangement groups, see [CAF documentation](https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/landing-zone/design-area/resource-org-management-groups)). These policies and initiatives can be implemented in existing brownfield scenarios that don´t adhere to the ALZ Management Group hierarchy. For example, in hierarchies where there is a single management group, or where the structure does not align to ALZ. At least one management group is required. In case you haven't implemented management groups, we included guidance on how to get started.
 {{< /hint >}}
 
 ## Getting started