Blog Post

Microsoft Security Community Blog
2 MIN READ

Trusted Signing Public Preview Update

IanCS_MSFT's avatar
IanCS_MSFT
Icon for Microsoft rankMicrosoft
Apr 02, 2025

Nearly a year ago we announced the Public Preview of Trusted Signing with availability for organizations with 3 years or more of verifiable history to onboard to the service to get a fully managed code signing experience to simplify the efforts for Windows app developers. Over the past year, we’ve announced new features including the Preview support for Individual Developers, and we highlighted how the service contributes to the Windows Security story at Microsoft BUILD 2024 in the Unleash Windows App Security & Reputation with Trusted Signing session.

During the Public Preview, we have obtained valuable insights on the service features from our customers, and insights into the developer experience as well as experience for Windows users. As we incorporate this feedback and learning into our General Availability (GA) release, we are limiting new customer subscriptions as part of the public preview. This approach will allow us to focus on refining the service based on the feedback and data collected during the preview phase. The limit in new customer subscriptions for Trusted Signing will take effect Wednesday, April 2, 2025, and make the service only available to US and Canada-based organizations with 3 years or more of verifiable history. Onboarding for individual developers and all other organizations will not be directly available for the remainder of the preview, and we look forward to expanding the service availability as we approach GA.

Note that this announcement does not impact any existing subscribers of Trusted Signing, and the service will continue to be available for these subscribers as it has been throughout the Public Preview.

For additional information about Trusted Signing please refer to Trusted Signing documentation | Microsoft Learn and Trusted Signing FAQ | Microsoft Learn.

Updated Apr 01, 2025
Version 1.0

7 Comments

  • GillesNoyer's avatar
    GillesNoyer
    Copper Contributor

    This solution is truly very interesting. Given the constraints imposed by certificate vendors, which make using a certificate attached to a dongle unusable, the need for a dongle-free signing solution is very important.

    I hope Microsoft will quickly implement GA for all countries around the world. It's urgent.

  • AEK's avatar
    AEK
    Copper Contributor

    It's been nearly two months and there is a desperate demand for this in the EU or other countries outside US/CA.

    Any updates regarding a timeline for GA?

  • pl4nty's avatar
    pl4nty
    Copper Contributor

    Bit disappointing that signing was blocked immediately after this post, we missed out by a couple days. Would really help to have a timeline on GA, even "<3 months" or "6+ months", so we can decide whether to wait for GA or renew our existing cert

  • Inmatrix's avatar
    Inmatrix
    Copper Contributor

    With non-microsoft certificates costing nearly $400/year to sign an EXE to upload to the Microsoft store, this is a serious pain for developers and you've just excluded most of the world from the "cheaper" $120/year option.

    It's not fun being a developer for Windows these days. Why are you making our lives more difficult instead of trying to help us develop for your platform?

  • GalSNetBet's avatar
    GalSNetBet
    Copper Contributor

    We missed it as well by a few days. 
    Do you know when the service will be available again for other countries?

     

  • ocarro's avatar
    ocarro
    Copper Contributor

    The same thing happened to us, for a day we did not arrive.
    We will be waiting for the final version to arrive.

  • Unfortunately, we were a day late for the registration - we had tried in vain yesterday as a German company.
    Can you already estimate when you are planning the General Availability (GA) release of this service? We would like to make our TestWeasel available this month in version 1.0 code-signed via Windows Installer.