What is the Servicing Model? What s in it for Enterprise Organizations?

Change In a traditional development model it can take months of planning, development,

and testing before a large release is ready. Traditional deployments take
You want up-to-date features, but you also want the control and support you need to
run your business. With the variety of release programs for Windows 10 and Office 365,
you can evaluate new features, pilot them with specific groups in your organization,
enterprises years to plan, evaluate test, pilot, and deploy and then maintain the

Management entire environment. and then deploy them widely to your organization. You can also keep specialty systems
on a long-term build for control.

for Office 365

Traditional release model Use the update option that s right for your devices and your business needs. We
Plan Develop Test Release recommend:

Clients Multiple months cycle

Device
Type
Traditional deployment model
Phones and tablets Laptops and desktops Specialty systems

A New Update
Evaluate
iOS or Android devices
and Plan Pilot and Test Deploy Maintain Update receive regular updates Use Current Branch (Windows) Use Windows 10 Long
and Current Channel (Office Term Servicing Branch
option
Strategy: The
from their respective app
365) to get regular updates with and Office Professional
stores. Devices running the
the latest features. Plus 2016 client installs
Multiple months cycle Office Universal apps
(using MSI files) for
Servicing Model automatically receive
regular updates from the
Microsoft store.
Have custom add-ins? Choose
Current Branch for Business
control.

In a servicing model, new features and innovations can be developed and released (Windows) and Deferred
Both Windows 10 and Office 365 have in a quick cadence, so that customers are always seeing improvements. Because Channel (Office 365) so you
adopted the servicing model for client For Windows 10 devices,
development has changed, so does the deployment process for an enterprise use Current Branch to get have time to test.
updates. This means that new features, non- organization. Quicker release of features mean that you can evaluate, pilot, and regular updates with the
security updates, and security updates are deploy different sets of features at the same time. latest features.
released regularly, so your users can have the
latest functionality and improvements. The
servicing model also includes time for Releases in a servicing world Focus on your business, not managing the software.
enterprise organizations to test and validate
releases before adopting them. Plan, Develop, Test, Release - repeat Regular updates mean your users phones, tablets, and desktops
Stay up to date
stay up to date with the latest fixes.

Follow your business needs – not all systems need to follow the
Mix and match
same deployment model. You can even use different models for
programs
Windows and Office on the same devices.

Allow automatic updates to the fully tested Current Branch for

Multiple cycles in a year Save on
Business (Windows) and Deferred Channel (Office 365) instead
management
of managing the software packages yourself.
Deployment in a servicing world
See what s coming in the next releases and find out what
This topic is 1 of 6 in a series Stay in the loop security updates have been included by reviewing
Evaluate, Pilot, Deploy - repeat
communications from Microsoft.
1 2 3 4 5 6 Use Current Branch for Business (Windows) and Deferred
Manage risk Channel or First Release for Deferred Channel (Office 365) to
test critical line-of-business applications that must keep running.

First, check the marketplace – others may have a solution that

Save on
Multiple cycles in a year works. If you need custom development, use best practices to
development
ensure add-ins work after updates.

February 2016 © 2016 Microsoft Corporation. All rights reserved. To send feedback about this documentation, please write to us at [email protected].
 Summary of Release Options
Change Choose the right release option for your business needs: Which Release Option?

Management
This chart shows all of the release options for Windows 10 and Office 365 clients.

Office 365 client Windows 10

for Office 365 Up to date innovation. Have time to evaluate. Security, always. Windows Insider Preview Branch
Lets you preview features and give

Freshness
Clients Get the latest features
right away.
Test with your existing
systems. Choose these
You ll always get the
latest security updates,
feedback.

releases: no waiting, whichever These options give your users the latest released
Choose Current Branch Current Current
program you choose. features. It s great for your mobile users who
(Windows 10) and  Windows 10: Current Channel Branch
Current Channel (Office bring their own devices, your sales force out in
Branch for Business
365). the field, and for test systems or pilot programs.

Release Options  Office 365: Deferred

