Artifact Signing identity validation failed twice at the Verified ID step (Authenticator error 500, Unexpected session payload

Ragav Yarasi 0 Reputation points
2026-11-13T06:00:41.7033333+00:00

Hi,

We're trying to complete Public identity validation for Artifact Signing for our company, Clikkin LLC (a Wyoming LLC, United States). It has failed twice, both times at the Verified ID step, and the portal doesn't show a reason.

What happened on the second attempt:

  1. Submitted a new identity validation request on 13 Nov 2026. Status went to Action Required.
  2. Received the "Action required: Complete your Artifact Signing identity validation" email and followed the link.
  3. Completed the check in Microsoft Authenticator. Authenticator showed success.
  4. Immediately after, Authenticator returned this error: Error Code: 500 Error Details: Unexpected session payload Timestamp: 2026-11-13T05:16:13.217Z
  5. The email link now says "Sorry, this link has been used already," and the request status changed to Failed.

The first attempt also failed at the verification step, so both failures happened at the same point, not on the organization details or documents.

We have one attempt left and don't want to use it until we know what went wrong. Could someone from the Artifact Signing team check the two requests on your side and tell us:

  • why they failed;
  • whether the latest one can be reopened or reset; and
  • if not, what we should do differently before submitting again.

I can share the identity validation IDs, subscription ID, Request-ID and correlation ID by private message.

Thanks,

Ragav
Clikkin LLC

Artifact Signing
Artifact Signing

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

0 comments

2 answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-11-13T06:01:56.7266667+00:00

    Do not use the third attempt yet; open an Azure support request for Artifact Signing and provide the failed validation IDs plus the Authenticator incident ID so Microsoft can diagnose the consumed Verified ID sessions and determine whether the latest request can be reset.

    The combination of a successful Authenticator check followed by HTTP 500 “Unexpected session payload” matches reports in which failure occurs while the Verified ID presentation response is being processed, after the device-side check succeeds.^1^ The message does not expose the definitive backend rejection reason, so only the service team can confirm why each request failed.

    Open the support case

    1. In the Azure portal, open the affected Artifact Signing account.
    2. From its resource menu, select Help → Support + Troubleshooting.
    3. Complete the suggested diagnostics, then select Create a support request.^2^
    4. Route the issue to Artifact Signing and describe it as:
      • Public Organization identity validation
      • Microsoft Authenticator/Verified ID presentation fails after success
      • HTTP 500: Unexpected session payload
      • Two requests failed at the same stage
      • Final attempt intentionally not submitted

    Artifact Signing’s FAQ identifies Azure Support as the appropriate assistance channel. It also says that creating additional validation requests for the same entity does not help while one is in progress and that requests cannot be expedited.^3^

    Ask support explicitly to:

    • Retrieve the server-side failure reason for both identity-validation requests.
    • Confirm whether the second request can be reset, reopened, or re-triggered.
    • Confirm whether the two technical failures count against the three-attempt allowance.
    • Preserve or restore the remaining attempt while the incident is investigated.
    • State any specific correction required before another submission.

    The public documentation does not describe a self-service reopening or reset procedure for this failed state. Similar unexplained Artifact Signing failures have required the validation team to inspect the request and complete or resolve it from their side.^4^

    Submit Authenticator diagnostics

    On the phone that encountered the error:

    1. Open Microsoft Authenticator.
    2. Open the top menu and select Send feedback.
    3. Select Having trouble?
    4. Complete and send the form with logs.
    5. Record the resulting incident ID.^5^

    Add the following to the private support case—not to the public Q&A post:

    • Both Identity Validation IDs
    • Artifact Signing account and resource name
    • Subscription and tenant IDs
    • Request ID and correlation ID/MS-CV, if shown
    • Authenticator incident ID
    • Exact UTC timestamp: 2026-11-13T05:16:13.217Z
    • Screenshot of the 500 error and failed portal status
    • Confirmation that Authenticator displayed success immediately before the error
    • Confirmation that the email URL now reports that it has already been used
    • Phone OS and Authenticator version

    Verified ID errors include fields such as requestId, timestamp, mscv, and an innererror; these identifiers are intended to support troubleshooting of the underlying failure.^6^

    If support authorizes a final retry

    Do not reuse the consumed email URL. If support says the failed request cannot be reset and authorizes a new request, apply the official technical-error precautions before using the new link:

    • Fully close every Authenticator instance and relaunch it.
    • Update Authenticator to the latest Android/iOS release.
    • Use a cleared browser session or another browser.
    • Use a stable connection without a VPN or proxy.
    • If available, use another supported phone.^3^

    These steps reduce client/session variables but do not explain the two existing failures. Wait for the backend diagnosis before deleting the failed request, removing the Verified ID, or consuming the final attempt.

    References

    1. Artifact Signing identity validation fails after successful Face Check ...
    2. Create an Azure support request
    3. Artifact Signing FAQ
    4. Artifact Signing ID validation fails repeatedly 9afac007-6e27-4e93-84b1-34ac87fcdc90 - Microsoft Q&A
    5. Send Microsoft Authenticator logs and get an incident ID
    6. Request Service API error codes
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Ragav Yarasi 0 Reputation points
    2026-11-13T06:18:42.9433333+00:00

    The issue remains unresolved.

    I've sent Microsoft Authenticator logs for the failed attempt. Incident ID: 5SKY8HTA. Happy to share the validation IDs, subscription ID, Request-ID and correlation ID by private message.

    Was this answer helpful?

    0 comments

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.