SqlCertForge TLS certificate binding for SQL Server and Reporting Services

Adoption guide

A 49-page guide covering every phase of putting TLS on SQL Server, Reporting Services, and Power BI Report Server, followed by the full command reference.

One document covering every phase of taking SQL Server and Reporting Services from unencrypted to verified TLS, written for a mixed audience — management, DBAs, sysadmins, and whoever signs off on new software each get a track that answers their question.

Download the adoption guide (PDF)

Who each part is for

  • Management / a budget owner. What the tool removes: a recurring, error-prone certificate chore and the outages its two classic mistakes cause.
  • A DBA. Getting the database engine encrypted correctly, including Always On replicas.
  • A sysadmin. The certificate store, URL reservations, service accounts, and restarts for Reporting Services and Power BI Report Server.
  • Compliance / an auditor. What is enforced — least privilege on the private key, no silent lockout, proof the endpoint actually serves — and what evidence each step leaves.

The six phases

Assess (free, read-only) → Plan (a decision, not a command) → Provision (issue from your own CA, or import a purchased certificate) → Apply (grant the private-key permission everyone forgets, then bind) → Verify (a real HTTPS round-trip, not a config read) → Operate (renewal). Everything runs inside your network — the commands talk to your own CA and your own servers, and the license is verified offline.

The command reference

The guide ends with every command in full — the same pages published in the online reference — so it stands alone offline, useful when the person reviewing it is not the person with access to the environment.