코드, 문서 및 애플리케이션을 디지털 방식으로 서명할 수 있도록 지원하는 완전 관리형 종합 서비스입니다. (이전의 신뢰할 수 있는 서명)
Artifact Signing: Verified ID submission fails with HTTP 504 after Face Check succeeds; link now already used
We are completing organization identity validation for Azure Artifact Signing Public Trust in Korea Central.
A newly issued AU10TIX Government Issued ID - GLOBAL credential has the correct legal name. Microsoft Authenticator on iOS successfully completes Face Check, but submitting the presentation fails.
Sanitized log summary:
FaceCheckStatus=success
AppIntegrityStatus=success
Operation=PostPresentationResponseOperation
HTTP status=504
CompleteRequestStatus=failed
FailureStage=response
The failure occurred on November 16, 2026 at approximately 11:21 UTC. An earlier QR retry returned HTTP 404 notFound while fetching a presentation request. A newly opened QR then reached Face Check successfully but failed with 504 during submission.
Azure still shows Action required. Reopening the verification link from the current Azure request now displays: "Sorry, this link has been used already. Please return to Artifact Signing to review the status of your request." This prevents another submission attempt.
How can Microsoft reset or reissue the presentation request while preserving the valid Verified ID and signing account? Could the backend have received the response despite the timeout, and how can its status be reconciled?
The Azure Basic support plan blocks technical support case submission. Please advise a supported escalation route for this onboarding failure. Account identifiers, correlation IDs and full logs can be supplied through an official private support channel if needed. No personal identity documents or sensitive logs are attached.