CoE Launch Checklist¶

Use this checklist alongside the Launch a CoE scenario. The scenario explains the why and the sequence; this checklist tracks the what.

Applies To

Audience: CoE Lead · Platform Admin · IT Director Frameworks: SCALE-OPS · BOLT · SHIELD

Phase 1 — Ownership & Structure¶

[ ] Platform Owner identified — executive-level accountability for Power Platform (CIO, CTO, or equivalent)
[ ] CoE Lead appointed — operational lead with mandate and time allocated
[ ] CoE team defined — roles, responsibilities, and time commitments documented
[ ] Fusion Team Lead model agreed — how business units will be represented in platform governance
[ ] CoE mandate documented — what the CoE owns, what it advises, what it does not own
[ ] Escalation path defined — how unresolved issues reach the Platform Owner

[ ] Default environment restricted — access locked to admin operations only; makers redirected
[ ] Developer environment policy established — how makers request and receive developer environments
[ ] Environment naming convention defined and documented
[ ] Minimum viable environment structure provisioned — Dev / Test / Prod for at least one BU
[ ] Managed Environments enabled on production environments
[ ] Environment ownership assigned — each environment has a named owner
[ ] Environment lifecycle policy defined — what happens to unused environments

[ ] Connector classification completed — all connectors in use classified (Business / Non-Business / Blocked)
[ ] Tenant-level baseline DLP policy applied
[ ] Environment-tier DLP policies created and applied (Default / Dev-Test / Production)
[ ] DLP exception process documented and published to makers
[ ] Quarterly DLP review cadence scheduled

[ ] BOLT tier model adopted — which tiers are operational and what applies at each
[ ] Maker role defined — what qualifies someone as a recognised maker
[ ] Fusion Team Lead role defined and filled for each participating BU
[ ] Tier escalation criteria documented — when and how solutions move between tiers
[ ] Pre-approved connector list published to makers
[ ] Solution request intake process defined

[ ] CoE Starter Kit deployed (or equivalent monitoring tooling)
[ ] Platform inventory baseline established — all environments, solutions, flows, apps documented
[ ] Orphaned resource policy defined — what happens to solutions with no active owner
[ ] Platform health dashboard configured — key metrics visible to CoE Lead and Platform Owner
[ ] Alert thresholds set for capacity, compliance drift, and orphaned solutions
[ ] Monthly platform health review scheduled

[ ] Maker onboarding process defined — how new makers are registered and given access
[ ] Minimum training requirement defined for each tier (Tier 1 self-service, Tier 2+ required training)
[ ] Internal training resources identified or created
[ ] Community of practice established — internal maker community with regular meeting cadence
[ ] Office hours or maker support channel established
[ ] Maker feedback loop defined — how makers raise issues and suggest improvements to governance

[ ] Security review process defined — three-mode model (Safe Zone / Pattern / Full Review) documented
[ ] Safe Zone criteria published — what constitutes a self-certifiable solution
[ ] Pattern Library started — first approved patterns documented
[ ] Go-live security checklist published to makers and Fusion Team Leads
[ ] Service account policy defined — all Tier 2+ connections must use service accounts

Before declaring the CoE operational, confirm:

Gate	Confirmed?
Platform Owner has signed off the CoE mandate
At least one BU has a Fusion Team Lead
Default environment is restricted
At least one DLP policy tier is active
CoE toolkit or monitoring is running
Maker onboarding process is functional
First maker cohort has been onboarded