Face API verification approval not working on my subscription

Face API Face verification and identification are Limited Access capabilities and are controlled per Azure subscription/tenant through a registration and vetting process. The available guidance covers how to request and hold access, but it does not describe any self-service way to move or “transfer” an existing approval between subscriptions.

To resolve the situation where approval is tied to the wrong subscription, the supported path is:

1. Ensure the target subscription is eligible
   • Limited Access features (Face identification and Face verification) are only available on Standard (S0) and Enterprise (E0) pricing tiers, not the Free (F0) tier.
   • The subscription must be an Azure subscription that is managed by Microsoft (you work directly with a Microsoft account team) and used for an allowed scenario.
2. Submit a new Limited Access registration for the correct subscription
   • Use the official registration process for Face API Limited Access features by submitting a registration form.
   • In the form, specify the correct subscription ID and tenant that should have Face verification enabled.
   • Make sure the use case and other details match the scenario that was previously approved, and that they comply with the allowed use cases described in the transparency note referenced in the documentation.
3. Work with the Microsoft account team or support
   • Because access is granted at Microsoft’s discretion and is tied to eligibility and vetting, any change to which subscription holds the approval must be handled by Microsoft.
   • Contact the Microsoft account team that manages the organization’s Azure relationship and provide:
     • The existing approval details (date, reference, and the subscription it was applied to).
     • The target subscription ID and tenant where Face verification is needed.
   • If there is no direct account team contact, open a support request for Azure AI services / Face API and include the same information so support can coordinate with the Limited Access team.
4. Wait for re‑evaluation/confirmation
   • Access to Face API Limited Access features is subject to Microsoft’s vetting and may require re‑verification of the use case and subscription.
   • Microsoft may ask for additional information or require periodic reverification.

If the original approval cannot be moved, the outcome will effectively be a new approval for the correct subscription via the registration process above, while the old subscription’s access can be left unused or adjusted by Microsoft as needed.

References:

• Limited Access to Face API