Language Understanding (LUIS) container limitations
Important
LUIS will be retired on October 1st 2025 and starting April 1st 2023 you will not be able to create new LUIS resources. We recommend migrating your LUIS applications to conversational language understanding to benefit from continued product support and multilingual capabilities.
The LUIS containers have a few notable limitations. From unsupported dependencies, to a subset of languages supported, this article details these restrictions.
The latest LUIS container supports:
- New prebuilt domains: these enterprise-focused domains include entities, example utterances, and patterns. Extend these domains for your own use.
To export for container, you must remove unsupported dependencies from your LUIS app. When you attempt to export for container, the LUIS portal reports these unsupported features that you need to remove.
You can use a LUIS application if it doesn't include any of the following dependencies:
Unsupported app configurations | Details |
---|---|
Unsupported container cultures | The Dutch (nl-NL ), Japanese (ja-JP ) and German (de-DE ) languages are only supported with the 1.0.2 tokenizer. |
Unsupported entities for all cultures | KeyPhrase prebuilt entity for all cultures |
Unsupported entities for English (en-US ) culture |
GeographyV2 prebuilt entities |
Speech priming | External dependencies are not supported in the container. |
Sentiment analysis | External dependencies are not supported in the container. |
Bing spell check | External dependencies are not supported in the container. |
LUIS containers support a subset of the languages supported by LUIS proper. The LUIS containers are capable of understanding utterances in the following languages:
Language | Locale | Prebuilt domain | Prebuilt entity | Phrase list recommendations | **Sentiment analysis and key phrase extraction |
---|---|---|---|---|---|
English (United States) | en-US |
✔️ | ✔️ | ✔️ | ✔️ |
Arabic (preview - modern standard Arabic) | ar-AR |
❌ | ❌ | ❌ | ❌ |
*Chinese | zh-CN |
✔️ | ✔️ | ✔️ | ❌ |
French (France) | fr-FR |
✔️ | ✔️ | ✔️ | ✔️ |
French (Canada) | fr-CA |
❌ | ❌ | ❌ | ✔️ |
German | de-DE |
✔️ | ✔️ | ✔️ | ✔️ |
Hindi | hi-IN |
❌ | ❌ | ❌ | ❌ |
Italian | it-IT |
✔️ | ✔️ | ✔️ | ✔️ |
Korean | ko-KR |
✔️ | ❌ | ❌ | Key phrase only |
Marathi | mr-IN |
❌ | ❌ | ❌ | ❌ |
Portuguese (Brazil) | pt-BR |
✔️ | ✔️ | ✔️ | not all sub-cultures |
Spanish (Spain) | es-ES |
✔️ | ✔️ | ✔️ | ✔️ |
Spanish (Mexico) | es-MX |
❌ | ❌ | ✔️ | ✔️ |
Tamil | ta-IN |
❌ | ❌ | ❌ | ❌ |
Telugu | te-IN |
❌ | ❌ | ❌ | ❌ |
Turkish | tr-TR |
✔️ | ❌ | ❌ | Sentiment only |
- In the
zh-CN
culture, LUIS expects the simplified Chinese character set instead of the traditional character set. - The names of intents, entities, features, and regular expressions may be in Chinese or Roman characters.
- See the prebuilt domains reference for information on which prebuilt domains are supported in the
zh-CN
culture.
The Language service includes keyPhrase prebuilt entity and sentiment analysis. Only Portuguese is supported for subcultures: pt-PT
and pt-BR
. All other cultures are supported at the primary culture level.