Citizen-built apps and flows grow faster than anyone tracks them
The questions are the ones you already ask of a Team or a SharePoint site: who built it, who can use it, what it connects to, what it costs and who retires it.
Who owns it
Apps and flows keep running after their maker changes role. With no current owner, nobody fixes a broken flow or answers for an app that handles business data.
Who can use it
Sharing an app takes one click. Without a ranking by reach, an app that thousands of people rely on looks the same as one only its maker opens.
What it costs
An app that uses a premium connector needs a premium licence for its users. You find out at renewal, not when the maker adds the connector.
Whether it still runs
A stopped flow keeps its connections and licence until someone acts. Seen one environment at a time, the flows nobody uses stay invisible.
What Rencore sees and does in the Power Platform
Every app and flow, and how widely each is shared
Rencore scans your Power Platform and records every environment, canvas app and flow, so you see the estate instead of one environment at a time. Power BI workspaces and Copilot Studio agents sit in the same inventory, next to the Teams and sites they depend on.
- Environments, canvas apps and flows in one inventory
- Flow state and last run for every flow
- The canvas apps shared with the most users, ranked, with the total number of shares
- Connections, including premium and custom connectors
Find the apps that need a premium licence
Flows and apps can run on standard and premium connectors, and it is hard to tell which is which at scale. Rencore finds the apps that need a premium licence because of the connectors they use, so platform teams act before the invoice arrives.
- Apps that need a premium licence because of their connectors
- The premium and custom connectors they run on, and the makers behind them
- A policy count of apps in violation, with the three-month trend
- Duplicates and unused apps to consolidate or retire before they add to the licence bill
Stopped and unused flows, found and followed up
Flows are the glue behind many business processes, and the broken or redundant ones are easy to miss. Rencore lists them by policy, with the environment, the owner and the last run, so someone can be asked before the flow is left to run on.
- Flows in the Stopped state
- Flows without runs, and unused flows
- Long-running flows and flows with many runs
- Each flow with its environment, its owner and its last run, and the three-month trend of the policy
Apps nobody owns, with the owner asked first
Unclear accountability makes it hard to resolve problems quickly. Rencore names the canvas apps that have neither an owner nor a co-owner, shows who they are shared with, and notifies the owner through an automation, with an approval step where a decision is needed.
- Canvas apps with neither an owner nor a co-owner
- Each app with its last use and the people it is shared with
- An automation that notifies the owner, and can ask for an approval before an action runs
- Quarantine and delete actions for Power Apps
Where Power Platform governance stops today
What Rencore reads in the Power Platform, and what stays with the Power Platform admin center or outside the product.
The admin center stays
You still configure environments, data policies and Managed Environments in the Power Platform admin center. Rencore does not replace it.
No data policy management
Rencore does not read your data policies or connector allow-lists, and no action changes them or moves an app between environments.
Limited actions on flows
Actions on flows add or remove run-only users and groups. Rencore does not stop, delete or quarantine a flow.
Canvas apps and flows only
Model-driven apps and solutions are not in the inventory, and the owners of apps and flows are not part of access reviews.
Apps, Automation and BI
Power Platform questions, answered
Which Power Platform services does Rencore cover?
The Apps, Automation and BI module covers Power Platform, Power Apps, Power Automate, Power BI and Fabric. Every app, flow, report and connection lands in one inventory with its environment and how widely it is shared. This page covers environments, canvas apps and flows; Power BI and Fabric have their own pages, for Power BI and Fabric.
Does Microsoft already cover this in the Power Platform admin center?
In part. The admin center gives you Inventory, Usage, Monitor and Actions, plus the Power Platform CLI and APIs, and it stays the place where you configure environments, data policies and Managed Environments. Monitor and the full set of Actions need Managed Environments, and every user running an app in a managed environment needs a premium licence. Rencore complements it: it adds current ownership, an owner-led lifecycle and cost attribution, and puts the Power Platform in the same inventory as your Microsoft 365 workspaces and Copilot agents.
We run the CoE Starter Kit. Do we have to switch at once?
No. Nothing in Rencore depends on the kit, so you can keep its reports while you move governance over and retire it when you are ready. Microsoft no longer actively maintains the kit, and the comparison of Rencore and the CoE Starter Kit sets out what changes.
Does this slow our makers down?
No. Makers keep building, and policy runs alongside them rather than in front of them. Rencore ranks what carries real risk or cost, such as an app shared with the entire organization or an app with no owner, and routes those to the people who can act. What is low risk stays out of everyone's way.
How is Power Platform coverage licensed?
It is part of the Apps, Automation and BI module, the optional paid module on the Premium and Enterprise plans, which also covers Power Apps, Power Automate, Power BI and Fabric. The pricing page has the full plan comparison.