Azure Artifact Signing: Microsoft Authenticator closes when presenting AU10TIX Verified ID

cazul 0 Reputation points
2026-11-02T19:54:22.1166667+00:00

I am trying to complete Organization Identity Validation for Azure Artifact Signing (formerly Trusted Signing).

My Artifact Signing account has the status "Action Required".

I successfully completed identity verification through AU10TIX. The resulting Verified ID is available in Microsoft Authenticator under "Verified IDs".

However, when I scan the QR code displayed at credentials.microsoft.com ("Present your Verified ID"), Microsoft Authenticator immediately closes and Android returns to the home screen.

No consent dialog appears, and the identity validation remains incomplete.

Device and software:

Huawei Mate 20 Pro (LYA-L29)

EMUI 12.0.0

Microsoft Authenticator 6.2610.7075 (updated October 22, 2026)

Google Play Store reports the app as compatible and offers no update.

Troubleshooting:

Confirmed that the AU10TIX Verified ID is present.

Cleared the Authenticator cache.

Restarted the app.

Tried newly generated verification QR codes.

Confirmed that the Authenticator otherwise opens normally.

The issue persists.

Questions:

Is this a known issue with Microsoft Authenticator and Verified ID presentation on Huawei devices?

Is there an alternative way to complete Artifact Signing organization identity verification?

Can the Artifact Signing identity verification team investigate or reset the pending verification request without requiring me to repeat the successful AU10TIX identity check?

My verification deadline is December 2, 2026.

I have an Azure Basic support plan, which does not allow me to submit a technical support request through the Azure portal.

Thank you for your assistance.

Artifact Signing
Artifact Signing

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

0 comments No comments

3 answers

Sort by: Most helpful
  1. Meha-MSFT 2,705 Reputation points Microsoft Employee Moderator
    2026-11-19T19:26:13.16+00:00

    Was this answer helpful?

    0 comments No comments

  2. cazul 0 Reputation points
    2026-11-03T07:28:18.42+00:00

    Answer deleted, wrong section

    Was this answer helpful?

    0 comments No comments

  3. Rukshan edirisinghe 2,930 Reputation points
    2026-11-03T04:47:29.84+00:00

    Hi @cazul

    I couldn't find a published known issue for Huawei devices. But a crash at the exact moment the QR code is scanned usually points to the camera/scanner hand-off on that phone, not your Verified ID. There's a good chance it can be worked around without redoing AU10TIX.

    Try these on the Mate 20 Pro first:

    1. Check the app permissions. Go to Settings > Apps > Authenticator > Permissions and make sure Camera is allowed. Then, under Battery > App launch, set Authenticator to Manage manually with everything on. EMUI is known for closing apps aggressively in the background.
    2. Try the other scanner. If you've been scanning with the phone's camera app, scan from inside Authenticator instead, or the other way round. The two paths hand the request to the app differently.

    If it still closes, the more reliable route is a different phone (a recent Android or iPhone with the current Authenticator). A Verified ID lives in the wallet on the phone it was issued to, so on a new phone you'd most likely need to go through the AU10TIX step again. That takes time, but you have until December 2, so it's a safe fallback.

    On resetting the pending request: only Microsoft's verification team can do that from their side. Please don't post your request or account IDs here.

    Does the app also close when you use the other scanner?

    If the presentation goes through, please consider accepting it as the answer. If it keeps crashing, let me know and I'll be happy to keep helping.

    Reference:

    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.