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-services/agents/how-to/virtual-networks.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ By default, the Standard Setup with Private Network Isolation ensures:
28
28
29
29
For customers without an existing virtual network, the Standard Setup with Private Networking template simplifies deployment by automatically provisioning the necessary network infrastructures.
@@ -124,18 +124,18 @@ The following DNS zones are configured:
124
124
* privatelink.search.windows.net
125
125
* privatelink.services.ai.azure.com
126
126
127
-
### Virtual Network (Vnet) Capabilities
127
+
### Virtual network (Vnet) capabilities
128
128
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.
129
129
130
130
131
-
### Network Rules
131
+
### Network rules
132
132
133
133
All accounts and their corresponding projects are protected by default with **deny-by-default network rules**, requiring explicit configuration to allow access through private endpoints.
134
134
135
-
These rules apply to **all protocols**, including REST and WebSocket. Even internal testing tools like Azure Portal's test consoles require explicit permission to access your account and its child resources—ensuring complete security across all agent projects.
135
+
These rules apply to **all protocols**, including REST and WebSocket. Even internal testing tools like Azure portal's test consoles require explicit permission to access your account and its child resources—ensuring complete security across all agent projects.
136
136
137
137
138
-
### Private Endpoints
138
+
### Private endpoints
139
139
140
140
For Agents, private endpoints ensure secure, internal-only connectivity for the following Azure resources:
141
141
@@ -145,7 +145,7 @@ For Agents, private endpoints ensure secure, internal-only connectivity for the
145
145
- Azure Cosmos DB
146
146
147
147
148
-
### DNS Zone Configurations Summary
148
+
### DNS zone configurations summary
149
149
150
150
| Private Link Resource Type | Sub Resource | Private DNS Zone Name | Public DNS Zone Forwarders |
@@ -156,7 +156,7 @@ For Agents, private endpoints ensure secure, internal-only connectivity for the
156
156
157
157
158
158
159
-
### Access Your Secured Agents
159
+
### Access your secured agents
160
160
161
161
Once your template deployment is complete, you can access your Foundry project behind a virtual network using one of the following methods:
162
162
* **Azure VPN Gateway**: Connects on-premises networks to the virtual network over a private connection. Connection is made over the public internet. There are two types of VPN gateways that you might use:
@@ -176,8 +176,8 @@ Once your template deployment is complete, you can access your Foundry project b
176
176
177
177
This setup enables AI agents to operate entirely within a dedicated, isolated virtual network. By leveraging private network isolation (BYO VNet), organizations can enforce custom security policies, ensuring that AI agents operate within their trusted infrastructure.
178
178
179
-
Our goal is to accelerate the development and deployment of AI agents without compromising critical security requirements. With our bicep and arm templates, you can quickly set up your agent environment while still maintaining full control over their networking and data.
179
+
Our goal is to accelerate the development and deployment of AI agents without compromising critical security requirements. With our bicep and ARM templates, you can quickly set up your agent environment while still maintaining full control over their networking and data.
180
180
181
181
182
-
## What's Next?
182
+
## What's next?
183
183
You’ve now successfully configured a Network Secure Account and project, use the [quickstart](../quickstart.md) to create your first agent.
0 commit comments