Azure Artifact Signing organization identity validation failed after verification link was already used

ShellieSoftwareTools 0 Reputation points
2026-08-31T23:55:21.92+00:00

I am creating a Public organization identity validation for Azure Artifact Signing in Japan.

The first request changed to Action Required. I completed the identity verification flow, but reopening the verification page now shows: “No Access — this link has been used already.”

I then created a new Public organization identity validation request with corrected business details. It initially showed In Progress but later changed to Failed. The Azure portal and notifications do not show a failure reason.

Could the Artifact Signing team clarify whether the failed request should be deleted before another request is created, whether a fresh verification flow can be issued or reset, and which fields or documents should be checked before resubmitting?

Subscription IDs, validation IDs, email addresses, business identifiers, and street addresses are intentionally omitted from this public post. I can provide them through a private Microsoft support channel if required.

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. AI answer

    2026-08-31T23:55:38.32+00:00

    Yes. Based on the documented behavior, the current failed request should not be reused.

    1. If the email verification link was already used, that link cannot be resent for the same request.
      • If the verification link expired or was missed, a new identity validation request is required.
      • If email validation shows Failed and the verification email was not effectively usable, create another identity validation request.
    2. Creating multiple requests for the same entity while one is already in progress does not help.
      • Guidance explicitly states that creating more identity validation requests for the same entity that is in progress does not help.
      • If another identity validation is required for the same organization but with a different primary email address, support must be contacted to continue onboarding.
    3. Before resubmitting, verify the request fields carefully because changes after creation require a new request. Check these fields in the Azure portal:
      • Organization Name: legal business entity for public identity validation
      • Website url: must belong to the legal business entity
      • Primary Email: monitored mailbox on a domain owned by the legal business entity; the link expires in seven days; mailbox must accept links from external senders
      • Secondary Email: different from primary; for organizations, domain must match the primary email domain; must accept external emails with links
      • Business Identifier
      • Street, City, Country/Region, State/Province, Postal code: business address of the legal business entity
      • First Name and Last Name: must exactly match the government-issued ID of the individual completing individual identity validation
    4. If more documentation is requested, only three upload attempts are allowed. Documents should meet these checks:
      • issued within the previous 12 months
      • expiration date, if present, must be at least two months in the future
      • official business documents should list the company name and address exactly as provided in the identity validation request
      • domain registration or renewal documentation should list the entity, contact name, and relevant domains included in the request
    5. If the request failed after the verification flow was completed, support is the correct next step for clarification.
      • For Artifact Signing identity validation questions, use Azure Support or Microsoft Q&A with the artifact-signing tag.
      • If the issue is specifically with the AU10TIX identity-verification experience, contact AU10TIX Support directly.
    6. If the original request is still merely In Progress or Action Required, avoid creating additional duplicate requests for the same entity. If the request is already Failed, a new request is required because the existing verification link cannot be reset or resent on that same request.
    7. If the failure involved email verification specifically, also confirm:
      • Junk or Spam folder was checked
      • the mailbox accepts messages from external senders
      • emails containing links are not blocked by firewall, security, or mail filtering policies
      • the email address is not a distribution list when that restriction applies

    References:

    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.