Skip to content

Private Endpoint Manual Setup

Sam Betts edited this page Nov 4, 2026 · 2 revisions

Private Endpoints → Private Endpoint Manual Setup

Manual Setup Guide

The following sections describe how to configure private endpoints manually, either as an alternative to the installer or to complete the steps the installer does not cover.

VNet Configuration

For these steps to work, we need a virtual network (VNet) pre-configured with x2 subnets - a default one and then one for app services.

All the dependencies will use the default subnet, and the app service will integrate with a second one.

Private endpoints are created on the VNet and add DNS zones for each resource as needed, so that each service has a private, internal IP address.

A private endpoint provides a private address and DNS mapping. Resolution is not connectivity or authorisation: test name resolution and HTTPS from every intended client. A failed ICMP ping does not establish that an Azure PaaS endpoint is unreachable.

For example, from a permitted machine test Test-NetConnection contosoanalytics.scm.azurewebsites.net -Port 443 (synthetic hostname), then confirm the required authenticated operation. A private DNS answer with no network path still fails; a network connection with no data-plane role still fails.

Your own infrastructure may have different requirements.

Important: if you have your own DNS infrastructure to integrate with, please add verification steps for each Azure service added below.

Configure Services for Private Access Only

In this guide, we assume that you have a working system created by either the installer or the manual configuration method.

Note: If you used the installer with VNet enabled, private endpoints and DNS zones for the services below (SQL, App Service, Storage, Key Vault, Service Bus, Cognitive Services and — if Graph usage reports are enabled — the Automation Account) are already created. To make those resources private-only, clear Allow public network access on Azure PaaS resources in the installer's Networking section and run it again, rather than disabling public access by hand: while that setting is ticked, every installer run, including upgrades, tries to re-enable public access. See Private endpoints → What you still need to do manually.

App Service

Add a private endpoint so access to it is restricted: in the App Service's Networking blade, add a private endpoint in your VNet. See What is a private endpoint?

Next, we need to integrate the app service into our VNet so the web-jobs can access private resources. Back in the networking blade click "VNet integration".

Note: When using the installer with VNet enabled, this outbound VNet integration is configured automatically against a dedicated app-integration subnet (delegated to Microsoft.Web/serverFarms). The WEBSITE_VNET_ROUTE_ALL and WEBSITE_DNS_SERVER app settings are also set automatically. The steps below only apply when configuring an existing environment manually.

VNet Integration Subnet Requirement

App Service VNet integration requires a dedicated subnet delegated to Microsoft.Web/serverFarms. You cannot use the same subnet that contains your private endpoints or VMs. The installer creates this subnet automatically (default name app-integration, default range 10.0.2.0/24). If you are configuring this manually, create one with:

az network vnet subnet create \
  --resource-group <your-rg> \
  --vnet-name <your-vnet> \
  --name app-integration \
  --address-prefixes 10.0.2.0/24 \
  --delegations Microsoft.Web/serverFarms

A /28 is the minimum size, but /24 is recommended. Once created, select this subnet when configuring VNet integration on the App Service.

Troubleshooting: If you disable public access on Service Bus (or other resources) and the App Service returns 401 - IP has been prevented to connect to the endpoint, this means the App Service is still routing traffic via its public IP. Verify:

  1. VNet integration is configured with the dedicated subnet above
  2. Route All is enabled (WEBSITE_VNET_ROUTE_ALL = 1)
  3. The privatelink.servicebus.windows.net (or relevant) private DNS zone is linked to the VNet used by the App Service integration

You can confirm DNS resolution from the App Service using Kudu console: nameresolvercli <namespace>.servicebus.windows.net — it should return the private IP (e.g. 10.0.0.x), not a public IP.

Now, any HTTP calls from outside the private network will not arrive at the app service.

SQL Server

Restrict public access and enable a private endpoint: in the SQL server's Networking blade, disable public network access and add a private endpoint for the sqlServer sub-resource in the same VNet. The endpoint gets a network interface with a private IP address; you can choose a specific address or let Azure assign one.

Keep the SQL connection's normal <server>.database.windows.net FQDN and make it resolve privately. Do not substitute a private IP or <server>.privatelink.database.windows.net; Azure SQL requires the normal FQDN.

