Power Platform
Environments, DLP, ALM and the Center of Excellence practice that keeps a platform governable.
Qui est propriétaire de vos applications Power Apps ?
Une application créée par un collaborateur parti, un flux qui s'exécute sous un compte désactivé. Comment inventorier applications, flux, environnements et propriétaires avant qu'un élément critique ne s'arrête.
من يملك تطبيقات Power Apps في مؤسستك؟
تطبيق بناه موظف غادر، وتدفّق آلي يعمل باسم حساب معطَّل. كيف تحصر التطبيقات والتدفقات والبيئات ومالكيها قبل أن يتوقّف أحدها في وقت غير مناسب.
Seven weeks and Christmas: planning the move off unmanaged developer environments
You will not move everything, so decide what you are abandoning. Waves grouped by dependency, state tracked per app rather than per environment, and the three questions a plan has to survive before you commit to a date.
Moving an app from an unmanaged to a managed developer environment
Two routes, and the one most people miss moves nothing at all. Converting in place, exporting and importing, the four steps where imports quietly go wrong, and the two Managed Environments behaviours that bite afterwards.
Microsoft is switching off unmanaged developer environments. How many do you have?
Unmanaged developer environments are suspended on 15 December 2026 and deleted from 15 January 2027. The dates are the easy part — the hard part is that most tenants cannot say how many they have or what is inside them.
Decommissioning a SharePoint site or a Power BI report? Search every app first.
Before you retire a SharePoint site, a Power BI report or a SQL server, you need every app and flow that references it. The references are inside the apps, not in any admin API. Here is how to find them.
Your makers built outside solutions. Can you still see what depends on what?
Most of what gets built never goes into a solution. That is fine until it has to move. How to recover the dependency picture a solution would have given you, and decide what to package together.
Who has access to what? One permissions report across every environment
Audit asks who can open what. The admin centre answers one app at a time, counts a four-hundred-person group as one share, and has no export. Here is how to build the tenant-wide version.
Moving apps and flows to another tenant: do you know everything that travels with them?
A migration list is a list of apps. What actually moves is a graph. The six classes of dependency that come with a Power Platform estate, including the one that never appears on an app’s own connector list.
Can you make one person co-owner of every app in the tenant?
A Power Platform administrator can list every app in the tenant and open none of them. Here is why that gap blocks migrations and leaver clean-ups, and how to close it in bulk rather than one app at a time.
Do you know what is hard-coded inside your fifty Power Apps?
Site URLs, SQL servers, Power BI links and environment ids get typed into formulas and never leave. No admin API reports them. Here is where they live and how to read them out at estate scale.
The three things that break every Power Platform migration
Apps outside solutions, flows without connection references and buttons opening hardcoded URLs — the three findings that derail a Power Platform migration, and how to find them first.
Power Platform Governance: A Practical Guide to Staying in Control Without Slowing Innovation
Learn how to implement effective Power Platform governance with this practical guide covering key areas such as environments, DLP (Data Loss Prevention)…
Understanding Power Platform Licensing
The plain-English guide to Power Platform licensing in 2026. Covers Power Apps, Power Automate, Power BI, Power Pages, Copilot Studio, and Dataverse…
Ready to get more from Microsoft 365?
Talk to a LogiSam consultant about your apps, automation or Copilot roll-out. No commitment, just clear next steps.