What Microsoft announced
Apps in a virtual network can connect to the scheduler over a private connection, without exposing traffic to the public internet. Microsoft's Apps on Azure blog post of November 17, 2026 says the feature is GA for both the Consumption and Dedicated SKUs. Apps reach the scheduler through a private IP in their virtual network using Azure Private Link. Traffic stays on Microsoft's backbone. Operators can also turn off public network access so the scheduler only accepts connections through private endpoints. Applications keep the same scheduler endpoint and Microsoft Entra authentication.
The Azure Updates listing carries the "Launched" status, which Microsoft defines as fully released and production-ready. The public rendering of that listing did not expose the individual update text. The details here come from Microsoft's blog post and Learn documentation.
The announcement was one item in a larger DTS roundup. Microsoft also said that customer-managed keys are GA for Dedicated SKU schedulers. Native disaster recovery and task queues are in public preview, and the Durable Task Go SDK is in preview. This article covers only the private endpoint launch.
Why it matters
DTS is a managed backend for durable execution. Apps connect to it over gRPC secured with TLS and authenticated by the app's identity. The public endpoint looks like {scheduler-name}.{region}.durabletask.io. The scheduler runs as a separate Azure resource from your app. Until now, that meant orchestration traffic from a locked-down network used a public endpoint. Teams in regulated or tightly segmented environments often can't accept that, so private endpoints were likely a blocker.
The scheduler works with apps on Azure Functions, Container Apps, AKS, App Service and VMs. A private endpoint therefore matters beyond Functions users.
Key boundaries
Microsoft's documentation sets out several limits to plan around.
- Resource type and group ID: The private endpoint targets the scheduler subresource on the Microsoft.DurableTask/schedulers resource type. Use
scheduleras the group ID in the portal, CLI and Bicep. - Network path only: Private endpoints secure the network path to the scheduler. You still have to configure identity-based access and RBAC.
- Scheduler-wide scope: A private endpoint connection applies to all task hubs within that scheduler. You can't isolate individual task hubs with their own endpoints. Microsoft's guidance, as relayed in the evidence brief, is that task hubs in one scheduler are not a network security boundary between tenants. Use separate schedulers for that.
- No emulator support: The local emulator doesn't support private endpoints, and the feature applies only to schedulers deployed in Azure.
- Dashboard impact: After setting up a private endpoint, you can optionally disable public network access. Doing so also affects access to the DTS dashboard. Plan a private route for anyone who uses the dashboard, such as VPN, ExpressRoute or a jump host in the virtual network.
- Regions: The private endpoint must be in the same region as its virtual network. The scheduler itself can be in another region, though Microsoft recommends co-locating them for latency. This follows the general Private Link behavior, where the private-link resource can be deployed in a different region than the virtual network and private endpoint.
DNS is the usual failure point
DNS settings must resolve to the private IP address of the private endpoint. According to Microsoft's DTS documentation:
- If your virtual network uses default Azure DNS, a linked Azure Private DNS zone can handle resolution.
- If you use custom DNS, you must add a record for the scheduler endpoint that points to the private IP.
- A hosts-file entry on a VM is documented as a testing option only.
- Without correct DNS, clients can't resolve the endpoint to the private IP and the connection fails.
Rollout checklist
- Create the private endpoint for the scheduler resource, using
Microsoft.DurableTask/schedulersandscheduleras the target. In the CLI this isaz network private-endpoint create, with the scheduler's full resource ID and--group-id scheduler. - Confirm the connection is approved. Private Link only passes traffic from endpoints in an approved state.
- Configure private DNS, and test name resolution from every network where clients run: app subnets, on-premises networks and developer machines.
- Verify that apps can still authenticate and that their RBAC assignments are intact.
- Only then consider disabling public network access, once the dashboard access path is sorted out.
- For scenarios that need tenant-level separation, use separate schedulers rather than separate task hubs.
Analysis
This is a modest launch that fills a real gap, and most of the work is in the DNS and operations planning rather than the endpoint itself. The main surprises will be the dashboard going dark when public access is disabled, and the scheduler-wide scope. Neither is a flaw, but both can catch teams out if they assume per-task-hub controls. The announcement doesn't say anything about pricing for the private endpoints. Standard Private Link charges may apply, so check Azure's pricing before rollout.
References
- (Launched) Generally Available: Private endpoints for Azure Functions durable task scheduler Azure Updates · 2026-11-17T20:00:32Z
- What's new in Azure Functions durable task scheduler: Durable agents, disaster recovery, and more | Microsoft Community Hub techcommunity.microsoft.com
- Private endpoints for Durable Task Scheduler - Durable Task learn.microsoft.com