Trusted Signing is in Public Preview

I tried doing the identity validation for my company from Brazil, but it always fails with this message:

Please provide additional document(s) dated within the past 12 months to verify your association with the organization. Examples of verification documents are as follows:

Notice that it doesnt say which documents it is expecting, nor it gives me a way to upload anything.
Does anyone have any idea how to solve this issue?

(Btw, my company is active for more than 3 years)

Trusted Signing is available for individual developers: Trusted Signing is now open for individual developers to sign up in Public Preview! | Microsoft Community Hub. We are working on making it available for organizations incorporated less than 3 years ago and also working towards GA, however, we are unable to share an ETA.

Hi, any ETA/plans when/if this will be available for individual developers and if there will be another pricing model for lets say a individual open source non-profit dev who just wants to share their app with a small group of people who could benefit from the app and don’t want to be scared off by smartscreen/defender? I have found a link to a ms blog article on google related to it but it seems to have been removed again…

Still no news on when this will be open to individuals.

I tried having my identify verified but they are asking for company formation documents, which are not necessary for sole proprietors!

Please let us know when this will be available! 🙂

rakiasegev- Do we have an update when this will become GA?

rakiasegev .. Do you have any update when this will be moved to GA to use.

Hello anduxen, The_Vard, rakiasegev,

It is important to know the answer regarding signing Excel VBA, Visio VBA, Word VBA, etc. files.  Is there a favorable answer that supports signing Office files which contain VBA?  Is there any special configuration for the signing to work correctly?  Is this only possible with the Azure CLI?  Is it possible with Windows PowerShell?

On a related topic, the three days certificate expiration can make the ISV look incompetent.  The end user can and will observe that freshly purchased and installed software has an expired digital certificate.  Has this been resolved?

mickiwForce ; for testing purpose, i log with my azure account (i have to add the azure role "Trusted Signing Certificate Profile Signer)

i will check later with a managedidentity account

niko33 Code signing depends on timestamp pls look at this documentation from digicert.
What is Code Signing? | DigiCert FAQ

can you please tell me, the account you sign on to your windows computer, is that the same you have given access to in azure, on your trusted signing account?
or how do you authenticate ?

hello

i'm trying this azure service to sign our executables and dll. 

- i follow the doc and could use the powershell module to sign some tests executables

$params = @{
Endpoint = "https://weu.codesigning.azure.net/"
CodeSigningAccountName = "account"
CertificateProfileName = "certname"
FilesFolder = "folderwithexe"
FilesFolderFilter = "exe,dll"
FileDigest = "SHA256"
TimestampRfc3161 = "http://timestamp.acs.microsoft.com"
TimestampDigest = "SHA256"
}

-> i have my .exe signed on my folder. no problems. 

But i don't understand the short live of the certificate, 3 days ?  So if we publish our .exe today, in 3 days it will pass as expired ?