How to Resolve Revoked Trusted Signing Certificate on Azure

Select Language:

If you received an email saying that your Trusted Signing certificate might be revoked, and then another email confirming the revocation, it can be a concerning situation. This can affect your ability to sign your Windows executable, and it might lead to security warnings that worry your customers.

First, don’t panic. Here’s what you can do to address this issue and ensure your executable remains trusted and secure:

Start by collecting all related emails and documentation. Make sure you have the exact notices from the Trusted Signing team. This information will be useful for future reference and any inquiries.

Next, contact Microsoft’s support team directly through their official channels. You can usually find the contact options on their website or within the support portal specific to digital certificates. If you’ve already tried emailing [email protected] and haven’t received a response, consider submitting a support ticket through Microsoft’s official support system. Be sure to include all relevant details, such as the emails you received, your certificate details, and the impact on your product.

While waiting for a response, investigate options to obtain a new signing certificate. Consider purchasing a new certificate from a trusted Certificate Authority (CA). Once you acquire a new certificate, you’ll need to re-sign your executable with it. This process involves generating a new signature and testing to ensure it is recognized correctly by Windows and third-party security tools.

To prevent issues like false positives from security software such as Windows Defender, make sure that your executable is properly signed with a valid certificate. Properly signed software helps establish trustworthiness and reduces the chance of being flagged as malicious.

In the meantime, inform your customers about the situation if necessary. Let them know you’re actively working on resolving the issue, and provide guidance to avoid confusion or alarm if warnings occur.

By taking these steps—getting in touch with official support, obtaining a new certificate if needed, and properly signing your executable—you can maintain trust and ensure your software remains accessible and secure for your users.