Azure Language

Text analysis for entities, PII, key phrases, sentiment, summarization and question answering.

Provider: azure
Kind: AI service
Category: Compute
Official docs: https://learn.microsoft.com/en-us/azure/ai-services/language-service/concepts/data-limits

Properties · 6 set by this component

property	type	values	required	kind default	this component
auth	enum	api-key \| oauth \| iam \| none	no	—	▸ api-key
contentFiltering	boolean	—	no	—	inherited
customModels · component property	boolean	—	no	false	inherited
customerManagedKeys	boolean	—	no	—	▸ false
dataResidency · advanced	enum	us \| eu \| asia \| global	no	—	inherited
dataRetentionDays	integer	—	no	—	inherited
invocation · component property	enum	synchronous \| asynchronous	no	synchronous	inherited
keyStore	boolean	—	no	false	inherited
managed	boolean	—	no	false	▸ true
maxCharactersPerDocument · component property	integer	—	no	5120	inherited
modality	enum	text \| vision \| speech \| multimodal \| structured \| image \| video \| audio \| embedding \| rerank	no	—	▸ text
publicEndpoint	boolean	—	no	—	▸ true
quotaUnitsPerMinute	integer	—	no	—	▸ 1000
rateLimitRpm · advanced	integer	—	no	—	inherited
rateLimitTpm · advanced	integer	—	no	—	inherited
tier · component property	enum	f0 \| s0 \| s-multi-service	no	s-multi-service	inherited
viaGateway	boolean	—	no	false	inherited

Rules that apply · 2

Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.

AI API key not managedwarning

ai-api-key-unmanaged

This AI vendor is reached with an API key, and nothing in the design holds or rotates that key. It ends up in environment files or code, every caller shares it, and a single leak runs up the vendor bill until someone notices. Put the key in a key-management component, or say it is held there with keyStore.

— all of these hold:
— the node's `auth` is "api-key"
— the node's `keyStore` is false
— the node has at least one incoming edge from an app-server, worker or client
— this does not hold:
— the design contains a node of kind key-management

Stateful node without zone redundancyerror

stateful-node-without-zone-redundancy

A stateful compute node pinned to exactly one availability zone disappears with that zone, and its state goes with it. Nodes inside a cell are exempt, because there the cell is deliberately single-zone and redundancy comes from the other cells.

— all of these hold:
— the node's `stateless` is false
— the node sits inside exactly 1 availability-zone group
— this does not hold:
— the node sits inside at least one cell group

Use it in a design

nodes:
  - { id: "ai-language", component: "azure-ai-language" }

Other AI service products · 125

and 85 more → AI service page

Source

1# yaml-language-server: $schema=../../schema/component.schema.json
2# Azure Language: preconfigured and customizable text features (NER, PII detection, key phrases, sentiment, summarization, question answering).
3# "Data limits for Language service features" gives the S / multi-service tier 1,000 requests per minute (S0 / F0: 300), a 1 MB maximum request and 5,120 characters per document for synchronous preconfigured features.
4schemaVersion: "1"
5type: "component"
6id: "azure-ai-language"
7kind: "ai-service"
8provider: "azure"
9docs: "https://learn.microsoft.com/en-us/azure/ai-services/language-service/concepts/data-limits"
10defaults:
11  auth: "api-key"
12  managed: true
13  modality: "text"
14  publicEndpoint: true
15  customerManagedKeys: false
16  quotaUnitsPerMinute: 1000
17properties:
18  tier:
19    type: "enum"
20    values: ["f0", "s0", "s-multi-service"]
21    default: "s-multi-service"
22  invocation:
23    type: "enum"
24    values: ["synchronous", "asynchronous"]
25    default: "synchronous"
26  maxCharactersPerDocument:
27    type: "integer"
28    default: 5120
29  customModels:
30    type: "boolean"
31    default: false

The same page as markdown, for an agent: /catalogue/components/azure-ai-language.md