Today14 stories

The Daily Org

Spring '27Sandboxes 6 Feb 2027

Curated by Abhinav (opens in a new tab)

Vol. I · No. 47The independent daily for Salesforce admins, developers and architects14 stories

Must-readArchitecture

Choosing replacements for Salesforce to Salesforce before its Spring '27 retirement (opens in a new tab)

You will know how Salesforce to Salesforce works, what its retirement means for cross-org sharing, and how to choose among Experience Cloud, Partner Connect, Salesforce Connect, Data 360 and MuleSoft as replacements.

Why read this

You will also see the steps to inventory existing connections and plan a controlled cutover. The piece is aimed at architects and admins who inherit orgs that share data with partners or other orgs.

  1. Inventory every connection in each org
  2. Retire connections no longer needed
  3. Gather business requirements for the rest
  4. Choose a partner or platform option
  5. Plan a controlled implementation
The first step in replacing S2S is inventorying every connection in each org

Salesforce to Salesforce (S2S) is a declarative, point-to-point integration that shares records between two Salesforce orgs without code or middleware. The publishing org chooses what to share, the subscribing org maps it to its own fields, and forwarded records are sent asynchronously with retries and errors logged in the Connection History. Authentication relies on a mutual invitation, so no credentials are managed. Salesforce is retiring S2S with the Spring ’27 release, so teams need a new strategy, and the article suggests using the retirement as a chance to close gaps the current setup leaves open.

The first step is an inventory of every connection in each org. Record what is shared, how records are forwarded and accepted, and who owns each connection, along with the automation, assignment rules and logic that depend on it. Retire connections no longer needed, then gather business requirements for the rest. For partner scenarios, Experience Cloud is the choice when partners can work in your org on records you own, with Default External Access set to Private and access granted through partner roles and Sharing Rules. Partner Cloud adds onboarding, tiers and channel revenue management on top of that site, at the cost of licenses and program design. Partner Connect (Beta) suits partners that need their own synced copy, but it supports only accounts, contacts, leads, opportunities and cases as of Winter ’27, and not formula, multiselect or most lookup fields. MuleSoft can replicate records as an alternative for production.

When no partner-facing option fits, the article works through platform options in order of how much data must move. Salesforce Connect’s cross-org adapter reads or writes records in place as external objects but suits only small, on-demand operations. Data 360 offers a shared view through Data Cloud One or Data 360 to Data 360 sharing, though neither creates or updates CRM records. MuleSoft for Flow or Anypoint Platform handles replicated records where each org keeps its own copy. A custom build, using Apex, REST, Change Data Capture or Bulk API 2.0, is a last resort and takes on duplicate handling, backfill, deletes and credential management.

Finally, the article recommends a controlled implementation. Agree timelines and field ownership with the other org’s owner. Identify every flow, trigger, report and integration that touches the moved data, since automation also runs on records the new integration writes. Test duplicate prevention and failure cases in a sandbox with pass criteria set in advance, and finish production cutover several weeks before the instance’s Spring ’27 upgrade date, without running S2S and the replacement side by side.

Read the original at Salesforce Architects (opens in a new tab)

Worth reading?

Must-readAgentforce and AI

Claude becomes Slack's default AI, with two Admin-Controlled experiences (opens in a new tab)

You will learn how Slackbot and Claude Tag differ in access, billing and admin control, and what to set up before users start tagging Claude.

Why read this

The piece gives a practical rollout checklist for Salesforce admins.

Channel or group DM

  • Uses tools set up for the channel
  • Runs under Claude's own identity
  • Billed to your organization

One-to-one DM or AI panel

  • Uses the user's own Claude account
  • Uses that user's own connectors
  • Billed to that user's account
Where a user messages Claude decides whose access and billing apply

Claude is now the default model for Slack, powering Slackbot and supporting team work through Claude Tag. The two experiences work differently and each has its own admin controls, so the article sets out what each does, who manages it, and what to check before users begin tagging @Claude.

