Power Platform COE Starter Kit: End of Life

In February 2026, Microsoft stopped releasing monthly updates to the Power Platform Center of Excellence (CoE) Starter Kit. In May 2026, it was officially confirmed: the Kit is no longer actively maintained and will receive no new features. For the thousands of organizations that built their Power Platform governance strategy around it, this is a material change, not a routine product update.

Microsoft's recommended path forward is the Power Platform Admin Center (PPAC), which now includes native inventory, usage monitoring, and environment controls. PPAC is a genuine improvement over where it was two years ago. But it does not cover everything the CoE Starter Kit did. In several governance-critical areas, it does not come close. IT teams that migrate to PPAC and stop there are accepting blind spots they may not have fully mapped yet.

This post covers three things: what Microsoft has actually communicated about the EOL, what PPAC does and does not replace, and where the 9 critical governance capabilities land when you map them against PPAC's native offering. The goal is to give your team an accurate picture so you can make an informed decision about what your governance program needs next.

What Microsoft Has Officially Said About the COE Starter Kit Sunset

Timeline and scope of the retirement

The CoE Starter Kit was never an official Microsoft product. It was a community-driven accelerator: a collection of Dataverse apps, Power Automate flows, and Power BI reports maintained by Microsoft employees but outside the normal product support structure. That distinction matters now, because there is no formal deprecation notice, no migration deadline, and no end-of-support SLA. Microsoft's position, stated publicly in GitHub issue #10990 and reflected in updated documentation, is that investment has shifted to building these capabilities natively in the platform.

The practical timeline:

• Through late 2025: Monthly Kit releases continued with incremental fixes and additions.
• February 2026: Monthly releases ceased. Active development stopped as key resources were reassigned.
• May 2026: Microsoft officially confirmed the Kit is no longer maintained and will not receive new features. Existing installations continue to function.

The Kit does not stop working immediately. Flows, apps, and dashboards already deployed will keep running until they break. What stops is support, bug fixes, and compatibility updates for new Power Platform features. For organizations on older versions, the gap between what the Kit can see and what your tenant is actually doing will widen over time.

What Microsoft is moving users toward

At Ignite 2025, Microsoft previewed the Agentic Center of Enablement, a successor concept to the traditional CoE targeted at AI-era governance. Separately, PPAC has received significant native investment: the Inventory, Usage, Monitor, and Actions experiences now provide real-time visibility into environments and resources at tenant scale.

"As Microsoft continues to invest in delivering these capabilities natively in product, the CoE Starter Kit is no longer receiving ongoing feature investments or updates."-- Microsoft, GitHub issue #10990 / Power Platform Documentation, May 2026

This is a genuine strategic shift. PPAC has improved substantially. The question is whether it covers the governance requirements your organization actually has.

PPAC as the recommended replacement: What it covers 

PPAC has become the operational center for Power Platform administration. For basic governance tasks, it is capable and increasingly mature. Here is what it handles well:

Where PPAC delivers

• Tenant-wide resource inventory: PPAC surfaces apps, flows, connectors, and environments across your tenant in a centralized view. This was a primary function of the CoE Starter Kit core components. PPAC's native version is more reliable and does not require a Dataverse environment to maintain it.
• Environment management: Creating, configuring, and controlling environments, including environment-level DLP policies and capacity management, is well-supported natively.
• Basic policy enforcement: DLP policy creation and assignment is available directly in PPAC, with connector classification controls.
• Usage monitoring: The Usage experience shows app launches, flow runs, and active users over time, which is sufficient for broad adoption reporting.
• Admin actions: Admins can act on resources directly from PPAC: reassign ownership, delete orphaned apps, manage sharing.

Where the limitations begin

PPAC's inventory tells you what exists. It does not tell you whether what exists is a risk. It lacks the business context layer needed to act on what it surfaces: no ownership workflows, no compliance classification, no lifecycle state. Governance teams consistently describe the experience as visibility without actionability. You can see the data, but closing the loop requires manual effort or external tooling.

PPAC's governance controls are also concentrated on environments and connectors. They do not extend meaningfully to what happens inside apps and flows, how customizations are structured, or how resources behave across tenant boundaries.

The 9 Governance Capabilities: Where PPAC Stops Short

