Artifact Signing org validation Failed: Verified ID presentation "Result: Failed" although FaceCheck matched (South Korea sole proprietorship)

Because the primary-email verification link never arrived, first check mail filtering and, if the link still cannot be located, delete the failed validation and submit a new request; open an Azure support case before deletion if Microsoft should investigate or attempt to continue the existing request.

What the FaceCheck result means

A successful FaceCheck confirms only that the live selfie matched the identity-document photo. It does not establish that the complete Verified ID presentation or the subsequent organization validation succeeded. The Result: Failed activity could therefore represent a failure elsewhere in the presentation, but the available user-facing information cannot establish whether that failure directly caused the final Artifact Signing status. A matching Artifact Signing case recommends backend investigation to distinguish those stages.^1^

The normal organization workflow returns to In Progress after successful individual verification, then continues organization validation. The request becomes Completed or Failed only when the overall process finishes.^2^

Recommended action

1. Check the primary mailbox’s Junk/Spam folder.
2. Ask the email administrator to check filtering, specifically whether the mailbox:
   • accepts messages from external senders;
   • permits messages containing links;
   • had any firewall, quarantine, or security rule block the verification message.
3. Open Azure portal → Help + support → Create a support request if the exact failure reason or continuation of this request is important.
4. Include:
   • the Identity Validation ID;
   • subscription ID and Artifact Signing account/resource details;
   • UTC and KST timestamps;
   • screenshots of Verification successful, the failed Authenticator activity, and successful FaceCheck;
   • confirmation that no primary-email verification link arrived;
   • organization type, country, identifier type, and the Korean/English-name issue;
   • Microsoft Authenticator diagnostics if support requests them.

Do not post the subscription ID, registration number, address, or mailbox details publicly.

Matching cases with silent validation failures have been investigated from the backend and, in some instances, the existing request was subsequently completed successfully.^3^ This is possible but not guaranteed.

If the email cannot be found and support does not continue the existing request, the documented self-service remedy is to delete the failed validation and create a new one. For a new request, use a monitored primary mailbox on a domain owned by the business; it must accept external messages containing links.^4^

To delete it:

1. Azure portal → Artifact Signing account.
2. Objects → Identity Validation.
3. Select the failed request → Delete.
4. Review any associated accounts or profiles and confirm deletion.

Deletion is irreversible. The request is currently Failed, so it satisfies the documented requirement that deletion is available only when the validation is not In Progress.^5^

Whether to remove the Verified ID

Do not remove it merely because the organization request failed. Artifact Signing permits presentation of an existing valid, unexpired Verified ID.^4^

Delete it and issue a new one only if support identifies a credential/presentation problem, or a new attempt reports a name, address, or FaceCheck mismatch. Credential deletion is irreversible and requires completing issuance again.^6^

Korean organization name

For Public organization validation, Organization Name must be the legal business entity name, and the resulting certificate organization value cannot be customized.^2^^4^

Microsoft’s public Artifact Signing documentation does not specify whether a Korean sole proprietor must enter:

• the Korean registry name, 세이퍼; or
• an official English rendering, SAFER.

Use the name exactly as it appears on the authoritative record that the validation team will use. If the Korean registry’s legal entry is only 세이퍼, that is the safer default. If the National Tax Service’s English certificate officially identifies the same registered entity as SAFER, attach it to the support case and ask the validation team to confirm which representation must be entered before resubmitting. Do not assume that a self-created English translation is interchangeable with the registered legal name.

References

1. Artifact Signing organization validation fails after Face Check match ...
2. Quickstart: Set up Artifact Signing
3. Artifact Signing ID validation fails repeatedly 9afac007-6e27-4e93-84b1-34ac87fcdc90 - Microsoft Q&A
4. Artifact Signing FAQ
5. Renew or delete Artifact Signing Identity Validations
6. Use the Microsoft Authenticator with Verified ID