
Guiding Principles
- Business enablement: Align to organization's business objective and risk framework
Foundations of Zero Trust
Identity
Devices
Network
Applications
Data

Example of a tailored Azure landing zone hierarchy

Points to consider
Tailoring the hierarchy isn't mandatory. The default archetypes and hierarchy we provide are suitable for most scenarios.
Don't re-create your organizational hierarchy, teams, or departments in archetypes.
Always try to build on the existing archetypes and hierarchy to meet new requirements.
Only create new archetypes when they're truly needed.
Don't create archetypes for environments like development, test, and production.
Green field. New environment
Brown Field. Existing environment
References
About the author
I'm technologist in love with almost all things tech from my daily job in the Cloud to my Master's in Cybersecurity and the journey all along.
Comments
Join the discussionNo comments yet. Be the first to comment.





