Artifact Signing email verification completed, but portal still says email verification pending and link already used

Keep both existing requests unchanged and ask an Artifact Signing moderator to route the existing validation IDs for private review, because onboarding the same organization with a different primary email is explicitly a support-assisted case.

What the current status means

• A one-time link reporting “this link has been used already” means it cannot be used again, but it does not establish whether email verification was correctly recorded.
• In Progress can be a normal processing state. After the individual verification step succeeds, an organization request returns to In Progress while validation continues; it changes to Action Required if more input is needed and ultimately to Completed or Failed.^1^
• A closely matching Public Trust case eventually completed asynchronously even though its verification link initially said it had already been used.^2^

However, the continuing “Please complete your email verification” message is not documented as an expected processing message after successful verification. Since there are also two requests for the same organization with different primary addresses, an account-specific state check is appropriate. Microsoft’s FAQ specifically instructs customers to contact support in that situation.^3^

Continue through Microsoft Q&A under Basic support

The documented Artifact Signing assistance channels are Azure Support and Microsoft Q&A using the Artifact Signing tag. The FAQ also says that creating additional requests for the same entity while one remains in progress does not help and that validation cannot be expedited.^3^

On this existing Q&A post:

1. Ask a Microsoft moderator or Artifact Signing product representative to arrange an authorized private handoff.
2. Request confirmation of:
   • which validation request is authoritative;
   • whether email verification was recorded on either request;
   • whether either request is awaiting organization or document review;
   • whether the earlier shared-mailbox request must be cancelled before the individual-work-email request can continue.
3. Provide privately, only after Microsoft supplies an authenticated channel:
   • Azure subscription and Artifact Signing account identifiers;
   • both validation IDs;
   • creation dates and primary-email types;
   • verification-click timestamps;
   • screenshots of the current status and exact message.

Microsoft publicly documents Q&A as an assistance route, but it does not document a self-service private escalation mechanism from a Q&A post. A moderator or product representative must arrange any required private exchange. If your organization later obtains an Azure technical-support entitlement, use Azure Support for the same investigation; Azure technical support requires an eligible support plan.^4^

Do not delete either request yet

Retain both requests and the existing Verified ID until Microsoft identifies which request should proceed:

• Do not create a third request.
• Do not repeatedly reopen the consumed link.
• Do not delete the earlier request merely because it used a shared mailbox.
• Do not remove the Verified ID unless support instructs you to do so or a documented mismatch/Face Check recovery condition applies.

The FAQ’s delete-and-recreate guidance applies to specific conditions such as an expired link, explicit email-validation failure, or documented identity-data mismatch. Your requests remain In Progress, so those restart conditions have not been established.^3^

If either request changes to Action Required, follow the newly issued portal or email instruction. If it changes to Completed, use that completed validation and ask support how to dispose of the duplicate. If it changes to Failed, preserve the failure details and wait for direction before recreating it because the different-primary-email condition still applies.

References

1. Quickstart: Set up Artifact Signing
2. Artifact Signing verification link was already consumed on first use
3. Artifact Signing FAQ
4. Create an Azure support request for an Enterprise Agreement issue