
Access Azure AI Language via SDKs (Python, JavaScript, .NET) or the REST API. Prebuilt endpoints accelerate common scenarios (summarization, NER, sentiment), while custom models and prompt tuning help adapt results to your data and workflow.
Core capabilities
Below are the primary text-analysis capabilities available in Azure AI Language Services, with typical use cases and short descriptions to help you choose the right tool.| Capability | What it does | Typical use case |
|---|---|---|
| Language detection | Detects the language of a text snippet and returns a language code and confidence score | Route multilingual content to the appropriate processing pipeline or model |
| Key phrase extraction | Identifies main phrases and concepts in text | Summarize meeting notes or index documents for search |
| Sentiment analysis | Classifies text sentiment (positive / neutral / negative), often with sentence-level scores | Monitor customer feedback or flag negative comments for escalation |
| Named Entity Recognition (NER) | Extracts entities (people, organizations, locations, products) and labels their types | Build knowledge graphs, power search facets, or tag documents |
| Entity linking | Links recognized entities to an external knowledge base (e.g., Wikipedia or custom KB) | Enrich extracted entities with canonical identifiers and external context |
| Summarization | Produces concise summaries (extractive or abstractive) of long documents | Provide quick overviews of long reports, papers, or transcripts |
| PII detection & redaction | Identifies and optionally redacts personally identifiable information (credit cards, SSNs, phone numbers) | Ensure compliance and privacy before sharing or storing data |

Quick examples
The examples below illustrate how to call Language capabilities. Replace <your-resource-endpoint> and <your-key-or-token> with your Azure resource values.Use the REST API for platform-agnostic integration; use an SDK for ergonomics and built-in authentication helpers. Refer to the official API docs for the exact endpoint and API version you should use.
REST (curl) — Language detection (illustrative)
SDK (Python) — Summarization (illustrative)
Best practices
- Preprocess text to remove irrelevant formatting and noise (HTML tags, scripts) before analysis.
- For large-scale document processing, batch inputs and parallelize requests within service limits.
- When working with sensitive data, prefer PII redaction and follow your organization’s compliance policies.
- Validate entity linking results against your knowledge base before automatic ingestion.
Links and references
- Azure AI Language overview: https://learn.microsoft.com/azure/ai-services/language/
- REST API and endpoint reference: https://learn.microsoft.com/azure/ai-services/language/reference
- SDK documentation and samples:
- Example external KB for entity linking: https://en.wikipedia.org/wiki/Albert_Einstein