Artifact Signing organization validation failed after two Verified ID sharing attempts

Florin Lazar 0 Reputation points
2026-11-10T21:56:06.3466667+00:00

I’m completing Public organization identity validation for Azure Artifact Signing. AU10TIX successfully issued a Verified ID, and it appears in Microsoft Authenticator.

I scanned the Artifact Signing QR code and tried sharing the credential twice. Authenticator Activity shows two entries for sharing the Verified ID with Artifact Signing, and both show “Result: Failed.” The verification page now says the link has already been used. After refreshing Azure Portal, the organization identity validation request shows “Failed,” with no reason or error code in the details.

Could a Microsoft moderator arrange a private channel for the Artifact Signing identity validation team to review the failed request? I can provide the Identity Validation ID and the attempt details privately. Please let me know whether the existing request can be reviewed or reset, or whether I need to submit a new request.

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

1 answer

Sort by: Most helpful
  1. AI answer

    2026-11-10T21:56:51.1066667+00:00

    Open an Azure Support request for the existing failed validation and provide the Identity Validation ID plus a Microsoft Authenticator incident ID; do not post those identifiers publicly or repeat the now-consumed sharing link.

    Open the private support case

    1. In the Azure portal, open Help + support.
    2. Select Create a support request.
    3. Choose the affected subscription and route the request to Azure Artifact Signing, using Identity validation as the problem area where available.
    4. State clearly:
      • This is Public organization identity validation.
      • AU10TIX successfully issued the Verified ID.
      • Two presentations to Artifact Signing appear in Authenticator as Result: Failed.
      • The presentation page now reports that the link has already been used.
      • The Azure portal request is Failed, without a reason or error code.
    5. Ask the validation team to:
      • Review the existing Identity Validation ID and failed presentation transactions.
      • Confirm whether that request can be reset or retriggered.
      • Confirm whether it must be deleted and replaced before you submit another request.

    Azure Support is the documented private assistance channel for Artifact Signing identity-validation cases.^1^ A similar failed Artifact Signing validation was reviewed and resolved by the validation team after receiving its validation ID.^2^

    Attach Authenticator diagnostics

    Generate an incident ID while the relevant activity remains available:

    1. Open Microsoft Authenticator.
    2. Select Send feedback from the top menu.
    3. Select Having trouble?
    4. Complete and send the form and logs.
    5. Record the resulting incident ID and add it to the private Azure Support case.^3^

    Also attach screenshots showing the two failed Activity entries and the portal’s failed status, with unrelated account information redacted.

    Do not create another request until support responds

    The documentation says that creating additional identity-validation requests for the same entity while one is in progress does not help, and requests cannot be expedited.^1^ Although this request now shows Failed, support should first determine whether its backend state can be reviewed or reset.

    If support confirms that replacement is required:

    1. Go to Artifact Signing account → Objects → Identity validations.
    2. Delete the failed request if support instructs you to do so.
    3. Select Organization → New Identity → Public.
    4. Enter the organization and representative details again and submit the new request.^4^
    5. Use the new verification flow rather than the already-used link.

    A replacement is specifically documented for missed or expired email verification and certain mismatch/Face Check failures, but the documentation does not establish that your failed Verified ID presentation has the same cause. Therefore, support review should precede deletion or resubmission.

    A Microsoft Q&A moderator may request details through a private mechanism, but Q&A is public by default. Do not place the Identity Validation ID, tenant/subscription identifiers, Authenticator incident ID, or unredacted screenshots in the thread.


    References

    1. Artifact Signing FAQ
    2. Artifact Signing Account Organization Identity validations failed - Microsoft Q&A
    3. Send Microsoft Authenticator logs and get an incident ID
    4. Quickstart: Set up Artifact Signing
    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.