South Korea: Artifact Signing organization validation failed after successful Verified ID - request backend review

Do not delete or resubmit the failed identity validation yet; open an Azure Support request and ask the Artifact Signing validation team to inspect the existing Identity Validation ID and backend rejection details.

Request the backend review

1. In the Azure portal, go to Help + support → Create a support request.
2. Select the affected subscription and route the request to Artifact Signing / identity validation as closely as the available issue categories allow.
3. Provide these details privately in the ticket:
   • Identity Validation ID
   • Artifact Signing account name and resource ID
   • Subscription ID and tenant ID
   • Region and SKU
   • Organization’s exact registered legal name and country
   • Submission and failure timestamps, including the time zone
   • Screenshot of the failed status and the failure email
   • Confirmation that AU10TIX, Face Check, and Verified ID sharing completed successfully
   • The address-format limitation and both address forms:
     • the jibeon address submitted
     • the road-name address on the business registration
   • The identifier type entered as Tax ID
4. Ask support to:
   • retrieve the backend rejection reason;
   • confirm whether the submitted Korean address and business identifier matched the expected authoritative records;
   • determine whether the existing request can be reviewed or reset;
   • specify exact corrections before authorizing a new submission.

The Artifact Signing FAQ identifies Azure Support and Microsoft Q&A with the artifact-signing tag as the supported assistance channels.^1^ A closely matching case—organization verification failing after successful personal identity checks with no portal reason—was resolved after a support case supplied the Identity Validation ID and account details for backend investigation.^2^

This Q&A forum cannot directly inspect backend logs or route the request internally, so the actual failure reason cannot be determined from the visible status alone.

Why the successful Verified ID does not settle the request

The AU10TIX and Verified ID flow verifies the representative’s personal identity. The organization request still undergoes separate legal-entity validation, so successful sharing does not mean the overall organization validation has passed.

The “link has been used already” message is consistent with the verification link having been consumed; do not repeat that completed step unless support explicitly resets or replaces the request.

South Korea is supported for Public Trust organization onboarding, and Korea Central is a supported Artifact Signing region.^3^ The supplied country and region therefore do not, by themselves, establish the failure reason.

Do not delete before support responds

Deletion is permanent: a deleted identity validation cannot be recovered. It can also affect linked certificate profiles across Artifact Signing accounts in the subscription, and reviewing those links requires suitable read access.^4^

Do not delete the Artifact Signing account as a workaround either. Identity validations are scoped at the subscription level and remain available even when an Artifact Signing account is deleted.^3^

Only create a replacement request if support confirms that the failed record cannot be reviewed or reset and tells you what must change. Multiple requests for the same entity do not help, and onboarding with another primary email may itself require support.^1^

What to change if resubmission is authorized

There is not enough published guidance to conclude that the 30-character street field, use of the jibeon address, or use of the Korean business registration number as the Tax ID caused this failure. Do not guess between address formats.

Before resubmitting, obtain written direction from support on:

• the required Korean address representation;
• whether it must exactly match the business registration;
• the expected legal-name formatting, including punctuation and corporate suffix;
• the accepted business-identifier type and formatting;
• whether an organization-domain email is required;
• whether supporting documents are needed and how recently they must have been issued.

If support requests organization-association documents, provide official documents that clearly connect the representative to the organization and satisfy the requested date range. Similar Artifact Signing cases have required official documents dated within the previous 12 months.^5^

References

1. Artifact Signing FAQ
2. Artifact Signing ID validation fails repeatedly 9afac007-6e27-4e93-84b1-34ac87fcdc90 - Microsoft Q&A
3. Quickstart: Set up Artifact Signing | Microsoft Learn
4. Renew or delete Artifact Signing Identity Validations
5. Identity validation failed - Microsoft Q&A