So to continue our series on Intune in the ConfigMgr world today im looking at Office 365 deployment via Intune.

As many of you may know we have two flavours of Microsoft Office, Microsoft Office 2016 and Microsoft Office 365. If you are not familiar with the differences have a look at this page What’s the difference between Office 365 and Office 2016?, if you work in a large enterprise you maybe using Microsoft Office 2016 as I do, its a simple licensing model and does not rely on assigning a license to the user. I can see this changing in the near future as we integrate more and more of our services with Azure, we already use SSO for various applications so it makes sense. Its worth noting that even ConfigMgr CB supports patching Office 365 installations.

Microsoft see a future where everything is cloud first so it’s worth looking at Intune and Office 365 sooner rather than later.

Office 365  and Intune

Its important to note this will only work if there is no office installation on the target computer. I may do another post on deploying Office 365 as a line of business app and clean up any previous installations.

Create Office 365 Mobile App
  1. Log onto the Azure Management Portal
  2. Click on Intune (if this option isn’t available, then go to More Services and add it as a favourite for later)
  3. Click on Mobile Apps
  4. Click add
  5. From the dropdown menu add Office 365 – Windows 10 

  6. Now you will need to click Configure App Suite, this will allow you to add or remove features as needed. In my environment we have licences for  Project Online and Visio Pro.

  7. Next is the App Suite Information, you will need to give it a suite name and description. You can add an information URL (could be an internal page) and Privacy URL.

  8. Up next is App Suite Settings, this is the most important. Set the version, montly update channel and if you use Shared Computer Activation.

  9. Now set a language, I have selected English but you could add Swedish and Finnish I suppose.

  10. Thats it you now have the Office 365 Suite ready to deploy.

Deploy Office 365 Suite
  1. Once you have the application configured and ready to go you need to create an Assignment. You will need to create a group before hand.

  2. If you look under Device Install Status you can see that the application is assigned but has not been installed yet.

  3. On my test VM you can see Microsoft Office Click to Run running in the task manager, also if you need to look at the logs they are located under C:\Windows\Temp 

  4. After a few minutes we can see all of the Office 365 products installed.
  5. If we look back in Azure we can see that that Office 365 is installed.

Using Office 365

One of the main reasons I like Office 365 is slick end user experience once the suite has been deployed its ready to go.

When you open it up the end user just has to click Accept and Start

When the user opens any application they are licenced and good to go.

Any questions, comment below or catch us on twitter.

Until next time.

Series Links

  1. Traditional Management vs Modern Management – Part 1  – Encryption
  2. Traditional Management vs Modern Management – Part 2 – Office 365
  3. Traditional Management vs Modern Management – Part 3 – AAD/Auto MDM Enrollment
  4. Traditional Management vs Modern Management – Part 4 – Windows AutoPilot
  5. Traditional Management vs Modern Management – Part 5 – Security

(653)

An Irish man living in London, after completing a BSc in Computer Science in 2005 he started working in the IT Industry. Currently Senior Systems Officer at London Metropolitan University managing Azure and several thousand endpoints across several campuses in London.

Technology focuses include SCCM, MDT, Azure, Office 365, Active Directory, Group Policy, Application Packaging, PowerShell, Virtualization and Automation.

There are no comments.

Leave a Reply