Slackbot needs no installation. Recent August 2026 upgrades include Big Mode for drafting long documents, Deep Research that returns cited reports from org data and the web, Skill Sets that can be shared and assigned to groups or channels, a Skills Admin Dashboard showing usage, and a Tasks tab for recurring routines. Feature availability depends on rollout timing, licensing and extra license requirements, and compute-heavy Advanced Features are limited at Enterprise+ with 30 days’ notice before any new limits.

Claude Tag, Anthropic’s product, places Claude in channels as a shared teammate, replacing the older Claude in Slack app. It is in beta and requires a Claude Team or Enterprise plan. Whose access it uses and who pays depends on where the user messages it: channels use the tools set up for that channel and bill the organization, while one-to-one DMs use the user’s own account. Setup needs a Slack workspace admin to install the app and a Claude Owner to pair the workspace and set spend limits. Owners control access by workspace or channel, guest channel access (restricted by default), spend caps with alerts at 75% and 90%, and auditing of scheduled work and memory on the Activity page. Slack conversations are kept apart from Claude chat history and deleted within 30 days of disconnecting.

The article closes with a rollout checklist: confirm the roles, pilot a low-risk channel, scope connections by channel, set spend caps first, keep guest access restricted, check the Slack plan, review Skill Sets, and teach users when to use a channel versus a direct message.

Read the original at Salesforce Break (opens in a new tab)

Worth reading?

RecommendedArchitecture

Salesforce integrations fail on quota and data model, not protocol (opens in a new tab)

You will learn how the org-wide daily API allocation is calculated and why batching is a design decision rather than a tuning step.

Why read this

You will also see the Apex governor limit trap that breaks batch writes, and the external ID and upsert pattern that makes retries safe.

  • 5000: Contacts written one record per call
  • 25: Calls needed via sObject Collections at 200 per request
  • 100: SOQL query ceiling per synchronous transaction
Batching cuts the calls needed to write 5,000 Contacts by a factor of 200

The article argues that Salesforce integrations rarely fail on authentication or protocol. They fail on the daily API request allocation, which is shared across every consumer in an org, and on the data model choices that are costly to reverse once records exist. It walks through the main APIs, noting that REST and SOAP are both current, that Bulk API 2.0 is a different asynchronous programming model, and that Composite and sObject Collections cut call volume sharply because each counts as one call against the allocation.

The piece then covers the constraints that shape the architecture. The allocation is set by edition and license count, and requests fail with REQUEST_LIMIT_EXCEEDED once it is exhausted, with no grace on trial and Developer Edition orgs. Batching is presented as a design decision: a 5,000 record job costs 5,000 calls one at a time but 25 through sObject Collections. Caching reference data is also suggested. Governor limits are explained as applying to customer Apex that runs when an inbound write fires triggers, and an unbulkified trigger can exceed the 100 query ceiling on a 200 record batch.

Finally, the article addresses authentication, the Lead, Contact, Account and Person Account decisions, external IDs for idempotent upserts, partial-success handling, dead letter stores and reconciliation, and sandbox and API version pinning. It also discusses when middleware is justified and the UK GDPR obligations around controllers, processors and transfers. The cost ranges and vendor-agnostic claims are the author’s own estimates and are not independently verified.

Read the original at dev.to (opens in a new tab)

Worth reading?

RecommendedIntegration

Resuming a Salesforce CDC consumer from a durable replay checkpoint (opens in a new tab)

You will learn how to store Pub/Sub API replay IDs beside mirrored data, resume a gRPC subscription from them, and make replayed events harmless with an idempotent apply step.

Why read this

The reader also gets the 72-hour retention constraint that shapes the design.

  1. Begin transaction
  2. Decode each event and skip seen keys
  3. Apply fresh changes
  4. Save latest replay ID
  5. Commit or roll back
Each batch is applied and checkpointed in one transaction

A Change Data Capture consumer that restarts from the wrong position either drops record updates or replays several days of them. The article’s fix is a durable checkpoint: it stores replay IDs, resumes a gRPC subscription from them, and makes replays harmless. The worked example is a worker subscribing to the OpportunityChangeEvent channel and mirroring each change into Postgres, using Node.js, the Pub/Sub API and the pub_sub proto file from the Salesforce repository.

