Professional Documents
Culture Documents
Management
for Office 365
Clients
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 and branches for Windows 10
and Office 365, you can evaluate new features, pilot them with specific groups in your
organization, and then deploy them widely to your organization. You can also keep
specialty systems on a long-term build for control.
Develop
Test
Release
Device
Type
A New Update
Strategy: The
Servicing Model
Both Windows 10 and Office 365 have
adopted the servicing model for client
updates. This means that new features, nonsecurity updates, and security updates are
released regularly, so your users can have the
latest functionality and improvements. The
servicing model also includes time for
enterprise organizations to test and validate
releases before adopting them.
Evaluate
and Plan Pilot and Test
Maintain
In a servicing model, new features and innovations can be developed and released
in a quick cadence, so that customers are always seeing improvements. Because
development has changed, so does the deployment process for an enterprise
organization. Quicker release of features mean that you can evaluate, pilot, and
deploy different sets of features at the same time.
Use the update option that s right for your devices and your business needs. We
recommend:
Update
option
September 2015
Follow your business needs not all systems need to follow the
same deployment model. You can even use different models for
Windows and Office on the same devices.
Save on
management
See what s coming in the next branch releases and find out what
security updates have been included by reviewing
communications from Microsoft.
Manage risk
Use Current Branch for Business (and for Office, First Release for
Current Branch for Business) to test critical line-of-business
applications that must remain up and running.
Save on
development
Specialty systems
2015 Microsoft Corporation. All rights reserved. To send feedback about this documentation, please write to us at ITSPdocs@microsoft.com.
Summary of Branches
This chart shows all of the release branches for Windows 10 and Office 365 clients.
Security, always.
Release Branches
You need to understand the different release
branches for Windows 10 and the Office 365
client applications so you can choose the right
options for your business. You decide what
works and choose the combinations of
branches to support for your organization.
Which Branch?
Freshness
Change
Management
for Office 365
Clients
Office 365 includes different sets of client applications. Office 365 Business includes the
core Office applications, and Office 365 ProPlus includes the core applications plus
Skype for Business and Access. Project Pro for Office 365 and Visio Pro for Office 365
also follow this release model.
Control
Additional
Office 365 client
applications
By default, the client applications for Office 365 are set to these branch releases:
Windows 10
Freshness indicates rapid access to new features and the ability to provide feedback
to Microsoft.
Office 365 Business, Project Pro for Office 365, and Visio Pro for Office 365 are
You ll sacrifice features for extra control use the most controlled options for
specialty systems, like factory floors, air traffic control, or emergency room devices.
Current Branch for Business offers a balance between new features and control.
But you can determine which branch is used for your client applications, according to
your business needs.
For more information about the branches for Office 365 client applications, see
Overview of update branches for Office 365 ProPlus.
2015 Microsoft Corporation. All rights reserved. To send feedback about this documentation, please write to us at ITSPdocs@microsoft.com.
Change
Management
for Office 365
Clients
Windows Insider Preview Join the Windows Insider program to evaluate and
Current Branch New features, security updates, and fixes can be released to the
Current Branch After new features have been tested through the Windows
First Release for Current Branch for Business You can validate this branch for four
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.
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.
Long Term Servicing Branch This branch provides a supported OS platform for
Release Cadences
It is important to keep both Windows and
your Office clients up to date. Office 365 and
Windows 10 are working to align release
cadences to make this easier. Both will have
regular security updates and will have new
features releasing 2 or 3 times per year. There
is also a long-term service branch available for
Windows 10 for specialty devices.
10 years. Enterprises can choose to move to a new release or stay where they are
at and skip to the next one. Long Term Servicing Branches are infrequently for
specialty devices. Use Office Professional Plus 2016 clients with these devices.
Current Branch every month. This is the default release schedule for Office 365
Business clients.
months before it becomes a Current Branch for Business. New features are included
only at the beginning of a branch release. This branch is refreshed with non-security
updates and security updates every month.
Current Branch for Business The First Release for Current Branch for Business is
rolled up and released as the Current Branch for Business every 4 months. No new
features are added until the next Current Branch for Business, although security
updates will continue to be released. Each Current Branch for Business is supported
for an additional 4 months, at which point users must move to the next branch. This
is the default release schedule for Office 365 ProPlus clients.
Current Branch
for Business
Long Term
Servicing Branch
Current Branch
(Office 365 client)
LTSB
Security update
CBB3
LTSB
CBB2
CBB
CBB
CBB1
CB
CB
FR CBB 1-...
FR CBB...
FR CBB...
FR CBB...
CB
Current Branches
Preview Branches
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
Jan*
Multiple years
Deployment tools
Windows 10
Office Mobile Apps for iOS and Android and the Office Universal Apps for Windows
have regular releases available through the Microsoft Store.
Microsoft Intune
3rd party software deployment tools
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
outside of full product releases. Recommended for devices on the Long Term Servicing
Branch of Windows 10.
Manager
2015 Microsoft Corporation. All rights reserved. To send feedback about this documentation, please write to us at ITSPdocs@microsoft.com.
Types of Changes for the Office 365 Service and Client Applications
Change
Management
for Office 365
Clients
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.
Here are the types of changes you can expect for the Office 365 service and client applications:
Type of change
Functionality
Feature updates
New features or applications
Deprecated features
Advance
notice?
Communication
channel
30 days notice
for changes that
require action
Types of Changes
There are several types of changes that are
made to Office 365 on a regular basis. The
communication channels for those changes,
and the actions that you might have to take
for them will vary, depending on the type of
change.
Non-security updates
Security
Security patches
Non-security updates
Rarely check
business critical
Add-ins
changes to users
Validate
customizations
Security bulletin
Rarely
Change admin
settings
Sometimes
testing the fix
against processes
or customizations
Rarely
Change settings
Communicate
embedding videos
Sometimes
Sometimes
Requires
testing?
Functionality
What kind of
action?
Examples of changes
Message Center
Requires tenant
admin action?
2015 Microsoft Corporation. All rights reserved. To send feedback about this documentation, please write to us at ITSPdocs@microsoft.com.
Change
Management
for Office 365
Clients
Balance of Responsibility
Microsoft and you both play a role in managing change for Office 365:
For on-premises products, your organization takes on most of the responsibility for
managing change.
Your responsibility for change management is based on the type of
service. The following chart summarizes the balance of responsibility for
both Microsoft and the customer for online services and on-premises
software.
Before a change
Microsoft s role
Customer s role
management processes
On-premises
clients and servers
Roles and
Responsibilities
Responsibility
During a change
Microsoft s role
Maintain hardware
Microsoft
Customer
After a change
Microsoft s role
Customer s role
Don t wait have a pilot team use the Current Branch builds to start evaluating
new features. Use the Office 365 First Release for Current Branch for Business if
you need a longer lead time for testing.
Align your work with the release schedule schedule testing passes monthly.
Customer s role
Work with people in your organization to
2015 Microsoft Corporation. All rights reserved. To send feedback about this documentation, please write to us at ITSPdocs@microsoft.com.
Change
Management
for Office 365
Clients
Manage Update
Deployments
You choose when and how updates are deployed
to your organization by configuring:
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
packaging the updates yourself and manually delivering them to client computers
over your network.
Manual
From an on-premises
location
Microsoft makes an
updated build
available on the
Internet.
An administrator
downloads the
updated build to an
on-premises location.
An administrator
downloads the updated
build to an on-premises
location.
Customizations
Allow automatic updates
for...
Low customizations
Recommended Branch:
Current Branch
High customizations
Recommended Branch:
Current Branch for Business.
Validate by using First Release
for Current Branch for Business.
Use the following methods to configure which branches are used by which
client computers and how those clients computers are updated:
2015 Microsoft Corporation. All rights reserved. To send feedback about this documentation, please write to us at ITSPdocs@microsoft.com.