Artifact Signing: identity validation failed, second request In Progress — Czech sole proprietor

Zdeněk Švec DISPO+ 0 Reputation points
2026-10-19T16:52:56.83+00:00

Hello,

I am a sole proprietor based in the Czech Republic, setting up Artifact Signing for a Windows desktop application.

My first identity validation reached Failed status, although the document and facial verification steps appeared successful.

A second request currently shows In Progress. During its facial verification step, I received an error resembling “error face detect”.

My current account has these active roles:

  • Owner inherited from the subscription
  • Artifact Signing Identity Verifier on the signing account
  • Artifact Signing Certificate Profile Signer on the signing account

There are no deny assignments shown.

Could the validation team help determine why the first request failed and whether the second requires further action?

Please also clarify the correct validation category and address requirements for a Czech sole proprietor: Organization or Individual, and registered business address or residential address matching the ID.

I can provide validation IDs and account details through a private channel requested by Microsoft staff.

Thank you.

Artifact Signing
Artifact Signing

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

1 answer

Sort by: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2026-10-19T16:53:56.6366667+00:00

    Do not create or delete another request while the second validation is In Progress; open an Azure support ticket for Microsoft to inspect that request and the earlier failure, because duplicate requests for the same entity do not help and validation cannot be expedited.^1^

    Category for a Czech sole proprietor

    For a publicly distributed Windows desktop application:

    • Public Trust Individual is not available in the Czech Republic. Individual developers must be located in the United States or Canada.
    • Public Trust Organization is available in the European Union, which includes the Czech Republic.
    • Geographic restrictions do not apply to Private Trust, but Private Trust is intended for private/internal relying parties rather than publicly distributed applications.^2^^3^

    Therefore, for Public Trust, use Organization validation only if the Czech sole proprietorship can be validated as a registered business entity under its official legal details. The available Microsoft documentation does not explicitly define how every Czech sole-proprietor legal form is classified. Ask Artifact Signing support to confirm the category before replacing the current request.

    The documented rule that the legal name and sold-to address must match a government-issued ID applies specifically to Public Trust Individual validation. It does not establish that a Czech Organization request should use the proprietor’s residential address.^2^ For an Organization request, use the legal entity name and registered business address shown in the authoritative Czech business records unless the validation team instructs otherwise.

    Escalate the active request

    In Azure portal:

    1. Go to Help + support.
    2. Select Create a support request.
    3. Identify the service as Artifact Signing and the issue as identity validation.
    4. Include:
      • The first validation ID and its final Failed status.
      • The second validation ID and current In Progress status.
      • The approximate time and exact wording of the face-detection error.
      • Artifact Signing account name, subscription reference, Azure region, validation type, and whether the intended certificate profile is Public Trust.
      • A statement that the applicant is a Czech sole proprietor and needs confirmation of the supported Organization classification and address source.
      • Screenshots with unrelated personal or tenant information removed.

    Provide validation IDs and account details only through the private support case, not in the public Q&A thread. Similar unexplained Artifact Signing failures have required the validation team to inspect the request using the validation ID and account details.^4^

    Roles

    The assignments listed are sufficient for their respective operations:

    • Artifact Signing Identity Verifier manages identity validation.
    • Artifact Signing Certificate Profile Signer signs through a certificate profile.
    • Owner manages the account, certificate profiles, and role assignments, but does not replace the Identity Verifier role for identity validation.^3^

    Because the request was successfully created and progressed into verification, reassigning these roles or investigating deny assignments is not the next supported action.

    If support instructs you to restart validation

    The FAQ’s documented FaceCheck recovery procedure applies specifically to Individual validation: delete the failed request, remove its Verified ID from Microsoft Authenticator, then create a new request and Verified ID with accurate information and adequate lighting. It also recommends the latest Authenticator version, no VPN or proxy, a reliable connection, and another device if necessary.^1^

    Do not apply that procedure to the active Czech request unless support first confirms that the request is eligible for Individual validation or directs you to reset it. If the correct category is Organization, follow the support team’s correction/reset instructions rather than creating further parallel requests.

    References

    1. Artifact Signing FAQ
    2. Quickstart: Set up Artifact Signing
    3. Artifact Signing resources and roles
    4. Artifact Signing ID validation fails repeatedly 9afac007-6e27-4e93-84b1-34ac87fcdc90 - Microsoft Q&A
    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.