Identity validation keeps failing with no reason

Question

I have been trying to complete the identity verification process so that I can use the artifact signing service on Azure. I have not been able to complete the process despite having valid forms of trusted ID. I go through the process that is handled be Au10tix and they are not helpful in determining what is going on. Can someone please point me to logs or give me some support on why identity verification is failing?

Answer 1

Have you tried this: Close all open instances of the authenticator app on your mobile, this is usually done by swiping up, finding the app, then swiping up again.  Ensure you close all instances of the authenticator app before relaunching.

• Make sure you are using the latest version of Microsoft Authenticator (Android/iOS). Older versions may not fully support Verified ID.
• Clear your web cache, if you are accessing the Verified ID setup through a browser, clear your cache or try completing the process using a different browser.
• Avoid Weak Internet Connections or VPNs. Do not use a weak Wi‑Fi connection or any VPN/Proxy service. These can interrupt the secure handshake between the browser and Microsoft Authenticator, causing technical errors.
• Try a different device. Some device‑specific settings or security policies may interfere with the process. If possible, try completing the setup on another phone.

Also, please tag Microsoft Authenticator to seek help on this.

Answer 2

If your identity validation is failing without a clear reason, here are some steps you can take:

1. Check Email Verification: Ensure that you haven't missed an email verification link sent to the primary email address you provided during the identity validation request. This link expires after seven days. If you missed it, you'll need to create a new identity validation request.
2. Documentation Issues: If the validation fails not due to a missed email, it may be because the Microsoft validation team couldn't determine your request based on the information provided. In this case, even if you provide additional documentation, it may not be sufficient for onboarding. You might consider deleting your Artifact Signing account to avoid being billed for unused resources.
3. Exhausted Attempts: If you have already exhausted all attempts for additional documentation, the onboarding process cannot proceed further.
4. Contact Support: For further assistance, you can reach out via Azure Support or Microsoft Q&A, using the tag artifact-signing. Creating a support ticket in the Azure portal may also help you get more specific guidance regarding your situation.
5. Role Assignment: Ensure that you have the Artifact Signing Identity Verifier role assigned to your account, as this is necessary to create an identity validation request.

Following these steps should help you identify the issue or provide a path to resolve it.