The design has three parts. The first is a checkpoint table holding one replay ID per channel, stored as bytes because Salesforce treats replay IDs as opaque, alongside a table of applied transaction keys so that replayed events become no-ops. The second is a subscription that resumes with the CUSTOM replay preset and the saved bytes, using LATEST only on the first run, with a fixed request count to keep memory flat and the stream paused while the database is awaited so that order is preserved.

The third part applies changes idempotently and checkpoints in the same transaction. Each event’s schema is fetched once and cached, its Avro payload is decoded, and it is inserted into the applied-keys table; only fresh keys are applied. The latest replay ID is saved even on empty keep-alive replies so quiet channels do not age out. The article notes the time limit: change events are kept for 72 hours, so the applied-keys table can be pruned after that period. It also points out the trade-off against the older CometD route, which costs gRPC setup and Avro decoding in exchange for flow control and replay tightening.

Read the original at dev.to (opens in a new tab)

Worth reading?

RecommendedDevOps

How an MCP tool cut triage of 600 test failures to about 90 minutes (opens in a new tab)

You will learn how Salesforce engineers split deterministic code from AI reasoning in an MCP workflow that clusters and reassigns test failures, and which guardrails prevented duplicate work items and misrouting.

Why read this

The reasoning is useful even if you never touch the GUS internals.

  1. Retrieve failures
  2. Gather context from stack traces
  3. Detect patterns or apply categories
  4. Reassign individually, in bulk or by team
The workflow runs through four stages, from retrieval to reassignment

Salesforce’s engineering team faced over 600 test failures triggered by the retirement of the SOAP API login mechanism. Expected failures and genuine regressions could produce similar exceptions and span several scrum teams, so a wrong classification could hide a real defect or send engineers chasing the wrong problem for days. The existing process required manual stack trace reading and reassignment through an interface limited to 50 failures at a time, and it could create duplicate work items or misroute failures.

The team built AI-Assisted Test Failure Buddy as a Python and FastMCP process exposing eight tools to Claude Code or Cursor, connected to the APIs behind GUS, Salesforce’s internal work item system. The design separates an interface layer of typed MCP tools, a core logic layer that controls API calls, identifiers, parsing, validation, batching, clustering and reassignment, and a support layer for authentication and tokens. The workflow runs in four stages: retrieve failures, gather context from stack traces, detect patterns or apply categories, and reassign failures individually, in bulk or by team.

Grouping was the hardest part. Stack traces offer no stable key for root cause, and the same exception type could mean an expected SOAP login failure in one context and an unrelated bug in another. The team combined deterministic processing, such as regular-expression matching and a preset recognizing strings like INSUFFICIENT_ACCESS, with AI reasoning reserved for novel traces, unmatched clusters and ambiguous ownership. To avoid duplicates, the tool assigns related failures to one existing work item and uses explicit failure IDs in place of the broader interface action that had caused misrouting.

The estimated two or three days of manual triage for one 600-failure work item fell to roughly one to one and a half hours for a single engineer. The tool has since been used by three or four teams, though it has no adoption telemetry yet. The article also notes that Claude Code helped build the tool, starting from a markdown design document with human review throughout.

Read the original at Salesforce Engineering (opens in a new tab)

Worth reading?

RecommendedAgentforce and AI

Staging an AI agent's Salesforce access in three permission levels (opens in a new tab)

You will learn a staged way to grant an AI agent access to Opportunity data: read first, then propose tasks, then write a few fields.

Why read this

You will also see how the staging exposes data gaps and undocumented exceptions before any record changes.

  1. Level 1: read Opportunity and activities
  2. Level 2: propose Tasks for the owner
  3. Level 3: write a few fields
The agent gains write access only after each lower level works

The author describes an AI agent that reviews Salesforce Opportunities with no activity for 30 days, checks recent interactions and prepares follow-up actions. The design question is what the agent is allowed to do, and the author splits this into three permission levels that the agent moves through only once the level below works.

