Skip to content

Configure network access

Configure the network path for the access model selected during deployment.

The Your deployment is ready notification provides the public and private endpoints available for the deployment.

If public access is enabled

Public endpoints are available over HTTPS.

Confirm that:

  • the required client networks are allowed to reach the public endpoints;
  • outbound HTTPS on TCP port 443 is permitted;
  • any organization firewall, proxy, or access restrictions allow the required service hostnames.

Do not configure DNS on this page. DNS is handled in the next step.

Continue to configure public DNS.

If private access is required

Create an Azure Private Endpoint that connects your customer network to the platform's Private Link Service.

You need:

  • the Private Link Service resource ID provided for the deployment;
  • an Azure VNet and subnet where the Private Endpoint will be created;
  • network connectivity from the required client networks to that subnet.

Follow Create a Private Endpoint.

After the Private Endpoint is approved and reachable, continue to configure private DNS.

Verify the network path

Before moving to DNS configuration, confirm that the required network path exists.

For public access, confirm that TCP port 443 can reach the public endpoint.

For private access, confirm that:

  • the Private Endpoint is created;
  • the connection is approved;
  • the endpoint has a private IP address;
  • required client networks can route to the endpoint.

DNS and TLS validation are completed in the following steps.

Next step

Continue to Configure DNS for the endpoints you plan to use.