Skip to content

Commit cdedaf6

Browse files
committed
fixes
1 parent a7a121c commit cdedaf6

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

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

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ By default, the Standard Setup with Private Network Isolation ensures:
2828

2929
For customers without an existing virtual network, the Standard Setup with Private Networking template simplifies deployment by automatically provisioning the necessary network infrastructures.
3030

31-
## Architecture Diagram
31+
## Architecture diagram
3232

3333
:::image type="content" source="../media/private-network-isolation.png" alt-text="A diagram showing virtual network architecture.":::
3434
### Known limitations
@@ -124,18 +124,18 @@ The following DNS zones are configured:
124124
* privatelink.search.windows.net
125125
* privatelink.services.ai.azure.com
126126

127-
### Virtual Network (Vnet) Capabilities
127+
### Virtual network (Vnet) capabilities
128128
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.
129129

130130

131-
### Network Rules
131+
### Network rules
132132

133133
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.
134134

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.
136136

137137

138-
### Private Endpoints
138+
### Private endpoints
139139

140140
For Agents, private endpoints ensure secure, internal-only connectivity for the following Azure resources:
141141

@@ -145,7 +145,7 @@ For Agents, private endpoints ensure secure, internal-only connectivity for the
145145
- Azure Cosmos DB
146146

147147

148-
### DNS Zone Configurations Summary
148+
### DNS zone configurations summary
149149

150150
| Private Link Resource Type | Sub Resource | Private DNS Zone Name | Public DNS Zone Forwarders |
151151
|----------------------------|--------------|------------------------|-----------------------------|
@@ -156,7 +156,7 @@ For Agents, private endpoints ensure secure, internal-only connectivity for the
156156

157157

158158

159-
### Access Your Secured Agents
159+
### Access your secured agents
160160

161161
Once your template deployment is complete, you can access your Foundry project behind a virtual network using one of the following methods:
162162
* **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
176176

177177
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.
178178

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.
180180

181181

182-
## What's Next?
182+
## What's next?
183183
You’ve now successfully configured a Network Secure Account and project, use the [quickstart](../quickstart.md) to create your first agent.

0 commit comments

Comments
 (0)