# Orvi production signing Status: build integration is implemented. A trusted publisher certificate has NOT been issued, and no production signing account has been created or billed in this task. The installer is unsigned. Publisher expected by the installer/updater: **Blumberg Ventures, LLC**. Use the exact legal name returned by the certificate authority. If validation returns a different legal spelling, update and review the publisher pins before the first signed release. ## Activation 1. Sign in to Microsoft Azure with the business’s account. An Azure subscription and Microsoft Entra tenant are required. 2. Create an Artifact Signing account with a Public Trust organization identity. Microsoft’s Basic tier is a paid subscription; review the current price before creating it. 3. Complete Microsoft’s business identity validation. Supply legal entity details, business identifier, owned website and domain email, and any identity documents directly to Microsoft. Do not put them in source code or chat. 4. Create a **PublicTrust** certificate profile from the validated identity (not PublicTrustTest or PrivateTrust). 5. Grant the release identity only the certificate profile signer role for that profile. Use workload identity/OIDC or a managed identity for automation where available. Keep any required credentials in a secret manager. 6. Configure non-secret build variables: `ORVI_SIGNING_ENDPOINT`, `ORVI_SIGNING_ACCOUNT`, `ORVI_SIGNING_PROFILE`. Configure supported Azure Identity authentication on the Windows build host. The endpoint must match the account’s region. 7. Run `npm ci`, `npm run check`, then `npm run package:win:signed` on Windows. electron-builder signs the application and NSIS installer, with SHA-256 and an RFC 3161 timestamp. Packaging fails closed if credentials/profile are absent or signatures fail verification. 8. Run `scripts/verify-release.ps1` against the final installer and installed application. The updater independently verifies the Windows trust chain, timestamp and exact publisher name at download and again before installation. 9. Complete the Windows release checks in VERIFICATION.md before promoting to production. Deploy the exact installer with the matching release-record.json. Never mark an unsigned build as signed in feed metadata. The code does not export or generate a private signing key. Microsoft keeps Artifact Signing keys in its service. A locally generated self-signed certificate does not establish public publisher trust. Do not install a custom root on customer computers or ask customers to disable SmartScreen. Even a legitimately signed new application can initially show reputation warnings. ## References checked November 4, 2026 - https://learn.microsoft.com/en-us/azure/artifact-signing/quickstart - https://learn.microsoft.com/en-us/azure/artifact-signing/faq - https://learn.microsoft.com/en-us/windows/apps/package-and-deploy/code-signing-options - electron-builder 26.18.0 `WindowsAzureSigningConfiguration` and built-in Azure signing manager (installed source reviewed).