Retirement announcement – Language Understanding (LUIS) will be retired on 1 October 2025

YutongTie-MSFT 44,966 Reputation points
2022-09-30T18:52:48.237+00:00

On 1 October 2025, Language Understanding (LUIS) will be retired. Starting 1 April 2023, you will not be able to create new LUIS resources. All your existing LUIS resources and applications will continue to be fully supported until the retirement date. You can migrate your LUIS applications to the next generation service conversational language understanding, a capability of Azure Cognitive Services for Language.

Azure Machine Learning
Azure Machine Learning
An Azure machine learning service for building and deploying models.
2,508 questions
{count} votes

12 answers

Sort by: Most helpful
  1. sebastian-iaodew 16 Reputation points
    2022-10-04T08:39:23.227+00:00

    We're very sad to hear that LUIS will be retired and new resources won't be able to be created this early, giving us just 6 months of refactoring a core feature of our product.

    We've been playing around with CLU before and were always missing one crucial feature: nested ML entities.

    Our use case are utterances like "I'd like to have the sushi twice with nagiri and 2 maki, as well as a pizza tuna" where with LUIS we were able to get a structure like

    product 1: (amount: 2, name: sushi, including: [ (name: nagiri), (amount: 2, name: maki)] )
    product 2: (name: pizza tuna)

    Is there any recommended way of migrating such complex entities to CLU where we have 4 levels of nesting in the ML entity? We always failed to achieve similar results as we currently do with LUIS after migrating for testing purposes.

    We'd be happy to know if nesting is still on the roadmap so CLU won't be missing features LUIS provided for many years.

    Thanks in advance and kind regards,
    Sebastian

    2 people found this answer helpful.

  2. Yury Aslamov 11 Reputation points
    2022-10-04T09:10:41.91+00:00

    It is very frustrating that in the future development we will not be able to use LUIS...
    LUIS is used in our current project and we were completely satisfied with its functionality. Moreover, one of the reasons why we switched to LUIS is nested entities.

    It is unfortunate that little time is given for migration. But it is especially unpleasant that the CLU does not support the LUIS nested entities that we need so much!
    Therefore, we will have to not only migrate to a new Azure service, but do it without a guarantee of a good result!

    It would be nice to know if there is a roadmap that can be used to painlessly migration from nested entities to regular ones?
    Will it be possible, for example, to purchase and download the current LUIS model for local deployment so that it is not affected by future changes?

    Thanks and best regards,
    Yury

    2 people found this answer helpful.

  3. Felipe Santos 5 Reputation points
    2023-02-07T18:50:29.49+00:00

    Hi all,

    I was reading the comments here and I figured out that Sebastian and Yury already asked about what I was looking for: nested ML entities. Any news regarding that topic? I have been working with LUIS for a long time, and these days I have started to learn more about CLU and the first thing I missed was the nested entities. Overall, I feel that this new language portal has been more confusing to work with than LUIS

    1 person found this answer helpful.

  4. YutongTie-MSFT 44,966 Reputation points
    2022-09-30T18:53:40.483+00:00

    To migrate your LUIS applications to conversational language understanding, please follow the steps outlined in this guide. Please use comments on this thread to ask your specific queries and will try our best to answer them. Thank you!

    0 comments No comments

  5. Jhardy 1 Reputation point
    2022-10-18T11:06:02.12+00:00

    As Custom Commands uses LUIS, will this be migrated over aswell?