You will learn what Salesforce Health Insights does, its two pillars of Product Adoption and Implementation Health, and who can access it in the Winter '27 release.
Why read this
The piece stays at the level of an overview and does not explain how to configure it.
Scan org configuration and usage
Evaluate against benchmarks
Rank findings by severity
Deliver next best actions
How Salesforce Health Insights turns an org scan into next actions
Salesforce Health Insights is a Salesforce-native solution that scans an org, evaluates it against benchmarks, and turns the findings into prioritized next best actions. The article presents it as a way to replace a manual org health review, which it says can take up to three weeks, with an on-demand scan that returns ranked results in near real time. The recommendations are built from the org’s own configuration, feature set and usage patterns, and ranked by criticality and the effort needed to fix them.
The tool has two pillars. Product Adoption shows which licensed capabilities are owned, which are used, and where there is room to grow, including license utilization over the past 30 days. Implementation Health delivers severity-ranked insights across Security and Process Automation, with recommendations meant to reduce exposure and prevent automation failures. The article also describes a headless delivery model, with a conversational view inside Salesforce and access through Slackbot outside it.
According to the article, Salesforce Health Insights is available with the Winter ’27 release for Signature Success Plan customers on Core products at no extra cost, and is found by searching for it in the App Launcher. The piece is a product announcement written by Salesforce and gives no detailed configuration steps or measured results.
By Karishma Lalwani and Anand Vardhan · Salesforce EngineeringThe piece outlines the architectural patterns used to standardize hundreds of health signals and expose them through headless APIs.
Readers will learn how Salesforce Engineering correlates configuration metadata with production telemetry to identify and prioritize implementation anti-patterns.
Why read this
The piece outlines the architectural patterns used to standardize hundreds of health signals and expose them through headless APIs.
Salesforce Engineering addressed the challenge of monitoring enterprise org health at scale by moving beyond static reports to an in-app experience called Salesforce Health Insights. The team needed to correlate point-in-time configuration metadata with continuously changing runtime telemetry across systems that lack shared identity models.
To solve this, they built a harmonization layer that reconciles fragmented datasets and maps runtime activity to individual metadata components while accounting for traffic volume and seasonality. This architecture maintains clear boundaries between deterministic findings and external operational context, preserving data origin and freshness information.
The initiative expanded from roughly one hundred initial security signals to over four hundred covering process automation, customization, and agentic readiness. Each signal follows standardized metadata rules and remediation guidance derived from the Salesforce Well-Architected Framework and known system hotspots.
Findings are prioritized using operational context such as application CPU usage and peak business hour traffic to determine criticality and required effort. The system uses a headless schema that emits raw JSON for any user interface or agent, supports an MCP interface, and can deliver summaries directly to Slack channels.