You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/ai-foundry/agents/how-to/virtual-networks.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,7 @@ For customers without an existing virtual network, the Standard Setup with Priva
36
36
-**Subnet IP address limitation**: both subnets must have IP ranges under `172.16.0.0/12` or `192.168.0.0/16`, i.e. class B or C address ranges reserved for private networking.
37
37
-**All Foundry workspace resources should be in the same region as the VNet**, including CosmosDB, Storage Account, AI Search, Foundry Account, Project, Managed Identity. The only exception is within the Foundry Account, you may choose to deploy your model to a different region, and any cross-region communication will be handled securely within the Azure network infrastructure.
38
38
-**Region availability**:
39
-
- For a list of supported regions for Foundry workspace resources, see:
39
+
- For supported regions for Foundry workspace resources, see:
40
40
[Azure AI Foundry project region availability](https://learn.microsoft.com/azure/ai-foundry/reference/region-support#azure-ai-foundry-projects).
41
41
- For supported regions for OpenAI model deployments, see: [Azure OpenAI model region support](https://learn.microsoft.com/azure/ai-foundry/agents/concepts/model-region-support#azure-openai-models).
42
42
-**Azure Blob Storage**: using Azure Blob Storage files with the File Search tool isn't supported.
0 commit comments