Artifact Signing: unable to complete organization identity verification

The existing organization-validation request cannot be edited to change its primary email or identity details; open a private Azure Support case and ask Artifact Signing support to correct or continue the existing onboarding record without creating another request.

Open the support case

1. In the Azure portal, open Help + support.
2. Select Create a support request.
3. Choose the affected subscription and identify Artifact Signing as the service.
4. Describe the issue as an existing Public Trust organization identity validation stuck in “Action Required” because the verification flow is associated with a personal Microsoft account rather than the intended organizational identity.
5. Explicitly request that support:
   • Preserve and investigate the existing validation request.
   • Determine whether its identity association can be corrected server-side.
   • Update or otherwise resolve the primary-email association.
   • Avoid creating a duplicate identity-validation request or Artifact Signing account.
6. Supply the following only through the private support case:
   • Subscription ID.
   • Artifact Signing account and resource group.
   • Identity-validation/request ID.
   • Correlation or error ID, if displayed.
   • Current primary email and intended sign-in identity.
   • Screenshots showing Action Required, the Microsoft Accounts tenant, and the “no sign-in account exists” message.

Microsoft’s FAQ specifically directs customers to support when an organization already has an identity validation under one primary email and onboarding must continue with another email. It also warns that additional in-progress requests for the same entity do not help.^1^ The portal support route has also been used for account-specific investigation of an existing validation record.^2^

Why this cannot be corrected in the portal

For organization validation, the primary email is captured when the request is created. It must be a monitored mailbox on a domain owned by the legal entity, accept messages and links from external senders, and is where the individual-verification link is delivered. When the request reaches Action Required, that individual verification must be completed before processing returns to In Progress.^3^

The same quickstart states that changes needed after a public identity-validation request is created require a new request; it does not document a portal operation for editing an existing request’s primary email or identity association.^3^ Therefore, there is no supported self-service edit that can safely preserve this request.

Do not create a replacement request unless Artifact Signing support instructs you to do so. Although the normal documented correction is a new validation, the FAQ provides the support-assisted continuation path for the specific case where an existing organization validation has a different primary email.^1^

Identity to use if support re-enables the request

Ask support to confirm which identity must open the repaired link. The validation flow requires use of the email address entered when the request was created when credentials are requested.^3^

The assigned Owner and Artifact Signing Identity Verifier roles authorize Azure resource operations, but they do not establish that a personal Microsoft account is the sign-in identity expected by the verification link. Do not retry through the currently selected Microsoft Accounts tenant unless support confirms that association.

If the portal will not permit creation of a technical case, use Help + support and select the available subscription/support category, referencing the Artifact Signing identity-validation request in the case description. Artifact Signing’s documented support options are Azure Support and Microsoft Q&A, but request identifiers and account-specific evidence should be provided only in the private Azure Support case.^1^

References

1. Artifact Signing FAQ
2. Identity validation request failed. - Microsoft Q&A
3. Quickstart: Set up Artifact Signing