A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
Artifact Signing public identity validation failed without a rejection reason
An Azure Artifact Signing (formerly Trusted Signing) public organization identity validation changed to "Validation Fail", but the Azure portal shows no rejection reason.
The request was for a Hungarian limited company. Domain ownership documentation was uploaded, and the organization name and registered address matched the validation request. Email ownership was also verified. The portal only displays the failed status without any actionable detail.
We need guidance on the following:
- Is there a supported way to see the exact validation failure reason?
- Can Microsoft review the backend validation logs or reopen the existing request?
- If a new validation must be submitted, which exact evidence is required for a Hungarian organization: an official company registry extract, proof of registered address, proof of an authorized representative, or additional domain-ownership evidence?
- How can sensitive company documents and identifiers be provided securely without posting them publicly?
This is a non-production signing setup. We have an active Azure Developer support plan and were routed here through the Azure portal prioritized Microsoft Q&A support flow. A Microsoft engineer may contact us privately for the subscription and identity-validation identifiers.