SharePoint sites vs. Site Collections - CONFUSED!
So, SharePoint sites vs. Site Collections has completely baffled me despite reading endless articles and watching many videos! As a very advanced end user, with very little admin. experience, I've recently been given the task of sorting out the existing O365 SharePoint sites / hierarchy in my new company *HURRAH*. However, I'm utterly confused! Here's what I know: All sites / sub-sites to date appear to have been setup in a single site collection (https://<mycompany>.sharepoint.com/) - I've checked this via SharePoint Admin Centre and SiteManager. All sites setup to previously appear to be 'old-style' team sites with 10 or so directly under the root (https://<mycompany>.sharepoint.com/<site name>/). There are then various levels of sub-site beneath these 10. When I go to the Office 365 home page (https://www.office.com/), click the SharePoint tile and then the '+ Create Site' button it unexpectedly appears to create a new Site Collection under https://<mycompany>.sharepoint.com/sites/<site name>/. If I go to the SharePoint Admin Centre and create a new site collection, it creates it under https://<mycompany>.sharepoint.com/sites/<site name>/. So, my questions are: When I go to O365 > SharePoint > '+ Create Site', is it creating a SharePoint Site Collection, just a Site or something else entirely (e.g. Site Collection with all the other new Groups functionality thrown in). If I'd like to create 3 'buckets' into which all new and existing content could be put, what should I be using (Site collections, Sites, Groups, something else ...)? The buckets I'd like are: Operations (for internal employee use only; with 3 subsites (e.g. Finance; HR; Marketing). Associates (for use by employees or external consultants who have been provided with an Office 365 account by my company; with no subsites). Projects (for sharing project documentation with external clients; with a separate site / subsite for each project). If I'd like to restructure all the existing sites (which are currently in a single site collection) so that they are in the 3 'buckets' above how do I best go about this? When I'm creating new 'sites', what should I be using?: Create Site option on SharePoint homepage. New > Site in SiteManager. Something else. I appreciate that this is a lot of questions, but I've done a lot of reading, watching videos and viewing webinars and I'm at a loss! Thanks in advance for any help you can provide! OzDepreciation of 'Shared with us' on Group Sites
In leu of the latest update to the document library on groups sites showing 'In channels' and 'In site library' sections, the 'Shared with us' menu item that allowed you to locate any resources shared with the group centrally has been removed. After contacting Microsoft support, they indicated that this feature is being depreciated. There has been no admin notifications, timeline, or indication of how users are expected to locate resources shared with the group from the group context. My question is what next? It cant be logical to just drop a feature that supported collaborative working without a viable alternative. The expectation can't be to direct people to Onedrive to find these in the share section there...it defeats the concept of group-centric working and going to one place to locate everything to do with that group.
Cannot provision SP modern site with Group programmatically - "Alias is already in use"
Hi, I'm building a solution that can provision O365 Groups with associated Modern Team Site and Teams. While trying to create some new Sites with Groups, sometimes the creation fails with the error message "The alias for the group already exists". Provisioning : Tried both using New-PnPSite from PnP PowerShell v2.28.1807.0 , as calling directly the REST API /_api/GroupSiteManager/CreateGroupEx with the same result (error) Payload: {"displayName":"TestPosh2", "alias":"13015", "isPublic":false, "optionalParams":{"Description":"","CreationOptions":{"results":[],"Classification":""}}} Response: {"error":{"code":"-2147024713, Microsoft.SharePoint.SPException","message":{"lang":"nl-NL","value":"De alias voor de groep bestaat al."}}} There isn't any visible existing Alias created in the tenant with that ID. To verify this I did check - Exchange Admin Center - Get-UnifiedGroup (Exchange) - Get-PnPUnifiedGroup - /_api/GroupSiteManager/GetValidSiteUrlFromAlias?alias='13015' They all return no matching data, the last one returns an OK status code with the available URL for site: http://tenant.sharepoint.com/sites/13015 How can I further see whether this alias can be in use, or successfully use it for the new site?
Use modern team sites and communication sites without Exchange online mailbox
Hey everybody, We are planning to use sharepoint online for Collaboration within our Company. In order to keep things simple and easy to use for the users we plan to use the modern Team sites and modern Communication sites. On first sight everything's cool. But together with the teamsite an o365 Group is created. This isn't a problem as long as the users have Exchange online license assigned. But in our situation this isn't the case - we haven't rolled out EXO to our users. We have configured Exchange hybrid and also configured Groups for hybrid according to this tn https://technet.microsoft.com/en-us/library/mt668829(v=exchg.150).aspx, but have no user mailboxes online yet. As a consequence in the Team site there are multiple links and controls that point into o365 Group in EXO (e.g. to manage users, or to see the conversation or to check mails from this Group). The problem I'm facing right now is that users will run into error Messages all the time as soon as they follow one of these default links or controls. Do you have an idea if the modern team site can be created without o365 Group in the Background or to hide controls that point to o365group management in EXO? Really appreciate your comments! Philipp
