Individual identity validation repeatedly failing — "Sorry, you do not meet requirements to create a Verified ID at this time" (Public Trust, Organization validation, Australia)

Allan Stewart 0 Reputation points
2026-08-03T01:02:36.4066667+00:00

We're setting up Azure Artifact Signing (Public Trust) for our organization. We've completed the Artifact Signing account setup and submitted an Organization identity validation request. When proceeding to the individual identity verification step (required as part of the org validation), we consistently receive:

"Sorry, you do not meet requirements to create a Verified ID at this time"

Troubleshooting already completed, all with the same result:

  • Attempted with a driver's licence — failed
  • Attempted with a passport — failed with identical error
  • Confirmed the email signed in during the verification link matches the email entered on the identity validation request exactly
  • Deleted and recreated the identity validation request from scratch
  • Removed any existing Verified ID entries from Microsoft Authenticator before retrying
  • Assigned the account Global Administrator role in the Entra tenant (no change — expected, since this appears unrelated to directory permissions)
  • Retried across multiple attempts on different days

Details:

  • Artifact Signing account region: ( Japan East) Country of organization: Australia Any ideas what the issue could be?
Artifact Signing
Artifact Signing

A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Allan Solomon Mejia 1,460 Reputation points
    2026-08-03T02:23:59.05+00:00

    Hello @Allan Stewart

    The error message "Sorry, you do not meet requirements to create a Verified ID at this time" is typically generated by the identity verification provider during the individual identity proofing step rather than by Azure Artifact Signing itself. Since you've already tried multiple government-issued IDs, recreated the validation request, and confirmed the email address matches, this doesn't appear to be an Entra ID or RBAC issue.

    A few things I'd ask Microsoft to verify:

    • Whether your Microsoft account or verification session has been blocked or requires manual review by the identity verification provider.
    • Whether there are any country-specific limitations affecting Australia for individual identity verification, even though Australia is a supported country for Public Trust validation.
    • Whether there's an issue with the combination of an Australia-based organization and an Artifact Signing account in Japan East, although identity verification is generally tied to the individual and organization rather than the Azure region.
    • Whether backend logs provide a more specific rejection reason, as the client-facing message is intentionally generic.

    At this point, I don't think additional retries with the same identity documents are likely to change the outcome. I'd recommend opening or updating your Azure Support case and asking the engineering team to review the backend verification logs associated with the identity validation request.

    Please "Accept the Answer" if this information helped you. This will help us and others in the community as well.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.