Artifact Signing Public Trust organization validation failed after successful Verified ID

Open an Azure Support request for backend review of the existing failed validation and provide the validation ID only in the private ticket; a successful Verified ID presentation completes the representative step but does not mean the overall organization validation has completed.

Request the backend review

1. In the Azure portal, open Help + support and select Create a support request. The Artifact Signing FAQ designates Azure Support as the support channel for identity-validation issues.^1^
2. Select the affected subscription and identify Artifact Signing as the service. If no exact identity-validation problem type is offered, choose the closest technical issue and describe it as Public Trust organization identity validation failed after successful representative Verified ID verification.
3. Include:
   • Artifact Signing account and Azure region.
   • Organization name and country/region.
   • Identity Validation ID.
   • Approximate UTC time when Verified ID displayed Verification successful!
   • Timeline: Action Required → successful presentation → Failed.
   • Confirmation that reopening the link reported it had already been used.
   • Screenshots of the portal status and successful-verification page, with unrelated identifiers redacted.
   • A request for the exact failed stage and confirmation whether the existing request can be recovered or must be replaced.
4. Do not post the validation ID, subscription ID, tenant ID, or other account identifiers publicly in Microsoft Q&A. The Azure Support ticket is the appropriate private channel.

What the statuses mean

For organization validation, Artifact Signing changes the request to Action Required for representative identity validation. After that succeeds, the request returns to In Progress while organization validation continues. Only the final Completed status means the complete validation succeeded; Failed means a later or overall validation determination was unsuccessful.^2^

Therefore, the used-link message is expected after presentation and does not identify the failed stage. Since the presentation already succeeded, repeating Authenticator, clearing its cache, or reopening that one-time link is not the appropriate next action.

Germany is within the documented European Union availability for Public Trust organization onboarding.^2^

Resubmit only after support advises it

The portal does not expose the backend rejection reason in this situation. Microsoft’s FAQ says that when failure was not caused by a missed email-verification link, the validation team could not make a determination from the supplied information.^1^

If support confirms that a corrected submission is required:

• Create a new identity-validation request; an existing request cannot be edited when its submitted information needs changing.
• Match the legal organization name, business identifier, and registered address to current public business records.
• Use the representative’s first and last names exactly as shown on the government-issued ID.
• Use a monitored primary mailbox on a domain owned by the legal entity; the secondary address must differ while using the same organizational domain.
• Ensure both mailboxes accept messages and links from external senders.^2^

Do not create repeated requests while support is reviewing the case. Microsoft states that duplicate validations for the same entity do not help and cannot expedite validation.^1^

References

1. Artifact Signing FAQ | Microsoft Learn
2. Quickstart: Set up Artifact Signing | Microsoft Learn