Hello @Calu Andrei
Unfortunately, the Azure portal doesn't expose the specific reason when an organization identity validation fails for Trusted Signing. The detailed validation results are only available internally to Microsoft, so the most practical next step is to open an Azure Support request and provide your Validation Request ID, Subscription ID, and Tenant ID so the backend logs can be reviewed.
Based on your description, two things stand out:
- Your LLC is relatively new (registered in January 2026). Microsoft doesn't publish a minimum business age requirement, but identity verification relies on multiple trusted data sources, and newly formed organizations may not yet have sufficient public records for automated verification.
- Not having a D-U-N-S number could also be a contributing factor. While it isn't a documented requirement for Trusted Signing, having an active D-U-N-S record with matching legal name and address can improve verification confidence.
Once a request reaches Validation Fail, it generally can't be retried in place, so after addressing any verification gaps, you'll likely need to submit a new organization validation.
Based on Microsoft's documentation, it's also important to ensure your organization's public records are up to date, as public identity validation relies on information that can be verified externally. If any information changes, you'll need to submit a new identity validation request, since existing requests can't be edited after submission.
One additional consideration is your organization's age. Microsoft moderators have indicated that Public Trust organization validation currently requires a minimum of three years of verifiable operating history, which may be established through business registration records, tax records, D-U-N-S, or other third-party validation sources. If your LLC was registered in January 2026, that may explain the validation failure.
Please "Accept the Answer" if this information helped you. This will help us and others in the community as well.