Best practices from the field: Microsoft 365 change guide
This article was written by Microsoft experts in the field who work with enterprise customers to deploy Office.
The information in this article applies to the Microsoft 365 multitenant environment.
Continuous change in the cloud
The Microsoft 365 cloud environment is a hyperscale suite of service offerings that's constantly changing. In the technology industry, being consistently cutting-edge benefits productivity, security, and user happiness. Change in the Microsoft cloud has purpose: to deliver customer value, secure the environment, and delight users. The pace of change in Microsoft 365 is rapid and continuous - both adjectives describe the customer value pipeline that this model helps. Microsoft helps users increase efficiency in their organizations by offering innovative features and secure services.
Microsoft uses an agile development model that promotes rapid development. This model shortens the time from when a change is initiated to when it's in production. To help improve usability, we aim to shorten the time between feature implementation and value realization for our customers. Agile development is important in the modern cloud environment. Using it, we can nimbly adjust engineering priorities that's based on customer feedback, market dynamics, regulatory requirements, and emerging risks. Swift integration of changes into your environment means that we receive feedback data faster, and then we can iteratively improve our services.
Many changes relate to new features that are designed to enhance the user experience. These changes are a category of change that's within a broader set. The broader set of categories of change includes service maintenance, security updates, and updates to meet the needs of the ever-changing regulatory and compliance landscape.
Microsoft constantly improves Microsoft 365 services to help every person and every organization on the planet to achieve more. Our commitment to enhancing the user experience means that we offer a continuous stream of updates to the service. And to ease your deployment planning, we release client updates in alignment with release cycles. We design new features to improve productivity and delight users. Equally important is for features to operate in a secure and compliant environment. As part of the shared responsibility model, Microsoft takes extensive measures to secure our environment. Our certifications hosted on the Microsoft Service Trust Portal evidence our compliance with 100+ frameworks. The other half of the responsibility model – your environment – must also be secure and compliant, so we carefully consider potential customer impact when we structure our changes and the surrounding processes.
Historically, the deployment of changes within customer organizations has been tightly controlled by IT departments. Controlling deployments within your tenant holds a place in the modern cloud landscape, but faster feature deployment is key to realizing value for your users. As the Microsoft cloud further adopts a continuous update model, organizations’ ability to make risk-based decisions on which changes require granular evaluation and which can be implemented immediately becomes paramount.
When Microsoft adds capabilities, and users leverage these capabilities, the user experience improves as supported by data. At the time of writing, a comparison of net promoter score (NPS) between customers using the continuous update channel (Current Channel) and the Semi-Annual Enterprise Channel shows a 10-point advantage to the continuous update channel for Microsoft 365 Apps. Figure 1 shows a comparison.
Our goal is to provide your organization with changes that can be controlled (where possible), if deemed impactful to the organization, while still allowing most changes to flow to users to enhance value, productivity, collaboration, and security.
Controlling change: challenges and strategy
Despite the overwhelming benefits of rapid feature release and adoption, it's important to use a robust change management strategy. We recognize that managing change, especially continuous cloud change, can be challenging for organizations. IT departments and other lines of defense often believe that each change must be reviewed in depth before they deploy new software in their environments. This might be an advantageous strategy for a subset of high impact changes, but reviewing 100 percent of changes is a burdensome strategy that delays deployment of the endlessly evolving features that enable your users.
Not all features or changes have the potential to impact your security or compliance stature, so it might not be necessary to deeply analyze every single change. For changes that are impactful, we provide configuration options for controlling related features. To help users adopt new features, by default, these changes are generally on - action is required on your part to disable or limit these features.
The ability to control impactful changes is a differentiator offered by Microsoft. The technology industry is predominantly focused on innovation, which is generally assumed to have positive impact on users. It isn't common to find granularity of control over these innovations offered by technology leaders or other cloud providers. By respecting your right to control most impactful changes, we're demonstrating our commitment to partnership and ultimately your success. Furthermore, we're committed to improving the overall change experience. By providing transparency into our change process, procedures, and roadmap, and by monitoring customer feedback, we want to enable our customers to evaluate and deploy the rapidly increasing volume of updates that we release.
From industry observations, feedback, and supporting data, we've identified a key challenge that our customers face when they apply highly restrictive change ingestion models to the continuous release policy of Microsoft 365. The challenge lies in how frequently Microsoft updates services in the modern cloud. To illustrate the challenge, assume that Microsoft pushes 720 changes per year, released linearly. If these changes are restricted for evaluation, IT departments that are gating changes could be behind up to 60 changes after the first month. The resulting backlog of changes heightens the entropy in the environment and prevents users from utilizing the latest features and updates. The question becomes: is the organization capable of processing these rapid changes according to existing procedures or are changes left disabled because they can't match the pace of release?
"Is the organization capable of processing these rapid changes according to existing procedures or are changes left disabled because they cannot match the pace of release?"
The challenge can be further explained by the “automobile metaphor.” Many organizations focus only on functionality and security. In the context of a vehicle, this is the equivalent of focusing on getting from point A to point B. In this case, owners are content if they can fix the vehicle, if they know how it works, and if the vehicle has seat belts for security. However, we challenge the IT professionals reading this to consider the user. To the average vehicle consumer, transportation is more than A to B. Users (consumer drivers) want a radio for entertainment, air conditioning for climate control, and power windows for convenience. Drivers want anti-lock braking systems, airbags, and seat belts for security. If the focus is solely on enabling users to reach the destination, you might be disenfranchising the population that wants to be more secure, comfortable, and efficient on the journey. If organizational lines of defense spend valuable time divining which features are important, which features users care about, and which features are causing disruption to the IT environment, the burden becomes unsustainable. This calls for democratization of change evaluation; for more information, see the section, Change Evaluation Democratization.
Although Microsoft doesn't provide a default off option, we find that very few customers take advantage of the options that we provide to disable features in their environments. When organizations employ an “everything off” strategy by leveraging our provided configurations, the result is similar to managing on-premises software. The benefits originally sought by moving to the cloud are largely alienated by this approach, because the innovations that users care about are unavailable. Moreover, the Microsoft ecosystem suffers from the gap in usage data created by this strategy. For example, diagnostic data provides Microsoft with valuable information about how our customers use features, how the features are (or are not) improving overall experience, and crash reports that help us to stay apprised of widespread issues. Although we provide customers control over diagnostic data, exercising these controls limits the data we have for keeping our service secure, up to date, and functioning as expected.
We cite this as a challenge because we acknowledge the delicate balance that must be reached between controlling the environment, ensuring proper training, and providing employees exciting new features. IT professionals are at the forefront of maintaining this balance - this is why Microsoft provides tools, transparency, and guidance for making risk-based deployment decisions. Configuration management tools, product roadmaps, change notifications, and documentation are manifestations of our commitment to aid you in reaching change-risk equilibrium.
This conversation is focused on the features that we deliver, not the security updates that happen in the background. The same features that we develop with exhaustive market research to increase productivity and user satisfaction. The features that help empower our customers to achieve more, with open feedback channels to adjust for negative feedback in an agile manner. We require customer participation to validate our features, which means features must first be deployed in customer environments for users to leverage.
Three categories of customers can be identified based on their observed change strategies: Maximize Change, Allow Most Restricting High Impact, and Restrict All Change. Figure 2 summarizes these categories.
The Maximize Change strategy is most applicable to small- or medium-sized businesses that seek to optimize user productivity, and that operate without compliance or regulatory requirements.
The Allow Most Restricting High Impact category is the strategy that we recommend you target, especially if your organization operates in a regulated environment, or if you have strict security requirements (like in the financial services, healthcare, and aerospace industries). The case for implementing a risk-based approach for evaluating changes is supported by the NPS data in Figure 1.
Microsoft advises customers to be intentional with their decisions to disable a change and to avoid unconsciously leaving all changes disabled. Microsoft strives to enable you to make risk-based decisions about changes that require in-depth evaluation, while allowing the rest of the changes to be deployed immediately with minimal evaluation (and risk). By proactively identifying our change impact levels, described in change classification and notification, and by keeping you apprised of upcoming changes, described in sources of change information, we aid you in making risk-based decisions on which changes require evaluation.
The Microsoft industry observation shows that the Restrict All Change strategy is overly burdensome and less effective at user empowerment because it limits the benefits of continuous innovation.
Consuming and managing change – Message center and Planner
All change strategies require communication and messaging for users to consume and act on the change. Message center is your notification hub for planned changes and other important Microsoft 365 announcements. Message center is located in the Microsoft 365 admin center. It includes upcoming new and changed features, planned maintenance, and other important announcements. There are three categories for messages:
- Prevent or fix issues
- Plan for change, and
- Stay informed
The message attributes that Message center provide include Publish Date, Message ID (for tracking specific messages), Title, and (change/event) Description. The Message center is a critical source of information that's important for change planning and update consumption across Microsoft 365. Building projects and tasks from these often-actionable notifications is critical to successful change strategy. To help you better understand this content, Planner has been integrated with Message center allowing messages to be directly synced with Planner.
Planner features include:
- Syncing messages from Message center.
- Selecting the type(s) of messages synced.
- Setting a cadence for the message sync.
After a message is synced to Planner, it shows up in Planner as a task. Messages center post titles are prefixed with the associated service in brackets. If a message is updated, that update also syncs to the Planner task.
Each task is structured as:
- The message post title has a prefix in brackets (for example, "[SharePoint] New feature") that indicates the service that the post is associated with. Figure 3 shows an example.
- The Start Date is set to the time the task was created in Planner.
- The Published Date of the message post can be found in the Notes.
When you use Planner to manage tasks, group tasks, and formulate a plan of action for completing tasks strategically, you can review boards and change management teams to track change efficiently.
Change types and control methods
Microsoft provides various release choices and tools to help control and deploy changes in a manner that aligns with your strategy. We previously discussed our recommended strategy; in this section, we describe how you can implement this strategy.
Microsoft 365 changes are released to both services (like SharePoint Online and Teams) and clients, referred to as Microsoft 365 Apps (like Microsoft Word, Excel, and PowerPoint). Services and clients have different release choices and deployment controls, so it's important to understand the differences as you implement your release management strategy.
Types of changes for Microsoft 365 services and clients
Microsoft 365 changes can be planned or unplanned, depending on the nature of the changes. For example, security updates aren't always planned, because they're reactions to emergent risks or issues in our products or services. Depending on the type of change, the communication channel might also vary. Communication channels are further described in the section, Change classification and notification. For a summary of change types for both services and client applications, see Table 1.
Table 1: Change types for Microsoft 365 services and client applications
|Type of change||Feature updates
New features or applications
|Client hotfixes for issues||Security patches|
|Advance notice?||30 days' notice for changes that require action||No; these are included in the monthly build for all channels||No; these are included in the monthly build for all channels|
|Communication channel||Message center in the Microsoft 365 admin center
Microsoft 365 roadmap
Microsoft 365 blog
Microsoft 365 area of the Microsoft Tech Community
|Release information for updates to Microsoft 365 Apps||Security bulletin or CVE|
|Requires admin action?||Sometimes||Rarely||Rarely|
|What kind of action?||Change settings
Communicate changes to users
|Change admin settings|
Responsibility for managing these changes is shared between Microsoft and you as the administrator of your Microsoft 365 tenant. For more information, see the Microsoft shared responsibility model.
Now that we've outlined the types of changes that you can expect from Microsoft 365 services and client applications, including associated responsibilities, the next section explores the different release choices and the controls available for each.
Service release options and controls
Service release options
Microsoft 365 services provide two options for receiving new product updates and features as they become available: Standard Release and Targeted Release. These release options help you to manage how your organization receives service updates. We provide controls for you to designate which users receive updates, based on their association to one of the release options.
As Microsoft develops products and features, new releases are validated in various stages. Figure 4 depicts these stages, with each validation stage reaching a broader audience. Before moving to the next stage, a threshold of deployments in the prior stage must complete without any issues.
Microsoft feature teams are first to validate the features that they develop.
After identified bugs or issues are resolved, the feature is released to the Microsoft 365 organization, spanning a wider user base for validation.
After the feature is deemed ready, it's released to all of Microsoft, which is referred to internally as “dogfooding” our products to identify issues, before updates reach the public.
The next stages are public releases. Targeted Release is comprised of customers who have configured their tenant, or specific users, to be on the Targeted Release option. Substantial feedback and product performance data is collected in this stage as our customers perform integration testing and broad validation across many countries or regions, cloud architectures, and IT professionals or power users. If your tenant, or a subset of your users, are configured for Standard Release, this last stage is when these users – and the rest of the world – receive the new features.
To implement the democratization of change strategy within your organization, leverage Targeted Release for both IT and power users.
Service release controls
Your primary control for receiving service updates is the configuration of your release options. Although Microsoft provides you control over the cadence at which your users receive updates, these changes are deployed to our hyperscale cloud services (instead of to software installations that are running in your IT infrastructure). It would be impractical for Microsoft to manage, update, and secure a global cloud with specific versions of our services running for specific tenants. This means that service changes give you less granularity of control over deployment than Microsoft 365 Apps do, because Microsoft 365 Apps have both release channels and various deployment tools available.
You can configure release options in the Microsoft 365 admin portal as described in Set up the release option in the admin center. Navigate to the portal, and then select Settings > Org Settings > Organizational Profile > Release Preferences. Figure 5 shows the configuration pane where you can select to have everyone on Standard Release, everyone on Targeted Release, or specific users on Targeted Release.
It's important to have a staging or test tenant as part of your change strategy. Certain features require tenant changes before manifestation in the user experience. These tenant changes can be implemented in the staging tenant, so you can preview features, while preserving production tenant configurations.
Client release channels and controls
Client release channels
Microsoft offers different update channels to which customers can subscribe for updates to our click-to-run clients, Microsoft 365 Apps. These channels determine how frequently changes are released to their entire tenant or subscribed subdivisions their tenant, depending on customer configuration. Channels are a powerful mechanism through which IT departments and power users can evaluate and test upcoming changes without hindering their release to the greater user population. For more information, see Overview of update channels for Microsoft 365 Apps.
Table 2 provides a comparison of the Microsoft 365 Apps channels, Current Channel, Monthly Enterprise Channel, and Semi-Annual Enterprise Channel.
Table 2: Microsoft 365 Apps update channels
|Channel name||Current Channel||Monthly Enterprise Channel||Semi-Annual Enterprise Channel|
|Recommended use||Provide your users with new Office features as soon as they're ready, but not on a set schedule.||Provide your users with new Office features only once a month and on a predictable schedule.||For select devices in your organization, where extensive testing is needed before rolling out new Office features. For example, to comply with regulatory, governmental, or other organizational requirements.|
|Release frequency||At least once a month (likely more often), but not on a set schedule||Once a month, on the second Tuesday of the month||Once a month, on the second Tuesday of the month|
|Feature updates||As soon as they're ready (usually once a month), but not on a set schedule||Once a month, on the second Tuesday of the month||Twice a year (in January and July), on the second Tuesday of the month|
|Security updates (if needed)||Once a month, on the second Tuesday of the month||Once a month, on the second Tuesday of the month||Once a month, on the second Tuesday of the month|
|Non-security updates (if needed)||Usually at least once a month (possibly more often), but not on a set schedule||Once a month, on the second Tuesday of the month||Once a month, on the second Tuesday of the month|
|Support duration for a specific version||Until the next version is released with new features, which is usually about one month||Two months||Fourteen months|
Microsoft provides three main methods to modify Microsoft 365 Apps update channels for devices in your organization:
When you switch channels, there are certain considerations - such as loss of features when switching users from Current Channel to Semi-Annual Enterprise Channel. For a complete list of considerations, see Considerations when changing channels.
Client release controls
In conjunction with release channels, which are inherently controls themselves, Microsoft provides a selection of tools and configurations for further deploying, controlling, and managing your Microsoft 365 clients. The tools for managing your devices and the Microsoft 365 clients installed on them have historically been decentralized. In addition to a multitude of third-party options that are available, the Microsoft solutions include the following tools:
Other features in the Device Management Admin Console
By attaching Intune to your Configuration Manager deployment (referred to as co-management), you can attach the intelligence from the Microsoft 365 cloud to your workflows in powerful ways. You can:
- Completely automate compatibility testing for Windows upgrades.
- Deploy client updates faster to make your organization secure and compliant quickly.
- Take immediate actions on your devices.
Manage updates to Microsoft 365 Apps with Microsoft Configuration Manager is your source for understanding:
The prerequisites that are required when using Microsoft Configuration Manager to update Microsoft 365 Apps.
How to enable Configuration Manager to receive Microsoft 365 client package notifications.
How to enable Microsoft 365 clients to receive updates from Configuration Manager.
Your options for enabling clients to receive updates from Configuration Manager.
For comprehensive instructions to configure your deployment strategy, see the Microsoft Configuration Manager documentation.
The Microsoft 365 Apps admin center is designed to help admins lower their total cost of ownership while being able to quickly deliver features, security, and quality updates with Microsoft 365 Apps. The insight and control capabilities can provide deeper and near-real-time deployment information, issue notification, and quick actions (snooze, restore, pause, and resume) to ensure minimal user downtime.
Drill into detailed views of Office devices and add-in information.
View insights like channel/build spread, add-in diversity, and more.
Export the data.
View a dashboard for security update compliance status cross-channel.
Set your target goal and timeline to track and report.
Identify failing devices and take mitigating action.
Set up profiles for devices to automatically receive updates based on custom requirements.
Throttle-based on network congestion and location.
Takes advantage of Windows 10 delivery optimization.
Act using the tool to Pause, Restore, and Snooze deployments.
Maintain device compliance with update deadlines and update date exclusions.
At the time of publishing, the Microsoft 365 Apps admin center is available to enterprise customers with E3 SKUs and later.
Client configuration controls
After Microsoft 365 Apps are deployed to devices and users, at your defined cadence and with enterprise-grade tools, Microsoft provides you granular client configuration controls. Microsoft 365 Apps have over 2,000 configuration options allowing you to alter client behavior to suit your organization’s risk, compliance, and operational profiles.
Although group policy has historically been used to enforce client settings and is still a viable method, we've developed a cloud-based synchronization nexus service that allows policies to roam with users: Cloud Policy. This service lets you enforce policy settings for Microsoft 365 Apps for enterprise on a user's device, even if the device isn't domain joined or otherwise managed. When a user signs into Microsoft 365 Apps for enterprise on a device, the policy settings roam to that device. You can also enforce some policy settings for Office web apps, both for users who are signed in and for users who access documents anonymously.
Figure 6 shows the portal and the vast number of policy settings available for configuration in the Microsoft 365 Apps admin center. You can also use Cloud Policy directly in the Microsoft Intune admin center.
Some configuration options control basic client behavior, such as scroll bar visibility in Excel or availability of Live Subtitles in PowerPoint, while other configurations may be important to your security, compliance, or risk departments. Figure 7 illustrates the Cloud Policy option to enable or disable connected experiences in Microsoft 365 Apps, which provide users with web-based services from their desktop clients (like Translator, Bing image search, and 3D Maps).
Microsoft provides privacy controls so that you can meet compliance and security obligations on a global scale, regardless of operational localities. With Cloud Policy, you can use a drop-down menu to modify these settings and apply the modifications across the devices that use that profile.
Change evaluation democratization
Earlier, we shared data that supports the user value of being on Current Channel, which provides continuous updates. We recommend this channel and Monthly Enterprise Channel as two solutions to expedite update evaluation and testing. Microsoft recommends two models for using these channels:
Test tenant: To evaluate and test incoming features, customers use a test tenant that mimics production. For clients, we recommend that the test tenant be subscribed to Current Channel or Monthly Enterprise Channel. For services, we recommend that the test tenant be subscribed to the Targeted Release option. Test tenants are used for integration testing and product evaluation separate from production. Traditionally, IT owns tests tenants and operates the test accounts within. This is an IT-centric model that may cause bottlenecks and incomplete evaluations to occur. We recommend inclusion of users from various departments and roles in your test tenant. IT departments aren't experts on every product and aren't always best suited to perform certain product evaluations. For Microsoft 365 services, Targeted Release and Standard Release options are available.
Microsoft 365 Apps: For information about the benefits and how to enroll or change update channels, see Change the Microsoft 365 Apps update channel for devices in your organization. For a description of benefits, see the Client release channels section of this article.
Microsoft 365 services: For information about the benefits and how to enroll in to these update channels, see Set up the Standard or Targeted release options. For an outline of the channels, see the Service release options and controls section earlier in this article.
Power user (expertise): To democratize update evaluations, identify power users in your production tenant and subscribe them to Current Channel or Monthly Enterprise Channel (Microsoft 365 Apps) and the Targeted Release option (services). Only the specified power users receive continuous or early updates and serve as an essential source of feedback, bugs, and experience across various lines of business and user expertise.
You can use these two models concurrently to provide comprehensive, effective, and efficient evaluation of incoming updates. Moving away from the IT-centric acceptance model and democratizing evaluation across your organization improves the speed and quality of the effort. If the remainder of your organization subscribes to Semi-Annual Enterprise Channel or Standard Release option (Microsoft 365 Apps and Microsoft 365 services, respectively), the updates evaluated in the test tenant, by IT and power users, will be ready to deploy with reduced friction.
Internally, Microsoft employs these change evaluation strategies in a program called Microsoft Elite. The Microsoft Elite program is beyond dogfood and serves as our early adopter program. Our employees test features and specific scenarios; they provide quality feedback that improves programs and features before they're released to our customers and colleagues. You can use the release cadences and change strategy described earlier to mimic this program in your own environment.
Microsoft change plans, policies, and procedures
The Microsoft change mission is to enable rapid delivery, improve productivity, and delight customers with new applications and features while minimizing friction and disruption. Managing change is an evergreen program that delivers continuous innovation to users. Changes are necessary to keep products and services secure, up to date, and working as expected. Although innovation is key to delivering user value, we recognize that impactful changes to your environment may create legal, regulatory, security, or compliance risks. To reduce potential risk, Microsoft commits to:
- Following defined change control policies and procedures.
- Notifying you of impactful changes at least 30 days in advance.
- Listening to community feedback to improve the change release process.
Change management plan
The Microsoft 365 Change Management Plan is essential for enabling customers to plan for and manage change. Figure 8 illustrates the pillars of the plan.
The Microsoft Change Management Plan outlines three change phases and recommended customer actions that are associated with each action. Table 3 summarizes the three change phases.
Table 3: Microsoft Change Management Plan phases
|Phase 1: Before change||Phase 2: During change||Phase 3: After change|
|Identify a change center of excellence or cloud governance board with representatives from each line of defense in the business.
Validate existing change policies and create policies as required.
|Consider the change’s impact to your organization and your users.||Provide feedback about an upcoming service change by using the Message center communication.|
|Know about the change:
- Check Product Roadmap
- Check the Message center in the Microsoft 365 admin center
|Stay aware of workflow changes to help deployment teams and increase user productivity through proactive adoption and change management.||Review factors that drive successful deployment in your organization and adapt to reduce impact and increase awareness and efficiency.|
|Provide feedback about an upcoming service change by using the Message center communication.||Ensure that the stakeholders and contacts section of your customer profile is complete and provided to your Technical Account Manager (TAM).||Changes are designed to benefit customers. Help your users be aware of changes, understand them, and get the most out of them.|
Regardless of change strategy, ensuring that your users understand the latest changes is important for successful adoption. The criticality of adoption and change management continues to trend upward as Microsoft and the greater market move toward continuous change.
Change classification and notification
Microsoft classifies changes to assist customers in understanding and planning appropriately for each update. Major updates should be a key focus for customers evaluating and analyzing upcoming changes. If a change is classified as a major update, Microsoft commits to notifying customers at least 30 days before implementation when an action may be required.
To be classified as a major update, changes must meet one or more of the following criteria:
- Changes to daily productivity such as inbox, meetings delegations, sharing, and access.
- Changes to the themes, web parts, and other components that may impact customizations.
- Increases or decreases to visible capacity such as storage, number of rules, items, or durations.
- Rebranding that might cause user confusion or result in help desk/collateral changes or URL changes.
- A new service or application.
- Changes requiring an admin action (exclusive of prevent/fix).
- Changes to where data is stored (might impact regulatory or legal requirements).
The Message center in the Microsoft 365 admin center is your primary source of change information. Message center marks changes of high importance (major updates) with a red exclamation mark (❗) - this helps them to be easy to identify and track during various stages of release. Figure 9 shows a screenshot.
Messages are identified in the right-side column above by one of three categories:
Prevent or fix issues: These messages inform you of known issues that are affecting your organization and might require you to take action to avoid disruptions in service. Prevent or fix issues are different than Service health messages because they prompt you to be proactive to avoid issues.
Plan for change: These messages inform you of changes to Microsoft 365 that may require you to act to avoid disruptions in service. For example, you'll be notified about upcoming changes to system requirements and about features that will be removed. To keep the service running normally, we strive to provide at least 30 days' notice of any change that requires an admin to act.
Stay informed: This is where we notify you about new or updated features that we're turning on in your organization. The features are usually announced first in the Microsoft 365 Roadmap. Stay informed messages might also let you know about planned maintenance in accordance with our Service Level Agreement. Planned maintenance might result in down time, where you or your users can't access Microsoft 365, a specific feature, or a service like email or OneDrive for Business. For more information, see the Message center documentation.
Both "prevent or fix issues" and "plan for change" messages might require action from admins. To help you prioritize and plan, the Act by column contains the date by which action is required.
"To help you prioritize and plan, the Act by column contains the date by which action is required."
The Message center admin user interface is one way to obtain service change information. Using the Office 365 Service Communications API, you can build automated solutions to query the following relevant data:
- Get Services: Returns the list of services to which you're subscribed.
- Get Current Status: Returns a real-time view of current and ongoing services incidents.
- Get Historical Status: Get a historical view of service incidents.
- Get Messages: Find incident and Message center communications, which include change information.
We commit to continuously improving our change classification and notification processes. Our efforts to predict which changes may impact customer environments are the basis of our change classifications, but these predictions are limited without input from our community of customers. The customer feedback we receive through various channels enhances our ability to respond to change concerns in an agile, democratized, customer-centric manner.
Sources of information and feedback channels
To ensure broad dissemination and accessibility, Microsoft publishes change information in various locations. The Message center in the Microsoft 365 Admin Portal is a key source of tenant-specific information, but you should pay attention to the entire suite of sources to ensure that you're holistically informed in a timely manner.
Sources of change information
The Microsoft 365 Roadmap is a public website that relays the status of products that are in development, rolling out, or launched. You can view the status of each feature or workload, search using tags, and confirm release dates from a single portal. As illustrated in Figure 10, you can use filtering to easily find services or features of interest.
Message center weekly digest
Your admins can use the Message center weekly digest to review Message center communications via email in a digestible, easily shared, summary format. The digest was created in response to customer feedback and demonstrates the innovative ways the Microsoft community effects change in our processes. Customers can opt out of digest emails by changing settings in the admin portal. Figure 11 shows an example of the digest.
The Microsoft 365 admin mobile app has more than 80 features that help you manage your company when you’re on the go. The app is available for download in the Apple App Store and Google Play. Using the mobile app, you can perform common tasks like user password reset, add users to a group, and review change notifications and alerts. We recommend enabling mobile alerts, so that you stay apprised of updates the moment they're released. Figure 12 shows a screenshot of the mobile app.
To take advantage of the Microsoft 365 admin mobile app features, download the app.
Other change information resources
In addition to changing our services, we also update Microsoft 365 clients. Both sets of changes follow our Change Management Plan and are communicated in the Message center. For documentation about client changes, see:
- These update channels mirror those described earlier in the Change Management Plan.
- Client release notes provide a wealth of information about the latest security updates, update sizes, and updates for different platforms (for example, Mac).
- Read about the latest releases and features in our blog posts, which are separate from our formal documentation.
- Review Microsoft 365 services and features to learn more about existing features that you can leverage to improve security and productivity.
Outside of formal documentation, we recommend customers join the Microsoft Tech Community to keep a pulse on how changes are managed and deployed by industry peers. The Microsoft Tech Community is an active, raw, real-time source of information. We actively monitor the platform to better understand how changes are being received.
Microsoft establishes a virtuous feedback loop between customers and our products. There are several examples of changes that have been rolled back or modified because of feedback submitted by customers. Customers can provide feedback through multiple channels:
- Microsoft 365 admin portal
- Message center
- Microsoft Tech Community
Microsoft 365 admin portal
At the bottom-right of each page in the admin portal, customers can provide feedback by clicking the Give feedback button, which is illustrated in Figure 13.
The Give feedback button also exists in the Message center so that you can provide feedback about incoming changes or other notifications without switching portal pages. The feedback from the Message center goes directly to the owning engineering and marketing teams within Microsoft. Microsoft owners receive a daily report of new feedback that has been submitted. If your feedback is regarding a specific change or message, be sure to include the Message center ID so that the feedback can be correctly correlated. In Figure 14, you can see the Give feedback button in the lower-right of the Message center.
The Message center also supports Like and Dislike buttons, as shown in Figure 15, for each message. Using these, you can quickly provide feedback. We aggregate this feedback and use it to understand general customer reception of our recent changes.
This community serves both as a source of change information from your peers and as a forum for providing feedback. We monitor the Tech Community forums for valuable feedback and use the information to influence internal decisions. Figure 16 shows a list of feedback forums.
1: Net Promoter Score (NPS) is an industry calculation that measures user preferences for a product or service. NPS is calculated by accounting for users who detract, support, or are neutral toward the target of the examination. Subtracting the percentage of Detractors from the percentage of Promoters yields the Net Promoter Score, which can range from a low of -100 (if every customer is a Detractor) to a high of 100 (if every customer is a Promoter).
2: With a 1.5 margin of error.
3: Microsoft provides controls over the diagnostic data collected from user endpoints, as described in Use policy settings to manage privacy controls for Microsoft 365 Apps for enterprise. To the extent that Microsoft is a processor or subprocessor of Personal Data subject to the GDPR, the GDPR Terms in the Microsoft Online Services Data Protection Addendum Attachment 3 govern that processing and the parties also agree to the following terms in this sub-section (“Processing of Personal Data; GDPR”).
4: For guidance about opting in to these service release options, see Set up the Standard or Targeted release options.
5: If your entire organization is on a semi-annual cadence, you might find that the six-month period between feature updates causes your clients to fall out of compliance with regulatory requirements or internal policies as you wait for such an extended period between releases.
6: This consists of a selected subset of non-security updates for Semi-Annual Enterprise Channel.
7: For Configuration Manager to be able to manage Office updates, an Office COM object needs to be enabled on the computer where Office is installed. The Office COM object takes commands from Configuration Manager to download and install client updates. You can enable the Office COM object by using client policy in Configuration Manager, Group Policy, or the Office Deployment Tool. If you use more than one method, the Group Policy setting determines the final configuration.