microsoft-foundry / microsoft-foundry/foundry-samples
Unable to deploy network isolated Foundry (template 19): `SpecialFeatureOrQuotaIdRequired`
@m-gheini is already working on this.
Since Aug 18, 2026.
- Dominant language
- Bicep
- Stars
- 445
- Forks
- 494
- Avg merge
- 11h 35m
- Merged PRs (30d)
- 38
Description
We are seeing the following when trying to deploy template 19, which is for Microsoft Foundry with both agents and tools behind vnet (E2E network isolation):
{"status":"Failed","error":{"code":"DeploymentFailed","target":"/subscriptions/bc3b87b4-c684-43f6-b76d-a98c0e1568e8/resourceGroups/myapp/providers/Microsoft.Resources/deployments/main","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.","details":[{"code":"InvalidTemplateDeployment","message":"The template deployment 'myappcgbi-cgbi-deployment' is not valid according to the validation procedure. The following resource provider(s) - 'Microsoft.CognitiveServices/accounts (2025-04-01-preview)' reported preflight validation errors. Tracking id is '51d3b674-7e2d-47f5-bb45-2d1a755cd853'. See inner errors for details.","details":[{"code":"SpecialFeatureOrQuotaIdRequired","message":"The current subscription does not have access to this model 'Format:OpenAI,Name:gpt-4o-mini,Version:2024-07-18'."}]}]}}
We have tried a few different model names/versions, but all are failing:
- Format:OpenAI,Name:gpt-4o-mini,Version:2024-07-18
- Format:OpenAI,Name:gpt-4.1,Version:2025-04-14
- Format:OpenAI,Name:gpt-5.4,Version:2026-03-05
We have also tried deploying in multiple regions (North Central US and West US 2).
We are bringing our own vnet, AI search, storage account, and CosmosDB resources.
Please advise on how this issue can be resolved. Thank you!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.