Artifact Signing: Verified ID submission fails with HTTP 500 / callback_failure / 403 after successful Face Check

Andi Rexha 0 Reputation points
2026-11-03T16:11:12.2+00:00

I am trying to complete organization identity validation for Azure Artifact Signing using an AU10TIX Verified ID and Microsoft Authenticator on an iPhone.

Face Check succeeds, but submitting the credential fails repeatedly.

The Authenticator logs show:

FaceCheckStatus=success

AppIntegrityStatus=success

CompleteRequestStatus=failed

FailureStage=response

Error chain:

HTTP 500 / internalServerError

→ callback_failure

→ HTTP 403 / Forbidden

Azure still shows “Action required”. Retrying produces the same error.

According to the account overview, the signing account is located in North Europe. Its resource group is located in West Europe. Azure’s automated support diagnosis mentions a West Europe deny policy, but it is unclear whether this is related to the current callback failure.

How can I complete the existing identity validation request? Could a Microsoft engineer investigate why the callback is rejected after a successful Face Check?

Diagnostic logs, timestamps and request IDs are available and can be provided through a private support channel. My Basic Support plan does not allow me to submit a technical support ticket.

Artifact Signing
Artifact Signing

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

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.