Forum Discussion
Where to create an Office 365 group?
Myles Gallagher Per your requirements:
I am trying to build a system where a new Office 365 Group for a new project is created, a specific SharePoint site design/template is provisioned, and a Team is provisioned. Some other configurations are done using the site design script -> launch a flow feature.
The fastest way to have MS Teams, SharePoint and office365 group provision at the same will be through Teams. (GUI or Powershell). As they are not additional steps.
References:
- Powershell: https://blogs.technet.microsoft.com/skypehybridguy/2017/11/07/microsoft-teams-powershell-support/
- GUI: https://support.office.com/en-us/article/create-a-team-for-staff-in-microsoft-teams-314ac9d5-36a9-408e-8ae4-7ef20e9f1ddf
- FLOW: https://flow.microsoft.com/en-us/blog/microsoft-flow-in-microsoft-teams/ https://flow.microsoft.com/en-us/blog/microsoft-flow-in-microsoft-teams/
If you do it through SharePoint Online and then connect the site with a Team is an extra step. but would like to hear other opinions. Great question.
- does creating an Office 365 Group through Teams allow to edit the ALIAS of that group? SharePoint Home allows this, which makes the SharePoint URL and the e-mail address more readable.
When creating the group through AzureAD, the alias is pretty much a guid@domain.com.Hi Ivan
Creating an Office 365 Group through Teams doesn't allow you to edit the alias of the group today. This is because the expectation is that users who create groups in Teams tend to work in Teams instead of Outlook, so showing Outlook relevant properties like email address would make little sense.
I would say this would be OK if teams existing in isolation, but the big selling point for Microsoft is not the quality of the software, but rather the scope of the platform; the integration with all of the office software. While I agree Teams users should not really be bothered with email settings for setting up a chat based team, that's not really what they are setting up. They are setting up an Office 365 Group which is a massive concept that has interplay with almost every other service Microsoft has available. So whether they know it or not they are getting a SharePoint team site, a "shared mailbox", a planner plan etc.
If a company has defined customizations to each of these services that greatly enhances (and enables) their use towards a company goal, then we need to be able to deploy these customization when appropriate.Someone making a "team" call it "Project A" for a project that will only really use MS Teams, might be on another team (Group) "Project B" that was created in and primarily uses SharePoint. This person also uses outlook for communication because email isn't going anywhere.
The end result:
While this user is on SharePoint, they see their nice "Project B" site, but also this bare-bones, mostly useless other than for file sharing, "Project A" site that was auto-provisioned without any business process integrations.
While this user is in outlook they see their normal inbox, along with these "Group" inboxes that were auto-provisioned, potentially garbage, mail-addresses under "Groups".I am all for empowering users to initiate their collaboration environment. However, there needs to be a way to customize what that environment is at a global level. I want employees to be able to spin up SharePoint sites, Teams, Plans, etc but I want it to incorporate the tools and structure that make those environments useful within the context of our business (powerapps, flow, powerbi, sharepoint lists/documents/templates/teams bots the list goes on!!!).
The scope of Office Groups is too big to treat so carelessly.
- cfiessinger
Microsoft
Being able to edit the SMTP address is something we are working on, with a ETA in the summer, please stay tune.
