Artifact Signing organization validation failed twice without explanation — requesting validation-team review

We need assistance from a Microsoft representative with two failed Public Trust organization identity-validation requests for 株式会社LYMO, a Japanese company.

The portal shows only Failed, without a rejection reason or actionable correction. We want to understand the cause before submitting another request.

Our setup:

• Service: Azure Artifact Signing, formerly Trusted Signing
• Validation type: Organization / Public Trust
• Country: Japan
• Resource region: Japan East
• Azure support plan: Basic

For the second request, the sequence was:

1. Microsoft requested one document from Category 1, which explicitly included domain purchase invoices.
2. We uploaded the domain invoice on September 29, 2026. It appears in the portal with a green check.
3. We received an email-verification link on October 3, stating that it would expire after seven days.
4. We completed the email confirmation on October 4, but the request was already Failed before confirmation.

We understand that successful document upload and email confirmation do not necessarily mean organization validation has passed. However, we cannot determine which check failed or what we should correct.

Could a Microsoft representative please arrange a review by the Artifact Signing identity-validation or vetting team and confirm:

1. The specific failed check and the recorded failure timestamp.
2. Whether the October 3 verification email belongs to the second request, and whether the October 4 confirmation was recorded against it.
3. Whether the domain invoice was accepted as evidence or merely uploaded successfully.
4. How many submission or appeal attempts remain, and whether creating another request would consume a final attempt.
5. Whether the existing request can be reconsidered or requires a corrected submission.

We also need a usable support route. Basic support blocks creation of this technical ticket. We are willing to consider Developer support, but this closely related case reports that purchasing Developer support still redirected the customer to Q&A.

Please confirm whether Developer support would allow an internal case for this issue. If identity-validation cases cannot be handled through paid Azure Support, please identify the team and channel that can investigate it.

We can provide both validation IDs, subscription and tenant details, email timestamps, and supporting documents through a private channel. We are requesting a review of the actual validation decision so that we can make an informed correction before another attempt.That thread gives us little reason to expect a timely resolution. I’d make this an explicit request for Microsoft to take ownership, with the support-access problem included.