Introduction

Completed

Every organization that adopts Power Platform must decide how to organize its environments. Without a deliberate strategy, makers often build apps in the default environment, capacity goes unmonitored, and governance becomes reactive instead of proactive.

Deciding who builds where, what controls apply, and how the organization consumes capacity is an important part of an administrator's job. This module walks through the core concepts administrators use to plan an environment strategy, choose the right environment types, apply governance controls, monitor capacity, and configure key integrations.

In this course, you complete multiple exercises. In this module, you:

  • Design an environment topology using a zoned governance model.
  • Create and manage different environment types.
  • Enable Managed Environments with environment groups and routing rules.
  • Monitor storage capacity.
  • Configure SharePoint and Exchange Online integrations.

By the end of this module, you're able to plan, create, and govern Power Platform environments so makers can work productively within your organization's security and compliance requirements.

Throughout this course, examples help you apply the concepts. The primary examples come from this Zava scenario.

Imagine you're a Power Platform administrator at Zava, a global retailer expanding into financial services through its Zava Pay division. Zava's citizen developers build productivity apps for store operations, while a professional development team builds regulated payment-processing solutions that must meet Payment Card Industry Data Security Standard (PCI DSS) compliance and data-residency requirements. Leadership wants both groups to keep innovating, but with appropriate guardrails that are suited to the workload's risk level. You need an environment strategy that separates low-risk personal productivity work from high-risk regulated workloads, while keeping capacity costs under control and integrations properly configured.