Add GSA proxy bicep templates for private network agent setup#527
Draft
shyamshd wants to merge 4 commits intomicrosoft-foundry:mainfrom
Draft
Add GSA proxy bicep templates for private network agent setup#527shyamshd wants to merge 4 commits intomicrosoft-foundry:mainfrom
shyamshd wants to merge 4 commits intomicrosoft-foundry:mainfrom
Conversation
shyamshd
force-pushed
the
add_gsa_bicep_templates
branch
from
afe6b09 to
e009176
Compare
Add bicep modules to deploy a GSA AI Connector proxy VM with a BYO VNet, enabling egress traffic inspection and authentication for standard AI Foundry agent deployments. New files: main.bicep: Orchestrator template for full end-to-end deployment including VNet, GSA proxy, AI account, project, and capability host main.bicepparam / test-deploy.parameters.json: Parameter files with defaults modules/vnet.bicep: Creates VNet with agent subnet (delegated to Microsoft.App/environments) and GSA proxy subnet modules/gsa-proxy.bicep: Core module deploying: - GSA proxy subnet with NSG (allows VirtualNetwork traffic) - VM from GSA AI Connector marketplace image with managed identity - NIC with IP forwarding enabled - UDR routing 0/0 from agent subnet to proxy, with exceptions for AzureActiveDirectory, AzureResourceManager, AzureMonitor, GuestAndHybridManagement, AzureContainerRegistry, AzureKeyVault, and Storage service tags modules/agent-subnet-udr-association.bicep: Associates the UDR with the agent subnet while preserving existing delegation and NSG configuration modules/standard-dependent-resources.bicep: Creates Cosmos DB, AI Search, and Storage with cosmosDBZoneRedundant parameter for regions with AZ capacity constraints
shyamshd
force-pushed
the
add_gsa_bicep_templates
branch
from
e009176 to
594bb22
Compare
- Remove account-level capability host from add-project-capability-host.bicep (platform auto-creates it; having both causes 'conflicting state' error) - Rename default aiServices param from 'foundy' to 'foundry' across all files - Remove accountCapHost param from main.bicep - Successfully deployed and verified all 15 resources in rg-ai-agent-gsa-proxy-2
- Added AllowAzureFrontDoorFirstParty route to agent subnet UDR - Routes Azure Front Door first-party traffic directly to Internet instead of through the GSA proxy - Updated README with the new service tag
- Added AllowContainerAppsManagement route to agent subnet UDR - Routes Container Apps management plane traffic directly to Internet instead of through the GSA proxy - Also previously added AzureFrontDoor.FirstParty bypass - Updated README with both new service tags
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add bicep modules to deploy a GSA AI Connector proxy VM into the existing agent VNet, enabling egress traffic inspection and authentication for network-secured AI Foundry agent deployments.
New files: