Tech UpdatesMay-June 2017 Edition

Technology Communications & Readiness

Forward-Looking StatementsSafe harbor statement under the Private Securities Litigation Reform Act of 1995:This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize or if any of the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed or implied by the forward-looking statements we make. All statements other than statements of historical fact could be deemed forward-looking, including any projections of product or service availability, subscriber growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of management for future operations, statements of belief, any statements concerning new, planned, or upgraded services or technology developments and customer contracts or use of our services.The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new functionality for our service, new products and services, our new business model, our past operating losses, possible fluctuations in our operating results and rate of growth, interruptions or delays in our Web hosting, breach of our security measures, the outcome of any litigation, risks associated with completed and any possible mergers and acquisitions, the immature market in which we operate, our relatively limited operating history, our ability to expand, retain, and motivate our employees and manage our growth, new releases of our service and successful customer deployment, our limited history reselling non-salesforce.com products, and utilization and selling to larger enterprise customers. Further information on potential factors that could affect the financial results of salesforce.com, inc. is included in our annual report on Form 10-K for the most recent fiscal year and in our quarterly report on Form 10-Q for the most recent fiscal quarter. These documents and others containing important disclosures are available on the SEC Filings section of the Investor Information section of our Web site.Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are currently available. Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements.

We want to hear from YOU!One-Minute Survey

Let us know what you think of our Monthly Tech Updates

Key Questions include: ● How do you use the Monthly Tech

Updates?● What would you change?● What is your favorite topic?● How important are the Tech

Updates to you and your business needs?

MAY & JUNE 2017 TopicsAt-a-glance

System Maintenances● Site Switches (AP1, AP3, AP4, CS5, CS6,

CS31)

Feature Retirements● Stay-in-Touch Request Retiring in Summer ‘17● Salesforce Classic Mobile App to Retire on

December 1, 2017● Access and Support for Lightning Experience

with Internet Explorer version 11 extended to December 2020

● SOAP API Legacy Versions will retire in Summer ‘18

Product Innovation● The Summer ‘17 release is here● LockerService rollout plan is changing in the

Summer ’17 release● Update the Web-to-Case and Web-to-Lead

Endpoint by Summer ‘17

Security Enhancements● TLS 1.0 disablement will begin on July 22, 2017● Default certificate to retire August, 2017

Infrastructure Improvements● Marketing Cloud infrastructure upgrade● Sandbox Migrations (CS19, CS20, CS21, CS23,

CS25, and CS26)● Instance Refreshes (NA2, NA18, NA22, NA23,

NA41, NA4, NA5, NA13, NA19, NA20, NA26, AP2)

Summer ’17 is coming soon

Welcome to our Summer ‘17 release

See how our latest innovations help you blaze new trails to productivity.

● Check your release window for Summer ‘17 on status.salesforce.com/status

● Browse the release notes and use the filters to find what’s important to you

● Join our Success Community and check out all the Summer ‘17 blogs. Take part in the conversation to see what other customers are excited about in this release.

● Save the Date for Release Readiness Live On Friday June 2nd, we have live Developer and Admin Previews. Then join our Product Management teams from June 5th to 8th for each of our live Cloud sessions.

LockerService rollout changes with Summer ’17 release

See the Summer ’17 Release Notes and the Lightning Components Developer Guide article for more information.

● We previously communicated we planned to enable LockerService, including stricter Content Security Policy (CSP) in all orgs, starting with Summer ’17. However, based on customer feedback, we’ve made two changes.

● With the revised rollout CSP has been decoupled from LockerService and won’t be enforced in production orgs in Summer ’17,

● LockerService can now be disabled by adjusting your API version to 39.0 below

*Currently targeted for June 2017; date subject to change

What is the change?

Update the Web-to-Case and Web-to-Lead Endpoint by Summer ‘17

See the Updating the Web-to-Case and Web-to-Lead Endpoint URL article for more details.

What is the change?Websites using the W2C/W2L forms will cease to create new cases and/or leads within customers’ Salesforce orgs if the websites are not updated with the new endpoint URL by the Summer ‘17 release.

What action do I need to take?As the new endpoint URL is already available, customers are strongly encouraged to complete these updates as soon as possible to take advantage of the improved functionality performance.

