Self-service creation of Office 365 Groups gives office workers a flexible way to collaborate and to structure their content any way they like. While self-service is great, companies have rules and regulations to follow, metadata which makes perfect sense to their domain, basically wants around how to govern their solutions. If not, we’re very much left at the file server anarchy. Fortunately Office 365 and Azure comes with a rich toolset, making it far superior to a file server.
In this hands-on session we will see how you can continue to offer self-service, but self-service with control. We will see how to set up a group template, and discuss some of the challenges around governing an Office 365 Group.
By taking control of how an Office 365 Group is created you can, by using Azure WebJobs, PnP commandlets and templates, and interspersed with Microsoft Graph, set up a solution tailoring multiple business needs – giving your office workers a better starting point than just the out of the box Office 365 Group.
Topics covered in this session:
- How do you deal with branding of Office 365 Groups – internal projects might have a different look as opposed to a Group dealing with customers
- Lifecycle management of an Office 365 Group
- Approval (using Microsoft Flow)
- Updates
- Closing and archiving
- Naming conventions
- Handling of Public vs. Private groups
- Invitation policies for external people
- Use of Office 365 Groups classification labels
- Setting up ADAL / MSAL apps for worker processes
- (Pre-create planner tasks upon Group creation)
- (Pre-creation of a OneNote structure upon Group creation)