Service Bus

Private endpoints and network isolation require a Premium tier service-bus.

Note: The installer creates new Service Bus namespaces at Premium tier when VNet is enabled. However, existing non-Premium namespaces cannot be upgraded in-place - Azure does not support this. The installer will log an error with a link to the migration documentation. You will need to create a new Premium namespace and migrate manually.

Teams calls import needs Service Bus on Premium in a private deployment

Service Bus is used by one thing: the Teams calls import. It's the queue (graphcalls) that call-record notifications land in.

Because a private endpoint requires Premium, a private deployment has only three valid combinations. If a Standard namespace has public network access disabled, it can be reached neither publicly nor privately, and the calls import fails at runtime with a message that looks like an authentication problem but isn't:

Put token failed. status-code: 401, status-description: Ip has been prevented to connect to the endpoint.
   ... Virtual Network service endpoints / IP Filters ...

That's a network-layer rejection — the connection is blocked before the token is even checked — so no amount of RBAC/permission fixing will help.

Option What to do Result
(a) Premium + private queue Migrate/recreate the namespace, create the endpoint/DNS and re-run setup The queue is private; calls still require a Graph-reachable public webhook
(b) Keep Service Bus public Use an approved public-namespace configuration with RBAC Calls work only if the webhook is also reachable; the namespace is not necessarily the only public resource
(c) Turn the feature off Untick Service Bus in the installer (ServiceBusEnabled) and disable the Teams calls import No Service Bus at all, no calls data

What the installer does about it: if you choose a private deployment while the Teams calls import is on, the installer shows a warning dialog before the install starts. If it then finds the existing namespace is not Premium, it deliberately leaves public network access enabled on that namespace (option b) rather than disabling it and leaving the queue unreachable, logs a prominent warning, and repeats it in the install summary with a suggested next step. It also skips creating the Service Bus private endpoint and its privatelink.servicebus.windows.net DNS zone, since a VNet-linked zone with no endpoint behind it would break resolution of the public endpoint too.

The web portal's Administration → Service health page also flags this: if the Teams calls queue can't be read and the error looks like an IP/VNet block, the Service Bus component shows a warning that names the Premium requirement.

Do not assume a non-Premium namespace becomes Premium simply by re-running the installer. Plan a supported Standard-to-Premium migration, or recreate the required queue/configuration on Premium as appropriate. Confirm endpoint resolution and data-plane access before disabling public access. A deployment with every endpoint private cannot receive Graph notifications.

Storage Account

For storage, we need to configure private endpoints for table + blob services.

Note: The installer creates private endpoints for both blob and table storage when VNet support is enabled. The table endpoint carries AnalyticsState, including import checkpoints and Teams delegated tokens.

Create two endpoint sub-resources, blob and table, with the corresponding privatelink.blob.core.windows.net and privatelink.table.core.windows.net zones linked to the integration/client VNet. A blob endpoint alone cannot carry AnalyticsState or Table checkpoints. Verify both services with their documented identities; a firewall rejection can resemble a permissions failure.

Key Vault

The installer creates a private endpoint for Key Vault automatically. To disable public access, go to the Key Vault networking blade and set "Allow access from" to "Private endpoint only".

Note: If public access is disabled before the installer finishes adding secrets, the installer will log an error (HTTP 403) and continue. You can add secrets manually afterwards from within the VNet.

Optional: Language Service

Language service is optionally used for Teams channel sentiment analysis and other areas of Microsoft 365. If your configuration doesn't include this, you don't need to follow this step.

In the Language resource's Networking, create/approve its private endpoint and private DNS link before disabling public access. Verify name resolution and TCP/TLS reachability from the App Service's integrated VNet. See Azure AI virtual networks.

Disable public access and save changes.

Use the account sub-resource and its supported Cognitive Services private DNS zone. Keep the configured service endpoint; test private resolution and the actual enrichment call. A CNAME is not an inference-role grant.

Optional: prompt-categorisation backend

The opted-in installer service creates an OpenAI account endpoint and optional privatelink.openai.azure.com zone. Test the configured resource origin from the importer and grant Cognitive Services OpenAI User to its runtime client-secret identity. Provisioning/network access does not enable the separate durable processing opt-in.

