Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

User Story 34272 : AMBA - Documentation update about unsupported/unrecommended Tenant Root Group deployment #247

Merged
merged 3 commits into from
Jun 21, 2024
Merged

User Story 34272 : AMBA - Documentation update about unsupported/unrecommended Tenant Root Group deployment #247

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
471feb8
Update Introduction-to-deploying-the-ALZ-Pattern.md
ymehdimsft Jun 19, 2024
60b4172
Update FAQ.md
ymehdimsft Jun 19, 2024
5672f9d
Update FAQ.md
ymehdimsft Jun 19, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/content/patterns/alz/FAQ.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
2 changes: 1 addition & 1 deletion docs/content/patterns/alz/deploy/Introduction-to-deploying-the-ALZ-Pattern.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down