When it's time to deploy Office 365 ProPlus, you'll need to think about how you're going to deploy, how you're going to manage updates, and whether or not you need or want to deploy Office files from a local share on your network or from the cloud. Once you've completed your assessments and inventories, you can begin the deployment. What we'll touch on in this lesson are the basic high-level steps for deploying Office 365 ProPlus. 

To deploy Office 365 ProPlus, you'll need to choose what deployment tool you're going to use. You'll also need to decide if you want to install the Office files directly from the cloud, or if you'd rather install them from a local share on your network. 

Next, you'll need to determine how you wish to manage updates. You'll need to decide if you're going to have your client devices automatically updated. If so, you'll need to settle on a tool to use and whether or not you wish to install the updates right from the cloud or from a local share on the network. 

You have three primary choices when deciding how to manage updates. You can update automatically from the Office CDN, you can manage updates with Configuration Manager, or you can manage updates with the Office Deployment Tool. Microsoft recommends that you update client devices automatically from the Office CDN. 

Next, you'll need to choose your update channels. You'll need to decide how frequently your users should receive feature updates to their Office applications. You can choose the semi-annual channel, the targeted semi-annual channel, or the monthly channel. We covered each of these in detail earlier on, so I'm not going to force you to hear about them all over again. Just understand that these are your options. 

Once you've decided on your update channels, you'll want to define your source files. Essentially, what this means, is that you'll need to create an installation package of these source files that will be used to install Office. As you would expect, the source files for the 32-bit version of Office are different from the 64-bit version. So you may need to create multiple installation packages. 

Next, you'll need to define your deployment groups. You'll need to do this because, when you deploy Office, you have the option of installing different versions for different groups of users. The hardware that each user group uses, as well as their languages and other details, will largely determine what your deployment groups look like. 

Before rolling out Office 365 ProPlus, you'll need to come up with a plan for upgrading existing versions of Office that already exist in your environment. Microsoft recommends removing any existing versions of Office but also supports installing Office 365 Proplus alongside the most recent previous version of the Office suite. Your business needs will dictate which option you choose. However, if you do need to run two versions of Office on the same computer, what you should do is keep only the early apps that are necessary and have a plan to completely upgrade to Office 365 ProPlus at the earliest possible time. In cases where you are using shared computers, such as those cases where you're leveraging BDI, you'll need to enable shared computer activation when you deploy Office 365 ProPlus. By enabling shared computer activation, any users that have been assigned an Office 365 ProPlus license can log on to the shared computer and use the Office 365 ProPlus apps. 

Lastly, before you begin your deployment of Office 365 ProPlus, make sure that you've defined and documented your exit criteria. For example, be sure that you've documented your deployment methodology and how you plan to manage updates. Be sure that you've determined what your update channels will be and what and where your source files are. You should also ensure that you've defined your deployment groups and that you've properly planned for upgrades and for how you're going to handle shared computers. 

Once you've completed all these tasks, you can begin the rollout of Office 365 ProPlus.