ADFS 3.0 deploy Office 365 - pt. 7


Once the ADFS 3.0 infrastructure has been installed and configured, the last step of the procedure is the Office 365 deployment.

Two ways can be used to deploy Office 365 products: directly from the Office 365 portal or from a local network share.


Blog series

ADFS 3.0 setup UPN suffix for Office 365 SSO - pt. 1
ADFS 3.0 SSL certificate signing request - pt. 2
ADFS 3.0 install ADFS Server - pt. 3
ADFS 3.0 install WAP Server - pt. 4
ADFS 3.0 federating Office 365 - pt. 5
ADFS 3.0 install Directory Sync tool - pt. 6
ADFS 3.0 deploy Office 365 - pt. 7


Office 365 portal

The default method for an Office 365 user to install an Office product on a computer is to use the Office 365 portal.

From your favorite browser type the URL to access the Office 365 portal.


Enter the user's credentials (the user will be redirected to the federated login page) then click on Sign in button.


In the right side of the main screen select Options > Office 365 settings or click on Install link under Install Office on more devices item.


From the Software section, select the Language if required then click on Install button.


Office 365 is being installed in the computer.



Deploy Click-to-Run

To deploy Office products and languages to users from a local network share you need to use the Office Deployment Tool for Click-to-Run.

Administrators can run the Office Deployment Tool to perform the following tasks:

  • Download mode: download Click-to-Run installation source for Office 365 products and languages to an on premise location.
  • Configure mode: configure and install Click-to-Run for Office 365 products and languages.


Download mode

To download the source file, you need three components:

  • Office Deployment Tool
  • A batch file
  • An .xml configuration file




Create a .bat batch file with the following commands:

.\setup.exe /download o365_office_eng.xml



.xml configuration file

Create a .xml configuration file to specify language, edition and products to download.


<Add SourcePath="" OfficeClientEdition="32" >

   <Product ID="O365BusinessRetail">
      <Language ID="en-us" />
      <ExcludeApp ID="Publisher" />

   <Product ID="LyncRetail">
      <Language ID="en-us" />


<Updates Enabled="TRUE" UpdatePath="" />
<Display Level="Full" AcceptEULA="TRUE" />
<Logging Level="Standard" Path="%temp%" />
<!-- <Property Name="AUTOACTIVATE" Value="1" /> -->


Products IDs that are supported by the Microsoft Office Deployment Tool for Click-to-Run can be found here.

To save the Office 365 source files in a shared storage, add in the SourcePath="" field the path to the share.

<Add SourcePath="\\path\share" OfficeClientEdition="32" >

i.e. <Add SourcePath="\\lab-nas01\office365\" OfficeClientEdition="32" >

To get Office 365 updates from a shared network location, add in the UpdatePath="" field the path to the share.

<Updates Enabled="TRUE" UpdatePath=\\path\share />

i.e. <Updates Enabled="TRUE" UpdatePath="\\lab-nas01\office365\updates" />

Running the download.bat file, the source files are stored in a new Office folder created in the path specified in the SourcePath="" field.



Configure mode

To install Office 365, you need three components:

  • Office Deployment Tool
  • A batch file
  • An .xml configuration file



Create a .bat batch file with the following commands:

.\setup.exe /configure o365_office_eng.xml



.xml configuration file

The .xml file to use to deploy Office 365 to the clients can be the same used to download the products.

Running the install.bat file, the specified products are deployed to the clients.


The installation takes some minutes to complete and it is performed in the background.


ADFS 3.0 and Office 365 infrastructure setup is now complete.



  1. moncef rihani 20/11/2016