Skip to content

Power Platform Application Portfolio Management, Five Years On

Power Platform application portfolio management since 2021: what Microsoft changed, what is still on a Dynamics 365 owner, and what comes next.

Alex Pechenizkiy 8 min read
Power Platform Application Portfolio Management, Five Years On

If you own a Dynamics 365 or Power Platform estate, someone has asked you a simple question you could not answer quickly: who owns this app, and what breaks if we turn it off? Answering it is the job of Power Platform application portfolio management. For a Dynamics 365 application portfolio, the question has not gone away in five years. If the term is new to you, Citizen Development Academy has a plain explainer: what is application portfolio management.

In July 2021 I wrote about governing applications on Power Platform and published an open-source Dataverse solution under the MIT license: Enterprise Applications Governance. Its first feature was portfolio management, with portfolios and application groups as their own tables. This post looks at what Microsoft has changed since then, what is still on you, and what the next version is designed to do.

What I published in 2021

My view in 2021 was that ALM and CI/CD for Dynamics 365 were maturing fast, but governing the applications themselves at an organizational level was not. Many teams, many apps, and nobody holding the whole picture.

The 2021 release was a Dataverse solution with portfolios and application groups, applications, dependencies between applications, releases, deployments with a deployment type, and environments. It shipped as one model-driven app with two security roles, two classic workflows that named records, and a dashboard that embedded a Power BI report.

Today it stays on GitHub for reference. It is not maintained. For how Power Platform grew around Dynamics 365 before then, see Power Platform expanding Dynamics 365 CRM.

What changed on Microsoft’s side

Here is what matters for a CRM owner, from Microsoft’s own pages.

Managed environments became the default expectation

Microsoft describes managed environments as “a suite of premium capabilities that allow admins to manage Power Platform at scale with more control, less effort, and more insights.” Pipelines, solution checker, data policies, limit sharing and the catalog are all features of managed environments.

The bigger shift is enforcement. The admin deployment page says: “Pipeline target environments must be managed environments. Enforcement began rolling out in October 2026.”

There is a 30-day grace period. Deployments then pause until a maker or tenant administrator acknowledges, and one optional 30-day extension follows. Only after the extension ends are deployments to an unmanaged target blocked, until a tenant administrator enables managed environments on it.

Microsoft also says: “Enforcement blocks new deployments only. Deployed apps and solutions continue to run.” And the way out is one step: “Enabling managed environments on the target removes the block immediately.”

Developer environments changed too. Per the Developer Plan guide, new unmanaged developer environments could no longer be created from November 15, 2026. Existing ones are suspended starting December 15, 2026 and deleted starting January 15, 2027.

Deployment moved into the service

Pipelines in Power Platform bring “ALM automation and continuous integration and continuous delivery (CI/CD) capabilities into the service.” Microsoft says “Pipelines enable admins to centrally govern citizen-led and pro-dev-led projects at scale with less effort.” One line every CRM owner should remember: “Pipelines, or solutions in general, don’t contain data stored within Dataverse tables.”

Git integration now syncs solutions with Azure DevOps or GitHub. The GitHub connection is a preview feature, and Microsoft says both development and target environments must be managed.

The admin center got an inventory, with owner gaps

Power Platform inventory “gives tenant administrators a unified view of all agents, apps, flows, and sites built on Power Platform across their organization.”

Read its known limitations, though. “Model-driven apps don’t have an owner.” For cloud flows, the owner column “shows the user who created the flow. It doesn’t update when the owner changes.” In my view, for a Dynamics 365 shop, where the core business apps are model-driven, the inventory tells you what exists, not who answers for it.

The CoE Starter Kit is no longer actively maintained

Microsoft’s page now reads: “The Power Platform CoE Starter Kit is no longer actively maintained. Its core capabilities are part of the Power Platform admin center.” It remains available, but “it will not be enhanced with new capabilities.” The CoE Starter Kit page points to Inventory, Usage, Monitor and Actions in the admin center.

Apps are now built by AI, and agents need sponsors

The inventory now counts code apps, vibe apps, and apps created in the App Builder agent of Microsoft Copilot (formerly Microsoft 365 Copilot). Generative pages let makers build model-driven app pages with AI, and Microsoft is clear that “you’re ultimately responsible for validating the code.”

For agents, Microsoft Agent 365 “is generally available for the Commercial segment on a per user basis,” and its registry shows, for each agent, “who owns it.” In Microsoft Entra Agent ID, “At least one sponsor is required for each agent identity and agent identity blueprint.”

And AI tools can now reach your data directly. The Dataverse MCP server serves clients such as Copilot Studio agents, GitHub Copilot and Claude Code, and, per the Dataverse MCP FAQ, it “respects Dataverse security roles and row-level security.”

