A blue infographic depicts a secure cloud workflow with scheduled processing, encryption keys, protected storage, and backups.
Microsoft has made customer-managed keys (CMK) for the Azure Functions Durable Task Scheduler (DTS) generally available. The Azure Updates entry carries a November 17, 2026 timestamp, and the Apps on Azure engineering blog posted the same day. The Dedicated SKU is where the feature is production-ready. If you run workflow state on the Consumption SKU, this launch does not change anything for you.

A blue infographic depicts a secure cloud workflow with scheduled processing, encryption keys, protected storage, and backups. What shipped​

Microsoft says CMK is now GA for Dedicated SKU schedulers. Durable Task Scheduler uses managed identity for authentication, which is a separate concern from the encryption key. Microsoft's own framing of the CMK benefits is that customers can use a key they own in Azure Key Vault or Azure Managed HSM to encrypt scheduler data. The Microsoft Apps on Azure blog lists these benefits: separation of duties, centralized auditing of key access, and customer-defined key rotation policies. These are Microsoft's stated benefits. The company has not published compliance or operational outcome numbers.

The Ignite 2026 roundup gives the scope more precisely:

  • What is encrypted: task hub orchestration history, entity state, and payloads at rest.
  • Where: the Dedicated SKU only.
  • Key sources: Azure Key Vault or Azure Managed HSM.
  • Access mechanism: a user-assigned managed identity.
  • Setup routes: the ARM REST API, Azure CLI using az rest, or Bicep.

This covers DTS scheduler data. It does not cover every other resource in your Functions app, and it does not cover the rest of your application's data.

Why it matters​

DTS is a managed durable-execution backend. It stores the progress of long-running orchestrations so that work can resume after failures. That history can contain business data, such as approval payloads, order details, and agent conversation state. Microsoft's Learn documentation says the scheduler uses managed identity for authentication. Regulated organizations often need to control the encryption key for persisted data themselves, and CMK gives them that.

In practice the feature serves a few common needs:

  • Key custody: your security team owns the key and its lifecycle.
  • Revocation: you can cut off scheduler access to the key.
  • Audit: key access is logged centrally in the key service.

CMK is a control over encryption at rest. It does not replace:

  • RBAC on the scheduler and task hubs
  • Private endpoints or network restrictions
  • Careful handling of sensitive data inside orchestration inputs

Microsoft also warns that task hubs on a single scheduler share resources. Enabling CMK therefore does not turn task hubs into a tenant isolation boundary.

Setup and operational notes​

Microsoft's Learn page for DTS customer-managed keys exists. The copy I found was a Polish-language version still labelled as preview, so details may differ from the English GA page. It gives these practical points:

  • DTS encrypts data at rest by default. CMK is a choice to use your own key instead of the default.
  • The scheduler needs permission to read and use the key for encryption operations. You should grant it only the minimum permissions the key store requires.
  • With auto-rotation enabled (autoRotationEnabled set to true), the scheduler automatically uses the latest supported version of the configured key when a new version appears.
  • When auto-rotation is on, the page recommends a versionless key URI, such as https://<vault-name>.vault.azure.net/keys/<key-name>. That way the scheduler configuration does not pin a specific key version.
  • If the configuration status shows Failed, restore access to the key and run the configure command again.

That last point is the main operational risk. A key that is disabled, deleted, or inaccessible can break the scheduler's access to its own data. Comparable services work the same way. For example, AWS says that removing decrypt permissions or disabling the key stops Lambda from accessing previously checkpointed state for its durable functions. I have not seen Microsoft document the exact failure behavior for DTS, so test it before you rely on it. Use soft-delete and purge protection on Key Vault, and keep key lifecycle changes under change control.

Checklist for administrators​

  1. Confirm the scheduler is on the Dedicated SKU.
  2. Decide between Key Vault and Managed HSM according to your compliance requirements.
  3. Create a user-assigned managed identity for key access and grant it only the key permissions it needs. Keep it separate from the application identity that holds the Durable Task Data Contributor role.
  4. Choose an automation route: ARM REST, az rest, or Bicep.
  5. Decide on rotation: versionless key URI with auto-rotation, or manual rotation.
  6. Rehearse key-disable and recovery scenarios in non-production before enabling CMK on production schedulers.
  7. Turn on diagnostic logging for key access so your audit trail works.

What remains unverified​

The Microsoft posts do not say whether an existing scheduler can be switched to CMK in place. They also do not give regional rollout details, supported key types, or the exact behavior if a key becomes unavailable. Check the current Learn guide for the exact request schema and role names before changing production resources.

The bigger picture​

The same announcement bundle includes private endpoints, which Microsoft says are GA on both Consumption and Dedicated SKUs. It also includes preview features: native disaster recovery, task queues, and a Go SDK. Together these point to DTS being positioned as an enterprise backend for workflows and AI agents. Teams that were holding off on DTS because of key-ownership requirements now have a supported route on the Dedicated SKU. Teams on Consumption will need to move to Dedicated, or wait, if CMK is a hard requirement.

 

References

  1. (Launched) Generally Available: Customer-managed keys for Azure Functions durable task scheduler Azure Updates 2026-11-17T20:00:32Z
  2. What's new in Azure Functions durable task scheduler: Durable agents, disaster recovery, and more | Microsoft Community Hub techcommunity.microsoft.com
  3. What's new in Azure Functions and Durable Task Scheduler at Microsoft Ignite 2026 techcommunity.microsoft.com