At level 1 the agent only reads Opportunity, its activities and OpportunityHistory. It runs under its own integration user with a Permission Set limited to the objects and fields it needs, and any tool layer such as MCP exposes read tools only. Every query is logged with its filter. This level shows whether no movement is defined well, since LastActivityDate, stage changes in OpportunityHistory and LastModifiedDate give different lists, and LastModifiedDate also moves when a Flow, integration or bulk load touches a record.

At level 2 the agent proposes rather than edits, creating a Task for the Opportunity owner with the suggested next step, WhatId set to the Opportunity, OwnerId set to the owner and a subject prefix that marks it as agent-written. A person decides what happens. This level reveals exceptions, such as deals deliberately paused, which the agent cannot know unless they are stored in a field, and data gaps, such as calls logged outside Salesforce. The author suggests counting open Opportunities with no LastActivityDate and fixing the data before moving on.

At level 3 the agent writes a few fields, such as a next step or follow-up date, with field-level security keeping the rest read-only. Exceptions are encoded in the query, for example skipping records with a future resume date, and changes are tested in a sandbox with realistic data. Because the agent has its own user, LastModifiedById and field history separate its changes from people’s. The author’s point is that a wrong filter at level 3 corrupts every matching record at once, so the staging keeps mistakes cheap.

Read the original at dev.to (opens in a new tab)

Worth reading?

RecommendedAgentforce and AI

Agent Optimizer guides Agentforce agents through build, test, fix and improve stages (opens in a new tab)

You will see how Agent Optimizer moves an Agentforce agent from first build through production monitoring, root-cause fixes and A/B testing.

Why read this

You will also learn which of these features are still in beta or coming soon.

  1. Forming: Build the agent and pass custom-scored tests
  2. Storming: Rank production problems across real sessions
  3. Norming: Trace root cause and draft a fix
  4. Performing: Prove the fix with A/B tests and keep it
Agent Optimizer moves an agent through four repeating stages, not a single launch

The post borrows Bruce Tuckman’s model of forming, storming, norming and performing to describe how an AI agent matures. Forming covers building the agent and proving it is ready before it meets customers. Agent Optimizer drafts the agent in Agent Script from a plain-language description, combining deterministic business rules with Atlas Reasoning Engine planning, and builds on existing Salesforce data, Flows, Apex and permissions. Testing with custom scorers is described as coming soon.

Storming is the period after launch, when real customers expose gaps. Agent Optimizer reads production sessions one by one and ranks recurring problems behind escalations, abandonment and low satisfaction. With session tracing enabled, it reads the reasoning trace for each response, showing the topic chosen, actions called, knowledge retrieved and citations. The post says Agent Optimizer is included at no extra cost for standard use cases.

Norming means finding and fixing the cause. Agent Optimizer traces each issue to the exact step where it failed, classifies it as a broken action, knowledge gap or off-topic request, and recommends a fix such as a clearer instruction, a new topic or a knowledge article. It can build and, once testing arrives, test the fix, with the team choosing how much it acts on its own.

Performing covers proving improvements. A/B experimentation, also coming soon, runs a change on a slice of live traffic against the current agent, judged by the same custom scorers, before a winning version ramps to all traffic. Each proven fix stays in the agent’s configuration, and the post says the cycle restarts whenever something changes. The post notes Agent Optimizer is in beta and points readers to their account executive and the help documentation.

Read the original at Salesforce Blog (opens in a new tab)

Worth reading?

Agentforce and AI

How Salesforce Guardian's AIforce security tools govern admin and agent access (opens in a new tab)

You will learn how Salesforce Guardian is organised into three pillars and what the new Compliance Agent, Security Mesh and MCP Security beta each do.

Why read this

You will also get a short set of practices for moving from reactive to proactive security.

Salesforce Guardian

  • Data Security
  • Data Compliance
  • Data Resilience
Salesforce Guardian is built on three pillars, each with its own products

Salesforce describes security as a shared responsibility. It provides the foundational platform security, admins configure the built-in controls such as multi-factor authentication, IP allowlisting and Permission Sets, and Salesforce Guardian sits on top as a portfolio of enterprise security, privacy and data protection products. The article frames this as three layers: Foundationals, Configurables and Enhanceables.

