Artifact Signing organization identity validation failed twice with no reason (Spain)

Question

Artifact Signing organization identity validation failed twice with no reason (Spain)

Antonio Checa 0

Our organization identity validation (Public Trust, Organization, Spain) has failed twice with "Validation Fail", with no reason in the portal or the email. Validation IDs: 11bbd461-a844-4788-a172-3c632f45f55b and 3adfbc87-9c19-4076-89d5-3fd66ecd9dd6.

The company has been registered for more than 3 years, and the legal name entered matches the Spanish Mercantile Registry exactly.
The personal verification (Verified ID) completed successfully, so the failure seems to be in the organization check.
Our domain's WHOIS data is redacted by the registrar under GDPR, so it cannot be made public.

Could the Artifact Signing team tell us the reason for the failure and what we should correct or provide? We do not have a paid support plan.

0 comments

4 answers

Your answer

Answer 1

Antonio Checa 0

A support case has been opened: 2611100040002729

0 comments

Answer 2

kagiyama yutaka 5,750

I think the WHOIS explanation is premature. Successful Verified ID doesn't explain the organization failure. The suggested TXT record and email address aren't in the Artifact Signing FAQ or quickstart. Check whether the primary email verification link was used within seven days. If not, a new validation request is required.

Otherwise, ask a Microsoft moderator here if they can refer both validation IDs to the Artifact Signing team for the failure reason and what needs fixing. pls don't change WHOIS or resubmit based on a guess. Upload any requested documents through the Azure portal.　

Antonio Checa 0 Reputation points

2026-11-10T06:43:57.42+00:00
Thanks, Yutaka, that makes sense. We won't change WHOIS or resubmit based on a guess.

To clarify the email verification: in both requests, the verification links worked and were used within minutes. We completed the whole process, including the personal identity check (Verified ID, which showed "Verification successful"). At the very end of the process an error appeared, and the request changed to Validation Fail in the Azure portal. The "this link has been used already" message only appeared when we clicked the links again afterwards.

First request: 11bbd461-a844-4788-a172-3c632f45f55b (failed on 6 Nov)

Second request: 3adfbc87-9c19-4076-89d5-3fd66ecd9dd6 (failed on 8 Nov)

Both failed within two days, well inside the 7-day window.

Could a Microsoft moderator please refer both validation IDs to the Artifact Signing team, so they can tell us the reason for the failure and what we need to fix? We will upload any requested documents through the Azure portal.
kagiyama yutaka 5,750 Reputation points

2026-11-10T10:03:18.01+00:00

Thanks for the update. Hopefully a Microsoft moderator can help get both validation IDs reviewed by the Artifact Signing team.

Answer 3

Antonio Checa 0

Thanks. Could a Microsoft moderator confirm whether the TXT record and the [email protected] address are official? I couldn't find them in the Artifact Signing documentation.

0 comments

Answer 4

Summary

Organization Validation (OV) failed twice for Public Trust - Spain (IDs: 3adfbc87-9c19-4076-89d5-3fd66ecd9dd6 / 11bbd461-a844-4788-a172-3c632f45f55b) with generic Failed Verification. Personal Identity (IV) is verified.

Root Cause Analysis (Most Common in Spain)

This is not a personal identity issue.

1. WHOIS Privacy / GDPR - Main Reason

You mentioned WHOIS is privacy-protected by registrar. Public Trust automated check fails because it cannot read:

Registrant Organization = Your Exact Legal Name

Per GDPR, the registrar must show Organization Name in public WHOIS. This is mandatory for OV.

2. Legal Name Mismatch

Legal name in portal must match Registro Mercantil Central 100%, including suffix: S.L., S.L.U., S.A.

3. Domain vs Company

Domain must be registered to the company, not to an individual.

Fix - Step by Step

Step A - Fix Domain Proof (Do this BEFORE resubmit)

Option 1: Ask registrar to show Organization in WHOIS.

Option 2: Add DNS TXT record:

Type: TXT

Host: _validation

Value: ms-organization-validation=YOUR_EXACT_LEGAL_NAME_AS_IN_REGISTRO

Option 3: Ensure you can receive email on admin@, administrator@, hostmaster@ your domain.

Step B - Open Support Ticket (Recommended)

Don't just resubmit. Open Azure Portal > Help + Support >

Issue Type: Trusted Signing / Document Signing - Organization Validation Failure

Paste this text:

OV failed twice for Spanish Public Trust organization. Personal identity verified.
Legal name matches Registro Mercantil. WHOIS was privacy-protected per GDPR, now fixed to show organization. Please manually re-validate using attached docs and VIES.
Validation IDs: 3adfbc87-9c19-4076-89d5-3fd66ecd9dd6 and 11bbd461-a844-4788-a172-3c632f45f55b

Step C - Attachments Required

Certificación del Registro Mercantil Central (< 3 months) with CIF/NIF
VIES VAT screenshot showing VAT active + name match
DUNS / LEI if available
Screenshot of updated WHOIS showing Organization + DNS TXT screenshot
Authorization letter from legal representative

Note: Document Signing team can override automatic WHOIS failure if you provide DNS/email alternative. Resubmitting without fixing WHOIS will fail a 3rd time.

If no paid support plan: email [email protected] with same IDs.