This repo is a collection of useful PowerShell scripts to make deploying Office 2016 and Office 365 ProPlus easier for IT Pros and administrators.

Read more about it here: Office Blogs

The software is licensed “as-is.” under the MIT License.

For more detailed documentation of each script, check the Wiki or the readme file in the corresponding folder

Tired of manually editing the Office Click-To-Run Configuration XML File? Try our online XML Editor.

Office Click-To-Run Configuration XML Editor

Check out PowerShell for Office 365 for advice on getting started, key scenarios and script samples.

##Questions and comments If you have any trouble running this sample, please log an issue.

This is high level plan for contributing and the structure that we have in place for pulling changes.

• There will be 3 main levels of branches: 1 master branch, 1 development branch, feature and bug branches
• Each powershell script will have its own branch and changes will be made at that level
  • The 3rd level naming conventions will be as follows - Feature-FeatureName or Bug-BugName
• Pull requests will be made from the feature branches into the development branch and a code review will be completed in the development branch
• Pull requests should only be made from the feature branch after the script is tested and useable
• After the code review is complete a pull request will be made from the development branch into the master branch
• Changes to scripts (new functionality or bug fix) should be done at the thrid level (feature branches) by cloning the development branch using the naming conventions above
• Requests for changes to scripts can be made by submitting an issue and using the appropriate tag
  • For additional features to an existing script, use the label "enhancement"
  • For bugs, use the label "bug"
  • All issues will be reviewed and prioritized each day as we work to add new scripts and improve existing ones