Azure Artifact Signing – Identity verification fails after successful Face Check (HTTP 500, Unexpected session payload)

I'm attempting to complete organisation identity validation for Azure Artifact Signing (formerly Trusted Signing) for an Australian company that is already a Microsoft partner.

The Artifact Signing resource was successfully provisioned in East US under a Pay-As-You-Go subscription. Azure diagnostics indicate that the resource is healthy, with no provisioning or permission issues.

However, organisation identity validation has been rejected.

During the Microsoft Authenticator Verified ID process on iOS, Face Check appears to complete successfully, but the subsequent credential presentation fails with an HTTP 500 error.

Error details

The Authenticator diagnostic logs show:

FaceCheckStatus=success

AppIntegrityStatus=success

LinkedDomainsStatus=verified

However, the subsequent presentation request fails:

HTTP 500 – internalServerError

  └── claimValidationError

       └── facecheckSessionFailure

            └── Unexpected session payload

The logs also contain:

StatusCheck: status list token failed validation (missingExpiry)

StatusCheck: no verifiable status list found

StatusGate: status=unknown

The credential is recognised, and Face Check completes successfully on the device. The failure occurs when the presentation is submitted to Microsoft's backend.

Azure troubleshooting results

Microsoft's automated troubleshooting indicates:

• The Artifact Signing account was created successfully in East US.
• Role assignments completed successfully.
• No Azure resource errors or warnings were detected.
• The organisation identity-validation request was rejected.
• No specific rejection reason is available in the Azure diagnostics.

The troubleshooting guidance suggests checking business registration information, email verification and supporting documents, but doesn't explain the specific Verified ID error.

Questions

1. Has anyone encountered facecheckSessionFailure: Unexpected session payload during Artifact Signing identity validation?
2. Is this a known issue with Microsoft Authenticator, Entra Verified ID or the Artifact Signing validation service?
3. Could the missingExpiry status-list validation warning be contributing to the failure?
4. Is there a way to reset or retry the individual identity-verification step without restarting the entire organisation-validation process?
5. Has anyone successfully resolved this issue, particularly for an Australian organisation?

I'm using Microsoft Authenticator on iOS, and the Face Check itself consistently reports success.

Any advice or experience with this issue would be appreciated.