Salesforce Guardian rests on three pillars. Data Security covers Shield, for encryption, event monitoring and audit trails, and Security Center, for a single view of posture across orgs. Data Compliance covers Privacy Center, for retention and privacy rights requests, and Data Mask & Seed, for protecting sensitive data in sandboxes. Data Resilience covers Backup & Recover, for restoring lost or corrupted data, and Archive, for keeping the org lean while retaining what compliance requires.

The article names three AIforce security enhancements. Compliance Agent, part of Privacy Center, scans core metadata to set a compliance baseline and produce a score tied to regulatory goals, with actionable remediation plans. Because it relies on retrieval-augmented generation, the author stresses that grounding data must be classified, for example under GDPR, HIPAA or other PII categories, or the agent cannot tell public data from restricted data. Security Mesh, part of Security Center, normalizes signals from partners such as Okta and CrowdStrike and adds detections such as Impossible Travel. MCP Security, currently in beta, scans external MCP servers at registration and assigns Low, Medium or High risk scores before agents can reach them.

For implementation, the article recommends adopting a Zero Trust framework and the Principle of Least Privilege for both human and agent users, and setting up escalation paths for high-risk transactions to handle false positives and any human-in-the-loop regulatory requirements.

Read the original at Salesforce Admins Blog (opens in a new tab)

Worth reading?

Data Cloud

Informatica adds governed enterprise data to Copilot, Foundry and Fabric (opens in a new tab)

You will learn what Informatica's Microsoft integrations now provide: Copilot access to business context, MCP-based governance for Foundry agents, and broader Fabric lineage scanning.

Why read this

You will also see the new U.S. East Coast Azure deployment option and what is generally available.

  1. Informatica governance and lineage data
  2. Headless MCP servers and scanners
  3. Microsoft Copilot, Foundry and Fabric
  4. Governed AI agents and analytics
How Informatica trusted data reaches Copilot, Foundry and Fabric agents

Informatica from Salesforce has expanded its collaboration with Microsoft, announced at Microsoft Ignite 2026. The integration brings Informatica’s enterprise data intelligence into Microsoft Copilot and Teams, giving business users access to business definitions, data quality, governance and lineage through natural-language experiences. The article presents this as a response to the gap between agents that can access data and agents that understand it and operate within access policies.

For AI developers, the integration with Microsoft Foundry extends Informatica Headless MCP servers, which reached general availability earlier, with new governance, identity and administrative capabilities. These let developers ground agents in authoritative definitions, quality indicators and lineage, apply access controls, and trace agent interactions with data management services. Informatica’s MCP services are also being expanded across Azure-based IDMC points of delivery worldwide.

For data engineers and analysts on Fabric, Informatica’s scanners now cover notebooks and data pipelines as well as data at rest. The enhanced scanners provide lineage across multistep pipeline orchestrations, support impact analysis, and are administered through a consolidated interface. The article also announces a new U.S. East Coast Azure point of delivery for customers with data residency or procurement requirements, and notes that Informatica purchases through Microsoft Marketplace can count toward a Microsoft Azure Consumption Commitment.

Availability is staggered: the Copilot integration is generally available, the Foundry MCP server integration is generally available with its expanded capabilities, the Fabric scanners are generally available for notebooks and pipelines, and the Azure U.S. East IDMC point of delivery is generally available. The piece is largely promotional, with customer and executive quotes, so the technical detail on the MCP governance features is thin.

Read the original at Salesforce News (opens in a new tab)

Also told by Salesforce Time (opens in a new tab)

Worth reading?

Agentforce and AI

Carter, a shopper agent for B2C Commerce storefronts built on Agentforce (opens in a new tab)

You will learn how Carter is structured, with its four preconfigured subagents, page awareness and merchant controls over guided discovery, and what the Shopper Agent template gives you to start from.

Why read this

You will also see the customer results Salesforce reports, though they are vendor claims.

  1. Shopper asks in natural language
  2. Agentic Commerce Search reads the intent
  3. Carter routes to a subagent
  4. Answer grounded in the product catalog
