Chapter 6 of 6 · Validation and operations

Azure API Management AI gateway design and implementation

Runtime assurance 4.5 hours in a non-production POC

Chapter 6 of 6

Confirm the result#

Send one synthetic request with the valid workload subscription key and an invalid bearer token. APIM must return 401 Unauthorized before calling Content Safety or Foundry. Do not retain the response, key, or headers.

After implementation#

The delivery owner keeps the design record with the approved change records. The platform owner maintains the deployment definitions. The product owner owns subscriptions and limits. The safety owner owns the Content Safety backend and thresholds.

To remove the route, first confirm that no approved consumer uses it. Through the approved APIM change path, check implementationSession=06-apim-ai-gateway. Remove the APIM gateway API, product, backends, and four nonsecret named values. Leave APIM, Foundry, Content Safety, the logger, role assignments, and repository definitions in place.

Session 06

Azure API Management AI gateway design and implementation slide deck