Chapter 6 of 6
Confirm the result#
Run the live discovery check from a developer network path with the same Microsoft Entra access boundary used by the supported client.
The script reports every returned server name as approved, confirms every approved server name is present, reports zero unapproved server names, and reads every registry page. The client can then display the approved server record without receiving an MCP server credential.
After implementation#
Keep both JSON files with the API Center operating configuration. The API Center configuration owner owns Data API visibility and the registry metadata mapping. Server owners own lifecycle and review dates. The client configuration owner maintains the adapter that maps registry-client-settings.json to the current Visual Studio Code, GitHub Copilot, or other supported client setting.
Run check-discovery after a lifecycle change, visibility change, registry-client update, or MCP record synchronization. An unexpected count stops the rollout. Remove the registry from managed client configuration until the API Center owner restores the allowlist.
Restore uses the approved portal change path. First remove or disable the registry entry in the client-management system. Then restore the prior Data API visibility configuration referenced in registry-ownership.json. Return affected MCP records to their previous lifecycle stage only when the inventory owner approves that change. Leave the API Center inventory and MCP tool security runtime controls in place.
No removal script is included. Microsoft Learn does not document a stable management API for Data API visibility, and a script could not prove that it was restoring the recorded prior state.