Power Platform Admin Center’s New Governance Agents: What IT Teams Need to Know
Every business application team has faced the same problem this year: makers are building AI agents faster than IT can review them. A sales rep spins up a Copilot Studio agent to summarize accounts. A finance analyst automates an approval flow with Power Automate. An operations lead builds a customer-facing Power Pages site over a weekend. None of it goes through a formal request low-code tools were built to remove that friction. But that same speed is exactly what makes governance so hard: by the time IT finds out an agent exists, it may already be touching sensitive data or running unsupervised in production.
Microsoft’s answer isn’t to slow that speed down. It’s AI agents that govern other AI agents a shift that puts Power Platform governance at the center of the Admin Center rather than at its edges. If your organization runs Power Apps, Power Automate, or Copilot Studio, the changes rolling out now directly affect how much real control you have over what’s being built whether you’ve noticed the shift yet or not.
Why Power Platform Governance Couldn’t Wait
For years, the risk in low-code platforms was mostly about sprawl: too many apps, unclear ownership, orphaned flows nobody remembered building. AI agents raise the stakes considerably for Power Platform governance an agent can read from and write to business data, take actions on a user’s behalf, and interact with external systems, all without a human reviewing each step.
Gartner has projected that 40% of enterprise applications will be integrated with task-specific AI agents by the end of 2026, up from less than 5% in 2025 — and most of those organizations are still building the governance muscle to match. Security teams have flagged this gap directly: identifying risky AI usage and maintaining visibility into what agents are doing are now among the top concerns for anyone responsible for enterprise AI risk.
Microsoft’s response has been to treat governance as a platform feature rather than an afterthought bolted on once problems surface. That’s the context for everything below these aren’t isolated features, they’re pieces of a single strategy to keep pace with how fast agents are multiplying.
From Reactive Reviews to Proactive Power Platform Governance
Historically, Power Platform governance meant periodic audits: someone in IT would review app inventories, check for orphaned flows, and hope nothing risky had gone unnoticed between reviews. Microsoft is replacing that model with the Agentic Center of Enablement a set of AI agents built into the Admin Center that continuously monitor your tenant, flag risks in real time, and suggest remediations before an issue reaches production.
Instead of waiting for a quarterly audit to catch a data-loss-prevention violation or an agent with excessive permissions, the monitoring agents surface it as it happens. Real-time risk assessment now runs alongside deployment, catching security and compliance issues before an agent goes live rather than after. The platform also introduces “safe innovation zones” environments with contextual guidance for makers, so someone building their first agent gets steered toward compliant patterns instead of finding out afterward that they broke a policy.
This pairs with more mature application lifecycle management: only reviewed, tested changes reach production, and every change carries a complete audit trail. That matters most in regulated industries — finance, healthcare, professional services where “we didn’t know an agent was doing that” is no longer a defensible answer to an auditor.
What this means for your business: governance shifts from a scheduled task to a standing capability. IT teams should treat this as infrastructure they need to configure and tune as a core part of Power Platform governance not a report they check once a quarter.
Enhanced Admin Controls for Agent Security
A closely related feature manage agent security with enhanced admin controls reached general availability on September 2, 2026. It lets administrators centrally define authentication and access policies for agents at the environment or environment-group level, right inside the Admin Center a cornerstone of modern Power Platform governance, since it replaces per-environment guesswork with one place to set policy.
Concretely, admins can now require Microsoft Entra ID authentication for agents, allow only approved external identity providers, or block anonymous access outright. These policies are enforced both at publish time and at runtime, so an agent that doesn’t comply simply can’t go live or stay live.
What this means for your business: if your organization has been treating Copilot Studio and Power Platform agents as a citizen-developer free-for-all, this is the moment to set an authentication baseline before shadow agents multiply further.
This builds on groundwork Microsoft laid earlier: administrators could already configure whether agents required Microsoft Entra ID authentication, manual authentication, or allowed anonymous chat access. What’s new is that these controls now apply consistently across environment groups rather than one environment at a time, and the most restrictive setting always wins when policies overlap removing a common source of accidental gaps where one loose setting undermined a stricter one elsewhere.
Power Pages Gets Proactive Security Agents
Power Pages Microsoft’s low-code external website builder is getting its own layer of AI-driven protection. New security agents actively scan for risks like phishing attempts and denial-of-service patterns, flagging them before they escalate rather than relying purely on after-the-fact logs. Admin governance controls have also been added to prevent non-production Power Pages sites from being accidentally exposed to the public while still in development.
What this means for your business: any client-facing or partner-facing Power Pages site even ones still in testing needs a review of its current exposure settings. Accidental public exposure has historically been one of the most common and easily preventable Power Pages incidents.
Power Platform Governance Now Includes Cost Control
It’s not just security Power Platform governance now extends to cost as well. The Admin Center’s new Usage page gives leaders a summary view of adoption trends the most-used apps, flows, and AI agents across the organization useful for justifying spend or spotting waste. Alongside it, granular Copilot credit tracking lets admins set configurable consumption caps to prevent budget overruns, and automated license reclaim now returns unused licenses to the pool instead of letting them sit idle.
What this means for your business: finance and IT can finally answer “what are we actually getting for our Copilot spend” with real usage data instead of estimates and stop paying for licenses nobody’s using.
This is a meaningful change in how Power Platform costs get managed. Previously, licenses assigned to a departed employee or an abandoned project often sat unused for months before anyone noticed. Automated reclaim closes that gap without requiring an admin to manually audit every license assignment the system does the bookkeeping that used to fall through the cracks.
Rolling Out Power Platform Governance Without Slowing Makers Down
The instinct when governance tightens is to worry it will slow innovation down more approvals, more friction, more “check with IT first.” Microsoft’s design intent here is the opposite: automate the governance work so makers keep moving fast while IT gets visibility without becoming a bottleneck. The safe innovation zones mentioned earlier are part of that makers get guardrails built into the environment itself, rather than a person reviewing every app before it ships.
The practical rollout of Power Platform governance looks less like a lockdown and more like a phased turn-on: start with visibility (the Usage page and monitoring agents), move to authentication policy at the environment-group level, then layer in cost controls once you know what’s actually being used. Organizations that try to turn on every control at once tend to generate a backlog of exceptions and frustrated makers sequencing it avoids that.
Why This Matters Beyond IT
The broader signal here is that Microsoft is building governance in parallel with agent capability, not bolting it on afterward. That’s a meaningful shift from the early Power Platform era, when the Center of Excellence Starter Kit an unofficial toolkit of community-built apps and dashboards was the only real governance option, and every organization had to install, run, and maintain it themselves. Microsoft has stopped actively maintaining that kit; governance is now a native, supported platform capability instead of a DIY project a maturity milestone for Power Platform governance as a discipline.
For businesses that have been experimenting with Copilot Studio agents without a formal governance layer, that DIY era is effectively over. The tools now exist inside the platform itself the remaining work is configuring them correctly.
Power Platform Governance FAQs
What is Power Platform governance? Power Platform governance is the set of policies, monitoring, and controls IT teams use to manage how Power Apps, Power Automate, Copilot Studio, and Power Pages are built, secured, and used across an organization. In 2026, Microsoft shifted much of that work from manual, periodic audits to AI-driven monitoring and policy agents built directly into the Power Platform Admin Center.
Does this replace the CoE Starter Kit entirely? For most organizations, yes the native Admin Center capabilities now cover what the community toolkit used to handle manually, with the advantage of ongoing Microsoft support and updates. Teams with heavily customized CoE dashboards should plan a deliberate migration rather than an abrupt cutover.
Will this block citizen developers from building agents? No. The controls govern authentication, access, and compliance not who’s allowed to build. Makers can still create agents freely within the guardrails IT sets, which is the point of the safe innovation zones.
What if we don’t have dedicated Power Platform admins? This is exactly the scenario these tools were built for. The monitoring agents and automated remediation reduce the manual effort a governance program used to require, making it realistic for a smaller IT team to maintain oversight without a full-time Power Platform administrator.
Does this apply retroactively to agents we’ve already built? The monitoring and authentication policies apply to your environments going forward, including agents already deployed in them so existing agents will be evaluated against new policies once you turn them on, not exempted.
Power Platform Governance Checklist: Getting Started
- Audit which agents currently exist across your environments and who owns them the new Usage page is the fastest way to get this inventory
- Turn on enhanced authentication controls at the environment-group level before expanding agent use further
- Review Power Pages sites for accidental public exposure, especially anything still in testing or development
- Set Copilot consumption caps and review the new Usage page before your next license renewal
- Run automated license reclaim once, then schedule it to run on a recurring basis
- If you’re still relying on the CoE Starter Kit, start planning a migration path to native Admin Center governance
- Brief your makers on the new authentication requirements before they hit an unexpected block in production
If your organization is running Power Platform without a clear governance strategy, now is the right moment to build one, the tools finally exist to make it manageable rather than manual. Power Platform governance tends to work best when it’s designed deliberately, before an incident forces the issue rather than after.
CogentNext works with IT and business application teams across India, Australia, and the USA on exactly this kind of setup authentication policy, agent security, cost controls, and the underlying Dynamics 365 environment architecture. If it would help to talk through where your own tenant stands today, we’re glad to be a second set of eyes.
Get in touch with us:
Email: info@cogentnext.com
USA: +1 (628) 600-5070
AUS: +61 (4) 8080-5353