artifact-signing

Sławomir Głodzik 0 Reputation points
2026-09-09T19:31:23.4133333+00:00

My organization identity validation failed after I submitted all requested documents. The details panel shows no failure reason and no corrective action.

The primary email uses gmail.com. Could you confirm whether this caused the rejection, or identify the exact information that could not be verified?

Please specify the correction required and confirm how to resume verification. If a company-domain email is required, please explain how to change it for this organization without triggering a duplicate identity validation conflict.

My Azure plan does not include technical support, so I cannot open a technical support ticket. Please route this issue to the Artifact Signing identity validation team. I need an actionable rejection reason and instructions for correcting or reopening my application.

Artifact Signing
Artifact Signing

A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)

0 comments No comments

1 answer

Sort by: Most helpful
  1. SHOUMIK CHAKRAVARTY 575 Reputation points
    2026-09-10T02:28:46.8466667+00:00

    The gmail.com address is almost certainly your answer. Organization validation requires the primary email to be on a domain the business owns. From the Quickstart:

    "Enter a monitored email address on a domain owned by the legal business entity."

    The secondary email has to be on that same domain. Gmail doesn't satisfy either, and it isn't something the validation team can waive, since the certificate is asserting your organization's identity.

    The fix is a mailbox on a domain your business owns, then a fresh validation request using it. Whether you can simply start a new one, or whether the failed request has to be cleared first, I'm not certain. The FAQ does say that when a validation already exists under a different primary email you need to contact support to continue onboarding, but that's written for existing requests rather than failed ones. Try the new request first, and if it's blocked, that's when the support route applies.

    On the support plan, you don't need one for this. The Quickstart says identity validation issues go through Microsoft Q&A rather than a support ticket, so you're in the right place. I'm a volunteer rather than a moderator so I can't route it, but a Microsoft moderator picking up this thread is the path if the new request doesn't work.

    Help make this community better for everyone: if this answer resolved your issue, please accept it or leave an upvote. If not, share more details in a comment so we can continue the discussion and find the right solution.

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.