Forum Discussion
Mark-Kashman
Microsoft
MicrosoftROLLING OUT: SharePoint Online team sites + Office 365 Groups & Pages
Today marks the beginning of bringing the full power of SharePoint to Office 365 Groups, with additional benefits to SharePoint Online all up! New and existing groups will get modern team sites, which come with an updated Home page, the ability to pin items within the new Quick links web part, and to see what's going on in the site via the new Activity web part.
These team sites within Office 365 Groups, and existing team sites throughout SharePoint Online, will also have the ability to create publishing pages - fast, easy to author pages that support rich multimedia content, and look great on mobile browsers and via the SharePoint mobile app. Get ready to communicate and share your ideas within SharePoint like never before.
Additionally, Microsoft will increase the site collection limit in SharePoint Online to "up to 25TB" (previously "up to 1TB); this will be refelcted in an update to the official "SharePoint Online boundaries and limits" support article.
Please review the associated blog on blogs.office.com, "New capabilities in SharePoint Online team sites including integration with Office 365 Groups" with numerous links to new and updated support.office.com articles.
Let us know what you think,
Mark
207 Replies
Is this feature available to anyone yet? I would really like to try it out in our first release developer tenant: https://ahsdev.sharepoint.com
To me it should be easier to get the updated features for modern team sites. I think it would be wise to follow the example of the Android beta program. https://www.google.com/android/beta When I opted into the Android beta program, immediately I got a push notification to update to the beta version of Android. It should be that easy for a developer/testing tenant to update to the latest SharePoint feature such as these new modern team sites.
A few years back we ran a project where the goal was to have one corporate intranet to avoid having information silos by closing down local solutions as well as making a clear distinction between Team Sites (work in progress and collaboration area for ongoing work with many contributors) and Publishing Pages (ready and quality assured information handled by one responsible editor arranged in a strict navigation hierarchy).
With this announcement the border between Team Sites and Publishing Pages is getting blurry. What's the thoughts from Microsoft and the rest of the community how to tackle information architecture, governance, etc. to avoid creating silos?
To my understanding this is positioned with a lot of freedom for the individual and each Group/Site owner can basically create their own local intranet which also might be restricted to a specific group of users.
So, what's your thoughts?
- Hi Karl,
Not true, nothing is changing the border in that regard, as all current teams sites also have the "site pages" library today. The only thing changing is the WYSIWYG Editor and the displaying (mobile friendly, and stuff) of these pages itself. Teamsites don't just magically become publishing portals. The chosen terminology (publishing pages) might not have been the best, that I agree upon.Maybe this "misunderstanding" can be avoided as soon as you present the roadmap for "real" publishing pages and portals. When can we expect news on this front? 1,5 year ago you guys invested in a lot of energy around Next Gen Portals. It really looked promising! Can we now look forward to a comeback for Next Gen Portals, but based on the Sharepoint Framework?
- Can we test the new modern pages in our first release developer tenant today?
I think it depends on where it's your tenant and how Microsoft is doing the rollout in terms of rollout speed
- Is there any way to check Microsoft rollout?
Being in Australia we're seem to often be last on the list :(
Also does it matter if first release is assign to a group only or should it be for the whole organisation?
- How about "the other way around"? Are we going to have the opportunity to connect existing Team Sites to an existing/new Office 365 group=
- I believe, as far I remember from my readigs of what Microsoft has published so far, the answer is Yes
- We would like to know about " Upgrade Project Online and SharePoint Online". Below are the Some question regarding this: We want to Upgrade our Subscription and need response for the following queries. 1. what is the Cost of incremental SP Storage 2. what is the Capacity a 250 user SP/PS system has compared to 100 user 3. Is there a way to extend PS CPU capacity (beyond storage) if found slow? 4. what is the Plan for Backup & Disaster Recovery for Project online. Kindly do suggest for above. Thanks & Regards, Prashant
- 1. 0.20 $/GB/ month
2. I don't understand what you mean...if you are talking about storage, simply apply the following formula: 1 TB + 500 MB x # Users in your tenant
3. I don't understad what you mean.
4. Microsoft makes a daily backup of your data each day...each backup is retained by Microsoft 14 days...just check SPO service descriptionHi,
1. I mean, if we are purchasing a subscription by default we are getting fro 100 users and binifits along with. If we want to updgraded our subscription from 100 users to 250 users, What extra benifit we will get from MS office 365 team.
3. If we found SharePoint online site or Project online site is slow, what option we will there for faster Performance.
Thanks
Thats great, but the storage upgrade to 25TB is applicable to all tenant existing? or only for new plans of O365 that i acquire?
- The likelihood of it only being available to new tenants is slim to none. Everyone will get it.
- A question for the people in the know. How will the new Group Sites handle permissions. Will we be able to set different permission levels on a library basis, like on a SharePoint site? Will we be able to use the Group Admin level in our permissions, sort of like Site Owners - Site Members - Site Visitors? Thanks!
Tejas MehtaSharePoint does provide the ability for Site Owners to specify different permissions on resources. Office 365 Groups promises a permission model whereby all group members have access to the group’s resources across workloads (e.g. conversations, files, notebook, etc.). To deliver consistency, SharePoint site collections associated with a Group will also follow this model. So, a group (site) owner can add new permission levels and assign to new users or groups on a resource, but would not be able to remove the permission levels assigned to the group’s owners or members. We are working on delivering a new permissions management UX that will allow for group (site) owners to change the group members’ permission level from Edit to Read-only (and vice versa) but you would not be able to remove the members from resources in the SharePoint site collection.
Having the ability to assign read-only access is a big deal in our case and I believe many others. As much we try to be more inclusive instead of exclusive, everyone having the same access doesn't always sit right. Often we say "teams" but within those teams are different roles, responsiblities and tasks. Sometimes that team isn't always about working together on every part but more about presenting final data/assets/reports/documents/etc to others. That collateral ultimately we want to surface through the teamsite/page itself.
I really think one of the biggest issues some of us struggle with is that Groups give us great tools for the "doing" and "working on it" modes and then teamsites let us finish everything off with the "presentation" piece. The issue is that we don't always want to expose the "working" pieces to everyone. Not everyone needs to see the cake being made in the bakery, or the discussions/disagreements/chaos in the background. Teamsites are like that glass window where the cake is shown. That's the struggle most of us have is that with Groups + Teamsites, now everyone can go into the back room.
- Mark-KashmanIt follows the membership management Office 365 Groups offers. AKA, Office 365 Groups, the list of members, provides the authentication mechanism for these team sites; not the site settings > people and groups of SharePoint.
Joe Fedorowicz Office 365 Groups was always based on SharePoint Site Collection (i.e. top level site with one library).
The integration now expands this site into a full-blown SharePoint site as we know it. Therefore, more site ownership controls such as permissions and create other business apps, etc.
Yep, but we are now adding "Group Managers" into the mix. Are they going to live in the "Site Owners" by default? or will they just be members with permissions on the "Group" level?
Mark-Kashman with respect to customizing the site URL mentioned in the comments of the blog post, this is not quite "vanity" per se, but a desire to keep the URLs tidy. Even when the sites are standalone and not in a site structure (where 256 path names make short URLs very important).
e.g. Team Name is Emerging Technologies and Social Collaboration
They may want the URL to be "emsc"
At least group URLs don't include @%20 in the URLs. That's a super (long-overdue) positive step for sure.
Great news. Could someone please clarify if and how the root SharePoint Site Collection (domain.sharepoint.com) will be affected by this, for example if its still untouched?
Will this also get group features?
- Mark-Kashman
Untouched, and we are working on a plan for bringing groups to existing team sites, and this would be optional.
- This is great, but will you have videos of the samples you show in your blog so we can actually pause and look at it. I was trying to show it to some users and we had to watch it cycle through 3 or 4 times to catch what was going on.
Looking forward to this feature. It really helps get rid of the confusion of Groups vs. SharePoint. I look at it as a way to integrate a lot of functionality together. - What about Yammer, which we have embedded in our team sites. I outline some alternatives: 1) Will Yammer replace the newsfeed as the out-of-the-box social feed in sites 2) Will a Yammer feed still be embeddable as today. 3) Will Yammer be a web part that we will have access to via the new publishing pages, or 4) Do you have any other kind of integration between sites and Yammer in mind?
- I'm also interested in understanding how Yammer will be positioned and impact to embed and feed.
- @Lillian and @Morten, it seems there is a web part for Yammer to make it easy to embed it on a modern page.
- I'm also interested in understanding how Yammer will be positioned and impact to embed and feed.
