Skip to content

Commit 03935ad

Browse files
Merge pull request #6046 from meerakurup/patch-18
Update virtual-networks.md
2 parents e8eeea3 + 0286a37 commit 03935ad

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

articles/ai-foundry/agents/how-to/virtual-networks.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -68,6 +68,9 @@ For customers without an existing virtual network, the Standard Setup with Priva
6868
az provider register --namespace 'Microsoft.Storage'
6969
az provider register --namespace 'Microsoft.MachineLearningServices'
7070
az provider register --namespace 'Microsoft.Search'
71+
az provider register --namespace 'Microsoft.Network'
72+
az provider register --namespace 'Microsoft.App'
73+
az provider register --namespace 'Microsoft.ContainerService'
7174
# only to use Grounding with Bing Search tool
7275
az provider register --namespace 'Microsoft.Bing'
7376
```
@@ -169,6 +172,8 @@ The following DNS zones are configured:
169172
### Virtual network (Vnet) capabilities
170173
Virtual networks enable you to specify which endpoints can make API calls to your resources. The Azure service automatically rejects API calls from devices outside your defined network. You can establish allowed networks using either formula-based definitions or by creating an exhaustive list of permitted endpoints. This security layer can be combined with other security measures for enhanced protection.
171174
175+
> [!NOTE]
176+
> If you bring your existing virtual network and subnet with the *Microsoft.App/environments* delegation, the minimize size of your subnet should be /27 (32 addresses). We recommend a subnet size of /24 (256 addresses) and is the default subnet size set in the network secured template.
172177
173178
### Network rules
174179

0 commit comments

Comments
 (0)