Special platform address (WireServer) through which Azure delivers the VM agent channel, built-in DNS, DHCP and load balancer health probes. Traffic to it must stay open, or those platform functions stop working.
Also called WireServer.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains 168.63.129.16 in context, with comparison tables and the common traps.
Terms in this definition
- Agent
A specialised form of Microsoft Copilot set up for one particular job, pairing instructions with knowledge and skills. You can create one in Copilot Studio, SharePoint or Agent Builder, and administrators control them from the Microsoft 365 admin center.
- DNS
The system that turns names into addresses. In Azure, private endpoints depend on private DNS zones, which are queried through 168.63.129.16.
- DHCP
Azure delivers each NIC's private IP to the guest operating system using this protocol, so keep the OS set to obtain addresses automatically and configure any static IP on the Azure NIC.
- ELT
Extract, load, transform: raw data lands in the target system first and is transformed there. See ETL for the opposite order.
- Stop sequence
One of up to four strings that make the model halt generation; the sequence itself is not included in the output.
Related terms
- Azure-provided DNS
Default resolver for a VNet, at 168.63.129.16, which answers with records from private DNS zones linked to that VNet; a custom DNS server has to forward queries to it to resolve those records.
- AzureLoadBalancer (service tag)
Service tag standing for 168.63.129.16, which Azure's infrastructure load balancer uses as the source of its health probes; rules using it match probe traffic, never client requests.
- DNS forwarding ruleset
Up to 1,000 rules sending named domains to target IPs, bound to an outbound endpoint of a DNS Private Resolver and linked to same-region VNets, which needn't peer with the resolver's VNet. 168.63.129.16 can't be a target.
- Private DNS zone
A zone in Azure DNS for private records (A records, for example), linked to VNets. Because only 168.63.129.16 resolves it, clients on-premises must go through a DNS forwarder or Azure DNS Private Resolver.