Azure Artifact Signing: Identity validation stuck on "Action Required" - Verified ID QR presentation fails / hangs on "Processing..."

I am having this same problem also. The webapp needs to provide useful feedback in either success and failure cases. It doesn't even know it has failed.

Try below steps or also try tagging Authenticator App team in here if they can help.

• 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.

Hello @Colin Howard ,

Welcome to Microsoft Q&A.

Based on your description, this does not sound like the AU10TIX identity check itself is failing, because the personal ID verification has already completed and the Verified ID credential is visible in Microsoft Authenticator.

The failure appears to happen at the next step, where the already issued Verified ID must be presented back to Artifact Signing. Microsoft documents this flow as follows: after the identity validation request moves to Action Required, the user follows the verification link, completes the trusted ID-verifier flow, adds the Verified ID to Microsoft Authenticator, then scans the Present your Verified ID QR code, selects the Verifiable Credential, and selects Share. After a successful share, the browser should show Verification Successful, and the Azure portal status should update after a few minutes.

One thing I would try is using the identity validation link sent to the primary email address instead of starting only from the desktop browser QR page. Microsoft documents that the primary email address receives the Identity Validation link, and that the same email address used when creating the request should be used when accessing the Identity Validation link. This may help avoid a browser-to-mobile handoff issue, although it is not documented as a guaranteed fix.

I would also make sure that the Microsoft account used to open the validation link is the same account/email address that was provided in the identity validation request. The documentation specifically calls out using the email address provided at request creation when following the Identity Validation process.

Since the Authenticator app closes or loses focus before showing the credential selection and Share confirmation screen, and the browser stays on Processing..., this looks like a Verified ID presentation or service-side handoff issue rather than a normal validation delay. In a similar Microsoft Q&A thread about Trusted Signing Verified ID presentation failure, a Microsoft moderator asked for the identity validation ID to investigate further, so I would include both your Identity validation ID and Gateway request ID in the escalation.

If the issue continues, I would recommend escalating it through the Artifact Signing support path. Microsoft’s Artifact Signing FAQ states that users can create a support ticket in the Azure portal, or post on Microsoft Q&A with the Artifact Signing tag, or on Stack Overflow with the trusted-signing tag. Since you mentioned that a formal support ticket is not available under your current support plan, Microsoft Q&A with the Artifact Signing tag is the most appropriate next step.

When escalating, include the Artifact Signing account name, region, Identity validation ID, Gateway request ID, the fact that AU10TIX verification completed successfully, that the Verified ID exists in Microsoft Authenticator, and that the failure occurs specifically when presenting the Verified ID to Artifact Signing.

I hope this helps.