Trusted Signing - Identity Validation failed

Question

Trusted Signing - Identity Validation failed

Dimitar Mitov 20

I have submitted a Trusted Signing Identity validation and it failed without any information two days after. How can I see more information?

Vinodh247-1375 43,751 Reputation points Volunteer Moderator

2024-09-22T10:41:24.5033333+00:00
Go to the Azure Portal and check for any notifications related to your submission. Notifications may provide additional information on the failure. Did you by any chance raise an support request under the Help + Support section for the specific service? mentioning the submission ID or validation request number.

Common Causes of Failure:

Mismatched Information: Ensure that the submitted identity details exactly match the legal name, tax IDs, or other documentation of your organization.

Incorrect or Missing Documents: Ensure all required documents are correctly uploaded and meet the required format.

Expired Certificates: If you are using certificates, ensure they are valid and signed by a trusted Certificate Authority (CA).

You can resubmit the validation request after reviewing the documentation and fixing potential issues.
Givary-MSFT 35,791 Reputation points Microsoft Employee Moderator

2024-09-23T07:39:29.3733333+00:00

@Dimitar Mitov Thank you for reaching out to us, please help me with the identity validation id to review the above-mentioned issue.

Answer accepted by question author

Meha-MSFT 2,125 Microsoft Employee Moderator

The validation team shared the public records we reviewed indicated that the organization was incorporated less than 3 years ago. At this time we are unable to proceed with organizations less than 3 years old

https://learn.microsoft.com/en-us/azure/trusted-signing/faq#what-if-identity-validation-fails

https://learn.microsoft.com/en-us/azure/trusted-signing/quickstart?tabs=registerrp-portal%2Caccount-portal%2Ccertificateprofile-portal%2Cdeleteresources-portal#important-information-for-public-identity-validation

Dimitar Mitov 20 Reputation points

2024-10-01T05:47:47.3533333+00:00

Hi @Meha-MSFT - thanks for the explanation. This is unfortunate, however - it's not possible for emerging startups to validate their apps.

Are you going to relax this prerequisite?

Our company is almost 2 years old and we're working hard to release the app, but without Trusted Signing we're doomed - nobody would install an app that shows as "Not verified"

What are our other options here? Are there any other ways we can submit our app through the verification process?

2 additional answers

Your answer

Vinodh247-1375 43,751 Reputation points Volunteer Moderator

2024-09-22T10:41:24.5033333+00:00

Go to the Azure Portal and check for any notifications related to your submission. Notifications may provide additional information on the failure. Did you by any chance raise an support request under the Help + Support section for the specific service? mentioning the submission ID or validation request number.

Common Causes of Failure:

Mismatched Information: Ensure that the submitted identity details exactly match the legal name, tax IDs, or other documentation of your organization.

Incorrect or Missing Documents: Ensure all required documents are correctly uploaded and meet the required format.

Expired Certificates: If you are using certificates, ensure they are valid and signed by a trusted Certificate Authority (CA).

You can resubmit the validation request after reviewing the documentation and fixing potential issues.
Givary-MSFT 35,791 Reputation points Microsoft Employee Moderator

2024-09-23T07:39:29.3733333+00:00

@Dimitar Mitov Thank you for reaching out to us, please help me with the identity validation id to review the above-mentioned issue.
Dimitar Mitov 20 Reputation points

2024-10-01T05:47:47.3533333+00:00

Hi @Meha-MSFT - thanks for the explanation. This is unfortunate, however - it's not possible for emerging startups to validate their apps.

Are you going to relax this prerequisite?

Our company is almost 2 years old and we're working hard to release the app, but without Trusted Signing we're doomed - nobody would install an app that shows as "Not verified"

What are our other options here? Are there any other ways we can submit our app through the verification process?

Answer 1

Meha-MSFT 2,125 Microsoft Employee Moderator

Yes, plan is to open it up for all the organizations regardless of when they were incorporated, we are working on that, however, don't have an ETA to share.

0 comments

Answer 2

Dimitar Mitov 20

@Vinodh247-1375 Thank you for your response - we got everything you listed in check.

@Givary-MSFT The failed one is

4e5286d4-1651-48b1-9f83-532ced63dccc

After some reading on Github, I found out that we should remove the domain protection on the listed domain so you guys can check if it's registered to the proper legal entity. I did so and submitted a new Verification Request with the id:

ddcdb880-0aa4-4dd6-ad0c-3772f3303ee8

The last is with status "In progress" since September 21st, but hopefully it gets approved 🤞

0 comments