A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
Because both requests are already Failed and no verification email can be found, submit a new Public organization identity-validation request after confirming that the primary mailbox is not a distribution list and accepts externally sent messages containing links. ^1^
Submit the third request
A third request is appropriate in this situation:
- Confirm that the primary mailbox:
- Is an individual, monitored mailbox rather than a distribution list.
- Accepts messages and links from external senders.
- Has no mail-flow, firewall, quarantine, or filtering rule blocking the message.
- Has been checked for the earlier messages in Junk, Spam, and quarantine.
- In Azure Portal, open: Artifact Signing account → Objects → Identity validations → Organization → New Identity → Public.
- Enter:
- The LLC’s exact legal name.
- Its own website.
- Primary and secondary addresses on the company-owned domain; the secondary address must differ from the primary.
- The business identifier.
- The business address of the legal entity.
- The representative’s first and last names exactly as shown on that person’s government-issued ID.
- Select Certificate subject preview, review the values, and then select Create. A successful submission initially becomes In Progress; requests for identity verification or documents appear as Action Required and are also sent by email. ^2^
The documented three-attempt restriction applies when Microsoft requests extra documents and all three upload attempts are exhausted—not simply because three validation resources were submitted. An accepted Artifact Signing Q&A answer confirms that distinction. ^3^
Do not create another request if one is still In Progress; parallel requests for the same entity do not help and cannot expedite validation. ^1^
Which address to enter
Use the LLC’s business address as represented in the authoritative public business records used to verify the legal entity. The form requires the “business address of the legal business entity,” and Microsoft advises ensuring that the entity’s public records are current before Public Trust validation. ^2^
The published instructions do not define a special address type for an online-only US LLC whose state record omits a principal address. Therefore:
- Do not alternate between the registered-agent and mailing addresses merely to test which passes.
- Reconcile the address across the state record and any other public business-identity record associated with the submitted identifier.
- Ask the existing support case to confirm which publicly recorded address its validator expects for this LLC before changing it again.
A registered-agent address should be used only if it is actually recorded as the legal entity’s business address in the records being checked; the available guidance does not say that every registered-agent address qualifies.
The two Microsoft accounts
Having a personal Microsoft account and a work/company account is supported, and the two cannot be merged. They remain separate, with no synchronization of their account information. ^4^
The available Artifact Signing documentation does not establish that repeating company contact details across those two identities causes organization validation to fail. Artifact Signing validation is associated with the Azure subscription: Artifact Signing accounts in the same subscription can reuse it, while another subscription requires a separate validation. ^5^
Accordingly:
- Keep the currently working paid subscription and its Artifact Signing resources in place while the cases are investigated.
- Do not close either identity solely to fix validation.
- Do not create another subscription or Artifact Signing account as a workaround.
- If an identity validation already exists for this organization under a different primary email, Microsoft directs customers to contact support to continue onboarding. ^1^
Update and escalate the existing support case
Since a Developer support case is already open, update that case rather than opening a duplicate. Include privately:
- Both failed validation request IDs and timestamps.
- Subscription ID, tenant ID, and Artifact Signing account resource ID.
- Exact legal name, submitted business identifier, and the two addresses used.
- Primary email domain, without posting credentials or sensitive documents publicly.
- The still-open Azure subscription eligibility case number.
- A request to route the case to the Artifact Signing identity-validation/vetting team and identify whether the failure concerns the organization record, address, identifier, email stage, or an existing validation under another primary contact.
A concise escalation statement is:
Both Public organization identity-validation requests reached Failed within approximately one hour, with no visible reason and no verification email found. Please correlate the attached validation IDs, confirm whether another validation exists for this legal entity or primary contact, identify which legal-business address record must match, and route the case to the Artifact Signing validation team before further retries.
Do not post the case numbers, subscription ID, tenant ID, or validation IDs in the public Q&A thread; provide them only through the private support case.
References
- Artifact Signing FAQ
- Quickstart: Set up Artifact Signing
- Artifact Signing identity validation stuck on email verification – no resend option / third validation attempt - Microsoft Q&A
- Combining Microsoft accounts | Microsoft Support
- Windows endpoint security platform requirements, signing, and enrollment