At-a-glance

What is the change?Due to the upcoming expiration of the default client certificate (proxy.salesforce.com), and for security best practices, we will retire the use of this client certificate on August 7, 2017.

Customers using the following features may be impacted:● Single Sign-On using SAML● Delegated authentication● Workflow automated messaging● AJAX proxy

For more information join the Official: Salesforce Infrastructure Success Community group.

Default Certificate to Retire on August 7, 2017At-a-glance

Click here to learn more about what actions you need take to prepare for this change.

What is the change?TLS disablement will begin on July 22, 2017. TLS 1.1+ will be required for all orgs.

How does it impact my org and my users?If your production environment and your users’ browsers are not prepared to support the latest TLS versions by this date, your users will not be able to access your production org, and select Salesforce products and custom or partner integrations will experience disruption. Your access to the Salesforce Help & Training portal to open and manage Support cases will also be impacted.

Upgrade Production Instances to TLS 1.1+ by July 22, 2017At-a-glance

Read on to learn about what actions you need take to prepare for this change.

In order to prepare for your continued growth and success, Salesforce Marketing Cloud has kicked off a phased infrastructure upgrade that impacts Email Studio and Mobile Studio.

The infrastructure initiative includes three key phases: Phase 1, installation of new storage arrays; Phase 2, upgrading our network; Phase 3, upgrading each database.

Here’s what you can expect:

● Upgraded infrastructure supporting Marketing Cloud solutions● New software and hardware ● Improved reliability ● Increased capacity for growth using Marketing Cloud

For more information, please reach out to your Account team.

At-a-glanceMarketing Cloud Infrastructure Upgrade

In order to prepare for your organization’s continued growth, we occasionally need to perform an activity, called an instance refresh, where we upgrade the infrastructure supporting your instance in our data centers. This will enable us to continue to provide your organization with the same levels of performance you have come to expect from Salesforce.

Following the maintenance, you will be on new infrastructure and your instance name will change.

What instances are being refreshed and when?

● NA4, NA5, NA13, NA19, NA20, NA26 - Saturday, July 15, 2017 between 7 p.m.–11 p.m. US Pacific Time (Sunday, July 16 between 02:00–06:00 UTC)

● NA2, NA18, NA22, NA23, NA41 - August or September 2017● AP2 - September or October 2017

Read on to learn more about how to prepare for your instance refresh.

At-a-glanceInstance Refreshes

Similar to an instance refresh, during a sandbox migration, we are moving a sandbox instance to new infrastructure equipped with the latest and greatest technology.

What sandbox instances are migrating and when?

● CS19, CS20, CS21, CS23, CS25 & CS26 - Saturday, July 15, 2017 between 4 p.m.–5:30 p.m. US Pacific Time ( 23:00–00:30 UTC)

Read on to learn when and customer actions required to prepare.

At-a-glanceSandbox Migrations

What’s a Site Switch?● Each Salesforce instance is built and maintained in two geographically separate locations.

An instance is actively served from one location (the active site) with transactions replicating in near real-time to the other completely redundant location (the ready site). This infrastructure model allows Salesforce to switch the location of the active site to the ready site for maintenance, compliance, and disaster recovery purposes.

Upcoming Site Switches:● AP1, AP3, AP4, CS5, CS6, CS31 on June 17, 2017

Read on for more details on how to prepare for a Site Switch.

At-a-glanceSite Switches

Active!

Ready!

● Stay-in-Touch Request Retiring in Summer ‘17● Salesforce Classic Mobile App to Retire on December 1, 2017● Access and Support for Lightning Experience with Internet Explorer version 11 extended to

December 2020 ● SOAP API Legacy Versions will retire in Summer ‘18

Click into links for more information!

At-a-glanceFeature Retirements

Feature Retirements RepositoryA consolidated view

We made it easier for you to stay informed about all the Salesforce feature retirements.

The Salesforce Feature Retirements article lists all the upcoming feature retirements with links to more details and information for each.

Check out the new Salesforce Feature Retirements article today and be sure to bookmark it for future reference.

Official: Salesforce Infrastructure Got questions? Join the Conversation!

