Azure AI Face

Detects, analyzes, verifies and identifies human faces, with liveness checks, under Limited Access approval.

Provider: azure
Kind: AI service
Category: Compute
Official docs: https://learn.microsoft.com/en-us/azure/ai-services/face/overview-identity

Properties · 5 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
customerManagedKeys	boolean	—	no	—	▸ false
dataResidency · advanced	enum	us \| eu \| asia \| global	no	—	inherited
dataRetentionDays	integer	—	no	—	inherited
keyStore	boolean	—	no	false	inherited
limitedAccessApproval · component property	boolean	—	no	true	inherited
livenessDetection · component property	boolean	—	no	false	inherited
managed	boolean	—	no	false	▸ true
maxImageSizeMb · component property	integer	—	no	6	inherited
modality	enum	text \| vision \| speech \| multimodal \| structured \| image \| video \| audio \| embedding \| rerank	no	—	▸ vision
publicEndpoint	boolean	—	no	—	▸ true
quotaUnitsPerMinute	integer	—	no	—	inherited
rateLimitRpm · advanced	integer	—	no	—	inherited
rateLimitTpm · advanced	integer	—	no	—	inherited
recognitionOperations · component property	enum	detect-only \| verify \| identify	no	detect-only	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-face", component: "azure-ai-face" }

Other AI service products · 125

and 85 more → AI service page

Source

1# yaml-language-server: $schema=../../schema/component.schema.json
2# Azure AI Face: face detection, liveness, verification and identification against person groups.
3# "What is the Azure Face service?" states access is limited and granted only through the Face Recognition intake form, that liveness SDKs are gated, that input images must be 6 MB or less, and that a person group holds up to 1,000,000 persons with up to 248 faces each.
4schemaVersion: "1"
5type: "component"
6id: "azure-ai-face"
7kind: "ai-service"
8provider: "azure"
9docs: "https://learn.microsoft.com/en-us/azure/ai-services/face/overview-identity"
10defaults:
11  auth: "api-key"
12  managed: true
13  modality: "vision"
14  publicEndpoint: true
15  customerManagedKeys: false
16properties:
17  limitedAccessApproval:
18    type: "boolean"
19    default: true
20  livenessDetection:
21    type: "boolean"
22    default: false
23  recognitionOperations:
24    type: "enum"
25    values: ["detect-only", "verify", "identify"]
26    default: "detect-only"
27  maxImageSizeMb:
28    type: "integer"
29    default: 6

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