Bring-your-own deployments need equivalent approved routing/DNS. A private endpoint or hostname does not prove the model's regional/data-zone processing boundary; verify the actual deployment type and governance terms.

Application Insights

Note: Application Insights private link scope is not configured by the installer and must be set up manually.

Access to App Insights ingestion and tracking is limited via "Azure Monitor Private Link Scopes" on the "Network Isolation" blade.

Create the Azure Monitor Private Link Scope, add both the Application Insights component and its workspace, then create/link the required private endpoint/DNS. Review Microsoft's Azure Monitor Private Link guidance.

With public ingestion/query access disabled, SharePoint client browsers must also have approved private connectivity to send web tracking—not just the importer. Network-denied ingestion can report HTTP 403 with publicNetworkAccessForIngestion=Disabled; a SQL or Entra role change does not fix that path.

Log Analytics

Configure the workspace in the same way as Application Insights.

Important: if you don't configure log analytics with the same Azure Monitor Private Link Scope, no telemetry data will be readable.

Configure App Services

Once components have been configured, the app service configuration will need to be updated.

Note: If you used the installer with VNet enabled, the app settings WEBSITE_VNET_ROUTE_ALL and WEBSITE_DNS_SERVER are already configured. The connection strings (SQL, Storage, Service Bus) use the standard public DNS names which automatically resolve to private IPs via the private DNS zones. No manual connection string changes are needed in that case.

Disable Call Imports

Microsoft Graph call-record webhooks require a publicly reachable App Service endpoint. In an all-private deployment, disable call imports so the solution does not repeatedly try to register an unreachable webhook.

For installer-managed configuration, clear Call and meeting logs in Workloads before reviewing the deployment:

Released installer Workloads section with Call and meeting logs unchecked in a fictional configuration

Illustrative synthetic design preview only; the unchecked control does not prove that a deployed app setting changed or webhook registration stopped.

Set Calls=False in ImportJobSettings, preserving the other flags. This disables webhook/call collection, not the separate Teams usage-report import:

Edit App Service → Settings → Environment variables → ImportJobSettings, preserving every other key/value in the semicolon-separated setting. Applying it restarts the app; plan the change accordingly. See App Service app settings.

Save changes.

App Service Settings for VNet DNS Resolution

When using private endpoints, the app service must route outbound traffic through the VNet so that private DNS zones resolve correctly. The installer sets these automatically, but if configuring manually, add the following app settings:

Setting Value Purpose
WEBSITE_VNET_ROUTE_ALL 1 Routes all outbound traffic through the VNet (not just RFC1918)
WEBSITE_DNS_SERVER 168.63.129.16 Uses Azure-provided DNS which resolves private DNS zones

These settings require the app service to have outbound VNet integration configured (see App Service above).

Change SQL Connection

Note: If the installer created the environment with VNet enabled, the SQL connection string already uses the standard FQDN (e.g., myserver.database.windows.net) which resolves to the private IP via the privatelink.database.windows.net DNS zone. No manual change is needed — skip to the next section.

The following applies only when converting an existing (non-VNet) deployment to use private endpoints. Once you disable public network access on the SQL server, the web-jobs will crash with this error:

SqlException: Reason: An instance-specific error occurred while establishing a connection to SQL Server. Connection was denied since Deny Public Network Access is set to Yes. To connect to this server, use the Private Endpoint from inside your virtual network.

Do not change the server to its private-link FQDN or IP. Keep, for example, contosoanalytics.database.windows.net (synthetic), and fix VNet integration, DNS links/resolution and routing. Validate from the App Service and the installer machine, not only a separate VM.

Then verify both WebJobs complete enabled imports without connection errors. Running alone does not prove SQL writes or a complete cycle.

Service Bus

Equally the service-bus DNS should still work for the same reasons.

Power BI Service (Optional)

The Power BI service will need to access the private endpoint for SQL if you're using PBI reports - https://learn.microsoft.com/en-us/power-bi/enterprise/service-security-private-links


Return to Private Endpoints · All topics in this guide

Start here

Copilot analytics

Using the portal

Install & configure

Beyond Copilot

Operate

Upgrading from an older build

Reference

Project

Clone this wiki locally