Join the conversation with fellow Salesforce admins, IT sponsors and architects!

Major topics include: Instance or data center wide changes, IP range changes, Certificate changes, TLS Disablement

Links to resources like:Infrastructure Dreamforce Sessions, Infrastructure Overview & Best Practices

We want to hear from YOU!Pretty Please - we want this deck to be useful to YOU!

Security Enhancement

At-a-glance

What is the change?TLS disablement will begin on July 22, 2017. TLS 1.1+ will be required for all orgs.

How does it impact my org and my users?If your production environment and your users’ browsers are not prepared to support the latest TLS versions by this date, your users will not be able to access your production org, and select Salesforce products and custom or partner integrations will experience disruption. Your access to the Salesforce Help & Training portal to open and manage Support cases will also be impacted.

Read on to learn about what actions you need take to prepare for this change.

Upgrade Production Instances to TLS 1.1+ by July 22, 2017

Understand the impact to your production environment The level of impact will vary based on your production environment. Common key areas of disruption include:

Read on to learn about resources available to help you prepare for this change.

1. User browser access: Browser incompatibility will prevent your internal and external users from accessing your Salesforce production org and related services such as Marketing Cloud, Communities and Sites.

2. Email integration: Products such as Lightning for Outlook, Lightning Sync and Salesforce for Outlook won’t work if user local systems are not compatible with TLS 1.1 or later.

3. API integrations: Incompatible inbound and outbound integrations will cease to work, including AppExchange partner integrations.

4. Other areas: Mobile apps, Data Loader, Mobile SDK, SalesforceIQ Inbox, Files Sync, Chatter Desktop, Marketing Cloud

Upgrade Production Instances to TLS 1.1+ by July 22, 2017

Join our Infrastructure Security team and learn about the upcoming disablement of the TLS 1.0 encryption protocol across all Salesforce services on July 22, 2017. The team will explain how this change will impact Salesforce products, services and developer tools, and direct you to helpful resources and best practices so that you may better prepare your Salesforce org and your users for this change.

Attend a live session to get your questions answered live on air by our experts!

Sign up for the Salesforce TLS 1.0 Disablement webinars here.

● TLS Webinar Deck● TLS Webinar Recording● TLS Login History Demo

Have questions? Join our webinars!TLS 1.1+ Upgrade Events

TLS 1.0 Disablement Readiness Checklist.

TLS 1.0 Disablement Critical Update Console (CRUC) Setting: Test the disablement of TLS 1.0 for your orgs with the CRUC setting, "Require TLS 1.1 or higher for HTTPS connections", prior to the Salesforce disablement.

Guidance on Salesforce disabling TLS 1.0 impact: See the latest guidance on what actions are required to prevent any disruption to your Salesforce environment. Review the article for additional updates as they become available.

Post your questions to the Infrastructure Success Community group and follow the discussions, #TLSLIVE.

Key ResourcesTLS 1.1+ Upgrade Resources

Infrastructure Improvements

● Not sure what instance you are on? Click here to find out.● New Instance names are as follows:

○ NA4 → NA53/NA67* ○ NA5 → NA64○ NA13 → NA60○ NA19 → NA68○ NA20 → NA79○ NA26 → NA61/NA62*

● Although you now know your new instance name, please continue to follow best practices and avoid hard-coded references.

● Stay tuned for new instance names for the following: NA2, NA18, NA22, NA23 & NA41, and AP2. New instance names are announced ~six weeks before an Instance Refresh with the Date & Time.

*Confirm with your email communication.

Current & New Instance Names

More information in our article here!

Enable My Domain

Replace Hard-coded References

Plan around System

Maintenance Windows

Whitelist Salesforce

IPs

My Domain Updating Hard-coded References

What are the Salesforce IP Addresses & Domains to Whitelist?

Preferred Salesforce

Maintenance Schedule

Prepare for your Instance Refresh

We encourage you to register for our next live webinar on Tuesday, July 25, 2017, How to Prepare for Your Instance Refresh, or watch the recording if you’re unable to attend.

Other resources:

● Instance Refresh Readiness Assessment

● Instance Refresh Mini-Video

● Instance Refresh Maintenance article

Additional ResourcesInstance Refresh Events & Resources

