A glowing infographic shows secure database data flowing through code to distributed cloud computing nodes.
Microsoft has added Private Link private endpoint support to Azure HorizonDB, its managed PostgreSQL-compatible database service. The update's title is muddled. Its headline reads "[In preview] Generally Available," but the feature is still in preview. Treat it as a preview capability and don't build production assumptions on the "Generally Available" wording.

A glowing infographic shows secure database data flowing through code to distributed cloud computing nodes. What changed​

Azure HorizonDB clusters can now be reached through Azure Private Link. Clients connect to a private IP address from a virtual network. HorizonDB was first announced at Ignite as a private preview in Central US, West US3, UK South and Australia East. Microsoft said at the time that it had native support for Entra ID, Private Endpoints and data encryption. This week's update fills in the documentation and the operational model.

The announcement lists the supported client locations:

  • Azure virtual networks.
  • Peered networks.
  • On-premises environments connected through VPN or Azure ExpressRoute.

Private DNS integration is available. Public access can also be disabled so database traffic stays off the public internet.

How private endpoints work for HorizonDB​

According to Microsoft Learn, traffic between clients and the cluster travels over the Microsoft backbone rather than the public internet. The details below matter more than the headline.

One endpoint targets one cluster endpoint. A private endpoint reaches a single cluster, not the whole HorizonDB service. It also reaches only one endpoint within that cluster:

TargetGroup ID
Read-write endpointThe cluster's name
Read-only endpointThe pool's name, such as defaultpool

If clients need private access to both endpoints, create two private endpoints.

A pool must be active. Clusters created in the Azure portal get a defaultpool automatically. Without a pool, a connection can only be created with manual approval and stays Pending. Approving it fails with the error code PrivateEndpointRequiresPool.

Creating an endpoint does not disable public access. While public access is on, clients can still connect through the public endpoint from IP addresses the firewall rules allow. To require private endpoints, set the cluster's properties.network.publicAccess property to Disabled. This is a separate step, and it is the one most likely to be forgotten.

Location limits are loose. The cluster and the private endpoint can be in different regions, subscriptions or Microsoft Entra tenants. The private endpoint must be in the same region and subscription as its virtual network. Microsoft says private endpoints are available in every region where HorizonDB is available.

Prerequisites and permissions​

You need:

  • A deployed cluster with an active pool.
  • A virtual network and a subnet.
  • Permission to create the endpoint (Microsoft.Network/privateEndpoints/write) and to join the subnet (Microsoft.Network/virtualNetworks/subnets/join/action). Built-in roles such as Network Contributor include both.
  • For automatic approval, the Microsoft.HorizonDb/clusters/privateEndpointConnectionsApproval/action permission on the cluster. Otherwise someone with privateEndpointConnections/write on the cluster must approve the connection.
  • For Azure private DNS zones, permission to create and link the zone: Microsoft.Network/privateDnsZones/write, privateDnsZones/virtualNetworkLinks/write and Microsoft.Network/virtualNetworks/join/action.

Creating a private endpoint in the Azure portal​

  1. Open the HorizonDB cluster.
  2. Under Settings, select Networking.
  3. Open the Private endpoints tab and select Create private endpoint.
  4. On Basics, choose the subscription and resource group, name the endpoint and its network interface, and pick a region that matches your virtual network.
  5. On Resource, confirm the cluster and choose the target sub-resource. Use the cluster name for read-write or the pool name for read-only.
  6. On Virtual Network, choose the network and subnet, and pick dynamic or static private IP allocation.
  7. On DNS, choose whether to integrate a private DNS zone. If you do, verify that the zone is privatelink.horizondb.azure.com.
  8. Select Review + create, then Create.
  9. When deployment finishes, return to the cluster's Networking page and check the connection state.

Repeat the steps for the other endpoint if you need it. For automation, Microsoft documents ARM templates, Bicep, Terraform, REST APIs, SDKs and the Azure CLI. The CLI route uses az horizondb private-link-resource list to find the group ID, then az network private-endpoint create. If you don't use the portal, you must set up DNS yourself.

