fix(05,12): raise o3-deep-research TPM capacity from 10 to 200#13
Merged
corticalstack merged 2 commits intoMay 27, 2026
Merged
Conversation
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
ae26671
into
fix/deep-research-apim-key-lookup
1 check passed
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.
Summary
Raise the
o3-deep-researchmodel deployment SKU capacity from10(10K TPM) to200(200K TPM) in both Bicep files that define it:05-foundry-project-pattern-setup/05-02-deploy-foundry-core-gateway/main.bicep(the hub deploy)12-foundry-iq-deep-research/main.bicep(the optional standalone deploy)The original 10K cap throttles multi-step deep-research runs with 429 errors before they complete. 200K gives realistic headroom for the agentic deep-research loop while staying well under the Norway East
o3-DeepResearchsubscription quota (limit 3000 - confirmed viaaz cognitiveservices usage list -l norwayeast).GlobalStandard billing is pay-per-token, so raising the capacity ceiling does not change baseline cost; it only raises the rate-limit cap.
Existing deployments
Bumping the Bicep value does not update already-deployed resources. To update a live deployment in place without redeploying the whole template:
az cognitiveservices account deployment update \ -g rg-foundry-core-{suffix} \ -n aif-research-{suffix} \ --deployment-name o3-deep-research \ --sku-capacity 200Patch release 0.8.5.
Stacking note
This PR is stacked on
fix/deep-research-apim-key-lookup(PR #12). Base set to that branch so the diff shows only the Bicep + version-bump changes. Merge #12 first, then this PR.Test plan
az deployment group createof either Bicep produces ano3-deep-researchdeployment withsku.capacity = 20012-02-deep-research-loop.ipynbcompletes a multi-step research run without 429saz cognitiveservices usage list -l norwayeaststill shows theOpenAI.GlobalStandard.o3-DeepResearchtotal well under its limit