Azure Artifact Signing – Verified ID presentation consistently fails with HTTP 504 Gateway Timeout

Because the validation is already Failed, perform one controlled clean retry: update and restart Authenticator, delete the failed validation, remove its associated Verified ID from Authenticator, and create one new validation request.

A matching Artifact Signing report associates the Face Check-success/HTTP-504 flow with a Microsoft-side bug reported fixed on October 28, 2026; a fresh transaction is therefore appropriate, while another 504 should be treated as a potentially stuck transaction or regression and escalated immediately.^1^

Perform one clean retry

1. Prepare Authenticator and the connection
   • Update Microsoft Authenticator from the iOS App Store.
   • Force-close every open Authenticator instance, then reopen it.
   • Disable any VPN or proxy and use a stable connection.
   • Clear the browser cache or use another browser.
   • If available, use another phone.
   These are Microsoft’s documented first-line checks for technical failures during Artifact Signing validation with Authenticator and Verified ID.^2^
2. Delete the failed validation
   • Azure portal → Artifact Signing account → Objects → Identity Validation.
   • Select the failed request and choose Delete.
   • Review the displayed account/profile associations, then confirm deletion.
   The request must not be In Progress, and the user performing this action needs the Artifact Signing Identity Verifier role. Deletion is irreversible and can affect linked certificate-profile renewal; inspect the dependency list before confirming.^3^
3. Remove the corresponding credential from Authenticator
   • Open Authenticator.
   • Select the Verified ID used for this attempt.
   • Open its options and remove/delete that Verified ID.
4. Create exactly one replacement request
   • Azure portal → Artifact Signing account → Objects → Identity validations.
   • Select Organization → New Identity → Public.
   • Use the same intended legal-entity details, ensuring the representative’s first and last names exactly match the government-issued identification.
   • Complete the new Authenticator presentation and wait for the portal status.
   A successful individual step returns the organization request to In Progress while the remaining validation continues; final success is Completed.^4^

Do not create concurrent requests. Microsoft states that additional requests do not help while an identity validation is already in progress.^2^

If the clean retry also returns HTTP 504

Submit the Authenticator diagnostics immediately after the failure:

1. Authenticator → Send feedback.
2. Select Having trouble?
3. Submit the form and logs.
4. Record the resulting incident ID.^5^

Then open an Azure support request from the affected resource:

1. Artifact Signing account → Support + Troubleshooting.
2. If the suggested resolutions do not apply, select Create a support request.
3. Route it to Azure Artifact Signing and describe it as:
   “Organization identity validation: Face Check succeeds, Verified ID presentation POST returns HTTP 504.”

Include privately in the support case:

• Failed and replacement Identity Validation IDs
• Authenticator incident ID
• Exact failure time in UTC, including time zone
• Subscription and tenant identifiers
• Artifact Signing account, region, and endpoint
• iOS and Authenticator versions
• The diagnostic sequence:
  • FaceCheckStatus=success
  • DIDPresentationAllowed
  • PostPresentationResponseOperation
  • HTTP statusCode=504
  • CompleteRequestStatus=failed
  • FailureStage=response
  • WalletLibrary.VerifiedIdNetworkingError:1
• Confirmation that one clean retry was performed without VPN/proxy
• Screenshots or exported logs with unnecessary personal data removed

Azure Support can collect files and diagnostic information and route the case to the relevant engineer.^6^ Similar repeatedly failed Artifact Signing validations have required the validation ID and account details for backend investigation and were subsequently completed by the validation team.^7^

Error interpretation and alternatives

• FaceCheckStatus=success establishes that Face Check passed, but the subsequent 504 does not by itself identify whether the timeout occurred in the Verified ID endpoint, a downstream validation component, or transaction state.
• No public error-code reference in the available Artifact Signing documentation defines WalletLibrary.VerifiedIdNetworkingError:1 more precisely.
• There is no documented customer-accessible manual or CLI bypass for Artifact Signing identity validation. Microsoft documents identity validation as an Azure portal-only operation.^4^
• Check Azure Service Health for a subscription-specific Artifact Signing or identity advisory, but the absence of an advisory does not rule out a transaction-specific failure.^8^

References

1. Azure Artifact Signing: Verified ID presentation fails with HTTP 504/ ...
2. Artifact Signing FAQ
3. Renew or delete Artifact Signing Identity Validations
4. Quickstart: Set up Artifact Signing
5. Send Microsoft Authenticator logs and get an incident ID
6. Create an Azure support request
7. Artifact Signing ID validation fails repeatedly 9afac007-6e27-4e93-84b1-34ac87fcdc90 - Microsoft Q&A
8. Azure Service Health portal