DNS is where this usually breaks​

Always connect by fully qualified domain name, never by IP address. The same names work for public and private access. In public DNS, each name is an alias for a name in the privatelink.horizondb.azure.com zone. Private DNS must map each name to the private IP of the matching endpoint.

The formats Microsoft documents are:

  • Read-write: <cluster>.rw.<cluster_id>.<region>.horizondb.azure.com
  • Read-only: <pool>.<cluster>.ro.<cluster_id>.<region>.horizondb.azure.com

Some DNS pitfalls to avoid:

  • Link the private DNS zone to every virtual network that hosts clients.
  • Don't attach two private endpoints for the same endpoint to one zone if their client networks can't reach each other. The second endpoint overwrites the first one's A record, and some clients then resolve an address they can't reach. Use separate zones, or route those clients to a single endpoint.
  • Custom DNS servers and on-premises clients need DNS forwarding to resolve the private zone.
  • If you created the endpoint outside the portal, Microsoft's documented fix is a short CLI sequence. Create the zone, link it to each client network, then add a DNS zone group to each private endpoint. Azure then manages the A records.

Approving, rejecting and deleting connections​

If you hold the approval permission when you create the endpoint, the connection is approved automatically. Otherwise it stays Pending. The CLI offers az horizondb private-endpoint-connection approve and reject, and both require a description.

Deletion has some traps:

  • Deleting a connection does not delete the private endpoint resource. The connection state becomes Disconnected, and that endpoint can't reconnect. Delete the endpoint and create a new one.
  • Deleting a private endpoint resource also removes its connection from the cluster.
  • Deleting the pool disconnects every private endpoint connection on the cluster. After a new pool exists, delete the disconnected endpoints, recreate them and redo the DNS setup. If the new pool has a different name, point read-only clients at the new pool's FQDN.

Troubleshooting checklist​

If a client can't connect, work through these checks in order:

  1. Connection state. It should be Approved. Rejected connections can be approved by someone with permission. Disconnected ones must be recreated.
  2. Group ID. If a client reaches one endpoint but not the other, you probably created an endpoint for only one.
  3. Pool. A 409 with PrivateEndpointRequiresPool means the cluster has no deployed pool.
  4. Private IP. Check that the endpoint's network interface has the address you expect.
  5. DNS. From the client network, run nslookup on the FQDN. It should return the private IP of the matching endpoint. A public IP means the client network isn't using the private zone, or the zone lacks the A record.
  6. Routing. Look for route tables or network virtual appliances that redirect or block traffic to the endpoint's subnet.
  7. Network security groups. NSG rules and user-defined routes apply to private endpoints only if network policies are enabled on the subnet.

What this does and doesn't buy you​

Private Link narrows the network path. It doesn't replace authentication. Microsoft's public-access guidance says connections still need valid credentials and that encryption is enforced. It also says access to databases and tables is governed by PostgreSQL roles. Microsoft also notes that because an endpoint reaches only one cluster endpoint, it reduces data-exfiltration risk.

A reasonable rollout looks like this:

  • Create the read-write and read-only endpoints as needed.
  • Verify DNS from every client network.
  • Test connections.
  • Only then disable public access.

Flipping the public switch first is a fast way to produce an outage.

Because the service and its networking docs are labeled preview, plan around preview terms. That means no production commitments until Microsoft moves the service to general availability.

 

References

  1. (In preview) Generally Available: Private endpoint support for Azure HorizonDB clusters Azure Updates 2026-11-17T20:56:06Z
  2. Networking with Private Endpoints in Azure HorizonDB - Azure HorizonDB | Microsoft Learn learn.microsoft.com
  3. Networking Overview with Public Access (Allowed IP Addresses) in Azure HorizonDB - Azure HorizonDB | Microsoft Learn learn.microsoft.com