Microsoft Office Tutorials and References
In Depth Information
Chapter 7: Automating Office 365 management using Orchestrator
Automating Office 365 management
using Orchestrator
System Center 2012 Orchestrator .................. 325
Orchestrator overview and concepts ............... 326
Installing Orchestrator ............................ 330
Creating a new runbook for Office 365
email accounts .................................. 346
System Center 2012 Orchestrator
In this chapter, you will learn how to use System Center Orchestrator to automate
endto-end processes, reduce operational costs, improve IT efficiency, and cross organization
Orchestrator is a software solution that provides workflow automation for almost any
business process, known in the industry as IT process automation (ITPA). Forward-thinking
companies embrace automation to provide services and accomplish more with less. The
support for Microsoft Office 365 automation with Orchestrator is not limited to your
organization's data center, but also expands automation used to complete any cloud services.
When deciding to automate a business process, the rule-of-thumb to remember is return
on investment (ROI). A business process, such as manually creating an Office 365 email
account, might add 15 to 20 minutes a day. That process might be a good candidate
for automation and provides a great ROI. A new Office 365 account creation time using
Orchestrator is less than five minutes. In addition, a human resources (HR) task worker can
start the process without IT staff involvement. In this chapter, we focus on automating the
creation of Office 365 email accounts, but you can use Orchestrator to automate many
other administrative tasks, such as password changes or providing user information such as
a location or a name.
Orchestrator is designed for the enterprise because it uses the cloud model to deliver
automation for services so business application owners have greater flexibility and freedom to
grow their industries. Orchestrator includes the Runbook Designer component, which is
used to create and publish Orchestrator runbooks. The Runbook Server is the component
responsible for "running" the runbooks. The Management Server component is used to
import Integration Packs (IPs). After an IP is imported, the Management Server makes the
IP available to the Runbook Server.
Search JabSto ::

Custom Search