How Carter handles a shopper request across its subagents

Salesforce introduces Carter, a shopper agent from Commerce Cloud that gives online shoppers a conversational interface in place of keyword search and category pages. The article argues that shoppers now expect the guided, context-aware help a good in-store sales associate gives, and that Carter is meant to provide it. It is available through B2C Commerce and can be reached from the search bar, the header icon, or FAQ widgets on product detail pages.

Carter is powered by Agentic Commerce Search, which interprets the intent behind a natural language request rather than matching keywords. Its answers are grounded in the merchant’s product catalog, and brands can add other knowledge sources through Data 360. Merchants control how Carter sells by choosing which follow-up questions are required or optional in guided discovery and which selling points it highlights when comparing products.

Getting started means using the Shopper Agent for B2C Commerce template in Agentforce, which comes with all the subagents and actions preconfigured. Product Expert handles browsing, search, recommendations, comparisons and product questions. Site FAQ covers policies such as shipping, returns and refunds. Cart manages products, variants, promotions and coupons. Order Confirmation confirms orders and recovers carts after failed or cancelled payments. Carter orchestrates these behind one chat, and because it is page-aware it can answer questions about the product or cart the shopper is currently viewing.

The article cites several retailers using Carter under their own brand names, including Cuisinart’s Compass, Hibbett AI and SharkNinja’s combined commerce and support interface. Hibbett reports going live in six weeks and handling 90% of core shopper journeys. These are vendor-supplied results. Carter is generally available now as an add-on for B2C Commerce customers and works in every language Agentforce supports.

Read the original at Salesforce Blog (opens in a new tab)

Worth reading?

LWC and UI

Five ways Lightning Web Components can share data between components (opens in a new tab)

You will see how a parent passes data to a child, how a child reports back, and when to use Lightning Message Service or Lightning Data Service instead.

Why read this

The piece also lists common mistakes to avoid.

Parent to child

  • @api public property
  • Parent sets HTML attribute
  • Child reads the value

Child to parent

  • Child dispatches CustomEvent
  • Detail carries the payload
  • Parent handles the event
Parent-to-child uses public properties; child-to-parent uses custom events

The article surveys five ways Lightning Web Components can communicate. The simplest is parent-to-child communication through a public property marked with the @api decorator, where the parent sets an HTML attribute and the child receives it. Code examples show a child component declaring a message property and a parent passing a welcome string into it.

When a child needs to notify its parent, it dispatches a custom event carrying a detail payload. The example has a child button fire a valuechange event, and the parent handles it and stores the selected value. The author notes that this lets the child report upward without reaching into the parent’s internal properties.

For components with no parent-child relationship, such as a customer information panel and a related sales panel, the article describes Lightning Message Service. The steps are to create a message channel, import it into a publisher, publish a message, subscribe in the receiving component and process the payload. Lightning Data Service is presented for cases where the data is a Salesforce record, using getRecord through a wire adapter, with the benefit of caching and record sharing across components. Shared JavaScript modules are mentioned for reusable logic.

The article closes with a table matching each method to its best use and a list of mistakes to avoid, such as using custom events where a public property is enough, creating unnecessary message channels, and calling Apex when Lightning Data Service already covers the need.

Read the original at dev.to (opens in a new tab)

Worth reading?

Architecture

How the Salesforce order of execution sequences flows, triggers and validation (opens in a new tab)

You will learn the rough sequence in which Salesforce runs Flows, Apex triggers, Validation Rules and after-save automation when a record is saved, and why that order matters when several automations touch the same record.

Why read this

The article is a general overview rather than a detailed reference.

  1. Initial record submission
  2. Before-save Record-Triggered Flows
  3. Before Apex triggers
  4. Validation and duplicate rules
  5. Save to database, not yet committed
  6. After triggers and after-save flows
  7. Commit and post-commit operations
The main stages Salesforce runs when a record is saved

When a record is created, updated or deleted, Salesforce runs several kinds of automation in a defined sequence. The article says this matters because multiple automations touching the same record can produce unexpected results, repeated updates or errors. Understanding the sequence helps teams troubleshoot and avoid needless complexity.

