Durable Task Scheduler Not Available in West Europe Region

[benjamin-bezzi]

Hello

All of my infrastructure and resources are currently deployed in the West Europe region. I'm interested in using the Durable Task Scheduler for my orchestration needs, as it offers a managed, fault-tolerant backend for Durable Functions.

However, I’ve noticed that the Durable Task Scheduler is not yet available in the West Europe region. This presents a challenge for me, as deploying resources in other regions would introduce latency and complicate our architecture.

Could you please clarify:

Is there a timeline for when the Durable Task Scheduler will be available in West Europe?
Are there recommended alternatives or best practices for using Durable Functions in West Europe in the meantime?
Would it be advisable to wait for regional availability, or is cross-region deployment a viable interim solution?
We appreciate any guidance or updates you can provide.

Thank you!

[greenie-msft]

Hi @benjamin-bezzi,

Thanks for your question. We're actively working on expanding to West Europe, however, I do not have an ETA on when that will be enabled.

For the time being, I suggest you evaluate your performance in North Europe as that is listed as a paired region: https://learn.microsoft.com/en-us/azure/reliability/regions-list

I'll keep this issue open to serve as a reminder to follow up with you as soon as DTS is available in West Europe.

Please let me know if you have any other questions that I can help answer.

[benjamin-bezzi]

Thank you for the update!
If we start using the service in North Europe, will it be possible to move it to West Europe once that region becomes available? Would appreciate any guidance on migration or redeployment options.
Thanks again!

[lilyjma]

Hi @benjamin-bezzi, if you start in one region now and move to another later, you'll need to create a new scheduler in the new region and configure your app to use that scheduler (should just be a change in the connection info and setting up managed identity). One thing to keep in mind is that the orchestration state data will not carry over, so you'll need to either make sure all the inflight orchestrations are completed before migrating, or you're able to reschedule those orchestrations afterwards.

@torosent / @cgillum - anything you'd add?