Power Platform Governance & Platform Leadership
I hold platform leadership for Power Platform across this department's tenant, and led a whole-of-tenant governance uplift that put formal structure in place for the first time.
The challenge
Before it, there was no baseline DLP policy, no environment strategy, no defined ALM approach and no onboarding pattern. Solutions were built and promoted on judgment. In an organisation running government data across multiple business areas and peer agencies in the same tenant, that's a material risk that nobody owned.
The approach
I authored a tiered model and made the tiers line up. Environments are tiered, DLP policy is tiered against them, and ALM strategy follows the same structure, with defined gateways governing movement between tiers. Onboarding patterns and a documented playbook mean a new solution has a route to production that doesn't depend on who is asked.
Architecture
Alongside the policy work I re-architected the department's Center of Excellence, moving it off the legacy cloud flow architecture onto a bring-your-own data lake model integrated directly with the Power Platform management APIs. The distinction matters: the CoE went from a collection of flows to an instrumented telemetry pipeline, which is what makes the governance enforceable rather than aspirational. I also established the standard integration patterns teams build against — Azure Key Vault for secrets, Application Insights and Log Analytics for observability — so that security and diagnosability are inherited from the pattern rather than retrofitted per solution.
Outcome
Day to day I'm the escalation point for platform and infrastructure questions, liaise with security teams on configuration and compliance, review and advise on individual solution designs across the department, and contribute to tenant-wide strategy alongside other departments sharing the same tenant.
The durable outcome isn't any single policy. It's that the department now has a defensible answer to how Power Platform is governed, who owns that answer, and what a team has to do to build something and put it into production safely.