Skip to content

Commit 8f5d4ba

Browse files
Update virtual-networks.md
Removing "Option" & "manual" wording for ways to deploy secured agent service. We used to have automatic way, but not anymore. Also adding a note that this is only way to do that right now.
1 parent 5c6e63e commit 8f5d4ba

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

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

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,10 @@ For customers without an existing virtual network, the Standard Setup with Priva
7777
* A Microsoft-managed key vault is used by default.
7878

7979

80-
### Option 1: manually deploy the bicep template
80+
### Manually deploy the bicep template
81+
82+
> [!NOTE]
83+
> Bicep template is the only way available to deploy a network secured environment for Agent Services.
8184

8285
1. To deploy and customize the bicep templates, [download the template from GitHub](https://github.com/azure-ai-foundry/foundry-samples/tree/main/samples/microsoft/infrastructure-setup/15-private-network-standard-agent-setup). Download the following from the `private-network-standard-agent-setup` folder:
8386
1. `main.bicep`
@@ -180,4 +183,4 @@ Our goal is to accelerate the development and deployment of AI agents without co
180183

181184

182185
## What's next?
183-
You’ve now successfully configured a Network Secure Account and project, use the [quickstart](../quickstart.md) to create your first agent.
186+
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)