Introducing the Modern Service Management for Office 365 blog series! These insights and best practices are brought to you by Carroll Moon, Senior Architect for Modern Service Management.
Regardless of the size of the organization, the move to Office 365 brings changes from a Service Management perspective. In a small environment where there are no dedicated IT staff members, there is still someone who gets the phone call when the boss’ email is down. In enterprise environments, the Service Management aspects are broader, deeper, and more important because IT must integrate Office 365 Workloads into their existing IT Portfolio (e.g. moving Exchange to the cloud is one of hundreds of IT Services in the enterprise Service Catalog) and into their existing IT Operations strategy (e.g. monitoring). At one extreme, enterprise customers worry that their tooling, workflows, and IT Pro roles must drastically change. At the other extreme, customers do not focus on the Service Management aspects of integrating the cloud with their existing catalog and operational model. Given the importance of these Service Management topics, Microsoft is beginning a blog series to help simplify the discussion for customers of all sizes, but particularly for enterprise customers.
Service Management should be a focus for all customers, but especially for enterprise customers who need to have the outputs of Office 365’s processes become the inputs into their existing ITSM processes and tools
For Office 365, there are five major areas—four that are foundational/core and one that is more business focused:
In the coming months, we will publish additional blog posts for Office 365 Service Management in all of these areas. Each blog post in this series will provide the core framing for how to think about the topic and the integration of Office 365 into the existing IT Service Management Portfolio. The series will focus on integration with Office 365 APIs where appropriate, and in some cases, we will post sample scripts to help your business integrate with less effort. Each blog post will also layer in existing and announced features that support each framed scenario. And in the future, as we release new Service Management features, we plan to blog about them within the framing that is outlined here. In other words, the blog posts will not always map one-to-one to the bullets above, but we will always reference back to this simple model. The goal of this blog series is to continue to add layers onto the Service Management story for our customers while keeping the integration story as simple as possible.
The next post in this series will land in April and it will focus on Monitoring and Major Incident Management. In the meantime, get ahead by reading our “ITIL for Cloud and DevOps: Monitoring” blog series.
Senior Architect for Modern Service Management
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.