Course 04 · Founder cohort forming
Nine modules on the Power Platform governance stack — environments, DLP, managed environments, Copilot Studio agents, connectors, capacity, and the maker lifecycle. Written for the IT admin who inherited a Power Platform tenant that grew organically and now needs to be brought back under governance without breaking every citizen-developer solution in production.
Founder cohort — first fifty enrolments get 40% off launch pricing
Founder pricing
40% off standard CA$399 · locked in for founder cohort
Zero commitment · you pay only when the course ships
Why this course exists
Most IT admins first encounter Power Platform governance when it's already too late — 400 apps in the default environment, 200 orphaned flows still hitting production APIs, connectors reaching into places nobody documented, and Copilot Studio agents built by business users that IT never approved.
This course teaches the recovery playbook and the going-forward operating model. How to structure environments so citizen developers stay productive and IT stays in control. DLP policies that block the risky connectors without breaking the ones people actually need. Managed environments features (weekly reset, sharing limits, solution checker enforcement). Copilot Studio agent governance — the hardest part of Power Platform today. And the maker lifecycle programme that keeps the tenant clean six months after you set it up.
Curriculum
Each module includes video walkthrough, written reference, policy templates, and a knowledge-check quiz.
Default vs developer vs production environments. Environment provisioning policy. Environment naming standards. When to isolate a business unit vs sharing environments. The five environment topologies that fit 95% of organisations.
Connector classification (Business, Non-Business, Blocked). Tenant-wide vs environment-scoped policies. How to design DLP so the default environment is safe by default and specialised environments unlock capability. Exception process for makers who need a blocked connector.
What managed environments unlock (weekly limits, sharing controls, solution checker enforcement, Copilot Studio governance). Licensing cost vs value analysis. When to enable per environment. The three managed environments features every enterprise needs.
The hardest problem in Power Platform today. Approval workflow for Copilot Studio agents. Data source restrictions. Web grounding on or off. Publishing controls. How to prevent the "shadow Copilot" problem where business users build customer-facing agents without IT visibility.
Standard vs premium vs custom connectors. Custom connector approval process. On-premises data gateway management. HTTP connector governance (the one that quietly reaches into anything). How to audit connector usage across your tenant.
Dataverse capacity vs storage capacity vs log capacity. Per-user vs per-app vs per-flow licensing. Pay-as-you-go environments. Capacity monitoring and forecasting. How to prevent the "we blew through our Dataverse capacity" surprise bill.
Onboarding kit for new citizen developers. Solution ALM patterns for makers. Testing and promotion between environments. Hand-off from maker to IT. Retirement of unused apps. The maker lifecycle programme that keeps the tenant clean.
Finding orphaned apps and flows (creator left the org). Reassignment workflow. Bulk operations via Power Platform admin PowerShell. Bulk email to owners for the annual "do you still need this?" review. The clean-up runbook every inherited tenant needs.
Power Platform admin analytics. Unified audit log for Power Platform events. CoE Starter Kit — what to use, what to ignore. Executive-friendly reporting on maker activity, solution health, and governance posture.
First fifty enrolments lock in CA$239. Zero payment now — we'll email when the course ships.