What application portfolio management still needs from you

Every item above is a tool. None of them makes a decision for you. These questions are still yours:

  • Owners. Who is the business owner, the technical owner and the data owner, and who covers when they leave?
  • Decisions. Do we keep, invest in, replace or retire this app? Who decided, when, and why?
  • Dependencies. What other apps, data and outside systems depend on this one?
  • Change control. Was this deployment approved, and did it land inside its change window?
  • The portfolio view. One list of business applications, not technical parts, across Power Platform, agents, AI-built apps and other vendors’ SaaS.

In my view, the agent registry and the sponsor rule show that Microsoft agrees ownership matters. Today that rule covers agents, not the model-driven apps a CRM team runs on.

Area
Inventory
Microsoft gives you
A tenant view of agents, apps, flows and sites in the admin center
You still need
One business application that groups its technical parts
Area
Ownership
Microsoft gives you
Agent owners and sponsors; flow creators; no owner for model-driven apps
You still need
A business, technical and data owner for every app, each with a deputy
Area
Deployment
Microsoft gives you
Pipelines with approvals, Git integration, managed environment enforcement
You still need
A record of what was deployed, where, and who approved it
Area
Decisions
Microsoft gives you
Managed environment features such as data policies and limit sharing
You still need
Keep, invest, replace or retire, with a reason and a name
Area
Dependencies
Microsoft gives you
An inventory of resources, not the links between business applications
You still need
Links between apps, APIs, data and outside systems
Area
AI access
Microsoft gives you
The Dataverse MCP server, governed by security roles
You still need
Rules for what AI may draft and what only people approve
What Microsoft gives a CRM owner today, and what still has to be decided and recorded by the organization.

What the next version is designed to do

I am designing the next version of Enterprise Applications Governance now. Nothing in it is built yet. The short version: know every app and AI agent you run, who owns it, what changed, and what breaks if it goes. The idea is narrow: work with Microsoft Power Platform and add only the business view on top of Microsoft’s tools, never instead of them. Each point below answers a gap from the table above. The full description is on Citizen Development Academy’s open-source application portfolio management tool page.

  • Every kind of application. It is designed to hold one record per business application: Power Platform apps, agents, AI-built apps, code apps and SaaS from other vendors.
  • Owners recorded, not inferred. It is designed to record a business, technical and data owner itself and flag where that differs from what Microsoft shows.
  • Decisions and change on record. It is designed to keep an append-only decision log, run light change management or link to an existing change tool, and record deployments from your own pipelines. It is designed never to build, host or run a pipeline.
  • AI never approves. Records AI creates are designed to start as Draft or Proposed. Only people approve, on approval cards in Outlook and Teams.

Configuration, the live gap check, the ways in and the open-source (MIT) terms are described on that page. It is designed as a new solution, not an in-place upgrade of the 2021 release.

What I would tell a Dynamics 365 owner today

  1. Check your pipeline targets now. If any target environment is unmanaged, the 30-day grace period starts at the first deployment to it after enforcement is enabled. Decide before the block, not after.
  2. Move work off unmanaged developer environments. Since November 15, 2026, you can’t create new ones. Existing ones are suspended starting December 15, 2026 and deleted starting January 15, 2027.
  3. Write down owners for your model-driven apps yourself. A business owner and a technical owner, each with a deputy, is the minimum.
  4. Stop treating the CoE Starter Kit as your plan. It is no longer actively maintained. Learn what the admin center inventory and its limits give you instead.
  5. Register AI-built apps and agents like any other app. If a maker built it with AI, it still needs an owner, a risk tier and a decision on record.
  6. Keep a decision log, even a simple one. Keep, invest, replace or retire, with a reason, a name and a date. It needs no new tool, and it is one of the simplest governance habits to start.
  7. Start from shared guidelines. The Power Platform governance guidelines at Citizen Development Academy are a practical place to begin.

Common questions

Is the 2021 solution still maintained?

No. It stays on GitHub for reference under the MIT license. The next version is in design as a new solution, not an in-place upgrade.

Does the Power Platform inventory show who owns an app?

Not for every app. Microsoft lists as a known limitation that “Model-driven apps don’t have an owner,” and a cloud flow’s owner column shows its creator.

Will my deployed apps stop when managed environment enforcement reaches me?

No. Microsoft says: “Enforcement blocks new deployments only. Deployed apps and solutions continue to run.”

One next step

Everything above comes back to one question: who answers for this app? If AI tools are already building apps or agents in your tenant, Citizen Development Academy runs a 30-minute review of one of them: who owns it, how it ships, and what governance it is missing.

Request the free 30-minute AI app review with Citizen Development Academy

Related articles