Completing the Identity Validation process, unable to feed picture of ID into Microsoft Authenticator...

SForSW 30 Reputation points
2026-09-30T05:31:23.2833333+00:00

I am attempting to renew my identity validation following the instructions provided on the Azure site. After going through all of the steps, including installing the Authenticator app on my phone and completing the ID picture process through the website retrieved on my phone, I am presented with another instruction on the website to submit my ID by scanning a QR code with my phone. When I do that, the Authenticator app opens again on my phone automatically, which then opens the camera on said phone. There is no automatic image capture nor further instructions, it just leaves my camera on. So I take a picture of my ID as requested, nothing happens. I then attempted to forward the captured image to the Authenticator app, but there is no way to forward it or otherwise share the image with the app. I am now stuck in a loop with the website telling me to submit my ID, the Authenticator app opening my phone's camera, then no way to continue to proceed. The Authenticator app already indicates I have a verified ID with the details displayed (apparently retrieved from completing the -website- image captures on the phone sharing with the app). Please advise as to what I am supposed to do next or provide an alternate way to renew my identity validation. Thanks!

Artifact Signing
Artifact Signing

A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)

2 answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-09-30T05:31:40.2+00:00

    For Artifact Signing identity validation, the ID photo is not submitted through Microsoft Authenticator.

    The documented flow is:

    1. Complete the trusted ID-verifier steps on the mobile device and present the requested documents there.
    2. After that process completes on the mobile device, select Open Authenticator.
    3. In Microsoft Authenticator, select Add to add the verified ID.
    4. Back on the browser, when the page shows Present your Verified ID, scan that QR code.
    5. In Authenticator, select Verifiable Credential and then Share.
    6. The browser should update to Verification Successful.

    In this flow, the second QR code is for presenting the verified credential from Authenticator back to Artifact Signing, not for taking another picture of the ID. If scanning the QR code only opens the camera and leaves it there, use the Authenticator app itself to scan the QR code rather than relying on the phone camera app. The QR code in this process is intended to be scanned with Microsoft Authenticator unless otherwise stated.

    Also keep the browser page open during the QR-based steps. The documented flow explicitly says not to close the browser during the scan steps.

    Since Authenticator already shows a verified ID card, the next action is to present that credential:

    • On the browser, stay on the Present your Verified ID page.
    • Scan the QR code with Microsoft Authenticator.
    • When prompted in Authenticator, select the verified credential.
    • Select Share.
    • Wait for the browser to update to Verification Successful.

    If the issue continues:

    • Ensure Microsoft Authenticator is updated to the latest version.
    • If using Android, scan from within Microsoft Authenticator. The documented FAQ notes known QR-scanning issues on some Android scenarios, especially when the camera app launches the wrong app/profile.
    • Send Authenticator logs and note the incident ID: in Authenticator, open the top menu, tap Send feedback > Having trouble? > complete the form > Send.
    • If the validation still does not complete, create a support ticket.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. SForSW 30 Reputation points
    2026-09-30T22:39:50.0533333+00:00

    Here is the solution for others who may run into the same or similar problems:

    The primary issue related to using a 4-5 year old Android phone. Apparently, older versions of Android are unable to complete the required step to share a verified ID from the Microsoft Authenticator app to the receiving page on the desktop browser via the QR code. The Authenticator app simply shuts down, crashing back to the home screen without any error message nor any presented alternate option to forward the ID in a different way. Following AI advice and various other posts around the internet, all alternate options also failed along the way at one point or other (including copying and pasting URL's directly in the mobile browser to try and bypass certain QR steps, finding an alternate link on the receiving page that does not require a QR code when using a different web browser like Chrome or FireFox, and several others). What ultimately had to be done was going through the entire identity verification process again from scratch on an entirely different Android phone using a newer version that could handle one of the QR requests. The newer phone (~1 year old) was still unable to complete the step that requires launching the Microsoft Authenticator app via a QR code (only wanting to copy the QR link to the clipboard or display it), but manually launching the Authenticator app and then routing through various links and QR codes from within eventually allowed the steps to complete.

    The problems with this system are extensive, layered, and compounded when one step in the process fails and there is little to aid the user in finding alternate solutions (there are often none). The problems I encountered during this process include inconsistent behavior when selecting options (example: selecting an option the first time fails, the second time it works), limited or entirely unclear/missing directions on methods and procedures (example: 60 day window limit on identity validation renewal process, yet the renewal notice arrives prior to this timeframe), incompatibilities on dependent external hardware (older Android devices), and no alternative solutions when encountering unsolvable problems preventing further progress.

    This is a very convoluted, complex, and unnecessarily incompatible process to have to go through. Please either keep everything on the web browser side of things or the mobile device side of things and do not require QR exchanges between the two that apparently many phones are not capable of handling with the methods Microsoft is requiring. Too many elements are already unnecessarily sharded and separated (ie subscription, Azure+Entra, roles, etc). Please consider more unification and simplicity in the future. Additional guidance and clear instructions with alternate solutions would also be a huge help. The time spent (wasted) on sorting through problems like this deplete productivity and is excessive.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.