Our Swedish company is onboarding to Azure Artifact Signing (Public Trust organization validation, North Europe).
The original request remained In Progress for several weeks without a visible Action Required message. Following Microsoft's support guidance, we deleted it and submitted a replacement on 19 November 2026.
The replacement verification email arrived on 20 November. On the first attempt to use its link, signing in with the Microsoft account that owns the Azure subscription immediately displayed: "Sorry, this link has been used already." The verification flow could not be completed.
The verification email was sent to our corporate-domain address, while the subscription owner used a different personal Microsoft account. At that time, the corporate address had no Microsoft account; attempting it in a private window produced: "We couldn't find an account with that username."
We have since created a Microsoft account with the corporate address and, as a separate troubleshooting attempt, a new Azure subscription and Artifact Signing account using that same address for sign-in and primary verification contact. That new organization request is In Progress; it is not yet a confirmed solution. The earlier environment remains unchanged.
Our existing Azure support case directs us to Microsoft Learn Q&A to continue receiving help.
Could Microsoft clarify:
- Which Microsoft identity must authenticate for the individual-verification step within organization validation?
- How can a newly issued link report already used before verification is completed?
- Could the two active requests for the same legal entity interfere, and what is the supported way to coordinate them?
We can provide the support case and validation IDs through a private Microsoft support channel. Please advise how to arrange investigation of the original link/account association.