Skip to content
DOCS

Sign for Windows

Set up Azure Artifact Signing so Windows trusts your cloud builds, or use a .pfx certificate you already have.

Since June 2023, a code-signing certificate that Windows trusts must keep its private key in hardware or a cloud service, so it can't be exported as a file. Azure Artifact Signing is that cloud service, at $9.99/month on the Basic tier: Freqlab signs your builds with it, and Windows trusts the signature.

Allow time for this: Microsoft checks your identity, which takes 1 to 20 business days. See also Microsoft's quickstart.

1. Get a paid Azure subscriptionLink to this section

Sign in at portal.azure.com on a Pay as you go subscription. Free and trial subscriptions are rejected.

To upgrade one: Subscriptions, your subscription, Settings, Billing properties, the Plan link, Pay as you go, Upgrade your account, Basic (included), Upgrade now. If you'd already created the signing account, its deployment failed: open the failed deployment and redeploy it.

2. Create an Artifact Signing accountLink to this section

Search for "Artifact Signing" at the top of the portal, open Artifact Signing Accounts, and click Create:

  • Subscription: your paid subscription.
  • Resource group: Create new, for example freqlab-signing.
  • Account name: any name, for example yourname-signing.
  • Region: any the list offers. It doesn't need to match where you or your buyers are.
  • Pricing tier: Basic.

Click Review + create, then Create, and open the account once it's deployed.

3. Give yourself the Identity Verifier roleLink to this section

You need it to start an identity check; being the subscription Owner isn't enough. In the signing account, open Access control (IAM), Add, Add role assignment, search for Artifact Signing Identity Verifier, click Next, Select members, choose yourself, then Review + assign.

4. Validate your identityLink to this section

In the signing account's menu, under Objects, open Identity validations. Choose Organization or Individual, then New identity, Public:

  • Organization: your legal company name, website, two email addresses on your company's domain, address and business identifier (in the US, your EIN without the dash), plus one person who verifies their government ID when the status shows Action Required. You may need to prove you own the domain; a registrar invoice works. Only some countries are supported (see Microsoft's quickstart).
  • Individual: a government ID plus a utility bill or bank statement, with your Azure billing account set up as an individual under the same name and address. US and Canada only.

The status shows Completed when it's done.

5. Create a certificate profileLink to this section

Under Objects, open Certificate profiles, Create, Public Trust:

  • Profile name: any name, for example public.
  • Verified CN and O: your identity validation from step 4 (the rest fills in).
  • Program type: None. Leave street address and postal code unchecked.

6. Create an app registrationLink to this section

This is the login Freqlab signs with. Search for "Microsoft Entra ID", open App registrations, New registration:

  • Name: any name, for example freqlab-signing.
  • Supported account types: Accounts in this organizational directory only.
  • Leave Redirect URI empty, and click Register.

On its Overview, copy the Application (client) ID and Directory (tenant) ID. Then, next to Client credentials, click Add a certificate or secret, New client secret (up to 24 months), and copy its Value straight away: it's shown once, and the Secret ID isn't the secret.

7. Let the app signLink to this section

Back in the signing account, open Access control (IAM), Add role assignment, search for Artifact Signing Certificate Profile Signer, Next, Select members, and type the app's name (apps only appear when you search). Select the app, not your own account, then Review + assign.

8. Add it to FreqlabLink to this section

In Signing credentials, click Set up under Windows, choose Azure Artifact Signing, give it a Label, and enter the Tenant ID, Client ID and Client Secret Value. Click Connect to Azure, then pick the Signing Account and Certificate Profile.

Keep it workingLink to this section

Freqlab can't see these expiry dates, so it can't warn you. Put them in your calendar:

  • The client secret expires (up to 24 months). Make a new client secret on the same app registration, then click Update on the credential, enter the IDs and the new Value, Connect to Azure, and pick the same account and profile.
  • The identity validation expires; Azure shows the date. Renew it before then, or signing stops.

Certificate (.pfx)Link to this section

For a certificate you already have as a .pfx, such as a self-signed one or one from your organization's own certificate authority. Builds are signed with it, but Windows doesn't trust it: people see Not signed, and freqlab.co won't list the release.

  1. Export the certificate and its private key as a .pfx with a password.
  2. In Signing credentials, click Set up under Windows, choose Certificate (.pfx), give it a Label, upload the file and enter the .pfx Password.

After saving, check the credential shows an expiry date (Valid until or Expires in). If it doesn't, the file or password was wrong, and builds will fail with a Signing Error.

If Connect to Azure failsLink to this section

Message mentionsWhat to do
AADSTS7000215The secret isn't valid. Enter its Value, not the Secret ID, and check it hasn't expired
AADSTS7000222The client secret expired. Make a new one (see above)
AADSTS700016The Client ID or Tenant ID is wrong. Copy them again from the app's Overview
AADSTS90002 or AADSTS900023The Tenant ID is wrong
Cannot list Azure subscriptionsGive the app the Artifact Signing Certificate Profile Signer role (step 7)
No Artifact Signing accounts foundCheck the account deployed (step 2) and the app has its role on it
No certificate profiles foundCreate one (step 5), after your identity validation is Completed