BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//thedailyorg.com//Deadlines//EN
CALSCALE:GREGORIAN
METHOD:PUBLISH
X-WR-CALNAME:The Daily Org: Deadlines
REFRESH-INTERVAL;VALUE=DURATION:P1D
X-PUBLISHED-TTL:P1D
BEGIN:VEVENT
UID:update-release-notes-rn-security-oauth-device-htm@thedailyorg.com
DTSTAMP:20261122T063339Z
DTSTART;VALUE=DATE:20261130
DTEND;VALUE=DATE:20261201
SUMMARY:Restrict the OAuth 2.0 device flow to local External Client Apps
DESCRIPTION:To secure the OAuth 2.0 device flow\, Salesforce is restricting
  this flow to local external client apps with a localhost callback URL. To
  prepare for this change\, review your usage of the device flow and update
  your connected apps and external client apps to meet the new criteria.\n\
 nWhat to do: Review any use of the OAuth 2.0 device flow and update Connec
 ted Apps and External Client Apps to use a localhost callback URL before S
 pring '27.\n\nDue any time before Spring '27 arrives.\n\nRelease note: htt
 ps://help.salesforce.com/s/articleView?id=release-notes.rn_security_oauth_
 device.htm&release=264&type=5\n\nDeadlines: https://thedailyorg.com/deadli
 nes/
URL:https://thedailyorg.com/deadlines/
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:update-release-notes-rn-api-soap-login-htm@thedailyorg.com
DTSTAMP:20261122T063339Z
DTSTART;VALUE=DATE:20261201
DTEND;VALUE=DATE:20261202
SUMMARY:Assign Use Any API Auth permission for SOAP login()
DESCRIPTION:To authenticate with the SOAP API login() operation\, all users
  must have the Use Any API Auth user permission assigned to them. Users wi
 thout the Use Any API Auth user permission can no longer authenticate with
  SOAP API login() and will encounter an error.\n\nWhat to do: Assign the U
 se Any API Auth permission to every user who calls SOAP API login()\, sinc
 e users without it will get an error.\n\nComes with Winter '27.\n\nRelease
  note: https://help.salesforce.com/s/articleView?id=release-notes.rn_api_s
 oap_login.htm&release=264&type=5\n\nDeadlines: https://thedailyorg.com/dea
 dlines/
URL:https://thedailyorg.com/deadlines/
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:update-release-notes-rn-sales-email-maintain-verfication-exception-htm@
 thedailyorg.com
DTSTAMP:20261122T063339Z
DTSTART;VALUE=DATE:20261201
DTEND;VALUE=DATE:20261202
SUMMARY:Maintain your email verification exception
DESCRIPTION:If you previously disabled user email verifications through Sal
 esforce Customer Support\, configure an authorized email domain setting to
  maintain your exception and to preserve your users' ability to send email
 . When this release update is enforced\, Salesforce removes the existing d
 omain allowlists that disable email verification.\n\nWhat to do: Configure
  an authorized email domain setting before Spring '27 to keep your email v
 erification exception and preserve users' ability to send email.\n\nDue an
 y time before Spring '27 arrives.\n\nRelease note: https://help.salesforce
 .com/s/articleView?id=release-notes.rn_sales_email_maintain_verfication_ex
 ception.htm&release=264&type=5\n\nDeadlines: https://thedailyorg.com/deadl
 ines/
URL:https://thedailyorg.com/deadlines/
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:release-spring-27-sandboxes-1@thedailyorg.com
DTSTAMP:20261122T063339Z
DTSTART;VALUE=DATE:20270206
DTEND;VALUE=DATE:20270207
SUMMARY:Spring '27 reaches sandboxes
DESCRIPTION:Deadlines: https://thedailyorg.com/deadlines/
URL:https://thedailyorg.com/deadlines/
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:update-release-notes-rn-security-extension-mfa-enforcement-htm@thedaily
 org.com
DTSTAMP:20261122T063339Z
DTSTART;VALUE=DATE:20270206
DTEND;VALUE=DATE:20270207
SUMMARY:Finish preparing for MFA enforcement for all employee users
DESCRIPTION:To help protect your org from security threats such as phishing
 \, credential stuffing\, and account takeovers\, Salesforce requires multi
 -factor authentication (MFA) for all employee logins\, including direct UI
  and Single Sign-On (SSO). This release update applies only to orgs that r
 eceived an extension for MFA enforcement.\n\nWhat to do: Enable multi-fact
 or authentication for all employee logins before Spring ’27 enforcement.
 \n\nDue any time before Spring '27 arrives.\n\nRelease note: https://help.
 salesforce.com/s/articleView?id=release-notes.rn_security_extension_mfa_en
 forcement.htm&release=264&type=5\n\nDeadlines: https://thedailyorg.com/dea
 dlines/
