Skip to content
Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
Winter '27 overview
For Architects

Winter '27 for Architects

The identity retirement calendar, agent composition, MCP governance and Hyperforce on Google Cloud.

A partner's middleware has called SOAP login() every hour since 2018, using an integration user cloned from a stripped-down profile. On December 1, 2026, that call starts returning an error, and the only warning is a Release Update in Setup that nobody on the team may have opened. Winter '27 is full of changes like this one. The features get the keynote, but for an architect the release is a dated calendar of identity and integration work, plus a clear signal about where Salesforce wants agents, data and code to run.

This is the architect's map of Winter '27. Release notes first published the week of August 17, 2026, sandbox preview began the weekend of August 28-29, and production orgs upgraded through the weekend of October 9-10, 2026. Several sections now release monthly, so the dates below come from the release notes as they stood in mid-November.

The retirement calendar is now your integration roadmap

Read these in date order. Each one breaks something specific, and some, like idle refresh tokens, fail only when a dormant integration next runs.

  • October 2026 onward: instanced URLs. API traffic must use the org's My Domain login URL. Enforcement is phased, starting in sandboxes in October 2026 and production in January 2027. Custom domains do not work for API logins, and SOAP logins against one fail with HTTP 400 once blocking is on.
  • October 21 and November 4, 2026: refresh token idle limit. Refresh tokens unused for 30 days expire and their access tokens are revoked, in sandboxes from October 21 and production from November 4. This covers connected apps and External Client Apps, including installs in subscriber orgs.
  • November 30, 2026: device flow. The OAuth 2.0 device flow works only with local External Client Apps.
  • December 1, 2026: SOAP login() permission. Users need Use Any API Auth to authenticate through SOAP API login(), enforced uniformly across production and sandboxes. The same day, the email verification exception ends for orgs that Support had exempted.
  • January 7 and February 4, 2027: single sign-on configuration. Orgs that require SSO are migrated to a simpler configuration, sandboxes first.
  • February 20, 2027: OAuth flow retirements. The username-password flow for connected apps retires, moved from Winter '27. The user-agent and hybrid user-agent flows retire the same day. The username-password flow is already disabled in orgs created in Summer '26 or later, and the user-agent flows are blocked in new Winter '27 orgs.
  • Spring '27: Salesforce to Salesforce retires, and the Salesforce Connect cross-org adapter drops its legacy password and OAuth authentication in favour of named credentials.
  • Summer '27: SOAP login() retires in API versions 31.0 through 64.0, connected apps stop receiving bug fixes and support, and API versions 31.0 through 40.0 are deprecated ahead of retirement in Summer '28.

The target state is consistent across every item. Inbound integrations authenticate through an External Client App, using the web server flow with PKCE for user-facing clients and the client credentials flow for server-to-server work. Outbound calls go through named credentials. Every endpoint is addressed by its My Domain URL. ISVs get a migration tool that converts packaged connected apps to packaged External Client Apps while existing tokens and sessions stay valid. The OAuth 2.0 DPoP extension can bind tokens to the client's private key, and tenant-specific trust stores hold up to 50 root certificates for outbound TLS through named credentials.

Our External Client Apps migration guide covers the order of work, and our enforcement shuffle piece records which dates moved after the notes published.

Headless becomes a first-class architecture

On September 4, 2026, Salesforce renamed Headless 360 to AIforce and gave it a top-level section in the release notes, covering Agentforce Vibes, Salesforce Multi-Framework and Salesforce MCP Servers. The architectural message is that the Salesforce UI is one surface among several.

Multi-Framework apps as microfrontends. React and Angular apps built with Multi-Framework run on the salesforce.app domain and can now be embedded in Lightning pages and Experience Cloud pages through the lightning-ui-embedding base component. Help removed the beta disclaimer the week of November 9. Embedding requires Hyperforce. Salesforce hosts the app in a sandboxed iframe with a messaging channel to the page, which is the boundary to design your state and security around.

The Headless Experience Layer. Salesforce's platform blog for the release describes one widget definition that renders in Slack, Microsoft Teams, React and LWC, included in the platform licence. If your reference architecture has separate UI builds per channel, this is the feature to evaluate.

Headless developer environments. The same blog lists sandbox lifecycle management, Data Mask & Seed and scale testing without a Salesforce UI session. Combined with the new AI skills for sandboxes and scratch orgs, environment management is becoming something an agent or a pipeline does through APIs.