● If your corporate network settings or email security filters restrict access to IP ranges or data centers, please ensure that you are including the current Salesforce IP ranges. If you continue to restrict access to certain IP ranges or data centers, users may be unable to access the sandbox following the migration.

● Review the How to Prepare for a Sandbox Migration article for steps you may need to take to avoid unintended service disruptions.

Actions RequiredPrepare for your Sandbox Migration

System Maintenance

● Whitelist IP Ranges:○ If your corporate network settings or email security filters restrict access to IP ranges or data

centers, please ensure that you are including the current Salesforce IP ranges. If you continue to restrict access to certain IP ranges or data centers, users may be unable to access Salesforce following the site switch.

○ If you are restricting access to certain IP ranges or data centers, update your network settings to include the complete list of Salesforce IP ranges from the, ‘What are the Salesforce IP Addresses to whitelist?’ article by June 17, 2017 to avoid any unintended service disruptions.

○ No action is required if you are not restricting access to current Salesforce IP ranges.● For more FAQs on Site Switches, review the Site Switch Overview article.

How do I prepare for a Site Switch?Preparing for a Site Switch

● AP1, CS6, CS5○ Saturday, June 17, from 8:00 a.m. to 10:00 a.m. US Pacific Time (15:00–17:00 UTC)

● AP3, AP4, CS31 ○ Saturday, June 17 from 10:00 a.m. to 12:00 p.m. US Pacific Time (17:00–19:00 UTC)

During the maintenance, your org will be available in read-only mode.

*We will email customers a final reminder 1 week before the Site Switches and this schedule is currently posted to Trust. Customers can and should begin preparing now.

Dates & TimesSite Switch Schedule

Feature Retirements

See the SOAP API Legacy Versions Retirement article for more information.

● With the Summer ‘18 release*, SOAP API legacy versions:1.8, 2, 2.2, 2.5, 3, 4, 5 and 6 will be retired and no longer be supported by Salesforce.

● Prior to the Summer ‘18 release, customers will need to upgrade their applications to include the latest SOAP API version available to prevent any disruption to applications that are currently using the legacy versions.

* Currently targeted for June 2018; date subject to change.

What is the change?SOAP API Legacy Versions will retire in Summer ‘18

See the Stay-in-Touch Request Retirement with Summer ‘17 article for more information.

● The Stay-in-Touch Request feature, which allows users to request contact information updates from Contacts or Person Accounts via an email request from outbound Salesforce emails, will retire in the Summer ‘17* release.

● After the release, users will no longer be able to send such requests from Contacts or Person accounts.

* Currently targeted for June 2017; date subject to change.

What is the change?Stay-in-Touch Request will Retire in Summer ‘17

See the Salesforce Classic Mobile App to Retire on December 1, 2017 article for more information.

The Salesforce Classic Mobile app will retire on all supported platforms and devices on December 1, 2017. Upon its retirement, the Salesforce Classic Mobile app will be removed from Google Play and the App Store, and all user access to existing installed instances of the iOS and Android mobile app will be disabled.

NOTE: In addition, iOS 10 and Android 7.0 (Nougat) will be the final mobile OS versions tested for compatibility with Salesforce Classic Mobile. Issues with any mobile OS versions newer than iOS 10 and Android 7.0 will not be addressed.

What is the change?

Salesforce Classic Mobile App to Retire on December 1, 2017

See the Retirement of Support for Accessing Lightning Experience and the Salesforce1 Mobile Browser App Using Microsoft Internet Explorer version 11 article for more information.

● We previously communicated that the end of support date for Internet Explorer version 11 (IE11) for Lightning Experience was December 16, 2017. Because of your feedback, we’ll be offering Extended Support for IE11 through December 31, 2020.

● Starting with Winter '18*, a new Setup page will allow you to enable Extended Support for IE11. By default, this preference will be disabled. You will need to enable it to ensure continued use and support of IE11 with Lightning Experience.

● Extended Support for IE11 does not apply to the use of IE11 for the Salesforce1 Mobile web app.

*Currently targeted for October 2017; date subject to change

What is the change?

Access and Support for Lightning Experience with Internet Explorer version 11 extended to December 2020