Azure Artifact Signing (Trusted Signing) for EXE Code Signing

Updated

In This Article

Code signing is an essential process for software developers, ensuring that their applications are trusted by Windows and antivirus software. Many of our software products generate EXE files and can digitally sign them. Traditionally, developers had to buy an expensive code signing certificate (several hundred US dollars a year) and store it on a USB token or in a hardware security module (HSM).

Azure Artifact Signing is Microsoft's cloud-based alternative. It was launched as Azure Trusted Signing and renamed in 2026: the service is identical, only the name changed, and you will still meet the old name in the Azure portal search box, in role names and in tools such as the azure/trusted-signing-action GitHub Action. This article explains why Azure Artifact Signing is a cost-effective and secure way to sign EXE files, what Microsoft requires before you can use it, and how to set up an account.

Once your Artifact Signing account is ready, you can use it with our software tools, such as Paquet Builder, our Windows installer creator, or XLS Padlock, our Excel workbook compiler, to sign the generated EXE files.

Why Choose Azure Artifact Signing Over Traditional Code Signing?

Section titled “Why Choose Azure Artifact Signing Over Traditional Code Signing?”
  • Cost-Effective Pricing Model

    Traditional EV code signing certificates cost $300 to $900 a year. Azure Artifact Signing is billed monthly per account: the Basic tier costs $9.99 a month and includes 5,000 signatures a month, the Premium tier costs $99.99 a month for 100,000 signatures; beyond the quota each signature costs $0.005. There is no USB token or HSM to buy. Prices as published by Microsoft in October 2026; check the Artifact Signing pricing page for the current figures.

  • No USB Token or Hardware Module Required

    Traditional signing methods require an HSM or a USB token to hold the private key. With Azure Artifact Signing the keys live in Microsoft-managed FIPS 140-3 Level 3 hardware modules and never leave them: no key to lose or to have stolen, and your file never leaves your computer either, only its digest is sent for signing. Access goes through your Azure identity, with multi-factor authentication.

  • Automated Certificate Management

    Certificates are renewed every day and each one is valid for only 72 hours, which limits the damage a stolen or misused certificate could do. Microsoft handles the whole lifecycle; there is nothing to renew or to install.

  • Easy Integration with Our Developer Tools

    Works with Microsoft SignTool (through the Artifact Signing Client Tools), the Azure CLI, GitHub Actions and Azure DevOps pipelines. Our installer Paquet Builder and XLS Padlock 2026.2 sign with it directly, without SignTool.

Azure Artifact Signing pricing tiers, Basic and Premium, as shown in the Azure portal (the screenshot still carries the Trusted Signing name)

Why Do Azure Artifact Signing Certificates Only Last 72 Hours?

Section titled “Why Do Azure Artifact Signing Certificates Only Last 72 Hours?”

Unlike traditional code signing certificates, which are valid for one or more years, Azure Artifact Signing issues a new certificate every day and each one is valid for 72 hours. This is a security measure: if a certificate is misused, Microsoft can revoke that day's certificate alone, and only the code signed with it on that day is affected.

Will My Signed EXE Files Expire With the Certificate?

Section titled “Will My Signed EXE Files Expire With the Certificate?”

When you sign your EXE files with Azure Artifact Signing, a timestamp countersignature from Microsoft's timestamp authority (http://timestamp.acs.microsoft.com) is attached to the signature. This means that:

  • The signature remains valid after the signing certificate expires.
  • Windows and security tools keep recognizing the signature, because the timestamp proves it was made while the certificate was valid.

Step-by-Step Guide: Setting Up Azure Artifact Signing

Section titled “Step-by-Step Guide: Setting Up Azure Artifact Signing”

If you don't already have an Azure account, create one at Microsoft Azure Sign-Up.

Once signed in, create a new subscription (Pay-As-You-Go recommended).

Step 2: Create an Artifact Signing Account

Section titled “Step 2: Create an Artifact Signing Account”
  1. In the Azure portal, search for "Artifact Signing" (the resource was listed as "Trusted Signing Accounts" before the rename, and the search box still finds it under that name).

    Trusted Signing Accounts in the Azure portal search box

  2. Click "Create". Enter an account name, select your Azure subscription and resource group, then choose your region and pricing tier (Basic for most publishers).

    Create an Artifact Signing account

  3. Click "Create" and note the account URI, which you will need later.

To control who may validate identities and who may sign, assign two roles on your new account. Their names still carry the old service name:

Assign the Identity Verifier Role to Your Azure User Account

Section titled “Assign the Identity Verifier Role to Your Azure User Account”

This role grants your Azure user account the permission to manage identity validation requests. Even as the administrator of the subscription, you need it: without it the New identity button stays greyed out.

  1. Navigate to your Artifact Signing account in the Azure portal.
  2. Click on Access Control (IAM).
  3. Select Add, then Add role assignment.
  4. Search for and select the Trusted Signing Identity Verifier role.
  5. Proceed through the wizard to assign this role to your Azure user account.

Artifact Signing account: Access control (IAM), Role assignments

Assign the Certificate Profile Signer Role to Your Application's Service Principal

Section titled “Assign the Certificate Profile Signer Role to Your Application's Service Principal”

This role allows your application, or your own user account for manual signing, to sign code with the service.

Do the same steps as above, but choose the Trusted Signing Certificate Profile Signer role this time.

  1. Navigate to Identity validations in your Artifact Signing account.

    Identity validations page of the Artifact Signing account

  2. Choose "Organization" or "Individual" depending on your situation (see the eligibility rules above).

  3. Click New Identity, then Public. Provide your business details and supporting documents. The legal name you enter becomes the name in the certificate; it cannot be customized.

  4. Submit the request and wait for Microsoft's verification: 1 to 20 business days, longer if documents are requested.

  1. Once your identity is validated, go to Certificate profiles.

    Certificate profiles

  2. Click "Create", then "Public Trust". Select your identity in Verified CN, O and choose the type of code signing certificate needed.

  3. Save the certificate profile name for later use.

Conclusion: Using the Azure Artifact Signing Service

Section titled “Conclusion: Using the Azure Artifact Signing Service”

Now you can sign your executable files. With SignTool you need the Artifact Signing Client Tools (winget install Microsoft.Azure.ArtifactSigningClientTools) and a small metadata.json naming your account endpoint and certificate profile; the standard SignTool of the Windows SDK cannot talk to the service on its own. Our tools do it for you: Paquet Builder signs installers and 7-Zip self-extracting archives with Azure Artifact Signing from its own settings, and XLS Padlock 2026.2 brought the same Azure signing options to compiled workbooks.

Paquet Builder configuration of the Azure Artifact Signing account