URL:https://thedailyorg.com/deadlines/
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:update-release-notes-rn-security-extension-mfa-exempt-users-htm@thedail
 yorg.com
DTSTAMP:20261122T063339Z
DTSTART;VALUE=DATE:20270206
DTEND;VALUE=DATE:20270207
SUMMARY:Finish preparing for MFA enforcement for previously Exempt Users
DESCRIPTION:To help protect your org from security threats such as phishing
 \, credential stuffing\, and account takeovers\, Salesforce requires multi
 -factor authentication (MFA) for all employee logins\, including direct UI
  and single sign-on (SSO). This release update applies only to orgs that r
 eceived an extension to use the “Waive Multi-Factor Authentication for E
 xempt Users” permission.\n\nWhat to do: Remove the waive multi-factor au
 thentication permission and enforce MFA for exempt users.\n\nDue any time 
 before Spring '27 arrives.\n\nRelease note: https://help.salesforce.com/s/
 articleView?id=release-notes.rn_security_extension_mfa_exempt_users.htm&re
 lease=264&type=5\n\nDeadlines: https://thedailyorg.com/deadlines/
URL:https://thedailyorg.com/deadlines/
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:update-release-notes-rn-security-extension-phishing-resistant-mfa-htm@t
 hedailyorg.com
DTSTAMP:20261122T063339Z
DTSTART;VALUE=DATE:20270206
DTEND;VALUE=DATE:20270207
SUMMARY:Finish preparing for phishing-resistant MFA enforcement for privile
 ged users
DESCRIPTION:To help protect your org's most privileged accounts from phishi
 ng and account takeover risks\, Salesforce requires phishing-resistant mul
 ti-factor authentication (MFA) for users with the System Administrator pro
 file or privileged permissions. This release update applies only to orgs t
 hat received an extension for phishing-resistant MFA enforcement.\n\nWhat 
 to do: Configure phishing-resistant multi-factor authentication for system
  administrators before Spring ’27.\n\nDue any time before Spring '27 arr
 ives.\n\nRelease note: https://help.salesforce.com/s/articleView?id=releas
 e-notes.rn_security_extension_phishing_resistant_mfa.htm&release=264&type=
 5\n\nDeadlines: https://thedailyorg.com/deadlines/
URL:https://thedailyorg.com/deadlines/
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:update-release-notes-rn-security-extension-step-up-exports-htm@thedaily
 org.com
DTSTAMP:20261122T063339Z
DTSTART;VALUE=DATE:20270206
DTEND;VALUE=DATE:20270207
SUMMARY:Finish preparing for step-up authentication enforcement on report e
 xports
DESCRIPTION:To help protect your org's data from unauthorized exfiltration\
 , Salesforce requires users to complete a step-up authentication challenge
  when they export reports. This release update applies only to orgs that r
 eceived an extension for step-up authentication enforcement.\n\nWhat to do
 : Implement step-up authentication challenges for all report exports befor
 e Spring ’27.\n\nDue any time before Spring '27 arrives.\n\nRelease note
 : https://help.salesforce.com/s/articleView?id=release-notes.rn_security_e
 xtension_step_up_exports.htm&release=264&type=5\n\nDeadlines: https://thed
 ailyorg.com/deadlines/
URL:https://thedailyorg.com/deadlines/
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:release-spring-27-production-1@thedailyorg.com
DTSTAMP:20261122T063339Z
DTSTART;VALUE=DATE:20270219
DTEND;VALUE=DATE:20270221
SUMMARY:Spring '27 reaches production
DESCRIPTION:Deadlines: https://thedailyorg.com/deadlines/
URL:https://thedailyorg.com/deadlines/
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:update-release-notes-rn-api-soap-login-retirement-htm@thedailyorg.com
DTSTAMP:20261122T063339Z
DTSTART;VALUE=DATE:20270219
DTEND;VALUE=DATE:20270220
SUMMARY:SOAP API login() call in SOAP API versions 31.0 through 64.0 is bei
 ng retired
