Artifact Signing organization validation failed after successful ID/selfie verification — escalation requested

Trevor Old 0 Reputation points
2026-10-26T22:33:19.7466667+00:00

I am requesting help from a Microsoft moderator with Azure Artifact Signing Public Trust organization identity validation for Trevor Old LLC (submitted organization name: Trevor Old LLC DbA TrevBot).

On October 26, 2026:

  1. I submitted the organization validation request with our D-U-N-S number.
  2. I completed the government-ID and selfie verification on my phone. The phone reported success, and the Verified ID was saved in Microsoft Authenticator.
  3. The web verification page then reported failure.
  4. After refreshing the Azure portal, the organization request changed from In Progress to Failed.

The failed request's details show no failure reason and no retry, resume, or reset option. My Verified ID is still on the phone. I have preserved the failed request rather than deleting it or creating duplicate requests.

This looks like a possible problem transferring the successful mobile verification result back to the web flow, but I do not have a diagnostic error code establishing the cause. I would like Microsoft to investigate the backend result before I repeat the identity process.

Could a Microsoft moderator please route this to the Artifact Signing identity-validation / Verified ID team and advise:

  • What failed after the mobile verification reported success?
  • Can the existing request be reset or resumed, and can my existing Verified ID be reused?
  • If a new request is necessary, what supported recovery steps should I follow?

The Azure support flow requires a paid technical-support plan. The Artifact Signing FAQ lists Microsoft Q&A as an identity-validation support option, so I am requesting assistance here.

I can provide the identity-validation request ID, account/resource details, and any available diagnostics privately through a Microsoft-approved support channel. I have intentionally omitted identity documents, selfies, D-U-N-S number, private contact details, tenant/subscription IDs, and verification links from this public question.

Artifact Signing
Artifact Signing

A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2026-10-26T22:35:13.7333333+00:00

    Keep the failed validation request intact and ask the Microsoft Q&A moderator handling this thread to escalate its Identity Validation ID to the Artifact Signing validation team for backend review.

    Closely matching cases—successful personal identity checks followed by an unexplained organization-validation failure—were resolved after moderators collected the Identity Validation ID and Artifact Signing account details privately and the validation team reviewed the request on the backend.^1^ ^2^

    Information for the escalation

    When a moderator provides a Microsoft-approved private channel, be prepared to supply:

    • Identity Validation request ID
    • Azure subscription, resource group, and Artifact Signing account details
    • Tenant ID, if requested
    • UTC timestamps for the mobile success and subsequent web/portal failure
    • Screenshot of the failed status and blank failure details
    • Browser, operating system, phone platform, and Microsoft Authenticator version
    • Whether the Verified ID remains valid in Authenticator
    • Correlation or activity IDs, if any are available

    Do not post identity documents, selfies, verification links, D‑U‑N‑S number, email address, tenant/subscription identifiers, or the validation ID publicly.

    Microsoft Q&A with the Artifact Signing tag is an explicitly documented identity-validation support option, alongside Azure Support.^3^

    What can currently be concluded

    • The successful ID/selfie operation confirms completion of one component of the workflow; it does not establish that the overall organization validation completed.
    • The displayed information does not identify what failed afterward. Only Microsoft’s validation-side records can answer that for this request.
    • The supplied Microsoft documentation does not describe a customer-accessible reset or resume operation for a failed organization request.
    • A valid, unexpired Verified ID can be presented again for Artifact Signing, but whether this specific request can reuse the credential must be determined during the backend review.^3^

    Do not delete the request while investigation is pending. A failed request can be deleted because it is no longer In Progress, but deletion is irreversible and a deleted validation cannot be recovered.^4^

    If Microsoft requires a new request

    Before resubmitting, check these conditions:

    1. Primary contact email domain: If the failed request used a free-hosted email address, use an address on a domain associated with the legal entity when Microsoft confirms that resubmission is appropriate. A closely matching Q&A case was resolved by changing from a free-hosted address to an entity-associated address.^5^ Verify this privately; do not publish the address.
    2. Legal organization name: For Public identity validation, enter the legal business entity to which the certificate will be issued. The portal also supports organization/DBA requests.^6^
    3. Email verification: Ensure the primary contact receives and opens the verification link within seven days. The FAQ specifically directs creation of a new request when that link was missed or expired.^3^
    4. Portal path: Azure portal → Artifact Signing account → Objects → Identity validations → Organization → New Identity → Public. The submitting account needs the Artifact Signing Identity Verifier role.^6^
    5. Verified ID: If Microsoft confirms that the existing credential is valid and reusable, present it rather than deleting it. Remove it and create a new one only when instructed or when the documented individual-validation errors—address mismatch, name mismatch, or FaceCheck failure—apply.^3^

    Because no such individual-validation error was shown here, deleting the Verified ID or repeating the selfie process is not yet the supported first action.

    References

    1. Artifact Signing ID validation fails repeatedly 9afac007-6e27-4e93-84b1-34ac87fcdc90 - Microsoft Q&A
    2. Artifact Signing Account Organization Identity validations failed - Microsoft Q&A
    3. Artifact Signing FAQ
    4. Renew or delete Artifact Signing Identity Validations
    5. Artifact Signing identity validation failing repeatedly with no reason shown — need backend diagnosis - Microsoft Q&A
    6. Quickstart: Set up Artifact Signing
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.