Governance as code after the CoE Starter Kit
Diesen Beitrag auf Deutsch lesen
Use PAC CLI inventory APIs, versioned governance rules and repeatable capture to track Power Platform tenant risks.
TL;DR
PAC CLI inventory APIs can show apps, flows and agents by environment within minutes, without the CoE Starter Kit database and nightly sync flows. Keep PAC CLI updated, verify the active authentication profile, and validate community code in a sandbox before any production use. Store environment zones, governance rules and captured tenant state in versioned, repeatable controls.
Original by Karl-Johan Spiik, on Karl-Johan Spiik, Microsoft MVP. Read the original
This is our own summary, not a republication or full translation.
Governance takeaway
- Admins/CoE: Use PAC CLI inventory data to identify environment sprawl and keep the active authentication profile under review.
- Admins/CoE: Turn on Managed Environments, but do not rely on weekly digests as a complete operations tool.
- Security/Compliance: Validate third-party packages and community dashboards in a sandbox before connecting them to production.
- Leadership/Business: Define clear, non-contradictory governance rules and retain human decisions for actions affecting tenant solutions.
Frequently asked questions
What happened to the CoE Starter Kit, and what gap remains?
Microsoft archived the repository in July. The speaker had used the kit since 2020 and describes keeping up with its releases as nearly full-time work.
Which three stages does the maturity ladder for governance as code describe?
Stage one is the PAC CLI in the terminal with AI chat. Stage two runs existing community code that shows inventory in dashboards. Stage three is a custom solution adding purpose, policies and ownership.
Which warnings apply when using the PAC CLI with an AI agent?
Keep the CLI current, since recent updates added fifteen new command groups, mostly in preview. Verify the active authentication profile, because the speaker accidentally enabled features in the wrong tenant.