A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
For Artifact Signing, the name used in individual identity verification must match the government-issued ID exactly and must also match the personal details provided in the identity validation request.
From the documented process:
- For Organization identity validation, the form explicitly requires the First Name and Last Name of the individual representing the organization, and it states: “Use the exact name as it appears on your government-issued identification document for the Identity Validation process.”
- If there’s a mismatch (for example, government ID shows “Jonathan Doe” but the details in the identity validation or Verified ID flow show “John Doe”), the identity verification provider will surface a name mismatch error and the verification fails.
To resolve a “Name Mismatch” in this scenario, the supported path is:
- Ensure that the individual’s details in the identity validation request (First Name, Last Name) exactly match the government ID used during verification (for example, change “John” to “Jonathan” if the ID says “Jonathan”).
- If the identity validation request was created with incorrect personal details, the guidance for public identity validation is that changes require a new identity validation request. After creation, if information is wrong, the request must be recreated with the correct data.
- When recreating the Organization identity validation, enter the individual’s name exactly as on the government ID in the First Name and Last Name fields. This is the name that will be used for the individual identity verification step.
Changing only the Outlook display name is not mentioned as a supported fix. The critical data for Artifact Signing identity validation is:
- The legal name entered in the identity validation request (Organization → First Name / Last Name fields), and
- The name on the government-issued ID used by the individual during the verification flow.
If identity validation ultimately fails (for reasons other than missed email verification) even after correcting the data and recreating the request, the documented guidance is:
- The Microsoft validation team couldn’t make a determination based on the provided information.
- In that case, onboarding to Artifact Signing can’t proceed, and it’s recommended to delete the Artifact Signing account to avoid being billed for unused resources.
If further help is needed with this specific identity validation case (for example, repeated failures after correcting the name), the documented escalation path is to contact Azure Support or use Microsoft Q&A with the artifact-signing tag.
References: