Support Request: Artifact Signing organization validation remains In Progress after Face Check succeeds; Authenticator response fails HTTP 504

RaidCore 0 Reputation points
2026-10-24T16:36:23.2933333+00:00

When did the problem start?

Description

We are completing Organization / Public identity validation for RaidCore, a registered Dutch business (KVK 42141295). The Azure portal still shows In Progress on 23 October 2026. We have attempted the Microsoft Authenticator verification on two separate days. Face Check succeeds and the desktop verification page reports success, but Authenticator fails when submitting the final response. These are user-reported diagnostic details; please verify them against your backend telemetry.

Affected identity validation: e65a062a-01d1-4a46-af1a-b0442ffeab96. A second organization validation, 44ef2a15-1391-4d1a-97cc-f26787dfef19, is also currently In Progress. Please advise which existing request should be retained and whether the original can resume, rather than requiring another new request.

Authenticator diagnostic event:

20 October 2026, 08:25 UTC (10:25 Amsterdam).

FaceCheckStatus=success;

AppIntegrityStatus=success;

failed operation=PostPresentationResponseOperation;

HTTP 504; error=networking_error;

FailureStage=response;

CompleteRequestStatus=failed;

correlation vector=VcVI9c3YQuqnt8V1ZPrPZg.3.

Account: raidcoresigning; resource group: raidcore-signing; subscription: a08d183a-b68a-4c7e-b520-cb37ff079152; current account region: North Europe. An earlier failed account creation attempt in West Europe was denied by policy sys.blockwesteurope. Azure's automated troubleshooting keeps citing that earlier Microsoft.CodeSigning/codeSigningAccounts/write denial, but it has not established any connection to the later Verified ID presentation failure or the current North Europe account.

Please investigate:

(1) actual processing status and whether the successful verification/presentation reached the backend;

(2) why the final response returned 504 after Face Check and app integrity success;

(3) whether any policy actually blocked the identity-validation transaction, identifying the exact operation/policy/timestamp if so;

(4) correct subscription/account association;

(5) supported recovery or resumption of the existing validation without deleting it or restarting identity proofing. Please route to the Artifact Signing / Verified ID validation team as appropriate.

Impact: onboarding is blocked and we cannot create/use a Public Trust signing certificate for our software.

This is an onboarding issue, not an existing production outage.

Artifact Signing
Artifact Signing

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

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Zoha Fatima 675 Reputation points
    2026-10-27T17:08:09.0833333+00:00

    Hi RaidCore,

    The HTTP 504 error during PostPresentationResponseOperation, despite successful Face Check and app integrity checks, suggests a failure during the final response submission. However, only Microsoft's backend logs can confirm whether the presentation reached the validation service.

    I recommend updating Microsoft Authenticator, closing and reopening the app, and retrying on a stable network without a VPN. Since both requests remain In Progress, avoid creating additional validation requests.

    If the issue persists, ask a Microsoft Q&A moderator to route this to the Artifact Signing team. Provide the correlation vector, UTC timestamp, HTTP 504 details, and validation IDs privately. Request confirmation of the current validation status and supported recovery options.

    Reference: https://learn.microsoft.com/en-us/azure/artifact-signing/faq

    Thank you, and feel free to respond back for more assistance.

    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.