This is a small update to the Office 365 Groups report PowerShell script that makes reporting on new, modified, and deleted Office 365 Groups easy. It includes several bug fixes and functionality improvements. If you haven't already got the script, grab it from the TechNet Script Gallery or GitHub and extract it to your computer. If you're already using the script, just extract the new files over the top of your existing files, and then make a new configuration XML file from the sample provided so that you get the new features included.
- SMTP Parameters are now accepted, so you can specify email settings in the command line to override what's in the XML configuration file.
- UnifiedGroups.xml is now separated per tenant. This allows you to run the report for one or more tenants from the same directory, simply by using different credentials, and the history files for each tenant will be kept separate.
- Previous copies of the UnifiedGroups-*.xml file are now retained in a \history sub-folder. The default retention is 10 copies, and this can be modified by changing the value of HistoryItemsToKeep in the configuration file.
- Updates will only be saved to disk if the email is successfully sent. This reduces the chance of any group changes slipping through the cracks.
- On first run, the script now makes the user aware that it has no historical data and that all groups will be reported as “new”.
- Bug causing groups with multiple owners to always appear modified is fixed. Thanks to Roger-at-GT on GitHub for raising and helping to resolve this bug.
Questions and feedback are welcome in the comments below. If you encounter a bug please let use know in the comments, or by raising an issue on GitHub.
Chris is a solution architect living in Melbourne, Australia, specializing in Office 365, Amazon/Microsoft public cloud, identity management, and security.