Organization identity validation stuck in a document loop — need the specific missing item before exhausting the 3-attempt limit

Question

Organization identity validation stuck in a document loop — need the specific missing item before exhausting the 3-attempt limit

Andreas Apeldorn 0

Hello, We are onboarding to Azure Artifact Signing (formerly Trusted Signing) with an Organization (Public Trust) identity validation for an EU-registered company. We are stuck in a loop we cannot resolve from the portal and need direct help before we exhaust the three-attempt limit. Our details will be shared privately on request.

The problem: 1. We repeatedly receive requests for "additional documents", but the requirements are not specified — we cannot tell which document, which field, or what exactly was insufficient in the previous submission. 2. After submitting, we can neither view nor update what we sent. The portal shows no upload control in the current state. 3. Weeks later we receive a request for the SAME documents again, with no indication of what was missing or why the prior submission was rejected. What we need from you: 1. The SPECIFIC document and the SPECIFIC field/data point that failed validation, and the exact reason it was rejected — not a generic "additional documents required" message. 2. The correct, secure channel and steps to (re)submit the requested documents, given that no upload control is currently shown in the portal. 3. Confirmation of how many of the three validation attempts we have already used and how many remain, so we do not exhaust them blindly. One point we suspect may be causing the mismatch:

Our registered legal name in the D&B/DUNS record contains the German umlaut "ä" (in "haftungsbeschränkt"), and this cannot be changed on the D&B side. Please tell us the exact spelling the validation team expects in the Azure identity-validation form so it matches our DUNS record — i.e. whether we must enter the umlaut as-is, transliterate "ä" → "a", or "ä" → "ae". We want to submit it correctly on the next (and possibly last) attempt rather than guess. We would appreciate a concrete, itemized response so we can complete the validation in a single further submission.

Best regards, Andreas

Zoha Fatima 430 Reputation points

2026-08-27T12:11:40.86+00:00
Hi Andreas,

I understand why you do not want to risk another submission. Microsoft documentation confirms that additional-document requests allow only three upload attempts, but the portal does not expose the remaining-attempt count or detailed rejection reason. A Microsoft Artifact Signing moderator must review the validation ID internally and share the exact mismatch privately.

Before proceeding:

Confirm your account has the Artifact Signing Identity Verifier role. The upload option should appear only while the request is Action Required.

Do not create another request or upload documents again until Microsoft confirms the backend status and remaining attempts.

Enter the organization name exactly as recorded in the official registry and DUNS record, retaining “ä” unless Microsoft’s validation team specifically instructs otherwise. Also ensure the Azure billing profile, address, website ownership, and submitted documents match that spelling exactly.

Do not post documents or identifiers publicly. Identity-validation issues are handled through the Artifact Signing Q&A channel, where Microsoft staff can initiate private communication.

Thank you, and feel free to respond back for more assistance.
Andreas Apeldorn 0 Reputation points

2026-08-28T07:23:12.36+00:00
Hi, thank you — this is very helpful.

One clarification on sequencing: I did not voluntarily resubmit. Vetting Operations closed my original application after the third appeal ("As this is your third appeal, we have closed your application"). With the original closed and no upload option remaining on it, creating a new validation request was the only path left open to me.

Update: that new request has now failed again — validation ID xxx. As before, the portal does not expose the actual rejection reason or the remaining-attempt count, so I have no way to know what to correct.

Could a Microsoft Artifact Signing moderator please:

Review validation ID xxx internally and share the exact failure reason (missing document, name mismatch, category, phone verification, etc.) privately, and

Confirm the current backend status and remaining attempts on this request before I touch it again?

Context that may explain the repeated failures: my earlier application was closed on an incomplete set — the commercial-register extract (Handelsregisterauszug) was never correctly categorized in the portal flow and was only attached to my paid support ticket (2608260050001267), never entered into the validation request itself.

Confirmations on your points:

My account has the Artifact Signing Identity Verifier role.

The organization name is entered exactly as in the commercial register and D-U-N-S record, retaining "ä" (full legal form "UG (haftungsbeschränkt)"); Azure billing profile, address, and domain ownership match that spelling.

Understood — I will not resubmit or post documents/identifiers publicly until a moderator confirms the backend reason and initiates private communication.

Given two closed/failed cycles with no visible reason, I really need a moderator to look at the backend log for xxx. Should I share anything else here, or will Microsoft staff reach out privately?

Thank you, Andreas

Your answer

Zoha Fatima 430 Reputation points

2026-08-27T12:11:40.86+00:00

Hi Andreas,

I understand why you do not want to risk another submission. Microsoft documentation confirms that additional-document requests allow only three upload attempts, but the portal does not expose the remaining-attempt count or detailed rejection reason. A Microsoft Artifact Signing moderator must review the validation ID internally and share the exact mismatch privately.

Before proceeding:

Confirm your account has the Artifact Signing Identity Verifier role. The upload option should appear only while the request is Action Required.

Do not create another request or upload documents again until Microsoft confirms the backend status and remaining attempts.

Enter the organization name exactly as recorded in the official registry and DUNS record, retaining “ä” unless Microsoft’s validation team specifically instructs otherwise. Also ensure the Azure billing profile, address, website ownership, and submitted documents match that spelling exactly.

Do not post documents or identifiers publicly. Identity-validation issues are handled through the Artifact Signing Q&A channel, where Microsoft staff can initiate private communication.

Thank you, and feel free to respond back for more assistance.
Andreas Apeldorn 0 Reputation points

2026-08-28T07:23:12.36+00:00

Hi, thank you — this is very helpful.

One clarification on sequencing: I did not voluntarily resubmit. Vetting Operations closed my original application after the third appeal ("As this is your third appeal, we have closed your application"). With the original closed and no upload option remaining on it, creating a new validation request was the only path left open to me.

Update: that new request has now failed again — validation ID xxx. As before, the portal does not expose the actual rejection reason or the remaining-attempt count, so I have no way to know what to correct.

Could a Microsoft Artifact Signing moderator please:

Review validation ID xxx internally and share the exact failure reason (missing document, name mismatch, category, phone verification, etc.) privately, and

Confirm the current backend status and remaining attempts on this request before I touch it again?

Context that may explain the repeated failures: my earlier application was closed on an incomplete set — the commercial-register extract (Handelsregisterauszug) was never correctly categorized in the portal flow and was only attached to my paid support ticket (2608260050001267), never entered into the validation request itself.

Confirmations on your points:

My account has the Artifact Signing Identity Verifier role.

The organization name is entered exactly as in the commercial register and D-U-N-S record, retaining "ä" (full legal form "UG (haftungsbeschränkt)"); Azure billing profile, address, and domain ownership match that spelling.

Understood — I will not resubmit or post documents/identifiers publicly until a moderator confirms the backend reason and initiates private communication.

Given two closed/failed cycles with no visible reason, I really need a moderator to look at the backend log for xxx. Should I share anything else here, or will Microsoft staff reach out privately?

Thank you, Andreas