Artifact Signing organization identity validation: AU10TIX "Oops! Something went wrong", now "No attempts remaining"

Azure Support should investigate the exhausted attempt; Microsoft does not document a self-service reset, so support must determine whether the existing request can be restored or must be recreated.

Open an Azure support request

1. In the Azure portal, open Help + support and select Create a support request.
2. Choose the closest available Artifact Signing or identity validation category.
3. State that this is a Public Organization identity validation on the Basic tier and that:
   • AU10TIX ended with “Oops! Something went wrong”.
   • No Verified ID was issued to Microsoft Authenticator.
   • The verification page now reports “No attempts remaining.”
   • The request expires at 10:22 PM EST on November 8, 2026.
4. Ask support to:
   • Investigate the AU10TIX/Verified ID issuance failure.
   • Determine whether attempts can be restored on the current request.
   • If restoration is unavailable, confirm whether the current request should be deleted and recreated.
5. Provide these details only through the support case’s private channel:
   • Identity Validation request ID
   • Subscription ID
   • Artifact Signing account name and region
   • Organization name
   • Primary email used for the request
   • Request creation time and failed-attempt timestamps, including time zone
   • Screenshots of both messages
   • Browser/device versions

Artifact Signing’s documented support routes are Azure Support and Microsoft Q&A with the Artifact Signing tag. Microsoft also warns that creating additional requests for the same entity while one is in progress does not help and that requests cannot be expedited.^1^ Similar exhausted AU10TIX/Verified ID cases are being directed to Microsoft-side investigation rather than a signing-client repair.^2^

Attach an Authenticator incident ID

The Artifact Signing FAQ instructs users contacting support about Authenticator/Verified ID technical errors to submit Authenticator logs and include the resulting incident ID.^1^

In Microsoft Authenticator:

1. Open the app.
2. Select Send feedback from the top menu.
3. Select Having trouble?
4. Submit the form and logs.
5. Record the generated incident ID and add it to the Azure support request.^3^

Retry only after support restores or replaces the request

Because the current page says “No attempts remaining,” changing browsers cannot unlock it. If support restores the attempts or directs creation of a fresh request:

• Use a different supported browser, since every previous attempt was in Firefox.
• Fully close and relaunch Microsoft Authenticator before starting.
• If practical, try another phone or network.
• Use the same primary email address entered in the identity-validation request.

These are the documented technical-error measures, but they apply only once a usable attempt is available.^1^

There is no documented CLI completion path: Artifact Signing identity validation can be completed only through the Azure portal.^4^ Presenting the QR code is an alternative only if there is already a valid, unexpired Verified ID; no Verified ID was issued in this case.

References

1. Artifact Signing FAQ
2. Azure Artifact Signing organization identity validation blocked by ...
3. Send Microsoft Authenticator logs and get an incident ID
4. Quickstart: Set up Artifact Signing