Azure Artifact Signing organization validation failed without reason after successful Verified ID

Quatro Bytes LLC 0 Reputation points
2026-08-03T06:03:03.59+00:00

My Public organization identity validation for QuatroBytes LLC changed to Failed without displaying a reason in the Azure portal.

The Microsoft Verified ID and Face Check were completed successfully. No additional-document request or specific rejection reason is visible.

Artifact Signing account type: Basic Region: East US Identity type: Public organization

Could the Artifact Signing team confirm why the organization validation failed and whether I should delete the failed validation and submit a new request?

Artifact Signing
Artifact Signing

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

0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Quatro Bytes LLC 0 Reputation points
    2026-08-03T06:05:31.1133333+00:00

    Thank you. I completed the entire verification flow, and Microsoft Authenticator shows that the Verified ID and Face Check were shared successfully with Artifact Signing. I did not miss an email verification link, and I did not receive any request for additional business documents. The Azure portal subsequently changed the organization validation to Failed without providing a reason.

    Could a Microsoft employee or Artifact Signing moderator review this case or route it to the validation team before I delete and recreate the request?

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-08-03T06:03:21.9466667+00:00

    A failed organization identity validation can occur even after Microsoft Verified ID and Face Check succeed. Those steps complete the individual identity portion, but the organization validation can still fail if the validation team can't determine that the submitted organization information is valid based on the information and documents provided.

    Supported next steps:

    1. Check whether the primary email verification link was missed or expired. That link expires after seven days. If it was missed or not selected in time, a new identity validation request must be created.
    2. If no email verification was missed, a failure means the validation team could not validate the organization from the submitted information. If additional documents were requested, only three upload attempts are allowed.
    3. Check Junk or Spam, confirm the primary email can receive external messages with links, and confirm mail filtering or security policies did not block the message.
    4. If the verification email cannot be found, delete the current identity validation request and submit a new one.
    5. For confirmation of the exact failure reason or onboarding help, contact Azure Support or post on Microsoft Q&A with the artifact-signing tag.

    About deleting and recreating the request:

    • Deleting an identity validation is supported only when it is not in In Progress state.
    • A deleted identity validation cannot be recovered.
    • Deleting an identity validation can affect linked certificate profiles and signing across accounts in the same subscription, so verify whether it is linked before deleting.
    • If the failed request is not linked and the failure was caused by a missed or expired email verification, creating a new identity validation request is the documented path.

    A related documented case also exists where, if an organization already has an identity validation tied to a different primary email address, support must be contacted to continue onboarding.

    AI-generated content may be incorrect. Read our transparency notes for more information.

    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.