Agents compose, inside the org and across vendors

Multi-Agent Orchestration is generally available. An orchestrator agent connects other Agentforce agents in the same org as subagents, with variable mapping between them. That makes specialized agents with narrow instructions the default design, rather than one agent that knows everything.

Salesforce's Winter '27 Top 10 goes further with Third-Party Agent Orchestration: Agentforce can orchestrate agents from AWS, Azure, Google and other A2A-compliant ecosystems, or act as a subagent under an external orchestrator. We did not find a matching Help release note, so treat cross-vendor orchestration as announced and prove it in a sandbox before it appears in a target architecture.

Agent Skills and Plugins is the packaging story. The Top 10 says more than 100 prebuilt skills shipped at launch, and customers can publish their own to the same registry, which Salesforce's platform blog says verifies naming, accuracy and outcome quality automatically. Plug-ins bundle skills with MCP connectors, hooks and configuration.

Memory is now an architecture decision. Agent Memory is generally available, admins have an org-wide switch to turn conversational memory off, and users can import memories from third-party AI tools. In Data 360, the Agent Context Engine adds custom memory categories and lets an agent use up to two real-time data graphs, one for the customer and one for the employee. Decide retention, consent and masking before memory reaches a production agent.

Agents also became portable metadata. From API 68.0, AiAgentDefinition and AiAgentDefinitionVersion let Salesforce CLI retrieve an agent with its dependencies. Managed packaging of agents is not supported, so ISVs still need another distribution plan.

MCP is an integration surface you now govern

MCP works in both directions on the platform now, and that turns it into an integration tier with its own controls.

Salesforce hosts more MCP servers. The Metadata Grounding server (Beta) gives AI clients permission-aware, read-only access to metadata across more than 60 types through Salesforce Catalog. The CRM Analytics MCP Server (Beta) lets Claude, Cursor, GitHub Copilot and ChatGPT query governed analytics data through an External Client App with OAuth and PKCE. Salesforce in Claude can create and update records in beta, and only when the MCP server's Dispatch API setting is Needs Approval or Always Allowed. You can also create custom Salesforce-hosted MCP servers through the API Catalog Connect REST API, which is generally available.

On the consuming side, Agentforce Employee agents can reach external MCP servers with each user's own OAuth credentials instead of a shared service user, which gives you a per-user audit trail. Salesforce's platform blog adds MCP Risk Scores in Security Center, rating every third-party MCP server Low, Medium or High at registration and continuously after, with an option to block high-risk servers.

Treat an MCP server like an API: register it in API Catalog, authenticate through an External Client App, prefer per-user credentials over shared ones, and review its risk score before an agent can call it.

Event-driven and API surface changes

Event-driven designs have two changes to absorb. Standard-volume platform events retire on December 15, 2026, and Salesforce offers a one-click migration to high-volume events. Plan it like any other cutover: replay behaviour, subscriber limits and monitoring all deserve a test. Separately, a release update enforced in Spring '27 rolls back the whole platform event trigger transaction on an unhandled exception, so partially written records stop being committed. If your error handling assumed partial commits, it needs a rethink before Spring '27.

The API surface is being pruned and modernized at the same time. Platform API versions 31.0 through 40.0 are deprecated in Summer '27 and retired in Summer '28. The REST API accepts latest in place of a version number, which suits tooling but not a pinned production integration. On API 68.0, the Streaming API sends a per-channel replay watermark on every successful connect response, so subscribers can advance their replay position without waiting for an event. A newer OpenAPI document for the sObjects REST API is in beta, and admins can now control unauthenticated guest access to the GraphQL API.

Least privilege moves into the defaults

Several changes push the platform toward least privilege without asking first.

  • Enable Profile Filtering is enforced. Users cannot view profile names other than their own unless they hold View All Profiles. Test any automation, report or integration that reads another user's profile name.
  • User Context - Enforces User Permissions is a new flow run option that keeps a flow in the running user's context even when Apex or another flow calls it from system context.
  • View Setup Audit Trail becomes its own permission, enforced in Spring '27.
  • Blocking anonymous Apex from managed package sessions enforces in Summer '27.
  • Conceal Personal Information Fields from Guest Users arrives as a release update for Spring '27.