Effective Power Platform governance at enterprise scale requires nine distinct capabilities. The table below maps each against what PPAC natively provides, and what a complete governance program needs to cover. Use it as a framework for evaluating where your current toolset stands.

◑ = Partial coverage | ✓ = Full coverage | ✗ = Not covered natively

The five gaps that carry the most operational risk

Shadow IT detection (#2): Without automated detection, ungoverned apps proliferate silently. In large tenants, thousands of flows and apps can exist outside any formal governance process. PPAC surfaces these in inventory but applies no risk classification. Admins have no systematic way to prioritize which resources need attention first.

Lifecycle management (#5): Apps lose their owners. Business-critical flows get built by employees who leave. PPAC has no ownership transfer workflows, no mechanism to flag abandoned resources, and no lifecycle state model. Orphaned resources accumulate, compliance exposure grows, and cleanup is entirely manual.

Cross-tenant visibility (#6): Organizations that manage multiple tenants, which is common in enterprise groups, holding companies, and MSPs, cannot aggregate governance data in PPAC. Each tenant is an isolated silo. Multi-tenant governance requires tooling built specifically for it.

DLP enforcement at scale (#3): PPAC lets you create and assign DLP policies. What it does not do is alert you when a policy is being violated, surface which apps are operating in environments with misconfigured policies, or provide an enforcement health view across your full estate. Policy creation is not the same as policy enforcement.

Customization governance (#9): Apps built on premium connectors consuming unbudgeted capacity, flows structured in ways that generate API call volume spikes, connector misuse that exposes sensitive data: none of this is visible through PPAC. The CoE Starter Kit did not address this deeply either, but that does not make the gap any smaller.

Live webinar: The COE is dead. Who's govenerning your power platform now?
17 June 2026. Join our governance team to walk through the PPAC gap analysis live with Q&A. Register today 

What happens to organizations that rely solely on PPAC post-EOL

The risk is not immediate. It is cumulative. Existing CoE Starter Kit installations keep functioning. PPAC covers the basics. But governance debt compounds: ungoverned apps multiply, DLP exceptions go untracked, ownership gaps widen, and audit requests become harder to satisfy. Organizations that discover these gaps during an audit or a data incident pay a significantly higher cost than those that addressed them proactively.

Gartner's research on low-code/no-code governance failures consistently identifies the same root causes: inadequate visibility into what has been built, no lifecycle process for managing what exists, and DLP policies that exist on paper but are not actively monitored. The CoE Starter Kit's retirement removes a layer of governance tooling without automatically replacing it. PPAC is not a drop-in substitute for the full governance capability set.

What a Complete Governance Program Needs Post-COE

Whether you stay with PPAC, extend it with additional tooling, or move to a dedicated governance platform, the nine capabilities in the framework above represent the minimum your program should be able to account for. The right answer depends on the scale of your Power Platform estate and what your compliance obligations actually require.

For IT teams currently assessing their options, here is what to evaluate:

• Dataverse dependency: The CoE Starter Kit required a Dataverse environment to operate, which carried its own maintenance and licensing overhead. Any replacement should be assessed for the same hidden costs.
• Actionability, not just inventory: A tool that shows you what exists but does not help you act on it transfers the manual work burden to your team. Look for ownership workflows, lifecycle state, and risk classification built in.
• Multi-tenant support: If your organization manages more than one tenant, single-tenant tools will not give you a consolidated view. Confirm this requirement before committing.
• AI and agent governance: Copilot Studio adoption is accelerating. Governance tooling that does not extend to agents and AI-generated flows will have the same problem in 18 months that the CoE Starter Kit has today.

Not every organization needs a third-party platform immediately. Teams with a limited Power Platform footprint may find PPAC sufficient for now. What we do recommend is completing a formal capability gap assessment before assuming PPAC covers everything the Kit did. The table above is a starting point. We built Rencore Governance specifically to cover all nine capabilities, including the gaps PPAC leaves open, and we have documented exactly how that maps to the framework in the infographic below.

If your estate includes more than 50 environments, operates across multiple tenants, or has a significant population of ungoverned apps and flows built over the past three years, the gap between what PPAC provides and what your governance program requires is likely material.