Channel and First
Release for Deferred First Release for Deferred Channel
Channel Gives you time to check out the
You need to understand the different release features and test your
options for Windows 10 and the Office 365 customizations or processes.
client applications so you can choose the right
options for your business. You decide what Default channels for client applications
works and choose the combinations of Deferred These options give you a couple of months lead- Current
releases to support for your organization. Office 365 includes different sets of client applications. Office 365 Business includes the Channel time before you get the latest version. They re Branch
core Office applications, and Office 365 ProPlus includes the core applications plus best for desktops and laptops in the office. Enjoy for
This model provides an overview and helps Skype for Business and Access. Project for Office 365 and Visio Pro for Office 365 also new features, and the fact that millions of users Business
you choose. follow this release model. have tested and validated them.

Client applications included Additional Office Professional Plus 2016

with Office 365 Business Office 365 client client installs (using MSI files)
applications Good for scenarios where maximum
control is required and the device
has limited internet access.
Long Term Servicing Branch
Best for scenarios where control
over the operating system

Control
Project Visio Pro deployment is of prime
Client applications included
for Office for Office importance.
with Office 365 ProPlus
365 365
This topic is 2 of 6 in a series By default, the client applications for Office 365 are set to these channels:
 Office 365 Business, Project for Office 365, and Visio Pro for Office 365 are set Freshness indicates rapid access to new features and the ability to provide feedback
1 2 3 4 5 6 to use Current Channel to Microsoft.
 Office 365 ProPlus is set to use Deferred Channel You ll sacrifice features for extra control – use the most controlled options for
But you can determine which channel is used for your client applications, according to specialty systems, like factory floors, air traffic control, or emergency room devices.
your business needs.
Current Branch for Business (Windows) and Deferred Channel (Office 365) offer a
For more information about the channels for Office 365 client applications, see
balance between new features and control.
Overview of update channels for Office 365 ProPlus.
© 2016 Microsoft Corporation. All rights reserved. To send feedback about this documentation, please write to us at [email protected].
 Windows 10 Release Cadence Office 365 Client Release Cadence

Change
Windows 10 has four types of release branches: Office 365 clients have the following types of releases:

 Windows Insider Preview Join the Windows Insider program to evaluate and  Current Channel New features, security updates, and fixes can be released to the

Management
provide feedback on pre-release features, and perform application compatibility Current Channel every month. This is the default release schedule for Office 365
validation testing. New features are released frequently. Business clients.

 Current Branch After new features have been tested through the Windows  First Release for Deferred Channel You can validate this release for four months

for Office 365 Insider program, they are released along with bug fixes and security patches as the
Current Branch. A new Current Branch is released a few times a year.
before it becomes a Deferred Channel release. New features are included only at the
beginning of a release. This channel is refreshed with non-security updates and
security updates every month.

Clients  Current Branch for Business The features from Current Branch are rolled into the
Current Branch for Business (CBB) a few times a year. Microsoft will support a
Current Branch for Business release for at least 8 months.
 Deferred Channel The First Release for Deferred Channel is rolled up and released
as the Deferred Channel release every 4 months. No new features are added until
 Long Term Servicing Branch This branch provides a supported OS platform for the next Deferred Channel release, although security updates will continue to be
10 years. Enterprises can choose to move to a new release or stay where they are released. Each Deferred Channel release is supported for an additional 4 months, at
at and skip to the next one. Long Term Servicing Branches are infrequently for which point users must move to the next release. This is the default release schedule
for Office 365 ProPlus clients.
Release Cadences specialty devices. Use Office Professional Plus 2016 clients with these devices.

It is important to keep both Windows and Releases for Windows 10 Releases for Office 365 ProPlus
your Office clients up to date. Office 365 and Preview Current Current Branch Long Term Current Channel First Release for Deferred Channel Security update
Windows 10 are working to align release Branches Branch for Business Servicing Branch (Office 365 client) Deferred Channel (Office 365 client)
(Office 365 client)
cadences to make this easier. Both will have
LTSB
regular security updates and will have new DC3
LTSB
features releasing 2 or 3 times per year. There
is also a long-term service branch available for
DC2
Windows 10 for specialty devices. CBB
CBB
DC1

CB
CB FR DC 1-... FR DC... FR DC... FR DC...
CB

Current Channel

Preview Branches
Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan*

Multiple years * Dates are for illustrative purposes only

