Azure Artifact Signing — AU10TIX Verified ID rejected after ID and selfie verification

Question

Azure Artifact Signing — AU10TIX Verified ID rejected after ID and selfie verification

Andrew Richards 0

Hello,

I am the owner of Astrolobe LLC, a registered US company, and I am attempting to complete Organization / Public Trust identity validation for Microsoft Azure Artifact Signing.

My existing Artifact Signing account is in East US. The identity validation request currently shows Action Required.

When I follow Microsoft's verification link, I am directed to Microsoft Verified ID and then AU10TIX.

I completed the driver's license scan and selfie verification on my phone, without using a VPN. However, the verification failed with this message:

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

No specific reason was provided.

I attempted to create an Azure technical support request, but my Basic support plan does not permit submitting technical tickets without upgrading.

I previously registered my company's D-U-N-S number using a different email account. I do not know whether this is related.

Could a Microsoft Artifact Signing or Verified ID specialist help with the following?

Identify why AU10TIX rejected my verification.

Advise whether my existing verification session can be manually reviewed, reset, or reissued.

Provide a private support or escalation method to complete verification without creating a duplicate Azure identity-validation request.

I can provide the identity validation reference and additional account information privately through an authorized Microsoft support channel.

Thank you.

0 comments

1 answer

Your answer

Answer 1

Microsoft must review the failed AU10TIX/Verified ID transaction because there is no documented self-service reset for this exact rejection; keep the current identity-validation request and escalate it through Microsoft Q&A under Artifact Signing or through Azure Support if a technical case becomes available.^1^

Request a backend review

Since the document and selfie stages were completed without a VPN, repeating those steps without a reset is unlikely to expose the rejection reason.

Do not create another identity-validation request. Microsoft states that additional requests for the same entity while one is in progress do not help and cannot be expedited.^1^
Keep the current request in Action Required so its identifiers and transaction history remain available.
Continue with this Microsoft Q&A post using the Artifact Signing tag, which is an official assistance route listed in the FAQ for identity-validation problems when Azure technical support is unavailable under the current plan.^1^
Ask a Microsoft moderator to arrange a private exchange with the Artifact Signing/identity-validation team. Request:
- The specific reason or rejection category returned by AU10TIX.
- Backend review of the existing validation and Verified ID transaction.
- Reset or reissuance of the verification session, if supported.
- Confirmation that the existing request should remain in place.
Do not post subscription, tenant, request, or transaction identifiers publicly. Provide them only in an Azure support case or moderator-established private channel.

A closely matching Artifact Signing case—validation repeatedly failing without a reason after the external identity checks—was resolved after support collected the Identity Validation ID and account details and had the internal team investigate the request from the backend.^2^

Information to prepare privately

Collect the following before the escalation:

Artifact Signing account name and East US region.
Identity Validation ID/reference and current Action Required status.
Azure subscription ID and Microsoft Entra tenant ID.
Exact message: “Sorry, you do not meet requirements to create a Verified ID at this time.”
Approximate failure timestamp and time zone.
Primary email used in the Artifact Signing validation request.
Email used with AU10TIX.
Phone OS, browser, and Microsoft Authenticator version.
Confirmation that no VPN or proxy was used.
Screenshot of the rejection with personal information redacted.
Whether any previous Artifact Signing identity validation or Verified ID exists for the company or applicant.

If Microsoft Authenticator participated in the flow, submit its diagnostics:

Open Microsoft Authenticator.
Select Send feedback from the app menu.
Select Having trouble?
Submit the form and logs.
Record the resulting incident ID and provide it privately with the escalation.^3^

About the D‑U‑N‑S registration email

A D‑U‑N‑S registration under another email does not, by itself, establish the cause of this rejection. It becomes relevant if an Artifact Signing identity validation for the same organization already exists with a different primary email address. Microsoft’s documented action for that condition is to contact support to continue onboarding rather than create another request.^1^

Include the prior email address privately and ask the team to check for an existing organization-level validation record or email association. Do not attempt to work around it by creating another Azure tenant, Artifact Signing account, or validation request.

The exact AU10TIX message has also been reported for Artifact Signing after document and selfie submission, with escalation to Microsoft rather than a public self-service reset identified as the recovery path.^4^

References