A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
Open an Azure Support request before submitting again, because only Microsoft can identify the undisclosed reasons for failures #3 and #4 and confirm whether the three-attempt limit now prevents further onboarding.
Request the backend findings and attempt-status decision
In the Azure portal, go to Help + support → Create a support request and route it to Artifact Signing / identity validation. Microsoft directs unresolved identity-validation cases to Azure Support; repeated submissions do not expedite validation.^1^
Provide privately in the ticket:
- Subscription ID and Artifact Signing account/resource name.
- All four identity-validation IDs.
- Submission and failure timestamps, including the time zone.
- Screenshots showing Verification successful and the subsequent Failed status.
- The emails or portal messages requesting additional documents.
- The legal name, business identifier, registered address, website, and email domains entered in each attempt.
- Whether each attempt used the registered headquarters or Seoul branch address.
Ask Support to answer these points explicitly:
- What backend rejection reason and validation stage applied to requests #3 and #4?
- Did the successful Verified ID step complete only the representative’s personal verification, with organization verification failing afterward?
- Which legal-name script/transliteration and address representation should match the Korean source used for validation?
- Has the organization exhausted its permitted attempts?
- Is another request permitted under the published policy, and if so, what exact correction or document is required?
Do not post the subscription ID, documents, or unredacted emails publicly.
Also verify the date for request #4 before filing: November 10, 2026 is later than today, November 8, 2026. Correcting that timestamp will help Support locate the relevant logs.
The attempt limit may already apply
Microsoft’s FAQ states that when extra documents were required, all three attempts are considered exhausted and onboarding cannot proceed further. It also states that when a non-email failure means the validation team could not determine the organization’s identity from the supplied information, further documentation does not guarantee onboarding.^1^
Because your first attempt requested documents and you subsequently made several attempts, ask Support to confirm whether this restriction applies before creating another request. There is no published self-service reset or guaranteed reconsideration path.
If Support confirms that Microsoft could not validate the entity and that no further attempt is available, the documented outcome is that onboarding cannot continue; Microsoft recommends deleting the unused Artifact Signing account to avoid further billing.^1^
If Support authorizes another submission
Use one consistent representation that matches the authoritative registry record and Support’s instructions:
- Organization name: the legal business entity name—not a brand or former sole-proprietorship name.
- Business identifier: the corporation’s identifier.
- Address: the corporation’s registered business address. Do not switch between headquarters and branch addresses unless Support directs you to do so.
- Website: a site belonging to the legal entity.
- Primary email: a monitored mailbox on the entity-owned domain that accepts messages and links from external senders.
- Secondary email: different from the primary mailbox but on the same domain.
- Representative name: exactly as shown on the government-issued ID used for Verified ID.
These are the documented organization-validation field requirements.^2^
Prepare—but do not assume these are mandatory unless requested:
- Current corporate-registry certificate.
- Current English-language business-registration certificate.
- Evidence connecting the representative to the corporation.
- Evidence connecting the corporation to the website/domain.
- Documents issued within the past 12 months; prior cases have specifically requested recent official proof.^3^
Company age and South Korean eligibility
South Korea is explicitly supported for Public Trust organization validation.^2^ The published prerequisites do not state a minimum corporate age or minimum tax-history period. Therefore, the February 2026 incorporation date cannot by itself be identified as the rejection reason from the available portal status.
The former sole proprietorship’s history should not be substituted for the corporation’s details unless Support specifically confirms that it is relevant evidence. The entity being validated is the corporation named in the request.
References