Repository navigation
Update AI Gateway sample to standalone aigateways resources - #1157
Open
ayushhgarg-work wants to merge 1 commit into
Open
ayushhgarg-work wants to merge 1 commit into
ayushhgarg-work wants to merge 1 commit into
Conversation
Use the Standard SKU, compatible preview child operations and payloads, a callable model alias, returned runtime hostname, and scoped permission guidance. Regenerate the sample ARM template and update its parameters and documentation. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
🔵 Needs a closer look
Missing preview child-resource schemas, omitted default-deployment checks, and quota-blocked inference leave deployment-name compatibility and the end-to-end Foundry connection path unverified, requiring validation in an enabled Azure tenant.
No open issues 🎉
What changed in this PR
Updates the Foundry golden-path AI Gateway sample to deploy standalone Microsoft.ApiManagement/aigateways resources instead of the legacy API Management service. This creates a new resource type rather than upgrading or removing existing APIM resources.
Changes:
- Uses the standalone Standard SKU gateway with compatible preview child operations and a callable model alias, preserving managed-identity backend access.
- Derives the runtime URL from the returned hostname, updates key retrieval, and removes obsolete publisher parameters.
- Regenerates the ARM template and documents compatibility, scoped permissions, and live-validation limits.
All paths are under infrastructure/infrastructure-setup-bicep/01-connections/ai-gateway-tier/.
| File | Description |
|---|---|
samples/parameters.json |
Removes obsolete publisher parameters. |
samples/connection.parameters.json |
Updates the example URL to use the returned gateway hostname. |
README.md |
Documents standalone deployment, permissions, compatibility, and validation results. |
metadata.json |
Updates the sample description and publication date. |
main.bicep |
Migrates gateway resources, adds a callable alias, and updates outputs. |
connection.bicep |
Updates key-retrieval guidance and the URL parameter description; connection logic is unchanged. |
azuredeploy.json |
Reflects the Bicep changes in the generated ARM template. |
Review effort: Balanced
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Update the existing AI Gateway tier Bicep sample to use the standalone
Microsoft.ApiManagement/aigatewaysresource instead of the legacy API Management service representation.2026-11-01and SKUStandardfor the parent gateway, with compatible2026-09-01-previewworkspace/provider/model/alias/key operations and payloads.<connectionName>/<modelName>reference and managed-identity backend access.properties.frontend.defaultHostname, remove obsolete publisher parameters, and update runtime-key retrieval.azuredeploy.jsonand update the sample's parameters, metadata, README, and scoped RBAC prerequisites.Scope: seven files under
infrastructure/infrastructure-setup-bicep/01-connections/ai-gateway-tier/only. No shared workflows, other samples, or higher-level infrastructure are changed.Compatibility: this creates a different Azure resource type; it is not an in-place upgrade of an existing
Microsoft.ApiManagement/service. Existing APIM resources are not removed. Custom parameter files must removepublisherEmailandpublisherName.Verification
Local checks, run from the sample directory:
az bicep build --file .\main.bicep --stdoutaz bicep build --file .\connection.bicep --stdoutazuredeploy.json, excluding only compiler generator metadatagit diff --check