This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(195.2, 61%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETA%3C/text%3E%3C/svg%3E)
Hello Support,
I was under the impression that Azure Trusted Signing is available to individuals (not just organizations) according to this article: https://techcommunity.microsoft.com/blog/microsoft-security-blog/trusted-signing-is-now-open-for-individual-developers-to-sign-up-in-public-previ/4273554
However, when I go to create a new Identity Validation for an Individual in my subscription, the "New Identity" button is disabled with the message:
At this time Trusted Signing is only available to organizations based in the USA and Canada that have a verifiable history of three years or more.
I have enabled the CodeSigning resource provider in my subscription, and added myself to the "Trusted Signing Identity Verifier" access role.
Is the individual option no longer available or am I missing something? Thank you!
Hey @SrideviM , thank you for the response. I was hoping this wasn't the case, but I'll wait for GA.
Thanks again!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(6.4, 5%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
Hello Tony Anziano,
If this answers your query, do click Accept Answer which may help members with similar questions. And, if you have any further query do let us know
Hello Tony Anziano,
I understand you're trying to set up Azure Trusted Signing as an individual, and you're seeing the "New Identity" option disabled with a message stating it's only available to certain organizations.
As of April 2, 2025, Microsoft has updated the onboarding requirements. Trusted Signing is currently limited to organizations based in the USA and Canada that have a verifiable history of at least three years.
This updated requirement is also clearly reflected in the official documentation under the Prerequisites section:
Due to this change, individual developers or organizations that don’t meet these criteria will see the "New Identity" button disabled in the Azure portal.
Microsoft has mentioned plans to expand availability closer to General Availability (GA), you can refer this Microsoft Security Blog for further updates.
Hope this clarifies things a bit!
If this answers your query, do click Accept Answer and Yes for was this answer helpful, which may help members with similar questions.
If you have any other questions or are still experiencing issues, feel free to ask in the "comments" section, and I'd be happy to help.