Security operations also gained automation. When Salesforce detects credential stuffing, it revokes the user's sessions and refresh tokens and forces a password reset. When it detects suspicious API data access, it terminates the session and emails admins, and in extreme cases freezes the user. Step-up authentication can now guard sensitive security settings. Security Center adds investigations with remediation plans and an Inactive Privileged Users metric for administrators who have not logged in for more than 90 days. Salesforce Shield Platform Encryption now covers Archive app data with Salesforce-managed keys, BYOK or Shield EKM backed by AWS KMS, and Privacy Center adds a Global Consent Manager for consent at scale.

Data 360 and the zero-copy fabric

Data 360 keeps closing the distance between the platform and the warehouse.

  • Zero copy everywhere. The Snowflake connector moved to a V2 with OIDC authentication, Microsoft OneLake sharing arrived in beta, and Google BigQuery sharing works in any region. Private Connect now reaches BigQuery and Databricks on Azure.
  • Code next to the data. Code Extension runs Python on zero-copy data lake and data model objects, and can call external HTTPS services through named credentials.
  • Better environments. Data 360 now runs in scratch orgs at lower credit cost, and companion sandboxes for Data Cloud One need no manual metadata cleanup for sandboxes created or refreshed after October 9, 2026.
  • Governed graphs. Data graphs gained pruning and masking, plus lookups on fields other than the primary key.

Two Top 10 items extend the fabric toward agents. Tableau Knowledge builds knowledge graphs from structured and unstructured data to ground agents in governed business context. Informatica Headless exposes Informatica's data management back end to developers in VS Code, Cursor and Slack, or through MCP servers. Neither had a detailed Help release note we could read, so plan proofs of concept rather than commitments. One deadline is firm: Tableau agents built on the legacy V1 template stop working at the end of 2026, and new agents must use the V2 template.

Hyperforce: a second hyperscaler and routing you control

Hyperforce is generally available on Google Cloud Platform in North America from November 1, 2026, covering most Sales Cloud, Service Cloud and Service Cloud real-time features. Salesforce chooses the infrastructure placement, and your account team holds the documented cloud-provider restrictions. Update IP allowlists from the published ranges rather than hard-coding addresses. On AWS, Hyperforce now spans 18 countries.

Salesforce Edge Network routing is self-service under Setup, My Domain, Routing and Policies, and Regional Routing is open to every Hyperforce org. If a third party fronts your custom domain, point it at your My Domain login URL as a stable target host, so an instance or cell change does not cause downtime. For public sector, MuleSoft is planned for Government Cloud Plus and Government Cloud Plus - Defense by the end of 2026, and Sandbox Quick Create and Quick Clone run two to three times faster there.

Lifecycle, testing and observability

Next Generation DevOps Center is now Lifecycle Center. Its Governance feature (Beta) defines policies that apply to coding agents in Agentforce Vibes, such as Code Analyzer checks, which gives you a native control over what coding agents in Agentforce Vibes can ship. A generally available migration moves DevOps Center managed package projects into Lifecycle Center, and validate-only deployments let a promotion complete within 10 days without rerunning Apex tests.

Testing improved at every layer. Flow Test Mode gives admins assertion-based flow tests, Apex integration tests can call real endpoints in scratch orgs as a Developer Preview, and Testing Center can now generate agent tests with context variable values. For agents in production, Salesforce's platform blog lists Observability Center (Beta) for session tracing, error detection and performance monitoring, and Agentforce Observability can mask personal data in session logs at query time (Beta). Note that Agentforce Observability recalculated Success Rate and changed metric names, so trend lines across the upgrade are not comparable.

Environments and test data

Environment strategy gets cheaper and safer. Data Mask & Seed, now a native app rather than a managed package, adds proactive PII detection in masking policies and locale-specific masking data. Data 360 runs in scratch orgs at a lower credit cost than production usage, so Data 360 configuration can finally sit in the same source-driven pipeline as the rest of the org. In sandboxes and scratch orgs, DX Inspector validates metadata against a target org without deploying and can redeploy a previous deployment after edits. Builder Central (Beta) validates generated apps and agents in an ephemeral preview org before anything reaches a sandbox.

AI skills now cover the environment lifecycle too, creating, refreshing and activating sandboxes or managing scratch orgs and Dev Hub from a coding client. That is useful, and it is also a new identity to govern: decide which environments a coding agent may create or refresh before someone asks it to.

