Mandatory Changes Taking Effect

1. Modernized Record Experience in Aura Sites (Enforced)

What’s Changing:

  • The Create Record Form, Record Banner, and Record Detail components will be upgraded to Lightning Web Components (LWC).
  • Benefits: Improved accessibility, performance, and future scalability.

Action Required:

  • No opt-out available—this upgrade will be automatically enforced for all orgs in Summer ’25.
  • Test components in a sandbox before rollout.

2. Secure Roles Behavior & Sharing Group Updates in Sandboxes (Enforced)

What’s Changing:

  • To prevent unintended external access, Salesforce is securing role-based record access in non-preview sandboxes.
  • The sharing group “Roles and Subordinates” is renamed to “Roles and Internal Subordinates” (visible before enabling Digital Experiences).

Action Required:

  • Update any code, workflows, or customizations referencing the old group name.
  • Timing: Originally released in Spring ’25; enforcement begins Summer ’25.

3. LinkedIn Lead Capture Configuration Update (Enforced)

Why the Change?
LinkedIn is retiring its legacy Ads Lead Sync APIs, requiring Salesforce admins to reconfigure lead sync.

Action Required:

  1. Disconnect your LinkedIn account from Salesforce.
  2. Enable the new setting in Salesforce setup.
  3. Reconnect your LinkedIn account.

Deadline:

  • Originally planned for Winter ’25, enforcement is now Summer ’25.
  • Failure to act: LinkedIn leads will stop syncing after the deadline.

4. API Versions 21.0–30.0 Retirement (Enforced)

What’s Happening?

  • Legacy APIs (v21.0–30.0) will be fully retired in Summer ’25 (previously delayed from Summer ’23).
  • After retirement, requests using these versions will fail with an error.

Action Required:

  • Audit integrations and upgrade all applications to current API versions.
  • Critical impact: Custom apps, middleware, and automated processes using deprecated APIs will break.

5. SAML Framework Upgrade (Enforced)

Why the Change?

  • Salesforce is enhancing its SAML security framework, improving compliance and protection.
  • Affects SSO (Single Sign-On) and SLO (Single Logout) integrations.

Action Required:

  • Test SAML integrations in Summer ’25 sandboxes as soon as available.
  • Potential impact: Authentication failures if configurations aren’t updated.
  • Timeline: Announced in Winter ’25; enforced in Summer ’25.

Key Takeaways

✅ Test modernized Aura components for compatibility.
✅ Update “Roles and Subordinates” references in code.
✅ Reconfigure LinkedIn Lead Sync before enforcement.
✅ Upgrade legacy API integrations to avoid disruptions.
✅ Validate SAML setups in Summer ’25 sandboxes.

Need Help?

Deadline: All updates take effect in Summer ’25. Act now to avoid service interruptions! 

Related Posts
Who is Salesforce?
Salesforce

Who is Salesforce? Here is their story in their own words. From our inception, we've proudly embraced the identity of Read more

Salesforce Marketing Cloud Transactional Emails
Salesforce Marketing Cloud

Salesforce Marketing Cloud Transactional Emails are immediate, automated, non-promotional messages crucial to business operations and customer satisfaction, such as order Read more

Salesforce Unites Einstein Analytics with Financial CRM
Financial Services Sector

Salesforce has unveiled a comprehensive analytics solution tailored for wealth managers, home office professionals, and retail bankers, merging its Financial Read more

AI-Driven Propensity Scores
AI-driven propensity scores

AI plays a crucial role in propensity score estimation as it can discern underlying patterns between treatments and confounding variables Read more

Share