On July 26, 2018, Microsoft announced updates to self-service site creation in SharePoint Online. It's an exciting news for organizations that have been prevented from easily evolving to newer modern team site experiences for several reasons, including:
Legacy Team Sites Built using a subsite infrastructure . Until the changes announced in this update, organizations were only allowed to create modern sites as top-level site collections. With this announcement, Microsoft introduced the possibility of having a modern subsite .
The inability to create a modern team site without also creating an Office 365 group . Some organizations have restricted the ability to create Office 365 groups as part of their governance plan. Previously, if creating Office 365 groups was disabled for a set of users, these users could only create "classic" SharePoint team sites. With this update, organizations can allow users to create modern team sites from the new site creation link on SharePoint, even if they are not able to create an Office Group. 365. The created site is a new type of SharePoint team site that looks like a classic team site (no shared inbox or group calendar) but with a home page , modern web pages and components. Since I can not think of a better term, I will call it a team site supported by a non-group .
Here are some things to note about the implications of these updates and what
Team sites not benefiting from a group do not accrue benefits associated with Office groups 365
There is no inbox or shared e-mail address for members of the team's site.
There is no group calendar for the team powered by Outlook. There will probably be a list of modern events, but the list of events is a SharePoint calendar, not an Outlook calendar. Site members and owners should be able to create events such as on a communication site, but team members will have to add each event individually to their personal calendar. There will be no way to invite the entire team to the list of events in the site of the team "out of group"
There is no planner card configured for the team.
does not have the ability to associate the team's site with a Microsoft team to benefit from the team discussion and connectors. Each Microsoft team gets a "group-supported" team site – so it would not make sense to connect this type of team site to a team via a connector because the team already has a workplace. ] Team sites supported by non-groups use SharePoint groups for permissions
This may be a good thing since group and team site permissions may be different – and this can be be confusing to explain to users. For example, you can add a member to the team's site without adding them to the group, which means the member can view the documents but can not use any of the other services associated with the group. There are special use cases where this makes sense, but in general, I always try to remind group owners to add people to the group, not just the website. team associated to the Group
<img src = "https://images.idgesg.net/images/article/2018/07/add-group-members-from-team-site-100765850-large.jpg" border = "0" alt = "] Susan Hanley
From a team-supported team site, you can add a member to the group or just the site of # Team
Non-group team sites may be a sub-site or a collection site
Many organizations have a history of subsites as part of their site infrastructure. 39 team – for example, a parent portfolio team site with subsites for each individual project. The best way to create this scenario in the modern SharePoint infrastructure is to create a hub site and associate the associated team sites. As Mark Kashman has said on Twitter, "Hub forward from under". But there may be cases of use where for some reason it is just not practical. For example, if the team should easily share a search list or content type. With this announcement, it is now possible to create a modern subsite. This update allows organizations to modernize their families of inherited nested team sites.
I do not like the idea of creating a subsite of a team site originally created with an Office 365 group. I guess that will be possible, but the likelihood of disturbing permissions seems quite high, and if you're already comfortable with the concept of Office 365 groups to empower teams, that does not seem like a good idea. It makes more sense to have a modern team subsite if the parent site is a non-group supported team site.
The team sites supported by non-groups are and not only the communication sites with left navigation
Although it may seem that create a modern team site without Office 365 Group is the same as creating a communication site – this is not the case. Communication sites can not be "grouped". In other words, they are designed for communication, not for collaboration. The future of a communication site is only that – communication. A non-group-supported team site has a future state that can take advantage of the 365 Office groups. In other words, it's a way to access the Office 365 groups.
Why? Because it's the easiest way to sustain your team collaboration scenarios. Site collections broke long-term subsites. Sub-sites may have a place today but as hubs mature and allow more scenarios (especially metadata sharing), subsites should become less useful
if you can. It's not because you can create a modern subsite that you should . As the Microsoft blog says, "subsites leave little room for flexibility and changes in projects and teams." For me, subsites have almost always started with 99 problems !! Hub sites are designed to create site families like sub-sites with a big difference: Hub sites are designed to change, and subsites are designed to stick.
Love the ability to set the language of the site. This is a great feature of the ad – you can now select the desired language for the team site when you create the site. It's a hugely exciting ad for global organizations.
Organizations have choices – and with great choices come great responsibilities. It is always important to think about governance before going too far in the Office 365 deployment curve. This means thinking about naming conventions, self-service, and taking charge new owners of sites, etc. I'm doing my best to keep my SharePoint and Office 365 Governance Decisions document up-to-date as new ads are released. It will be the subject of a complete redesign this summer. If you follow me on Twitter, you will see the announcement once the updates are complete. In the meantime, I am constantly refining the margins.