DESCRIPTION:In Summer ‘27\, the SOAP API login() call in SOAP API version
 s 31.0 through 64.0 will no longer be supported and no longer be available
 .\n\nWhat to do: Replace SOAP API login() calls in API versions 31.0 throu
 gh 64.0 with supported authentication before Summer '27\, when the call is
  no longer available.\n\nComes with Spring '27.\n\nRelease note: https://h
 elp.salesforce.com/s/articleView?id=release-notes.rn_api_soap_login_retire
 ment.htm&release=264&type=5\n\nDeadlines: https://thedailyorg.com/deadline
 s/
URL:https://thedailyorg.com/deadlines/
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:update-release-notes-rn-experiences-conceal-pii-guests-htm@thedailyorg.
 com
DTSTAMP:20261122T063339Z
DTSTART;VALUE=DATE:20270219
DTEND;VALUE=DATE:20270220
SUMMARY:Conceal personal information fields from Guest users
DESCRIPTION:Set field visibility for guest users without affecting your set
 tings for other external users. Turn on Independent Guest Field Masking to
  hide certain fields specifically from guest users.\n\nWhat to do: Turn on
  Independent Guest Field Masking and set field visibility so personal info
 rmation is hidden from guest users without changing other external users' 
 settings.\n\nComes with Spring '27.\n\nRelease note: https://help.salesfor
 ce.com/s/articleView?id=release-notes.rn_experiences_conceal_pii_guests.ht
 m&release=264&type=5\n\nDeadlines: https://thedailyorg.com/deadlines/
URL:https://thedailyorg.com/deadlines/
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:update-release-notes-rn-general-accessibility-todo-listboxes-ru-262-htm
 @thedailyorg.com
DTSTAMP:20261122T063339Z
DTSTART;VALUE=DATE:20270219
DTEND;VALUE=DATE:20270220
SUMMARY:Enable accessibility enhancements for To Do lists and Lightning dua
 l listboxes when zoom is greater than 200%
DESCRIPTION:To help meet Web Content Accessibility Guidelines (WCAG) 2.2 fo
 r Resize and Reflow\, enable Lightning Experience to adapt the behavior of
  To Do lists and Lightning dual listboxes when viewed at high magnificatio
 n. This is part of our effort to comply with WCAG 2.2 Resize and Reflow gu
 idelines.\n\nWhat to do: Test To Do lists and Lightning dual listboxes at 
 zoom levels above 200% in Lightning Experience before Spring '27 enforceme
 nt.\n\nComes with Spring '27.\n\nRelease note: https://help.salesforce.com
 /s/articleView?id=release-notes.rn_general_accessibility_todo_listboxes_ru
 _262.htm&release=264&type=5\n\nDeadlines: https://thedailyorg.com/deadline
 s/
URL:https://thedailyorg.com/deadlines/
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:update-release-notes-rn-lc-rus-remove-nonpublic-fields-ru-htm@thedailyo
 rg.com
DTSTAMP:20261122T063339Z
DTSTART;VALUE=DATE:20270219
DTEND;VALUE=DATE:20270220
SUMMARY:Remove non-public fields from Custom Object data in Aura action res
 ponses
DESCRIPTION:To improve security\, Salesforce is removing non-public system 
 fields from custom object data returned in Aura action responses. This upd
 ate filters out internal system fields that aren’t part of the public Sa
 lesforce API.\n\nWhat to do: Check Aura components that rely on non-public
  system fields in Custom Object data\, since those fields will be removed 
 from action responses in Spring '27.\n\nComes with Spring '27.\n\nRelease 
 note: https://help.salesforce.com/s/articleView?id=release-notes.rn_lc_rus
 _remove_nonpublic_fields_ru.htm&release=264&type=5\n\nDeadlines: https://t
 hedailyorg.com/deadlines/
URL:https://thedailyorg.com/deadlines/
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:update-release-notes-rn-roll-back-platform-event-trigger-transactions-o
 n-unhandled-exceptions-htm@thedailyorg.com
DTSTAMP:20261122T063339Z
DTSTART;VALUE=DATE:20270219
DTEND;VALUE=DATE:20270220
SUMMARY:Roll back Platform Event trigger transactions on unhandled exceptio
 ns
DESCRIPTION:This update rolls back the transaction of a platform event Apex
  trigger when it throws an unhandled exception\, so that partially written
  records are no longer committed.\n\nWhat to do: Review Platform Event Ape
 x triggers for unhandled exceptions\, since their transactions will roll b
 ack instead of committing partial records in Spring '27.\n\nComes with Spr
 ing '27.\n\nRelease note: https://help.salesforce.com/s/articleView?id=rel
 ease-notes.rn_roll_back_platform_event_trigger_transactions_on_unhandled_e
 xceptions.htm&release=264&type=5\n\nDeadlines: https://thedailyorg.com/dea
 dlines/