See Windows 10 servicing options for updates and upgrades for more information. Office Mobile Apps
Office Mobile Apps for iOS and Android and the Office Universal Apps for Windows
This topic is 3 of 6 in a series have regular releases available through the Microsoft Store.
Deployment tools Windows 10 and Office 365 clients
1 2 3 4 5 6
Windows 10
 System Center Configuration Office Professional Plus 2016 client installs
Manager
 Windows Update for Business  Microsoft Intune Security updates are made available for the Office clients that you install by using .MSI
files as part of the Office Volume Licensing program. New features are not delivered
 Windows Server Update Services  3rd party software deployment tools outside of full product releases. Recommended for devices on the Long Term Servicing
Branch of Windows 10.

© 2016 Microsoft Corporation. All rights reserved. To send feedback about this documentation, please write to us at [email protected].
 Types of Changes for the Office 365 Service and Client Applications
Change Not all changes have the same impact on your users or require action. Some are planned and some unplanned by their nature (non-security
updates and security updates aren t usually planned in advance). Depending on the type of change, the communication channel also varies.

Management
Here are the types of changes you can expect for the Office 365 service and client applications:

for Office 365 Type of change Advance Communication Requires tenant What kind of Requires
notice? channel admin action? action? testing?
Clients Functionality 30 days notice  Message Center Sometimes  Change settings Rarely – check
 Feature updates for changes that  Office 365 Roadmap  Communicate business critical
require action changes to users Add-ins
 New features or applications  Office 365 Blog
 Deprecated features  Office 365 Network on  Validate
Yammer customizations
Types of Changes
Non-security updates No, these are  TechNet Office 365 client Sometimes  Change admin Sometimes –
There are several types of changes that are included in the update channel releases settings testing the fix
made to Office 365 on a regular basis. The  Client hotfixes for issues against processes
monthly build page
communication channels for those changes, for all channels or customizations
and the actions that you might have to take
for them will vary, depending on the type of
change.

This model explains the types of changes you Security No, these are  Security bulletin Rarely Rarely
can expect, when to expect changes, and what  Security patches included in the
you need to do to be prepared for changes in monthly build
Office 365. for all channels

Examples of changes Guidelines for managing change when using Office Add-ins:
 We recommend that customers use Current  If your developers built the Add-in, we
Functionality Channel to get the latest updates. If you have suggest they update the code and redeploy
Office customizations or Add-ins deployed, you the custom Office Add-in.
 Feature updates: PowerPoint – simpler process for
can use the Deferred Channel, which delays  If you built your customization using VBA,
embedding videos
updates to Office until you have had the chance VSTO, or COM, consider rebuilding your
 New features or applications: Skype for Business to fix and test your customizations. To fix and
This topic is 4 of 6 in a series customization as an Office Add-in, or check
test your customizations before updates are the Office Store to see if there is a 3rd-pary
Non-security updates applied to Deferred Channel, use First Release Add-in that provides similar functionality.
1 2 3 4 5 6
for Deferred Channel. Use the Office Telemetry
Dashboard to check Add-ins for compatibility.  Consider decommissioning Office Add-ins
 Hotfixes based on customer reported bugs that are no longer used or have low
utilization.

© 2016 Microsoft Corporation. All rights reserved. To send feedback about this documentation, please write to us at [email protected].
 Balance of Responsibility Microsoft s Role and Your Role
Change In a service offering, the balance of responsibility for things such as hardware
maintenance and security updates shifts to the service provider (Microsoft) instead
of the customer (you). However, you still need to ensure that custom software
Microsoft and you both play a role in managing change for Office 365:

Before a change
Management continues to function as expected when updates are rolled out.

For on-premises products, your organization takes on most of the responsibility for Microsoft s role Customer s role

for Office 365

managing change.
 Set expectations for service changes  Understand what to expect for changes and
 Notify customers 30 days in advance for communications

Clients
Your responsibility for change management is based on the type of changes that require administrator action  Read Message Center, Office 365 Roadmap
service. The following chart summarizes the balance of responsibility for  Publish majority of new features and and Office Blog regularly
both Microsoft and the customer for online services and on-premises updates on the Office 365 Roadmap  Set up pilot teams to preview new
software. functionality using Current Channel
 Review and update internal change