The process starts with the initial submission, whether from the user interface, the API, Apex, Data Loader or an external application. Before-save Record-Triggered Flows then run before the record is written to the database, and are described as efficient for simple field updates because they avoid an extra save. Before Apex triggers follow, with a short example that sets a default value on a Contact description. Validation Rules and duplicate rules run before the save completes.

Once the record is saved to the database, the transaction is not yet committed, so later errors can still roll the changes back. After triggers and after-save flows then run, handling tasks such as creating related records, sending notifications or starting further processes. The article also notes that legacy workflow, escalation and assignment rules can cause extra updates that re-run parts of the sequence. After a successful transaction, the changes are committed and post-commit work such as Queueable Apex, future methods and scheduled paths can run.

The article closes with common mistakes: several Flows on one object without reviewing their order, duplicating field updates across Flows and Apex triggers, ignoring recursion, and skipping tests for API updates. Its advice is to review existing automation on an object before adding a new Flow, trigger or Validation Rule.

Read the original at dev.to (opens in a new tab)

Worth reading?

Releases

Spring '27 upgrade dates and how to find yours (opens in a new tab)

You will know where to check when your production instance and sandbox receive Spring '27, and why to test before the upgrade.

Why read this

The article gives the main release weekends and sandbox preview dates but not the release notes themselves.

  1. 9-10 Jan 2027: Sandbox upgrade weekend
  2. 10 Jan 2027: Sandbox preview period begins
  3. 16 Jan 2027: Main release weekend
  4. 6 Feb 2027: Main release weekend
  5. 20 Feb 2027: Main release weekend
Key Spring '27 dates for production and sandboxes

Salesforce Spring ’27 is approaching, and the article argues that admins need to know when their environments will be upgraded in order to prepare. It recommends testing key functions in production before the Winter ’27 release lands, even though upgrades rarely cause major problems.

The release date for each instance depends on which instance the org runs on. The main release weekends listed are January 16, February 6 and February 20, 2027. To find an exact date, the article says to open Salesforce Trust, search by instance name or domain, and select Maintenance. If the instance is unknown, Company Information in Setup shows it.

Sandboxes are the chance to test the new release against your own configuration. Sandboxes are either Preview or Non-Preview instances, and each has its own upgrade window. The Spring ’27 sandbox preview period begins on January 10, 2027, with upgrade activity over the January 9-10 weekend, though the exact date depends on the instance. A pre-release org is useful for a first look, but it does not contain your setup.

The article notes that release notes are the most anticipated item, and that they will be linked once published.

Read the original at Salesforce Ben (opens in a new tab)

Worth reading?

Architecture

Salesforce Services on Hyperforce now runs on Google Cloud and has first certifications (opens in a new tab)

You will learn that Salesforce Services on Hyperforce has now moved onto Google Cloud infrastructure and passed its first round of security assessments and certifications.

Why read this

You will also see which standards were covered and what Salesforce says comes next.

Salesforce has announced that Salesforce Services on Hyperforce now runs on Google Cloud infrastructure. The environment has completed its first round of security compliance assessments and certifications, covering SOC 1, SOC 2 and SOC 3, PCI DSS, ISO 27001, ISO 27017, ISO 27018 and NEN 7510. Salesforce says customers keep the Salesforce experience they already know, with the same security and compliance baseline as its other Hyperforce environments.

The post explains what each certification is meant to give customers. The SOC reports cover the controls behind the services, PCI DSS covers safeguards for payment card data, the ISO standards address information security, cloud security and personal data privacy, and NEN 7510 addresses information security in healthcare. Salesforce presents these as independent checks that customers can use to see how their data is protected.

Salesforce describes this as the start of an effort to achieve certification parity across its Salesforce Services environments. It says it will keep commissioning independent assessments so that customers can build on Hyperforce on Google Cloud with the same confidence they have elsewhere. The post points readers to the Salesforce Compliance site for the full reports and to a help article for which orgs sit in which location and which Hyperforce regions are available.

Read the original at Salesforce Blog (opens in a new tab)

Worth reading?