Some attributes (for example: age, gender, emotions, and identity matching/Face ID) require extra approval from Microsoft before they can be used. You can still retrieve landmarks and basic location data without that approval.

- Bounding boxes for each detected face.
- Detailed facial landmarks (eyes, nose, mouth, pupils, etc.).
- Optional face attributes (head pose, glasses, and other attributes where allowed).
- Optional unique face identifiers for cross-image matching (subject to approval).



- In the Azure Portal, create an Azure AI (Face) resource. Provide subscription, resource group, region, name, and pricing tier. Note: the free tier is limited to one per subscription and may not always be available.
- After creation, open the resource and copy the service endpoint and subscription keys from the “Keys and Endpoint” blade. You’ll use these values in SDKs and REST calls.


- If you request face IDs or certain attributes and your subscription lacks approval, the service may return an error—disable those parameters or request access via Azure support.
- Use returnRecognitionModel for traceability when running experiments across SDK versions.
- Verify pricing tier and quotas (especially in production) to avoid throttling.
- For persistent matching across images, you need faceId functionality and the appropriate approval.
- If you get permissions errors for sensitive attributes, file an Azure support request to request feature access.
- When debugging, log the recognitionModel and detectionModel returned so you can reproduce results later.
With these steps and examples you can detect faces, extract landmarks, and request face attributes where allowed. Explore the broader Azure Vision documentation for additional capabilities like OCR, object detection, and custom vision scenarios.