URL:https://thedailyorg.com/deadlines/
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:update-release-notes-rn-sales-salesforce-to-salesforce-retiring-ru-htm@
 thedailyorg.com
DTSTAMP:20261122T063339Z
DTSTART;VALUE=DATE:20270219
DTEND;VALUE=DATE:20270220
SUMMARY:Salesforce to Salesforce is being retired
DESCRIPTION:Salesforce to Salesforce is being retired in Spring ’27. Sale
 sforce has more powerful and integrated solutions that align with modern b
 usiness needs.\n\nWhat to do: Plan a migration away from Salesforce to Sal
 esforce before Spring '27\, since the feature is being retired.\n\nComes w
 ith Spring '27.\n\nRelease note: https://help.salesforce.com/s/articleView
 ?id=release-notes.rn_sales_salesforce_to_salesforce_retiring_ru.htm&releas
 e=264&type=5\n\nDeadlines: https://thedailyorg.com/deadlines/
URL:https://thedailyorg.com/deadlines/
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:update-release-notes-rn-setup-audit-trail-htm@thedailyorg.com
DTSTAMP:20261122T063339Z
DTSTART;VALUE=DATE:20270219
DTEND;VALUE=DATE:20270220
SUMMARY:View Setup Audit Trail permission to access Setup Audit Trail
DESCRIPTION:Control access to Setup Audit Trail with the dedicated View Set
 up Audit Trail permission. Admins can provide access without granting the 
 broader View Setup permission\, supporting the principle of least privileg
 e.\n\nWhat to do: Assign the View Setup Audit Trail permission to users wh
 o need Setup Audit Trail access\, instead of granting the broader View Set
 up permission.\n\nComes with Spring '27.\n\nRelease note: https://help.sal
 esforce.com/s/articleView?id=release-notes.rn_setup_audit_trail.htm&releas
 e=264&type=5\n\nDeadlines: https://thedailyorg.com/deadlines/
URL:https://thedailyorg.com/deadlines/
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:update-release-notes-rn-sf-connect-xorg-legacy-auth-retiring-ru-htm@the
 dailyorg.com
DTSTAMP:20261122T063339Z
DTSTART;VALUE=DATE:20270219
DTEND;VALUE=DATE:20270220
SUMMARY:Salesforce Connect cross-org adapter legacy authentication is being
  retired
DESCRIPTION:The password and OAuth 2.0 authentication methods for the Sales
 force Connect cross-org adapter are being retired. These authentication me
 thods rely on the SOAP login() call\, which is being retired.\n\nWhat to d
 o: Plan to move Salesforce Connect cross-org adapter connections off passw
 ord and OAuth 2.0 authentication before Spring '27.\n\nComes with Spring '
 27.\n\nRelease note: https://help.salesforce.com/s/articleView?id=release-
 notes.rn_sf_connect_xorg_legacy_auth_retiring_ru.htm&release=264&type=5\n\
 nDeadlines: https://thedailyorg.com/deadlines/
URL:https://thedailyorg.com/deadlines/
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:update-release-notes-rn-sharing-apex-recalc-htm@thedailyorg.com
DTSTAMP:20261122T063339Z
DTSTART;VALUE=DATE:20270219
DTEND;VALUE=DATE:20270220
SUMMARY:Update Apex code and flows for changed sharing recalculation behavi
 or
DESCRIPTION:To optimize performance after large-scale updates to groups or 
 roles\, Salesforce now performs some sharing recalculations asynchronously
 . If Apex code and flows require that share records be updated immediately
 \, the code and flows can break when this release update is enforced.\n\nW
 hat to do: Review Apex code and flows that need share records updated imme
 diately after group or role changes\, and make them handle asynchronous sh
 aring recalculation.\n\nComes with Spring '27.\n\nRelease note: https://he
 lp.salesforce.com/s/articleView?id=release-notes.rn_sharing_apex_recalc.ht
 m&release=264&type=5\n\nDeadlines: https://thedailyorg.com/deadlines/
URL:https://thedailyorg.com/deadlines/
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:update-release-notes-rn-update-instanced-urls-in-api-traffic-htm@thedai
 lyorg.com
