fix(12): drop az apim extension dependency in deploy-o3-backend#12
Merged
Conversation
12-01-deploy-o3-backend.ipynb failed on Step 5 with "'subscription' is misspelled or not recognized" because `az apim subscription list-secrets` requires the `apim` Azure CLI extension that is not part of the base CLI. Rewrote Steps 3 and 5 to use `az rest` against the ARM management endpoint, matching the pattern already used by 10-01 and 11-01. Step 2 now also resolves SUB_ID and an APIM_BASE_URI helper used by the two ARM calls. No new dependencies; works with the base Azure CLI.
The original SKU capacity of 10 (= 10K TPM) throttled multi-step
deep-research runs with 429 errors before completion. Raised to
200 (= 200K TPM) in both Bicep files that define the deployment:
- 05-foundry-project-pattern-setup/05-02-deploy-foundry-core-gateway/main.bicep
- 12-foundry-iq-deep-research/main.bicep
The new value stays well under the Norway East o3-DeepResearch
subscription quota (limit 3000). Existing live deployments must be
updated separately, either by a fresh bicep apply or via:
az cognitiveservices account deployment update \
-g rg-foundry-core-{suffix} -n aif-research-{suffix} \
--deployment-name o3-deep-research --sku-capacity 200
3 tasks
…pacity fix(05,12): raise o3-deep-research TPM capacity from 10 to 200
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
1 participant
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.
Summary
12-foundry-iq-deep-research/12-01-deploy-o3-backend.ipynbfailed on Step 5 with:Root cause: the cell used
az apim subscription list-secrets, which requires theapimAzure CLI extension. The base CLI doesn't include it. Step 3'saz apim backend showhad the same dependency.Rewrote both calls to use
az restagainst the ARM management endpoint - the same pattern already used by10-01-deploy-search-and-project.ipynband11-01-deploy-setup.ipynb. Step 2 now also resolvesSUB_IDand anAPIM_BASE_URIhelper used by Steps 3 and 5. No new dependencies; works with the base Azure CLI.Verified manually: against the same APIM service that produced the original error, the
az restPOST to…/subscriptions/foundry-gateway-alpha/listSecretsreturns the expected primary key.Known related issue (not in this PR)
09-content-understanding-integration/09-01-deploy-setup.ipynbhas the same systemic bug (az apim show ... --query identity.principalId). Same fix applies. Flagged as a follow-up to keep this PR focused on the reported failure.05-02-01-deploy-foundry-core-gateway.ipynbalso referencesaz apim deletedservice list/purgebut only in commented-out cleanup cells, so not on the hot path.Patch release 0.8.4.
Test plan
12-01-deploy-o3-backend.ipynbend-to-endfoundry-gateway-dror falls back tofoundry-gateway-alphacleanly, then writesDR_GATEWAY_KEYto.env