End-to-End Test (VNet Access Required)
Continues from post-deployment-validation.md. Steps 1–3 there must be complete first.
4. VNet Access Setup
⚠️ The remaining tests require connectivity to the VNet.
Use AskUserQuestion: "Steps 1-3 are done. The remaining tests need VNet access. How do you want to proceed?" Options:
I have a Bastion VM / jump boxSet up a point-to-site VPN for me— read vpn-dns-setup.mdI have VPN / ExpressRoute alreadySkip testing for now
Bastion VM: User has direct access to all private endpoints from the VM. Setup is complete — do NOT proceed to Step 5.
5. End-to-End Test (VPN users only)
Three phases:
- Network — DNS resolution + port 443 reachability
- Agent Lifecycle — Create agent, thread, run, verify, cleanup
- Isolation Proof — Repeat with VPN off — expect 403
⚠️ Chromium browsers may bypass VPN DNS via Secure DNS (DoH). If portal shows "Error loading agents" but CLI works, disable Secure DNS.
Requirements
bash
pip install azure-ai-projects azure-identity azure-ai-agentsPhase 1: Network Validation
Resolve DNS and test port 443 for all private endpoints. Substitute actual resource names from the deployment.
PowerShell:
powershell
$endpoints = @(