MOCA365 · Power Platform Governance
Cross-tenant Power Platform governance - without premium-licensing your maker base
Find the apps, flows, and Copilot Studio agents across your tenants - including the orphaned and over-shared ones, and the SharePoint sites they touch.
Overview
MOCA365 Power Platform Governance is a governance solution for Microsoft Power Platform and Copilot Studio, for organizations of all sizes. It gives you visibility across your tenants, surfaces ownership and oversharing issues, links Power Platform flows to the SharePoint sites they touch, and lets you reassign ownership of orphaned flows - all this without requiring Managed Environments or premium licensing for your users.
What it does
Discovery and oversight across your tenants
Find what's running
Apps, flows, and Copilot Studio agents - plus desktop flows, connectors, Power Pages and solutions - across your tenants, including the ones nobody told you about.
See who owns what - and who over-shares
Apps and flows validated for ownership against Entra ID. Orphaned and former-employee-owned resources are surfaced, and apps and flows shared with "Everyone" or with an unusually high number of editors are flagged before they become a breach. Signals are enabled per tenant.
Connect Power Platform to SharePoint
Resolve which SharePoint sites each flow actually reads and writes - then tie it back to the owner. Nobody else connects the two.
Detect and remediate
Most tools stop at "here are your problems." MOCA365 lets you act: reassign ownership of an orphaned or mis-owned flow directly from the MOCA365 Admin Center - so a flow whose owner has left gets a valid owner again, without rebuilding it.
Makers and shadow IT
See the makers who own or edit apps and flows, with their footprint ranked by blast radius - so you can finally answer "who holds the keys to Power Platform?"
Complete inventory
AI Builder models, business process flows, connections and DLP policies as first-class inventory - parity with what the CoE kit gave you, maintained.
Built for the Copilot era
Copilot Studio agents inventoried across your tenants, broadly shared agents flagged, and a weighted AI-readiness score across data protection, agent security, environment governance and identity. The Copilot risk surface - in one view. These are readiness signals, not a compliance verdict.
Why MOCA365
The wedge
No premium-per-user licensing
We read across all environments outside-in. Managed Environments would mean premium-licensing your whole maker base - we don't.
Multi-tenant, one view
Your tenants in a single pane - built for the partners and enterprises the admin center's one-tenant-at-a-time model leaves stranded.
Customer-owned, queryable store
A per-tenant SQL store you can query - not a preview-gated export.
Maintained
Actively developed and maintained - unlike the frozen CoE Starter Kit.
$240k/yr in Managed Environments licensing for 1,000 active makers ($20/user/month) - versus $0 per-user with MOCA365.
How it compares
| MOCA365 | Admin center (PPAC) | CoE Starter Kit | |
|---|---|---|---|
| Cross-tenant / multi-tenant view | ✅ | ❌ single-tenant | ❌ |
| Governs without premium-per-user licensing | ✅ | ❌ ME-gated | ✅ (but frozen) |
| Power Platform → SharePoint-site linkage | ✅ | ❌ | ❌ |
| Desktop flows · connectors · Power Pages · solutions as inventory | ✅ | ❌ | ✅ |
| Actively maintained | ✅ | ✅ | ❌ frozen Feb 2026 |
MOCA365 inventories, flags, and can reassign owners today. Deeper lifecycle automation and approval workflows are on the roadmap.
On the roadmap
From detection to action
Lifecycle management (active → monitor → archive), notifications, and maker self-service environment and DLP requests with approval workflows - so governance keeps extending beyond detection.