DTSTAMP:20261122T063339Z
DTSTART;VALUE=DATE:20270219
DTEND;VALUE=DATE:20270220
SUMMARY:Update instanced URLs in API traffic
DESCRIPTION:To prevent disruption when Salesforce ends support for API traf
 fic that uses an incorrect instanced URL\, make sure that API traffic to y
 our org uses the org’s My Domain login URL. First available in Summer 
 ’25\, this release update was scheduled to be enforced in Spring ’26\,
  but we postponed enforcement to a phased schedule that starts in October 
 2026 in sandboxes and January 2027 in production.\n\nWhat to do: Update AP
 I traffic to use the org's My Domain login URL instead of incorrect instan
 ced URLs\, starting with sandboxes in October 2026 and production in Janua
 ry 2027.\n\nComes with Spring '27.\n\nRelease note: https://help.salesforc
 e.com/s/articleView?id=release-notes.rn_update_instanced_urls_in_api_traff
 ic.htm&release=264&type=5\n\nDeadlines: https://thedailyorg.com/deadlines/
URL:https://thedailyorg.com/deadlines/
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:update-release-notes-rn-vf-accessible-pdf-ru-htm@thedailyorg.com
DTSTAMP:20261122T063339Z
DTSTART;VALUE=DATE:20270219
DTEND;VALUE=DATE:20270220
SUMMARY:Render Visualforce Pages as Accessible (Tagged) PDFs (Beta)
DESCRIPTION:With this update enabled\, Visualforce pages rendered with rend
 erAs="pdf" use the accessible PDF rendering engine\, which produces tagged
  PDF/UA output. Tagged PDFs include the document structure and metadata th
 at assistive technologies such as screen readers rely on.\n\nWhat to do: E
 valuate Visualforce pages that use renderAs="pdf" in the beta accessible P
 DF rendering engine to produce tagged PDF/UA output before Spring '27.\n\n
 Comes with Spring '27.\n\nRelease note: https://help.salesforce.com/s/arti
 cleView?id=release-notes.rn_vf_accessible_pdf_ru.htm&release=264&type=5\n\
 nDeadlines: https://thedailyorg.com/deadlines/
URL:https://thedailyorg.com/deadlines/
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:update-release-notes-rn-security-oauth-unpw-htm@thedailyorg.com
DTSTAMP:20261122T063339Z
DTSTART;VALUE=DATE:20270220
DTEND;VALUE=DATE:20270221
SUMMARY:Retirement of OAuth 2.0 username-password flow for Connected Apps
DESCRIPTION:When this release update is enforced\, we'll stop supporting th
 e OAuth 2.0 username-password flow for connected apps. This update will br
 eak all connected app integrations that use this flow.\n\nWhat to do: Move
  Connected App integrations off the OAuth 2.0 username-password flow befor
 e Spring '27\, since those integrations will break when it is retired.\n\n
 Comes with Spring '27.\n\nRelease note: https://help.salesforce.com/s/arti
 cleView?id=release-notes.rn_security_oauth_unpw.htm&release=264&type=5\n\n
 Deadlines: https://thedailyorg.com/deadlines/
URL:https://thedailyorg.com/deadlines/
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:update-release-notes-rn-security-oauth-useragent-htm@thedailyorg.com
DTSTAMP:20261122T063339Z
DTSTART;VALUE=DATE:20270220
DTEND;VALUE=DATE:20270221
SUMMARY:OAuth user-agent and hybrid user-agent flows retirement
DESCRIPTION:Salesforce is retiring the OAuth user-agent flow and the OAuth 
 hybrid user-agent flow. For better security\, update your integrations to 
 use the OAuth web-server flow or hybrid web-server flow with the Proof Key
  for Code Exchange (PKCE) extension.\n\nWhat to do: Update integrations th
 at use the OAuth user-agent or hybrid user-agent flows to use the web-serv
 er or hybrid web-server flow with PKCE before Spring '27.\n\nComes with Sp
 ring '27.\n\nRelease note: https://help.salesforce.com/s/articleView?id=re
 lease-notes.rn_security_oauth_useragent.htm&release=264&type=5\n\nDeadline
 s: https://thedailyorg.com/deadlines/
URL:https://thedailyorg.com/deadlines/
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
UID:release-winter-28-sandboxes-1@thedailyorg.com
DTSTAMP:20261122T063339Z
DTSTART;VALUE=DATE:20271009
DTEND;VALUE=DATE:20271010
SUMMARY:Winter '28 reaches sandboxes
DESCRIPTION:Deadlines: https://thedailyorg.com/deadlines/
URL:https://thedailyorg.com/deadlines/
TRANSP:TRANSPARENT
END:VEVENT
END:VCALENDAR