Cost architecture is changing too

Two billing models make agent cost a design input. Pay per Resolution is an opt-in model for Agentforce Service agents in which every resolution consumes the same number of Flex Credits regardless of actions or tokens. The default remains per-action metering. Agentforce Engagement now offers pay per lead worked as an alternative to pay per action. Model the expected conversation shape before you choose, because a chatty agent and a terse one cost very different amounts under per-action billing.

Licensing moved in a few places that change solution designs. Salesforce Contracts now works with Lightning Platform Starter or Plus licences instead of requiring a core CRM licence. A Dynamic Revenue Orchestrator read-only permission set lets people view fulfilment pipelines without a paid seat. Slackbot in Salesforce draws on Flex Credits, which must be turned on in both Salesforce and Slack, so a Slack-first design now has a consumption line item.

What this release means at the reference-architecture level

Winter '27 asks architects to finish three migrations and start two designs. Finish the identity migration to External Client Apps and modern OAuth flows, finish the move to My Domain URLs, and finish retiring Salesforce to Salesforce and other legacy integration paths. Start an agent architecture that assumes composition, memory and MCP, and start treating headless surfaces as peers of Lightning Experience.

The checklist below is ordered by the calendar above. For the implementation detail, see Winter '27 for Developers. For the setup changes your admins will make, see Winter '27 for Admins. The Consultant article covers how to position these changes with business sponsors, and the Top 10 is the short list.

Sources

What to test in your sandbox

  1. 1. Map every integration to the auth calendar

    Build an inventory of inbound integrations with their user, OAuth flow and API version. Tag each against the dates that apply: November 30, 2026 for the device flow, December 1 for SOAP login() permissions, February 20, 2027 for username-password and user-agent flows, and Summer '27 for SOAP login() and connected app support. Give each one an owner and a target date.

    Reference: oauth, connected-app, external-client-app-manager

  2. 2. Prove the External Client App target pattern

    In a sandbox, stand up one External Client App using the web server flow with PKCE for a user-facing client and one using the client credentials flow for a server-to-server job. Route outbound calls through named credentials, test DPoP where your clients support it, and document the pattern so every migration follows the same design.

    Reference: external-client-app-manager, named-credential, oauth

  3. 3. Design an orchestrated agent with clear lanes

    Choose two existing agents with distinct responsibilities and connect them under an orchestrator with Multi-Agent Orchestration. Write delegation descriptions, map variables, and test hand-offs in Testing Center. Record decisions on memory, retention and which data graphs each agent may use before the design reaches production.

    Reference: agentforce, agentforce-testing-center, agent-builder

  4. 4. Register and risk-score MCP connections

    List the AI clients and MCP servers already connected to your org. Register approved servers in API Catalog, authenticate them through External Client Apps with per-user credentials, and review MCP risk scores in Security Center. Decide the Dispatch API setting for Salesforce in Claude before anyone enables record writes.

    Reference: api-catalog, external-client-app-manager, oauth

  5. 5. Plan the high-volume platform event cutover

    Standard-volume platform events retire on December 15, 2026. Migrate them to high-volume events in a sandbox, retest replay and subscriber behaviour, and update monitoring. Then review error handling against the Spring '27 update that rolls back the whole platform event trigger transaction on unhandled exceptions.

    Reference: platform-event, change-data-capture

  6. 6. Review Hyperforce placement and network allowlists

    Ask your account team whether any org could be placed on Hyperforce on Google Cloud, generally available in North America from November 1, 2026. Replace hard-coded IP allowlists with Salesforce's published ranges, review Edge Network routing options in Setup, and point third-party custom domain targets at your My Domain login URL.

    Reference: hyperforce, my-domain

  7. 7. Test Data 360 zero copy against your warehouse

    Pick one warehouse dataset and test zero-copy access through the Snowflake V2 connector, Microsoft OneLake sharing (Beta) or Google BigQuery. Measure query latency and credit consumption against your current copy pipeline, and use Data 360 scratch orgs so the configuration lives in source control from the start.

    Reference: data-cloud, data-model-object, data-stream

Related dictionary terms

Read overall highlights →See top 10 features →See Admins take →See Developers take →See Consultants take →

Practise it

Five questions on Administrator

Exam-style questions with an explanation after each one. No account needed, and your answers build a weak-topic map once you have one.