-
Notifications
You must be signed in to change notification settings - Fork 0
Getting Started
This guide will walk you through the basics of using the Microsoft 365 Apps Deployment Toolkit to deploy Microsoft 365 Apps in your environment.
Before using the toolkit, ensure you have:
- Windows 10 1809 or later (64-bit) on the deployment target
- Administrator privileges on the target machine
- Internet connectivity for downloading Office files
- At least 4GB of free disk space on the target machine
- PowerShell 5.1 or later (included by default in Windows 10)
- Proper Microsoft 365 licensing for the applications you plan to deploy
- Download the latest release from the GitHub releases page
- Extract the ZIP file to a location of your choice (e.g.,
C:\M365-Apps-Deployment-Toolkit)
Alternatively, clone the repository using Git:
git clone https://github.com/sargeschultz11/M365-Apps-Deployment-Toolkit.git
The toolkit can be deployed in several ways:
- Manual Deployment - Direct execution on client machines
- RMM Deployment - Through Remote Monitoring and Management tools
- Intune Deployment - Via Microsoft Intune
- SCCM Deployment - Via Microsoft Configuration Manager
Choose the method that best fits your environment.
The toolkit includes ready-to-use XML configuration files in the config folder:
-
install-office365.xml- Standard Microsoft 365 Apps installation -
install-visio.xml- Microsoft Visio installation -
install-project.xml- Microsoft Project installation
You can customize these files to:
- Change the update channel
- Adjust language settings
- Exclude specific applications
- Modify other deployment options
See the Configuration Guide for detailed information.
Here are the most common installation commands:
.\Install-Microsoft365Apps.ps1 -ConfigXMLPath "config\install-office365.xml".\Install-Microsoft365Apps.ps1 -ConfigXMLPath "config\install-office365.xml" -RemoveConsumerOffice.\Install-Microsoft365Apps.ps1 -ConfigXMLPath "config\install-office365.xml" -Force.\Install-Microsoft365Apps.ps1 -ConfigXMLPath "config\install-office365.xml" -UninstallExisting.\Install-Microsoft365Apps.ps1 -ConfigXMLPath "config\install-visio.xml".\Install-Microsoft365Apps.ps1 -ConfigXMLPath "config\install-project.xml"When you run the toolkit, it performs these steps automatically:
-
Checks for existing Office installations (unless
-Forceis specified) -
Removes consumer versions (if
-RemoveConsumerOfficeis specified) - Downloads the Office Deployment Tool from Microsoft
- Extracts the tool to a temporary directory
- Downloads the necessary Office installation files based on your XML configuration
- Installs Microsoft 365 Apps with your specified settings
- Verifies the installation was successful
- Cleans up temporary files
The entire process is logged to %TEMP%\Microsoft365Install_*.log for troubleshooting.
The script supports multiple parameters that control its behavior:
| Parameter | Description |
|---|---|
-ConfigXMLPath |
Path to the XML configuration file (default: config\install-office365.xml) |
-RemoveConsumerOffice |
Detects and removes pre-installed consumer Office versions |
-Force |
Forces installation even if Office is already detected |
-UninstallExisting |
Uninstalls existing Office products before installation |
-SkipIfInstalled |
Skips installation if Office is already installed |
-DetectOnly |
Only detects Office products without installing |
-Uninstall |
Uninstalls Office products using the specified XML |
-Restart |
Restarts the computer after successful installation |
-OfficeInstallDownloadPath |
Specifies a custom download location for temporary files |
For a complete reference, see the Script Parameters page.
After successful installation, you might want to:
- Verify the installation by checking installed applications
- Configure update policies through Group Policy or Intune
- Activate Microsoft 365 Apps using your organization's licensing method
- Configure default application settings as needed
If you encounter problems during deployment, check these common issues:
- Script execution fails: Ensure you're running PowerShell as Administrator
- Installation timeout: Ensure stable internet connectivity
-
Existing Office conflicts: Use
-RemoveConsumerOfficeor-UninstallExisting - Detection issues: Check the logs for details on what the script detected
For more detailed troubleshooting help, see the Troubleshooting Guide.
The toolkit creates detailed logs in the Windows temp directory:
- Main log:
%TEMP%\Microsoft365Install_YYYYMMDD_HHMMSS.log - Office Deployment Tool logs:
%TEMP%\SaraOfficeClickToRun_*.log
Review these logs if you encounter any issues with the installation.
If you need assistance:
- Check the Troubleshooting Guide
- Review the Issues page on GitHub
- Open a new issue if your problem hasn't been addressed
- Consider contributing to the project if you develop a solution
The M365 Apps Deployment Toolkit is an open-source project that welcomes contributions. See the Contributing Guidelines for information on how to help improve the toolkit.