Azure Artifact Signing: Verified ID presentation fails with HTTP 504/404 after successful identity verification

Open an Azure Support request for the existing failed validation and ask that it be routed to the Artifact Signing identity-validation team for joint investigation with Microsoft Entra Verified ID; do not create a fourth validation request unless Support explicitly requests one.

Open the support case

1. In the Azure portal, open the affected Artifact Signing account.
2. Select Support + Troubleshooting under Help.
3. Complete the diagnostics, then select Create a support request.
4. Choose Technical as the issue type and select the Artifact Signing service/category available in the form.
5. Describe the failure sequence precisely:
   • Organization / Public identity validation
   • AU10TIX government-ID and facial verification completed
   • Government Issued ID credential successfully issued in Authenticator
   • Credential presentation returned HTTP 504 networking_error or HTTP 404
   • Artifact Signing validation subsequently changed to Failed
   • Three validation attempts and credential reissuance already completed
6. Explicitly request:
   • Backend lookup of the Verified ID presentation request/session.
   • Correlation between the Artifact Signing validation transaction and Entra Verified ID presentation transaction.
   • Confirmation whether the presentation request expired, was consumed, or could not be resolved.
   • A backend reset or recovery of the current validation, if supported, rather than another complete identity-proofing attempt.
   • Escalation between the Artifact Signing and Microsoft Entra Verified ID engineering teams.

The Artifact Signing FAQ directs unresolved identity-validation problems to Azure Support and warns that creating additional requests for the same entity while one is in progress does not help.^1^ A closely matching Artifact Signing case—repeated validation failure after successful identity checks—was resolved after Support obtained the validation ID and account details and worked with the internal team.^2^

Azure documents the resource-context route as Artifact Signing account → Support + Troubleshooting → Create a support request. Technical support requires an applicable support plan.^3^

Attach the transaction evidence privately

Provide these values as text—not only screenshots:

• Artifact Signing account and Azure region.
• Tenant and subscription identifiers.
• All three identity-validation request IDs, identifying the latest request.
• Authenticator/Verified ID correlation, request, session, or trace IDs.
• Exact UTC timestamps for:
  • QR code or presentation-link generation.
  • Credential presentation.
  • HTTP 504 and HTTP 404 responses.
  • Portal transition to Failed.
• Authenticator version, phone OS/version, browser/version, and network type.
• Screenshots of the issued credential and errors, with sensitive identity data redacted.
• Authenticator feedback submission time or reference, so Support can correlate the diagnostic upload.

Upload logs only through the private support case. The support-request form permits logs or a compressed archive and can authorize collection of advanced diagnostic information.^3^ Do not publish tenant, subscription, validation, or correlation IDs in Microsoft Q&A.

One remaining controlled client test

Since recreating requests and reissuing the credential have already failed, do not repeat those actions. If these client-side conditions have not already been tested, perform one controlled presentation attempt only if Support provides a fresh or confirmed-valid session:

1. Update Microsoft Authenticator.
2. Force-close every Authenticator instance and reopen it.
3. Use another browser or a cleared browser session.
4. Disable VPN/proxy and use a stable connection; switching between Wi-Fi and mobile data is also a valid isolation test.
5. If available, use another supported phone.

These are Microsoft’s documented checks for technical failures during Authenticator/Verified ID identity validation.^1^ Authenticator guidance also recommends submitting logs through Send feedback after those checks, which has already been done here.^4^

A generic Artifact Signing 404 signing-error mitigation about configuration or firewall rules should not be treated as the resolution here: that FAQ entry concerns signing errors, whereas this failure occurs during Verified ID presentation. Your successful account creation, role assignment, and credential issuance also make repeating RBAC setup inappropriate. A completed identity validation is nevertheless required before creating the corresponding certificate profile.^5^

References

1. Artifact Signing FAQ
2. Artifact Signing ID validation fails repeatedly 9afac007-6e27-4e93-84b1-34ac87fcdc90 - Microsoft Q&A
3. Create an Azure support request
4. Troubleshoot problems with Microsoft Authenticator | Microsoft Support
5. Artifact Signing resources and roles