Who wins when Bicep and the Azure portal disagree about a policy on the same API Management instance, and how do you find out before a partner does? In the order API from Parts 1 to 4, Bicep deploys every API, policy and product, so a fix someone makes in the portal's policy editor lasts exactly until the next azd up , and nothing records that it was ever there. APIOps moves the API surface into files that a pull request can review: extract what is live, commit it, and publish only approved commits. It only works if each resource has one owner, so the answer for the order API is a split: Bicep keeps the platform, APIOps takes the APIs, policies and products.

Part 4 ended with the products and the version set in Bicep and everything clicked in the portal living only in the instance.…