Artifact Signing: Public Trust Organization identity validation "Failed" with no reason or email, French sole proprietorship

jimmy 0 Reputation points
2026-10-16T12:14:22.1333333+00:00

Hello,

I created an Artifact Signing account (Basic SKU, North Europe, paid subscription) and submitted one Public Trust, Organization identity validation from France. It now shows "Failed" in the Identity validations blade.

Organization type: sole proprietorship (French "entreprise individuelle").

I entered my business/trade name as the organization name. It may differ from the legal name in the national registry.

I received no verification email and no failure email on the primary address (inbox and spam checked).

The portal shows no failure reason, and the activity log only shows the account creation. No additional documents were requested.

Questions:

Q1) Is a sole proprietorship in France eligible for Organization validation (Individual seems limited to US/Canada)?

Q2) For a sole proprietor, must the name be the entrepreneur's legal name as in the registry, or can the trade name be used? Could a mismatch give "Failed" without any email?

Q3) Can the failure reason be retrieved, or the request retried without using one of the three attempts?

Q4) The account is still billed monthly although validation failed. Is deleting the account the only option?

Thank you.

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: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-10-16T12:14:41.2466667+00:00

    Q1) The supported countries or regions for onboarding must be checked in the Artifact Signing prerequisites. No context here confirms whether a French sole proprietorship is eligible for Public Trust Organization validation specifically, so only the supported-country requirement is established.

    Q2) For Public identity validation, the organization name must be the legal business entity to which the certificate is issued. The quickstart also states that public records for the legal business entity should be up to date, and the website and email must belong to that legal business entity. A mismatch between the submitted name and the legal entity information can therefore cause validation failure. The context does not state whether this always fails without email, but it does state that if Microsoft can’t validate the information provided, onboarding can’t proceed.

    Q3) The portal does not expose a failure reason in the provided documentation. If Organization identity validation fails:

    1. First confirm that the primary email did not miss the verification link. That link expires after seven days.
    2. If no verification email was received, check Junk/Spam, confirm the mailbox accepts external messages and links, and ask the mail administrator to verify firewall, security, or filtering policies are not blocking the message.
    3. If the email still can’t be found, delete the current identity validation request and submit a new one.
    4. If another identity validation is needed for the same organization with a different primary email address, contact support to continue onboarding.
    5. For assistance with identity validation, use Azure Support or Microsoft Q&A with the artifact-signing tag.

    The context does not support retrying without consuming a new request. It explicitly says to create a new identity validation request when email verification was missed or failed, and notes that creating more requests for the same entity while one is already in progress does not help.

    Q4) If Organization identity validation fails for reasons other than a missed email verification, and the validation team can’t determine the request from the information provided, the recommendation is to delete the Artifact Signing account so it isn’t billed for unused resources. The context does not provide another billing stop mechanism.

    Practical next steps for this case:

    1. Recreate the Organization validation using the legal business entity name exactly as reflected in official public records, not only the trade name.
    2. Ensure the primary email is on a domain owned by the legal business entity, is monitored, and can receive links from external senders.
    3. If the organization already has an identity validation tied to a different primary email, open Azure Support.
    4. If the request fails again with no visible reason, use Azure Support for investigation.
    5. If onboarding cannot be completed, delete the Artifact Signing account to avoid charges for unused resources.

    References:

    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.