Okta

The organisation

Okta, The World's Identity Company, is a San Francisco-headquartered identity and access management provider trusted by thousands of organisations worldwide to secure authentication and authorisation for employees, customers and, increasingly, AI agents. Publicly listed since 2017, Okta operates its own low-code Power Platform estate internally to run parts of its business, and, like any fast-growing SaaS company, holds itself to a high internal bar for governance and security as that estate scales.

The challenge

As Power Platform adoption grew across Okta's internal teams, its Default environment, originally a sandbox for makers to experiment and test ideas, had become home to more than 100 active solutions, many of them business-critical Power Apps and Power Automate flows sitting entirely outside Okta's managed environment structure. Each solution had its own owners, live data connections and dependencies, ruling out a simple lift-and-shift. Every migration required identifying the owner, understanding dependencies, recreating connections in a target managed environment, validating functionality and decommissioning the original, all against a quarterly deadline tied to Okta's broader governance roadmap, with internal capacity already stretched.

The solution

the delivery team was brought in to give Okta's internal governance team the specialist capacity it needed at short notice, embedding two Power Platform engineers directly into the team rather than running the work at arm's length. The engineers worked solution by solution, first establishing ownership and mapping every dependency, then rebuilding each solution's connections inside the correct managed environment, validating that functionality was preserved before decommissioning the original from Default. Because these were live, business-critical tools relied on daily by Okta staff, the migration had to be sequenced carefully to avoid any interruption to day-to-day operations, coordinating with individual solution owners throughout rather than pushing a single big-bang cutover. This embedded model meant the team's engineers worked to Okta's existing governance standards and reporting cadence from day one, giving the internal team full visibility of progress against the quarterly deadline without having to manage a separate external workstream. The approach kept Okta's wider Power Platform governance roadmap on schedule while treating each of the 100-plus migrations with the same rigour, protecting the reliability that a security-first company like Okta demands of every internal system it runs.

How we ran it

1. 01

   Mobilise fast

   Embedded two Power Platform engineers directly into Okta's internal governance team at short notice.

2. 02

   Map ownership and dependencies

   Identified the owner and mapped every connection and dependency for each of the 100+ solutions in Default.

3. 03

   Migrate solution by solution

   Rebuilt connections in managed environments and validated functionality before decommissioning each original.

4. 04

   Protect continuity

   Sequenced every migration to avoid disruption to the staff relying on these tools day to day.

The result

In under two months, Okta's internal governance team had every one of its 100-plus Default environment solutions migrated into properly managed environments, with connections rebuilt and validated against their original owners. The Default environment was cleared as planned, Okta's quarterly governance milestone was met on schedule, and the migration was completed with zero disruption to the end users relying on those tools day to day, giving Okta a clean foundation to govern its Power Platform estate going forward.