A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
Artifact Signing Individual/Public — AU10TIX rejected issuance after ID and selfie capture; no Verified ID created
I am a US-based individual developer completing Azure Artifact Signing Individual/Public identity validation. The Artifact Signing account is active in East US on a paid Azure subscription.
I successfully completed the AU10TIX email/PIN, phone, Maryland driver’s-license capture, and selfie/liveness steps. AU10TIX then displayed:
“Sorry, you do not meet requirements to create a Verified ID at this time.”
No Verified ID was issued to Microsoft Authenticator. The Azure identity-validation request remains Action Required. I have preserved the existing request and stopped retrying.
I confirmed that the Azure billing account is Individual, the billing information matches my identity documents, the same primary email was used throughout, Microsoft Authenticator is current, and no VPN/proxy was active.
Azure’s automated troubleshooting found no diagnostics for this identity-proofing transaction; it only confirmed that the Microsoft.CodeSigning/codeSigningAccounts resource operations succeeded. My Basic Azure support plan does not permit creation of a private technical ticket.
Could an MSFT moderator route this to the Artifact Signing/Verified ID team and establish a private channel for my Identity Validation ID, subscription/resource information, timestamps, and AU10TIX reference identifiers? Please advise whether the verification session or issuance state requires a reset and whether another attempt is authorized.