SSRS URL certificate renewal

Question

SSRS URL certificate renewal

Gaddam Abhishek Reddy 0

The SQL Server certificate associated with the SSRS URLs will expire on June 26th. A replacement certificate has been installed on the SQL Server, but instructions are needed for correctly binding it to the SSRS URLs. Could you please advise whether the existing certificate should be removed before the new one is bound? Thanks in advance. Any suggestions are welcome

0 comments

2 answers

Your answer

Answer 1

Deepesh Dhake 80

I'd suggest leaving the existing certificate in place rather than removing it first, keeping it in the certificate store gives you a quick rollback if anything goes wrong.

Before you start, just confirm the new cert is in the Local Computer Personal store with its private key, the SSRS service account has read access to that key, and the Subject or SAN covers every hostname your SSRS URLs use. Backing up the SSRS encryption key beforehand is also a good habit.

To swap, open Reporting Services Configuration Manager, go to Web Service URL then Advanced then edit the existing HTTPS Identity to point at the new certificate, and Apply. Then do the same on Web Portal URL Advanced. Test both URLs from a client machine afterward to confirm the new cert is being served.

If anything looks off, simply point the binding back at the old cert, recovery only takes a minute since it's still in the store.

Akhil Gajavelly 1,825 Reputation points Microsoft External Staff Moderator

2026-06-04T04:37:38.3733333+00:00

Hi @Gaddam Abhishek Reddy ,

One additional point: after updating the bindings in Reporting Services Configuration Manager, verify that any load balancers, reverse proxies, or monitoring systems that connect to SSRS also trust the new certificate chain. In some environments, the SSRS URLs may work locally while external users still receive certificate warnings if an intermediate certificate is missing.

It can also be helpful to confirm the certificate thumbprint being served after the change by connecting from a client machine (not the SSRS server itself) to ensure there is no certificate caching or unexpected binding issue.

Otherwise, I agree with keeping the old certificate in place until the new one has been fully validated, as it provides a straightforward rollback option if any issues are encountered.

Thanks,
Akhil.

Answer 2

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more

Share via

SSRS URL certificate renewal

2 answers

Your answer