A parks chatbot platform proposes Bicep changes that add Foundry connections to municipal SharePoint knowledge bases. What review practice fits?

Reviewing Bicep diffs that introduce new Foundry connections before merge is the correct change-control practice when a parks chatbot platform proposes wiring Foundry to municipal SharePoint knowledge bases. Infrastructure-as-code is the auditable path for civic GenAIOps: a connection to SharePoint can expose parks policies, maps, and operational documents as grounding content, so reviewers must inspect which sites or libraries are connected, which identity the connection uses, and whether the template targets the right environment. Merging only after that review keeps knowledge-base attachment a governed infrastructure change rather than an unchecked portal tweak.

Approving new Foundry connections when Bicep build validation passes fails because build validation only checks template syntax, not which SharePoint scopes or identities were added, so reviewers cannot catch over-broad grounding without inspecting the diff. Verifying Key Vault secret names referenced by the Bicep connection parameters fails because checking secret names addresses credential handling, not which SharePoint libraries or identities the Bicep template newly connects to Foundry, which still requires a reviewed diff. Checking Foundry connection status in the portal after merging Bicep changes fails because post-merge portal review catches drift too late; the connection must be governed in the Bicep diff before merge to avoid unaudited production changes.

Exam caveat: connection review is about governing knowledge sources and identities in IaC—not about choosing a foundation model. When the stem mentions Bicep/ARM changes that add Foundry connections to SharePoint or similar civic content stores, the correct action is diff review before merge.

Operational check: require a pull request on the Bicep that adds the Foundry–SharePoint connection, verify the connected knowledge scope and managed identity in the diff, and confirm staging validation precedes production apply.