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
Update template 19 testing guide and add MCP HTTP server
Updates based on actual testing:
- Fixed SDK usage: use AzureAISearchTool class, not dict format
- Added note about portal limitation with network injection
- Added correct API version (2025-05-15-preview) for REST API
- Added MCP HTTP server implementation (Streamable HTTP transport)
- Updated MCP deployment instructions with proper HTTP-based server
- Added connection name lookup command
- Fixed test script to use AzureAISearchTool class
MCP Server:
- Added mcp-http-server/server.py - Flask-based MCP server
- Added mcp-http-server/Dockerfile for containerization
- Implements JSON-RPC over HTTP as required by Azure AI Agents
@@ -138,34 +138,66 @@ az search service update -g $RESOURCE_GROUP -n $AI_SEARCH_NAME \
138
138
139
139
## Step 4: Deploy MCP Server (Optional)
140
140
141
-
Deploy an MCP server to the private VNet:
141
+
Deploy an HTTP-based MCP server to the private VNet.
142
+
143
+
> **Important**: Azure AI Agents require MCP servers that implement the **Streamable HTTP transport** (JSON-RPC over HTTP). Standard stdio-based MCP servers (like `mcp/hello-world`) will NOT work.
Since the AI Services account has public access enabled, you can test directly in the portal.
254
+
> **Note**: Portal testing may be blocked even with public access enabled if your deployment uses network injection (`networkInjections` property). In this case, use SDK testing (Step 6) instead.
204
255
205
-
### 5.1 Access the Portal
256
+
### 5.1 Check if Portal Works
206
257
207
258
1. Navigate to [Azure AI Foundry portal](https://ai.azure.com)
208
259
2. Sign in with your Azure credentials
209
-
3. Select your project (created by the deployment)
260
+
3. Toggle **"New Foundry"** ON (top right)
261
+
4. Select your project
262
+
263
+
If you see this error:
264
+
> "Your current setup uses a project, resource, region, custom domain, or disabled public network access that isn't supported in the new Foundry experience yet."
210
265
211
-
### 5.2 Create an Agent with AI Search Tool
266
+
This is expected if network injection is configured. Use SDK testing instead.
267
+
268
+
### 5.2 Create an Agent with AI Search Tool (if portal works)
212
269
213
270
1. Go to **Agents** in the left menu
214
271
2. Click **+ New agent**
@@ -250,43 +307,51 @@ For automated testing or CI/CD pipelines, use the SDK:
This error occurs with **template 15** (fully private), not this template. If you see this error:
319
-
- Verify you deployed template 19 (hybrid), not template 15
320
-
- Check `publicNetworkAccess` is `Enabled` on the AI Services account
410
+
This error can occur even with public access enabled if **network injection** is configured:
411
+
412
+
```bash
413
+
# Check for network injection
414
+
az cognitiveservices account show -g $RESOURCE_GROUP -n $AI_SERVICES_NAME \
415
+
--query "properties.networkInjections"
416
+
```
417
+
418
+
If you see `networkInjections` with a subnet configured, the portal's "New Foundry" experience won't work. **Use SDK testing instead** - it works perfectly with network injection.
0 commit comments