Office 365 Office 365 On-premises management processes
Responsibility service clients clients and servers
 Understand the Office 365 system
Roles and Provide new functionality requirements and check compliance

Responsibilities Test new features for

quality assurance
During a change

Responsibility for managing change is shared Communicate about new Microsoft s role Customer s role
between Microsoft and you as the admin of features
your Office 365 tenancy. The balance of  Roll change out to customers  Check Message Center and review the
Integrate custom software additional information link
responsibility is different for an online service  Specifically for Office 365 clients: release a
than it is for an on-premises server or client. new Current Channel each month and new  Take any action required (if applicable) and
Apply security updates security and non-security updates for test any add-ins
Understand the roles both Microsoft and you Deferred Channel  If using an internal share for updates,
need to play before, during, and after a Maintain system software  Monitor telemetry and support escalations download the latest builds and upload to
change occurs to the service. for any unexpected issues your share.
Maintain hardware
 If a break/fix scenario is experienced, create a
Review what s included in each release on the Support Request
Office 365 client update channel releases
page on TechNet. Microsoft Customer
After a change

Microsoft s role Customer s role

 Listen to customer feedback to improve  Work with people in your organization to
Tips for Testing rollout of future changes adopt the change (get help on the Office 365
 Listen to feedback from the Office 365 Success Center)
 Don t wait – have a pilot team use the Current Channel builds to start evaluating
This topic is 5 of 6 in a series Network in Yammer and admin feedback  Review change management processes and
new features. Use the Office 365 First Release for Deferred Channel if you need a
tool bottlenecks for opportunities to streamline,
longer lead time for testing. and use more Microsoft resources
1 2 3 4 5 6  Update Office 365 Roadmap statuses and
 Use an Azure virtual environment to test against your customizations or add new features  Provide general feedback in the Office 365
processes. Network in Yammer and specific feedback in
 Align your work with the release schedule – schedule testing passes monthly. the admin feedback tool
 Train users to provide app specific feedback
using the Smile button in Office apps

© 2016 Microsoft Corporation. All rights reserved. To send feedback about this documentation, please write to us at [email protected].
 How to Apply Updates
Change You can decide how updates are deployed to your users computers. You can allow
the client computers to automatically receive updates over the Internet or from an
on-premises location. Alternatively, you might want to have more control by
Do you need to control the delivery of updates?
To decide which method to use, consider the following scenarios:

Management packaging the updates yourself and manually delivering them to client computers
over your network. Customizations
Methods for applying Office updates to client
for Office 365 computers
Allow automatic updates
for...
Use manual delivery of
updates for...

Clients Automatic Manual

Users or computers that are
primarily for productivity and don t
Users or computers that rely on
customizations or integrated
From an on- From an on-premises
From the Internet use customizations or integrated solutions that work with the Office
premises location location
solutions. 365 clients.
Microsoft makes an An administrator An administrator

Manage Update updated build

available on the
downloads the
updated build to an
downloads the updated
build to an on-premises

Deployments
Internet. on-premises location. location.

The client computers The client computers The administrator uses

automatically install automatically install scripts or software
You choose when and how updates are deployed the updates when the updates when distribution tools to Low customizations High customizations
to your organization by configuring: they are available. they are available. push the updated build
to the client computers.
Recommended Channel:
 Which channel to use. This controls how Recommended Channel: Deferred Channel. Validate by
often updates are available. Current Channel using First Release for Deferred
 Which update method to use (automatic or Channel.
manual). This controls how your client
computers get the updates.
Managed or un-managed computers?
Allow automatic updates Deploy from an on-
from the Internet for... premises location when...

Consumers and small businesses You want to control when updates

without an IT department. are pushed out to your
organization s computers.

This topic is 6 of 6 in a series

How to configure channels and update methods
1 2 3 4 5 6 Use the following methods to configure which channels are used by which
client computers and how those clients computers are updated:
 Office Deployment Tool
 Group Policy – for centralized administration of domain-joined computers.

© 2016 Microsoft Corporation. All rights reserved. To send feedback about this documentation, please write to us at [email protected].