Artifact Signing: organization identity validation "Failed" with document request, but no upload option in portal (Germany, sole proprietor)

Hovsep Aroyan 20 Reputation points
2026-09-10T19:08:18.0766667+00:00

Product: Azure Artifact Signing (formerly Trusted Signing), Public Trust, organization identity validation, country Germany, SKU Basic, region North Europe. I want to sign my software product.

What happened, in order:

(a) I created the organization identity validation request with my details.

(b) The status changed to "Action required". The link in the portal ("click here") opened a page with a QR code for the Verified ID / face check. I scanned it with Microsoft Authenticator, where my identity is already verified, and completed the check. The portal then showed a green check mark "Verified".

(c) Later the status simply changed to "Failed" with this message: "Please provide additional document(s) listed below dated within the past 12 months to verify your organization. Formation/incorporation records, franchise or agency appointment letters, government-issued licenses, registration certificates, or tax filing records."

At no point was there an option to upload documents. The identity validation pane now shows only the submitted data and the Failed status: no upload section, no second "Action required" step. I also did not receive an email asking for documents. I have the tax office letter, issued within the last 12 months, ready to upload.

My questions:

Q1: Is there any way to submit the requested documents for this validation, or is "Failed" final and I must create a new request?

Q2: For a German sole proprietor (Einzelunternehmen) without a Handelsregister entry, which document does the vetting team accept as a formation/registration record?

Q3: If I create a new request: must the organization name be the personal name, and is a German Steuernummer accepted as "Tax Id", or must it be the USt-IdNr (VAT ID)?

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 No comments

Answer accepted by question author
Meha-MSFT 2,375 Reputation points Microsoft Employee Moderator
2026-09-10T19:29:01.83+00:00

User's image

Was this answer helpful?

1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
  1. AI answer

    2026-09-10T19:08:33.7966667+00:00

    Failed is final for that identity validation request. Document upload is available only when the request status is Action Required after Microsoft asks for more documentation. If the request is already Failed, the documented path is to create a new identity validation request.

    Relevant details for this scenario:

    1. If more documents are required during processing, the request status changes to Action Required, and the documents can be uploaded in the Azure portal.
    2. When the process finishes, the status becomes either Completed or Failed.
    3. If organization identity validation fails because the email verification was missed or expired, a new request is required.
    4. If organization identity validation fails for other reasons, Microsoft states that the validation team was not able to determine the request from the information provided. In cases where extra documents were required, all three upload attempts may already be exhausted, and onboarding cannot continue on that request.

    For the current validation ID, there is no documented way to submit documents after it is already in Failed state.

    Next steps:

    1. Create a new organization identity validation request in the Artifact Signing account.
    2. Ensure the primary email can receive messages from external senders and emails containing links, because the verification link expires in seven days.
    3. If the new request moves to Action Required, upload the requested documents in the Azure portal at that stage.
    4. If assistance is needed for the onboarding flow or repeated failures, use Azure Support or Microsoft Q&A with the artifact-signing tag. Creating more in-progress requests for the same entity does not help, and requests cannot be expedited.

    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.