Know what is actually running in your tenant.
A fixed-scope scan of your Power Platform and Copilot footprint. Findings in 2-3 weeks, a 90-day fix list included.
- Duration
- 2-3 weeks
- Service line
- Power Platform governance
You probably cannot say today how many apps and flows sit in your default environment, who can reach production data through them, or which Copilot Studio agents are shared company-wide. That is normal, because the admin tools show pieces, not the whole picture. The scan puts the whole picture on one page, ranks the risks, and tells you what to fix first. It is read-only, it does not interrupt your makers, and it ends with a decision, not a binder.
Who it’s for
Heads of IT with a Copilot rollout on the calendar
You need to know what Copilot and agents will be able to reach.
Security and compliance teams
You need evidence of what is deployed, for DORA, NIS2 or an internal audit.
Tenants that turned on Managed Environments
Licensing enforcement is coming in February 2027 and you need to know your exposure.
What we do
- 1. Environment inventory: every environment, its type, owner and purpose
- 2. Maker and permission map: who can build, share and reach what
- 3. Connector usage and DLP policy review, including gaps and exceptions
- 4. Solution and ALM hygiene: what is in solutions, what is not
- 5. Dataverse security roles and access to sensitive tables
- 6. Copilot and Copilot Studio agent exposure
- 7. Managed Environments readiness and a licensing overview
- 8. Ownership: orphaned and unowned apps, flows and agents
What you get
- A findings report in Bulgarian or English
- A risk heat-map across environments, makers and data
- A prioritised 90-day remediation backlog
- An executive readout session for your leadership
How it works
- 1
Week 1: Access and inventory
We agree read-only access with your admin, run the inventory and talk to the people who own the biggest apps.
- 2
Week 2: Analysis
We work through the eight checks, test the findings against your real data flows, and rank the risks.
- 3
Week 3: Findings and readout
You get the report, the heat-map and the 90-day backlog, and we walk your leadership through the decisions.
What we don’t do
We do not change anything in your tenant during the scan. It is read-only, so there is nothing to roll back and no risk to the apps your teams use today.
Certifications behind the work
- SC-401
- SC-300
Questions we get
Do you need admin access?
We need read access, not the power to change settings. We agree the exact roles with your admin before the start, and we can work from exports your admin runs if you prefer. We never need your users' passwords, and access is removed when the scan ends.
Will this disrupt makers?
No. The scan is read-only, so apps and flows keep running as they are. We may ask a few makers for a short conversation about what their biggest apps do. Nothing is switched off, moved or restricted during the scan.
What about Copilot?
Check 6 covers it. We look at which Copilot Studio agents exist, who can publish them, which knowledge sources and connectors they use, and what Microsoft 365 Copilot would be able to reach through your current sharing. Copilot does not create oversharing, it reveals it, and the scan shows you where.
How is a Governance Scan scoped?
Scope depends mainly on tenant size: the number of environments, apps, flows and makers. After a short scoping call you get a written scope with deliverables and timing, before any work starts.
Can we get the report in Bulgarian?
Yes. The report and the readout are delivered in Bulgarian or English, whichever your leadership and auditors need. Product names stay in English because that is how they appear in your admin portals.
Why do this before February 2027?
Microsoft's licensing guidance says that from February 2027, users without an appropriate licence are blocked from opening apps in a Managed Environment. The scan shows which environments are managed, who uses them, and where licences may be missing, so you can decide before users are affected.
Find out where you stand, pillar by pillar.
Start the trial on your own tenant, or let a solution architect read the first scan with you.