Edit

Share via

Azure Face service quotas and limits

  • Article

This article contains a reference and a detailed description of the quotas and limits for Azure Face in Azure AI Vision. The following tables summarize the different types of quotas and limits that apply to Azure AI Face service.

Extendable limits

Default rate limits

Pricing tier Limit value
Free (F0) 20 transactions per minute
Standard (S0),
Enterprise (E0)		 10 transactions per second, and 200 TPS across all resources in a single region.
See the next section if you want to increase this limit.

Note

If you exceed the default rate limit, you'll receive a 429 error. To address this issue, refer to the Performance guide.

Default Face resource quantity limits

Pricing tier Limit value
Free (F0) 1 resource
Standard (S0)
  • 5 resources in UAE North, Brazil South, and Qatar Central.
  • 10 resources in other regions.
Enterprise (E0)
  • 5 resources in UAE North, Brazil South, and Qatar Central.
  • 10 resources in other regions.

How to request an increase to the default limits

To increase rate limits and resource limits, you can submit a support request. However, for other quota limits, you need to switch to a higher pricing tier to increase those quotas.

Submit a support request and provide the following information:

  • A description of your Face use case.
  • The reason for requesting an increase in your current limits.
  • Which of your subscriptions or resources are affected?
  • What limits would you like to increase? (rate limits or resource limits)
  • For rate limits increase:
    • How much TPS (Transaction per second) would you like to increase?
    • How often do you experience throttling?
    • Did you review your call history to better anticipate your future requirements? To view your usage history, see the monitoring metrics on Azure portal.
  • For resource limits:
    • How much resources limit do you want to increase?
    • How many Face resources do you currently have? Did you attempt to integrate your application with fewer Face resources?

We evaluate TPS increase requests on a case-by-case basis, and our decision is based on the following criteria:

  • Region capacity/availability.
  • Certain scenarios require approval through the gating process.
  • You must currently be receiving 429 errors often.

Other limits

Quota of PersonDirectory

Pricing tier Limit value
Free (F0)
  • 1 PersonDirectory
  • 1,000 persons
  • Each holds up to 248 faces.
  • Unlimited DynamicPersonGroups
Standard (S0),
Enterprise (E0)
  • 1 PersonDirectory
  • 75,000,000 persons
    • Contact support if you want to increase this limit.
  • Each holds up to 248 faces.
  • Unlimited DynamicPersonGroups

Quota of FaceList

Pricing tier Limit value
Free (F0),
Standard (S0),
Enterprise (E0)
  • 64 FaceLists.
  • Each holds up to 1,000 faces.

Quota of LargeFaceList

Pricing tier Limit value
Free (F0)
  • 64 LargeFaceLists.
  • Each holds up to 1,000 faces.
Standard (S0),
Enterprise (E0)
  • 1,000,000 LargeFaceLists.
  • Each holds up to 1,000,000 faces.

Quota of PersonGroup

Pricing tier Limit value
Free (F0)
  • 1,000 PersonGroups.
  • Each holds up to 1,000 Persons.
  • Each Person can hold up to 248 faces.
Standard (S0),
Enterprise (E0)
  • 1,000,000 PersonGroups.
  • Each holds up to 10,000 Persons.
  • Each Person can hold up to 248 faces.

Quota of LargePersonGroup

Pricing tier Limit value
Free (F0)
  • 1,000 LargePersonGroups
  • Each holds up to 1,000 Persons.
  • Each Person can hold up to 248 faces.
Standard (S0),
Enterprise (E0)
  • 1,000,000 LargePersonGroups
  • Each holds up to 1,000,000 Persons.
  • Each Person can hold up to 248 faces.
  • The total Persons in all LargePersonGroups shouldn't exceed 1,000,000,000.

Customer-managed keys (CMK)

Pricing tier Limit value
Free (F0),
Standard (S0)		 Not supported
Enterprise (E0) Supported