The Azure Landing Zones (Enterprise-Scale) architecture provides prescriptive guidance coupled with Azure best practices, and it follows design principles across the critical design areas for organizations to define their Azure architecture
This is a suggestion for a minor documentation update to three pages. It is intended to make sure that pre-requisite resource providers are obvious when following the Learn documentation, as they are not currently mentioned. It is therefore possible that a user follows the link directly from Learn to the Portal and initiates an ALZ deployment without being aware that RPs need enabling, as they are documented separately on the Github wiki.
Page 3 above also has a line "To successfully deploy an Enterprise-Scale with a predefined [template] (https://aka.ms/caf/ready/accelerator)...", but the 'template' link is directly to the ALZ portal wizard, not to the Bicep or Terraform templates
From these documents it is unclear when reading the first two that the resource provider pre-reqs exist, and so it is easy to miss them.
Suggestion:
Update the pre-reqs document (no. 2) to include a reference to all pre-reqs including a full list of all required resource providers (i.e. consolidate all pre-reqs into a single doc)
Update the Learn doc (no. 1) with an explicit link to the pre-reqs documentation
Update page no 3. above to link 'template' to a Bicep/Terraform/Portal options landing page, not directly to the portal
This is a suggestion for a minor documentation update to three pages. It is intended to make sure that pre-requisite resource providers are obvious when following the Learn documentation, as they are not currently mentioned. It is therefore possible that a user follows the link directly from Learn to the Portal and initiates an ALZ deployment without being aware that RPs need enabling, as they are documented separately on the Github wiki.
Current state:
/
scope/
scoped permissions but makes only a passing reference to resource providers in the context of AMBA and no link to the pre-reqs pageFrom these documents it is unclear when reading the first two that the resource provider pre-reqs exist, and so it is easy to miss them.
Suggestion: