Artifact Signing Public Trust blocked — AU10TIX won’t recognize valid New Hampshire driver’s license

Question

Artifact Signing Public Trust blocked — AU10TIX won’t recognize valid New Hampshire driver’s license

nicholas kasiaras III 0

I'm trying to complete Public Trust organization identity validation for Azure Artifact Signing.

The organization validation has reached the representative identity-verification step, but I cannot complete the AU10TIX government ID scan.

I'm using a current, valid New Hampshire driver's license. AU10TIX lists Driver's License as an accepted document type, but every attempt returns:

"We couldn't recognize your ID type."

I've tried multiple scans with the entire card visible, straight-on, good lighting, no flash, and different plain backgrounds. The result is always the same.

I contacted AU10TIX support on September 6 and followed up on September 10, but I have not received a response. Because this verification is required to complete my Artifact Signing Public Trust identity validation, I'm now completely blocked from completing the process.

My Artifact Signing resource and identity-validation request are still active. I do not want to delete or create a duplicate validation request.

Is there a Microsoft Artifact Signing/identity-validation team that can investigate the existing validation or escalate the AU10TIX verification issue? I can provide my validation ID, screenshots, business registration documentation, and any other identifying information privately to a Microsoft representative.

Thank you.

0 comments

1 answer

Your answer

Answer 1

You’re blocked at the representative identity‑verification step because AU10TIX isn’t able to read your New Hampshire licence, and their support team hasn’t responded to your ticket.

On escalation: Microsoft’s own documentation routes identity‑verification issues away from them. The Artifact Signing FAQ states:

“For issues related to the AU10TIX identity‑verification experience, contact AU10TIX Support directly. This includes problems uploading identity documents, completing facial verification, or using the AU10TIX verification flow.”

That’s why you’re not finding a path to a Microsoft identity‑validation team. The representative‑verification flow is owned by AU10TIX, not Microsoft, and Microsoft doesn’t have a documented escalation channel for cases where AU10TIX stalls.

There is one alternative on the same page that’s worth checking:

“What if I already have a Verified ID? Follow the steps to present your existing valid (not expired) VID for Artifact Signing.”

If you already hold a Microsoft Verified ID from another process, presenting it may let you complete the representative‑verification step without needing AU10TIX to scan your licence. If you don’t have one, that option isn’t available because obtaining a new VID goes through the same AU10TIX flow that’s currently blocked.

Your instinct not to delete or recreate the request is correct. A failed or duplicated validation is harder to recover than a stalled one.

Help make this community better for everyone: if this answer resolved your issue, please accept it or leave an upvote. If not, feel free to add more details in a comment so we can continue the discussion.