A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
Artifact Signing organization validation: Verified ID, business and domain pass, but EV email verification fails
We are trying to complete Public organization identity validation for ObviousIdea, a French company, in an existing Azure Artifact Signing account in West Europe.
The latest request completed the personal identity step through AU10TIX / Microsoft Verified ID successfully. The backend validation results show:
- DNE: Pass
- TSS: Pass
- VC_Ind: Pass
- BV: Pass
- DV: Pass
- EV: Fail
The Microsoft “Action required” link was completed on a desktop browser and the AU10TIX PIN email was received. The Verified ID was presented from Microsoft Authenticator on an Android Pixel device. The representative's first and last name checks, the business check, and the domain check all passed.
However, we did not receive a distinct organization email-verification message or link before the request changed to “Email verification failed”. The primary address is a named corporate address on the company's own domain, not a generic support/info/admin address, and it can receive external emails containing links. The domain uses OVH mail servers and the messages are currently delivered into Gmail. The AU10TIX PIN message was classified as spam, although the Verified ID stage still completed successfully.
This pattern has happened on more than one request. We now understand that each “Action required” email belongs to a different validation request and that reopening an older credentials.microsoft.com link only opens an expired or already completed request.
Could a Microsoft Artifact Signing moderator contact us privately so we can provide the tenant ID, subscription ID, Artifact Signing account name, identity validation IDs, and internal OneVet request IDs? We do not want to publish those identifiers or identity documents publicly.
Could you also confirm:
- Whether EV is a separate organization-email check after the successful AU10TIX / Verified ID stage.
- Whether using an OVH mailbox or forwarding the named corporate address into Gmail can cause EV to fail.
- Whether Microsoft can reset or inspect the EV stage before we submit another validation request.