A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
For Artifact Signing identity validation, this behavior is treated as a technical error in the Microsoft Authenticator and Verified ID flow. Use these steps in order:
- Fully close all open instances of Microsoft Authenticator on the phone, then reopen it.
- Update Microsoft Authenticator to the latest version. Older versions may not fully support Verified ID.
- Clear the browser cache on the device showing the QR code, or retry the flow in a different browser.
- Do not use a weak Wi-Fi connection, VPN, or proxy. If possible, switch networks.
- Try the validation on a different phone. Device-specific settings or security policies can interfere with the handshake between the browser and Authenticator.
- Keep the browser page open during the process. In the Artifact Signing flow, after the identity-verifier steps complete on the phone, the next step is to select Open Authenticator, add the Verified ID, then return to the browser and continue scanning/presenting the Verified ID until the browser shows Verification Successful.
If the failure is tied to a previous incomplete verification attempt, delete the existing identity validation request, remove the associated Verified ID from Microsoft Authenticator, then submit a new identity validation request and create a new Verified ID. When recreating it, make sure the information exactly matches the identity documents and complete the verification in good lighting.
Also verify these general Authenticator conditions, because they can cause the app to appear to fail and return to the QR screen:
- The app is unlocked.
- The phone has internet connectivity.
- Notifications are enabled.
- The device date and time are correct.
- If using mobile data, try Wi-Fi, and vice versa.
If the issue continues after these steps, capture logs from Authenticator by using Send feedback from the app menu before seeking further help.
References: