Blog Post

Apps on Azure Blog
9 MIN READ

Bulletproof agents with the durable task extension for Microsoft Agent Framework

greenie-msft's avatar
greenie-msft
Icon for Microsoft rankMicrosoft
Nov 13, 2025

What if your AI agents could survive crashes, execute across thousands of instances, wait weeks for human approval, and cost you nothing while idle, all automatically?

Today, we're thrilled to announce the public preview of the durable task extension for Microsoft Agent Framework. This extension transforms how you build production-ready, resilient and scalable AI a...
Updated Nov 14, 2025
Version 10.0
.net
azure functions
python
serverless
erik_oleary's avatar
erik_oleary
Copper Contributor
Nov 18, 2025

Can't wait to try it! But I'm not paying $600/month for a preview 🤣

  • greenie-msft's avatar
    greenie-msft
    Icon for Microsoft rankMicrosoft
    Nov 18, 2025

    erik_oleary​ - are you referring to the Durable Task Scheduler? If so, the Consumption SKU launched as public preview, which is a pay-for-what-you use model. https://aka.ms/dts-billing

    • erik_oleary's avatar
      erik_oleary
      Copper Contributor
      Nov 19, 2025

      Ahh, I see you can a consumption one with the AZ CLI or with Bicep. I created one, and I get errors on the dashboard "does not exist or this account has insufficient permissions to access it." even though I've assigned myself the "Durable Task Data Contributor Role" on every resource I can think of in there. Does it take a long time to propagate?

      • torosent's avatar
        torosent
        Icon for Microsoft rankMicrosoft
        Nov 19, 2025

        Hi erik_oleary​ ,

        I'm the engineering manager of Durable Functions and DTS.

        1. You need to assign yourself as a Durable Task Data Contributor to your Durable Task Scheduler resource if you are running locally. The connection string in the code should look like this "Endpoint=<Fqdn>;Authentication=DefaultAzure;TaskHub=<taskhub name>";
        2. The portal experience should light up today. 
        3. If you still have issues, please send me the fqdn of your scheduler to torosent at microsoft.com.