Salesforce ends public certificate rotation alerts on July 6, 2026, shifting TLS change tracking out of the Trailblazer Community
Salesforce ended public certificate rotation alerts on July 6, 2026, removing routine TLS certificate change notices from the Trailblazer Community and shifting tracking to official release channels. The change is documented in Salesforce’s release notes on certificate lifespans and summarized in the Salesforce Summer ’26 highlights, and it requires CRM teams to adjust how they monitor upcoming rotations immediately.
Salesforce removes Trailblazer Community certificate alerts for first-party production orgs
Salesforce states that it is stopping the existing public announcements for first-party production org certificate rotations, with the July 6, 2026 cutoff noted in its release notes on certificate lifespans. The same July 6 date is captured in the Salesforce Summer ’26 highlights, which consolidate what changed across the season’s security updates.
Shorter certificate lifecycles drive the policy shift
What typically happens during compressed certificate lifecycles is a rapid cadence of rotations that makes community posts noisy and easy to miss. Salesforce’s security blog outlines the push toward automation and shorter-lived keys in the “short‑lived certificate era,” reinforcing why customers should rely on internal processes rather than ad hoc community notices; see the taxonomy guidance in Salesforce’s security blog on automating certificate management. The Summer ’26 overview also flags that certificate lifespans for new public certificates are shorter than in prior years, adding pressure to modernize monitoring and renewal workflows, as summarized in the Salesforce Summer ’26 highlights.
Immediate implications for Salesforce admins and ISVs
In practice, teams that relied on Trailblazer Community posts must now track rotations via official documentation and environment-specific notifications. Start by watching Salesforce’s release notes on certificate lifespans for upcoming changes, and align internal alerting with your integration inventory so renewals happen before cutover windows. For organizations that have been moving to automated certificate procurement and rotation, the guidance in Salesforce’s security blog on automating certificate management maps cleanly to the new notification model.
Share With Others
