Chapter 1 of 6
Session scope#
What we will do#
Objective. Connect the existing Foundry account and its Storage, Azure AI Search, Cosmos DB, and Key Vault dependencies through private endpoints. Deploy seven private DNS zones and links plus five private endpoints against the approved network foundation.
From the approved nonproduction execution host, check that three Foundry endpoint families and four dependency FQDNs resolve to RFC 1918 addresses and accept TCP 443. Record all five prior public-access settings in the approved change system, disable public access, and run the check again.
Why it matters#
Problem. Disabling public access before the private path works risks locking the team out with no way back in.
Solution. This session proves the private path first. It deploys the endpoints and DNS, checks resolution and TCP 443, records every prior public-access state, and only then disables public access.
Boundaries#
The approved network foundation contains the VNet, route table, delegated Agent Service subnet, and private-endpoint subnet. Keep them unchanged. This session owns the private endpoints, DNS configuration, and guarded public-access cutover in the approved nonproduction resource group.
Azure holds live network and service state. The customer firewall source holds egress rules. The approved change system holds cutover and restore details.
These files implement the customer-managed BYO VNet path; Microsoft-managed networking needs a separate delivery path.
The connectivity check covers the approved client path, not agent-runtime traffic. Governed agent baseline guide runs that check.
Session preparation
Who should join
- Cloud and network platform engineers
- AI platform engineers
- DNS, firewall, and security reviewers
What you need
- The approved nonproduction VNet, route table, delegated Agent Service subnet, and private-endpoint subnet exist in the recorded scope. The landing-zone owner checks their resource IDs and the approved execution host reaches the VNet. (Session 01.)
- The approved network design names the DNS pattern, customer firewall source, and execution host inside the private network.
- When a corporate or on-premises identity provider authenticates users, the approved design names its application or API Management boundary and keeps agent and Azure service authentication on Microsoft Entra workload identity.
- The network deployment operator has time-bound Network Contributor on the exact nonproduction resource group used for this session.
- The DNS operator has time-bound Private DNS Zone Contributor on the resource group that holds the seven zones, or on every reused zone.
- Preflight has the two operator object IDs and every exact DNS role-assignment scope.
- The Foundry, Storage, Azure AI Search, Cosmos DB, and Key Vault owners will approve private endpoint connections through the service change process.
- The approved change record names the cutover owner, restore owner, and location for the five prior public-access states.