Forum Discussion
Curious- Are you allowing all users to create O365 groups or limiting self-service creation?
I had planned for it to leave it open, but recently changed my mind because of "sprawl". The fault is our own and not really an issue at the moment, because my users aren't yet fully familiar with Office 365 and are mostly using Exchange Online at the moment.
I ran a trial for a couple of weeks just to see what would happen, as as expected without training groups ended up for duplicate matters, users not remembering guidelines and not using expected prefixes.
In the last month or so, I've finally had the time to further refine the provisionin process and have manged to create an almost proper usage guildlines page in SharePoint where all requirements are explained and I have created a few default site classifications (all powershell by the way). Additionally I've created a request template in our ITSM solution for the purpose of request a group provisioning. This template includes additional information on usage and also asks for specific metadata about the wanted group.
Once our rollout is complete (sometime this year), I expect to relax the provisioning process again, and allow it for a limited group (my so called Office 365 Champions).
I wish we were able to automatically create different prefixes for different kinds of groups (projects, organizational groups, and so on - one size does not fit us at the moment).
Is there any specific documentation you can share on the provisioning process and best practices for rolling out groups.
Ivan54 wrote:I had planned for it to leave it open, but recently changed my mind because of "sprawl". The fault is our own and not really an issue at the moment, because my users aren't yet fully familiar with Office 365 and are mostly using Exchange Online at the moment.
I ran a trial for a couple of weeks just to see what would happen, as as expected without training groups ended up for duplicate matters, users not remembering guidelines and not using expected prefixes.
In the last month or so, I've finally had the time to further refine the provisionin process and have manged to create an almost proper usage guildlines page in SharePoint where all requirements are explained and I have created a few default site classifications (all powershell by the way). Additionally I've created a request template in our ITSM solution for the purpose of request a group provisioning. This template includes additional information on usage and also asks for specific metadata about the wanted group.
Once our rollout is complete (sometime this year), I expect to relax the provisioning process again, and allow it for a limited group (my so called Office 365 Champions).
I wish we were able to automatically create different prefixes for different kinds of groups (projects, organizational groups, and so on - one size does not fit us at the moment).
- Nothing special, as the provisioning process is just on the organizational side of things. I have groups for departments, department-overarching groups and project groups at the moment.
Exchang Mailboxes are already in EXO. Document are being transferred currently (within the year) to SPO to all the respective groups.
AS for the group creation. I just let my users fill out a specific request form and trigger multiple tasks for us (IT). Things like namechecks, create group, edit settings (time zones, languages, ...). That's it, after that I transfer group ownership to the requester.
Aside from all of that, I have a small group that gets regular Office 365 Updates from me directly - also through an Office 365 Group.