4.2 Azure AI Language Service
Key Takeaways
- Azure AI Language is the primary service for text analysis — it combines multiple NLP capabilities under a single endpoint.
- Pre-configured features (sentiment analysis, NER, key phrase extraction, language detection, PII detection, text summarization) work immediately without training.
- Customizable features include Conversational Language Understanding (CLU), custom NER, custom text classification, and custom question answering.
- CLU (Conversational Language Understanding) enables you to build models that understand user intents and extract entities from natural language utterances — it replaced LUIS.
- Custom question answering creates a knowledge base from FAQ documents, manuals, and web pages that answers natural language questions.
Azure AI Language Service
Quick Answer: Azure AI Language is the unified NLP service providing both pre-configured features (sentiment analysis, NER, key phrases, PII detection) and customizable features (CLU for intent/entity extraction, custom question answering, custom text classification). It replaces several older services including LUIS and QnA Maker.
What Is Azure AI Language?
Azure AI Language is Microsoft's comprehensive NLP service that provides a wide range of text analysis capabilities. It consolidates multiple NLP features under a single service with a unified endpoint, making it the go-to service for text-related AI tasks on Azure.
Pre-Configured Features (No Training Required)
These features work immediately — send text and get results:
| Feature | Description | Example |
|---|---|---|
| Sentiment analysis | Positive/negative/neutral sentiment with confidence scores | "Great product!" → Positive (0.98) |
| Key phrase extraction | Main topics and concepts | "The hotel was clean and affordable" → ["hotel", "clean", "affordable"] |
| Named entity recognition | Entities with categories | "John works at Microsoft" → Person: John, Organization: Microsoft |
| Entity linking | Links entities to Wikipedia knowledge base | "Paris" → Paris, France (Wikipedia link) |
| Language detection | Identify text language | "Hola mundo" → Spanish (es) |
| PII detection | Find and redact sensitive data | "Call 555-1234" → "Call [PHONE]" |
| Text summarization | Extractive and abstractive summaries | Long article → Key points summary |
| Opinion mining | Aspect-based sentiment | "The camera is great but battery is poor" → camera: positive, battery: negative |
Customizable Features (Training Required)
These features require training with your data:
| Feature | Description | Training Data |
|---|---|---|
| CLU (Conversational Language Understanding) | Understand intents and entities in utterances | Labeled utterances with intents/entities |
| Custom text classification | Classify text into your categories | Labeled documents |
| Custom NER | Extract your custom entity types | Labeled text with custom entities |
| Custom question answering | Answer questions from your documents | FAQ documents, manuals, web pages |
Conversational Language Understanding (CLU)
CLU enables you to build models that understand the intent (what the user wants to do) and extract entities (key information) from natural language utterances.
CLU Replaces LUIS
CLU is the successor to LUIS (Language Understanding Intelligent Service), which was retired in October 2025. If you see references to LUIS on the exam, know that CLU is the current replacement.
CLU Concepts
| Concept | Definition | Example |
|---|---|---|
| Utterance | The user's input text | "Book a flight to Paris next Friday" |
| Intent | What the user wants to do | BookFlight |
| Entity | Key information in the utterance | Destination: Paris, Date: next Friday |
How CLU Works
- Define intents — the actions users want to perform (BookFlight, CancelFlight, CheckStatus)
- Define entities — the key information to extract (destination, date, passenger name)
- Add utterances — provide example sentences for each intent with entities labeled
- Train the model — CLU learns patterns from your labeled examples
- Test and publish — test with new utterances and deploy the model
- Use in applications — send user input to CLU and receive intent + entities
CLU Example
Training utterances for BookFlight intent:
- "Book a flight to Paris next Friday" → Intent: BookFlight, Entities: {destination: Paris, date: next Friday}
- "I need to fly to London tomorrow" → Intent: BookFlight, Entities: {destination: London, date: tomorrow}
- "Reserve a seat to Tokyo on March 15" → Intent: BookFlight, Entities: {destination: Tokyo, date: March 15}
After training, a new utterance:
- "Find me a flight to Berlin next week" → Intent: BookFlight (0.95), Entities: {destination: Berlin, date: next week}
On the Exam: CLU is frequently tested. Know that it identifies INTENTS (what the user wants) and ENTITIES (key details) from natural language. It requires training with labeled utterances. LUIS is retired — CLU is the replacement.
Custom Question Answering
Custom question answering creates a knowledge base that answers natural language questions. It builds on your existing content:
How It Works
- Add sources — FAQ pages, product manuals, documents, or manually entered Q&A pairs
- Build the knowledge base — the service extracts question-answer pairs automatically
- Test — ask questions and verify answers
- Publish — deploy as an endpoint for chatbots and applications
Question Answering Sources
| Source Type | Example |
|---|---|
| FAQ web pages | company.com/faq |
| Product manuals (PDF/Word) | Product User Guide.pdf |
| Manual Q&A pairs | Manually entered questions and answers |
| Existing knowledge bases | Import from other Q&A systems |
Key Features
- Multi-turn conversations — follow-up questions that reference previous context
- Chit-chat — built-in responses for casual conversation (greetings, jokes)
- Synonyms — understand different phrasings of the same question
- Confidence scores — each answer includes a confidence rating
On the Exam: Custom question answering replaces QnA Maker (retired). It is for building FAQ-style chatbots that answer questions from your existing documents. CLU is for understanding intent and entities; question answering is for finding specific answers in your knowledge base.
When to Use Which Feature
| Scenario | Feature |
|---|---|
| Determine if a review is positive or negative | Sentiment analysis |
| Find the main topics in a document | Key phrase extraction |
| Identify people and organizations in an article | Named entity recognition |
| Detect and redact Social Security numbers | PII detection |
| Understand what a user wants in a chatbot | CLU (intent + entity extraction) |
| Build a FAQ bot from product documentation | Custom question answering |
| Classify support tickets into custom categories | Custom text classification |
| Extract custom data types from documents | Custom NER |
Which Azure AI Language feature understands user intents and extracts entities from natural language utterances?
Which retired Azure service did Conversational Language Understanding (CLU) replace?
A company wants to build a chatbot that answers employee questions about company policies using their existing HR handbook and FAQ documents. Which Azure AI Language feature should they use?
In CLU, what does an "intent" represent?
Which TWO of the following are pre-configured Azure AI Language features that require NO training? (Select two)
Select all that apply