Unable to complete "verify credentials"

SML 0 Reputation points
2026-05-06T17:10:36.6633333+00:00

I hope someone can help us. We are trying to use Azure services to sign our Windows app.
We have created an Artifact Signing account but we're stuck at the Identity Validation stage. We need to verify our credentials and we are on a browser page that is asking us to "Present your Verified ID". The instructions read: "Scan QR Code with Microsoft Authenticator."
We have a Verified ID in the Authenticator app. On the Verified IDs page of our app we see an icon which brings up a "Scan QR code" screen with the instructions "Your account provider will display a QR code".
We scan the QR code presented to us in the browser. This results in two things.
Firstly, the app screen disappears (that doesn't seem correct!) - it's still running, but it loses focus.
Secondly, the browser page reacts by replacing the QR code with "Processing....".
After a few minutes, the browser page refreshes and the QR code is back. Nothing has changed, i.e. our credentials have not been verified.
As you can imagine, this is a bit of a nightmare - we cannot see how to progress past this and it's a barrier to us completing what we need to sign our app.
There doesn't seem to be any alternative to using the Authenticator QR scan method which clearly is not working for us.
If anyone has any ideas, we'd be so grateful!

Microsoft Security | Microsoft Authenticator

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  2. AI answer

    2026-05-06T17:10:54.5566667+00:00

    The behavior described matches the normal “present a verifiable credential” flow, but the final callback from Verified ID back to the relying party (Artifact Signing) is not completing successfully. The QR scan and “Processing…” indicate that Microsoft Authenticator is sharing the credential, but the web app is not receiving or processing the callback.

    Key points from the documented flow:

    1. A verified credential must already be in Microsoft Authenticator.
    2. The browser shows a QR code and the page text “Present your Verified ID. Scan the QR code.”
    3. In Authenticator:
      • Open Verified IDs.
      • Use the QR code icon to scan the QR.
      • Select the Verifiable Credential requested.
      • Tap Share to present it.
    4. After sharing, the browser should move from “Processing…” to a success page (for Artifact Signing: Verification Successful) and the identity validation status in the Azure portal should change to Completed after a short delay.

    In the Artifact Signing individual developer flow, the documented steps are:

    1. Complete the AU10TIX identity verification and add the Verified ID to Microsoft Authenticator.
    2. Back in the browser, a QR code is shown with “Present your Verified ID. Scan the QR code.”
    3. Scan this QR code from Authenticator and select Verifiable Credential.
    4. Tap Share to share the credential with Artifact Signing.
    5. On success, the browser shows Verification Successful and, after a couple of minutes, the Identity Validation status in the Azure portal updates to Completed.

    Given that the QR scan triggers “Processing…” and then the QR reappears, the issue is most likely on the web app / callback side rather than in Authenticator itself. The Verified ID FAQ notes that the Request Service API uses callbacks to a URL that must be reachable from the Verified ID system; if that callback cannot be reached or processed, the verification cannot complete even though the QR scan and share succeed.

    Actionable checks based on the documented flows:

    1. Confirm the correct credential is in Authenticator
      • Ensure the Verified ID that was issued during the AU10TIX flow is present in Verified IDs in Microsoft Authenticator.
      • When scanning the QR on the “Present your Verified ID” page, ensure the app shows the expected credential and that Share is tapped.
    2. Ensure the browser session remains active
      • Do not close or refresh the browser tab while it shows “Processing…”.
      • Wait several minutes to allow the callback and status update.
    3. Verify network/callback reachability (for the Artifact Signing relying party)
      • The Verified ID Request Service sends callbacks to the relying party URL. That URL must be reachable from Azure in the tenant’s region.
      • If there is any network hardening (firewall, restricted inbound rules), ensure it allows traffic from AzureCloud service tags or the documented AzureCloud.region CIDR ranges so the callback from Verified ID can reach the Artifact Signing endpoint.
    4. Re-run the identity validation flow end-to-end
      • From the Artifact Signing account in the Azure portal, open Identity validations and confirm the request status.
      • If needed, create a new identity validation request and follow the documented steps again: AU10TIX verification → add Verified ID to Authenticator → scan the final “Present your Verified ID” QR → tap Share.

    If, after confirming the correct credential, keeping the browser session active, and ensuring network reachability, the page still returns to the QR without completing, this indicates an issue on the Artifact Signing / Verified ID service side. In that case, opening a support ticket for the Artifact Signing resource and referencing the identity validation request that will not complete is required so support can inspect the callback and validation status.

    References:

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

    Was this answer helpful?

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.