Skip to main content

Azure Artifact Signing vs an EV code signing certificate

An honest 2026 comparison of Microsoft's Azure Artifact Signing (formerly Azure Trusted Signing) against a Certum EV code signing certificate, including the cases where Azure is the better choice.

Verdict

If you already run on Azure, ship only Windows user-mode applications, and your business is registered in a supported country, Azure Artifact Signing is cheaper and easier — use it. Buy an EV certificate when you submit drivers to the Windows Hardware Developer Program, when you are outside the supported countries, when you need to sign artifacts that are not Authenticode, or when procurement requires a named certificate authority and an invoice.

Azure Artifact Signing compared with an EV code signing certificate
Azure Artifact SigningEV code signing certificate
PriceAbout $9.99 per month plus per-signature costFrom €289 per year, net
Signs Authenticode (.exe, .dll, .msi)YesYes
Kernel-mode drivers via Windows Hardware Dev CenterNoYes
Available worldwideNoYes
Requires an Azure subscriptionYesNo
Private key on certified hardwareYesYes
Signs Java, Android or other non-Authenticode artifactsNoYes
Works without cloud vendor lock-inNoYes

Sources: Certum product documentation; CA/Browser Forum baseline requirements for code signing (hardware protection since June 2023). Last reviewed 10 August 2026 by Luis Santos.

Microsoft’s signing service is the first thing most Windows developers evaluate before buying a certificate, and it deserves a straight answer rather than a sales pitch. Here is where each option genuinely wins.

Where Azure Artifact Signing wins

Cost, if you fit the profile. At roughly $9.99 a month it is cheaper than any commercial EV certificate for a team that signs continuously.

CI/CD ergonomics. Signing authenticates through Azure identity, which is a far better fit for an unattended build agent than a TOTP-protected desktop session. If your build already runs in Azure DevOps or GitHub Actions with an Azure identity, the integration is close to trivial.

No validation waiting period beyond the initial account verification.

Where an EV certificate wins

Kernel-mode drivers. Submissions through the Windows Hardware Developer Program require an EV code signing certificate. Azure Artifact Signing cannot do this. If drivers are on your roadmap at all, this decides the question by itself.

Geographic eligibility. Azure Artifact Signing is restricted to verified businesses in a limited set of countries. A certificate has no such restriction — which matters for Nordic and DACH vendors selling globally.

Non-Authenticode artifacts. Azure signs Authenticode targets. A certificate is just a certificate: use it for whatever your toolchain supports.

Procurement. Some buyers require a named commercial certificate authority, a subscriber agreement and a VAT invoice. That is a real requirement even when it is not a technical one.

What neither of them does

Neither gives you instant SmartScreen reputation. That changed in 2024 and it applies equally to both. Anyone telling you otherwise is working from pre-2024 material.

The practical recommendation

Start by answering one question: do you ship kernel-mode drivers, now or within the certificate’s lifetime? If yes, buy EV code signing and stop reading. If no, and you are inside Azure’s supported countries and already on Azure, use Azure Artifact Signing. If no but you are outside those countries or want independence from a cloud vendor, standard code signing is the cheaper certificate and does everything user-mode software needs.

Next step

Questions that decide it

Was Azure Trusted Signing renamed?

Yes. Microsoft renamed Azure Trusted Signing to Azure Artifact Signing in January 2026. Many comparison pages still use the old name, which is a useful signal of how recently they were updated.

Does Azure Artifact Signing give instant SmartScreen reputation?

No, and neither does EV any more. Microsoft removed the EV instant-reputation bypass in 2024. Both options build SmartScreen reputation the same way: through download volume against a stable signing identity.

Can I use both?

Yes, and some teams do — Azure for routine internal builds, an EV certificate for the driver submissions and the publicly distributed installer. The identities are separate, so the reputation is separate too.

Two products, one year, one price

Certificates are issued by Certum, a certificate authority on the EU Trusted List. We check the application before you pay and refund in full if it cannot be issued.