Share via

Azure Orchestration Workflow Expiry Date

Yin, Sue 40 Reputation points
2025-12-24T03:21:20.76+00:00

For Orchestration Workflow in Language Studio, the supported training config version is 2022-09-01 from Model Lifecycle article. And this is the only training config version I can select to train orchestration workflow in language studio, I can only select 2022-05-01 which is set as latest one.

User's image

With this training version, the expiry date of model will be 2026-04-30. Do we have any plan to release a new training config version? Or does it mean my orchestration model will be expired directly after 2026-04-30? How we should handle this?

Appreciate your suggestions, thank you.

Azure Language in Foundry Tools
Azure Language in Foundry Tools
An Azure service that provides natural language capabilities including sentiment analysis, entity extraction, and automated question answering.
{count} votes

Answer accepted by question author
  1. Anshika Varshney 7,785 Reputation points Microsoft External Staff Moderator
    2025-12-24T05:02:47.9533333+00:00

    Hi Yin, Sue,

    Thanks for bringing this up. This behavior is expected and is related to the Azure AI Language Service model lifecycle, not an issue with your orchestration workflow itself.

    The expiry date shown in Language Studio corresponds to the training configuration version used by your orchestration workflow (for example, 2022-09-01). Each training configuration has a defined lifecycle that includes a training expiration date and a deployment expiration date.

    Once the training configuration expires, you will no longer be able to train or retrain models using that configuration version. However, any model that was already trained and deployed can continue running until the deployment expiration date.

    When the deployment expiration date is reached, the deployed orchestration workflow will stop serving predictions unless you retrain the model using a newer supported configuration and redeploy it.

    To avoid disruption, it’s recommended to monitor new training configuration versions, retrain your orchestration workflow with the latest supported version before expiration, and then redeploy it. This will refresh the lifecycle dates and keep your workflow operational.

    In short: the workflow isn’t being removed automatically the expiry simply indicates when you’ll need to update and redeploy using a newer model configuration to continue using the service.

    Hope this helps clarify things! Please let me know if there are any remaining questions or additional details, I can help with, I’ll be glad to provide further clarification or guidance.

    Thankyou!

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.