Azure Trusted Signing (now Artifact Signing)
Azure Trusted Signing, renamed Artifact Signing in 2026, is Microsoft's own code signing service for Windows apps. It costs $9.99 a month, needs no USB token, and works from CI. Here's who can use it, how to set it up, and the exact SignTool command.
Azure Trusted Signing is Microsoft's managed code signing service. You verify your identity with Microsoft once, and from then on your builds are signed with certificates Microsoft issues and keeps in its own hardware. There's no certificate file to buy and no USB token to plug in, which makes it the easiest way to sign a Windows app from a CI pipeline.
It has a new name. In January 2026 the service became generally available and Microsoft renamed it Artifact Signing. In Microsoft's words, "Artifact Signing is simply the new name for Trusted Signing". The documentation, the Azure roles and the GitHub Action have all been renamed, and most people still search for the old name. This page uses both.
Everything below was checked against Microsoft's documentation and pricing page on November 17, 2026.
What it costs
| Basic | Premium | |
|---|---|---|
| Price per month | $9.99 | $99.99 |
| Signatures included per month | 5,000 | 100,000 |
| Extra signatures | $0.005 each | $0.005 each |
| Certificate profiles | 1 of each type | 10 of each type |
Basic is enough for nearly every independent developer: 5,000 signatures a month covers a lot of builds, even when each build signs several files. A few details from Microsoft's FAQ:
- Billing starts when you create the signing account, and it isn't prorated
- The signature quota is shared across the whole account
- Free, trial and sponsored Azure subscriptions aren't supported, so you need a pay-as-you-go subscription
For comparison, a certificate from a traditional certificate authority costs from a little over $100 a year to close to $1,000, and you also need hardware to hold the key. The page on EV code signing certificates has current prices.
Who can use it
This is the catch. Publicly trusted certificates are only available in some countries. Microsoft's quickstart says:
- Organizations in the United States, Canada, the European Union, the United Kingdom, Australia, New Zealand, Japan, South Korea, Singapore, Switzerland, Norway and Israel
- Individual developers in the United States or Canada only
(Some other Microsoft pages still show a shorter list for organizations. The quickstart is the one the service's own FAQ points to.)
If you're an individual outside the US and Canada, or a company outside that list, you can't get a Public Trust certificate from this service today, and a certificate from a traditional certificate authority is the route.
Identity validation is a real check:
- Individuals need an Azure billing account of type Individual, with a legal name and address that match a government-issued ID. The check runs through Microsoft Entra Verified ID in the Microsoft Authenticator app.
- Organizations provide their legal name, website, a business identifier, an address, and an email on the organization's own domain. Microsoft says this takes from 1 to 20 business days, and it may ask for documents.
How it works
Traditional code signing gives you one certificate that lasts a year or more, and you guard its private key. This service turns that around:
- Certificates last 72 hours. Microsoft renews them daily. You never see the private key, and it can't be exported.
- Keys live in Microsoft's hardware security modules. Signing happens by sending a digest of your file to the service.
- Timestamps do the long-term work. Since the certificate expires in three days, every signature has to be timestamped, so Windows knows it was made while the certificate was valid. Microsoft's timestamp server is
http://timestamp.acs.microsoft.com. - Your identity is constant even though certificates rotate. Each certificate carries your verified name, and that's what Windows shows as the publisher. You can't choose a custom name.
Three terms you'll meet in the Azure portal:
- Signing account: the Azure resource, tied to a region
- Identity validation: the one-time check of who you are
- Certificate profile: what you sign with. For software you give to the public, that's a profile of type Public Trust
Set it up
- Register the resource provider in your Azure subscription. It's still called
Microsoft.CodeSigning:
az provider register --namespace "Microsoft.CodeSigning"
- Create a signing account. Pick a region and remember it, because the endpoint depends on it:
az extension add --name artifact-signing
az artifact-signing create -n MyAccount -l eastus -g MyResourceGroup --sku Basic
Give yourself the "Artifact Signing Identity Verifier" role on the account, then complete identity validation. This part can only be done in the Azure portal.
Create a certificate profile of type Public Trust, once your identity is validated.
Give whoever signs the "Artifact Signing Certificate Profile Signer" role. That's your own user for signing locally, or a service principal for CI. Being Owner or Contributor of the subscription isn't enough: without this role, signing fails with a 403.
Sign with SignTool
Trusted Signing plugs into SignTool through a small library (a "dlib") and a JSON file that says which account to use. You need a recent Windows SDK SignTool, the .NET 8 runtime, and the client tools, which you can install in one step:
winget install -e --id Microsoft.Azure.ArtifactSigningClientTools
Create a metadata.json:
{
"Endpoint": "https://eus.codesigning.azure.net",
"CodeSigningAccountName": "MyAccount",
"CertificateProfileName": "MyProfile"
}
The endpoint is https://<region-code>.codesigning.azure.net, and it must be the region of your account: eus for East US, wus2 for West US 2, weu for West Europe, neu for North Europe, and so on. A mismatched region is the usual cause of a 403 Forbidden.
Then sign:
signtool sign /v /debug /fd SHA256 /tr "http://timestamp.acs.microsoft.com" /td SHA256 /dlib "C:\Program Files (x86)\Microsoft\ArtifactSigningClientTools\bin\Azure.CodeSigning.Dlib.dll" /dmdf "metadata.json" MyApp.exe
/dlibpoints at the signing library. Use the x64 library with the x64 SignTool/dmdfpoints at yourmetadata.json/trand/tdadd the timestamp, which isn't optional here/v /debugprint what's happening, which you'll want the first time
The library signs in with whatever Azure credentials it finds: your az login session on your own machine, or the AZURE_TENANT_ID, AZURE_CLIENT_ID and AZURE_CLIENT_SECRET environment variables in CI.
Check the result:
signtool verify /pa /v MyApp.exe
Sign in GitHub Actions
Microsoft maintains an action for this. It was azure/trusted-signing-action and is now azure/artifact-signing-action; the old repository redirects to the new one. It runs on Windows runners only.
permissions:
id-token: write
contents: read
steps:
- name: Azure login
uses: azure/login@v3
with:
client-id: ${{ secrets.AZURE_CLIENT_ID }}
tenant-id: ${{ secrets.AZURE_TENANT_ID }}
subscription-id: ${{ secrets.AZURE_SUBSCRIPTION_ID }}
- name: Sign files with Artifact Signing
uses: azure/artifact-signing-action@v2
with:
endpoint: https://eus.codesigning.azure.net/
signing-account-name: MyAccount
certificate-profile-name: MyProfile
files-folder: ${{ github.workspace }}\dist
files-folder-filter: exe,dll
file-digest: SHA256
timestamp-rfc3161: http://timestamp.acs.microsoft.com
timestamp-digest: SHA256
If you followed an older tutorial, note that the account input used to be called trusted-signing-account-name. In version 2 it's signing-account-name.
Sign in the right order: the executables and DLLs inside your installer first, then the installer itself. Otherwise the installer is trusted and what it unpacks isn't.
Does it remove the SmartScreen warning?
Not on day one, and Microsoft is direct about it: "Signing with Azure Artifact Signing does not provide instant SmartScreen trust."
What it does is let reputation build. An unsigned installer is treated as unknown forever. A signed one accumulates reputation as people download and run it, and Microsoft's FAQ says the prompt stops appearing once the file has enough download history. Its documentation puts that at typically several weeks and hundreds of clean installs, with no exact threshold.
Two things work in your favour:
- Reputation is tied to your verified identity and not to a single certificate, so it carries from one release to the next
- Nothing else does better. Extended validation certificates used to skip SmartScreen on the first download, and Microsoft removed that in 2024. Its own comparison lists the SmartScreen behaviour of a traditional certificate as the same as Artifact Signing
Trusted Signing or a traditional certificate
| Azure Trusted Signing | Certificate from a certificate authority | |
|---|---|---|
| Cost | $9.99 a month | From about $130 to about $1,000 a year, plus hardware |
| Where the key lives | Microsoft's hardware, never exported | A USB token, your own HSM, or the authority's cloud service |
| Signing from CI | Built for it | Needs a cloud signing service, since a token can't be plugged into a hosted runner |
| Available to | Listed countries only; individuals in the US and Canada | Worldwide |
| SmartScreen | Reputation builds over time | The same |
| Extended validation | Not offered | Available |
| Renewal | Automatic while your identity validation is current | Buy and validate again when it expires |
Microsoft's documentation recommends Artifact Signing for apps distributed outside the Microsoft Store. Choose a traditional certificate if you aren't eligible, or if you need an extended validation certificate for the Windows hardware program (kernel-mode drivers are signed through Partner Center, not with this service).
Limits worth knowing
- No extended validation certificates, and Microsoft's FAQ says there's no plan to issue them
- User-mode code only. Kernel-mode driver signing stays with Partner Center
- No custom publisher name. The certificate shows your validated legal name
- Accounts can't be moved between subscriptions, tenants or resource groups
- If your identity validation lapses, signing stops. Microsoft sends reminders starting 60 days before
- Files it signs: anything SignTool can sign, including
.exe,.dll,.msiand.msix
After signing
A signed installer gets your app past the first hurdle, which is being allowed to run. The next ones are getting paid, making sure each copy belongs to a customer, and delivering updates. If you sell your app from your own website, LicenseSeat handles license keys, device activation and update delivery for licensed customers. It charges a flat monthly fee and takes 0% of your revenue. The guide on how to sell software online covers the whole setup.
Common questions about Azure Trusted Signing
Is Azure Trusted Signing the same as Artifact Signing?
Yes. Microsoft renamed Trusted Signing to Artifact Signing when the service became generally available in January 2026. It's the same service, with renamed documentation, roles and GitHub Action. The resource provider is still Microsoft.CodeSigning.
How much does Azure Trusted Signing cost?
The Basic plan is $9.99 a month and includes 5,000 signatures. The Premium plan is $99.99 a month and includes 100,000. Extra signatures are $0.005 each on both plans.
Can individual developers use Azure Trusted Signing?
Only if they're in the United States or Canada, according to Microsoft's quickstart. Organizations can use it in a longer list of countries, including the EU and the UK.
Does Azure Trusted Signing bypass SmartScreen?
No. Microsoft says it doesn't provide instant SmartScreen trust. Signed files build reputation as they're downloaded, and the warning goes away once there's enough history. No certificate type skips that step any more.
Is it an EV certificate?
No. The service doesn't issue extended validation certificates. For SmartScreen that no longer makes a difference. It matters only if you need one to register for the Windows hardware developer program.
Do I need a hardware token?
No. The private key stays in Microsoft's hardware security modules and you sign by calling the service, which is why it works on hosted CI runners.
Why do I get a 403 Forbidden when signing?
The two usual causes are an endpoint that doesn't match your account's region, and a signing identity that's missing the "Artifact Signing Certificate Profile Signer" role. Check both, and make sure the account and profile names in metadata.json are exact.
Can I use it with Electron or Tauri?
Yes. Both can call SignTool or a custom signing command during the build, so you point them at the same dlib and metadata.json, or sign the output with the GitHub Action afterwards.