What has to pass before a merged pull request may change the production API Management instance without anyone opening the portal? Part 5's publish workflow already ran a dry run on every pull request and published on merge, but nothing required the dry run to pass, it signed in with the same identity that published to dev, and nothing read the spec or the policies before the CLI did. A pipeline you can trust with prod needs four gates, each catching something the others can't: checks that need no Azure at all, a dry run that can only read, a publish to dev that API Management itself validates, and a person who approves prod.
The companion repo keeps Part 5's layout: apiops/ holds the artifact tree, the extract filter and configuration.prod.yaml , and the APIOps CLI is still pinned at @azure-tools/[email protected] . The publish workflow is what changes.…