Landing Zones
Microsoft has created a reference implementation and architecture and design methodology for Power Platform called Landing Zones.
It allows you to scale the use of Power Platform and automate all the “plumbing” that is needed when an app is to be created. One can create “templates” for different types of setups to easily deploy new environment pipelines into the tenant when needed.
It considers all the required platform parts, which include the following:
- Access management
- Governance and compliance
- Connectivity, interoperability, and extensibility
Different parts of the architecture are for different roles, such as platform operations, security operations, and network operations, as well as design principles such as policy-driven governance, persona agnostic, and a single control and management plan.
The reference implementation includes several different governance structures, such as the following:
- Tenant governance
- Admin environment governance
- Default environment governance
- Citizen developer Landing Zones
- Professional developer Landing Zones
As you can see, Landing Zones are a huge topic that includes both specific implementation (as the reference implementation) and a lot of guidance and best practices.
In my experience, they are most useful to big companies with a lot of users. For small to medium companies, however, it is usually too much overhead.
As mentioned, Landing Zones are a very big topic and are beyond the scope of this book to cover in detail. I have therefore provided some additional links in the Further reading section for you to explore further.
