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! OzBest Practice for Site Collection Storage Size
One of my organization's business units is examining the feasibility of SharePoint Online as an alternative solution for photo storage. While I know that SharePoint does a great job of document storage and provides some decent tools for managing images, I'm uncertain how best to architect their solution from a storage limit standpoint. We estimate this business organization would need ~2 TB storage for their images, and while we have well more than that available in our tenant, I'm unsure what will happen if we hit a single site collection with that much content. Is there a known limit or threshold for a site collection's storage limit, or are there consequences where that much data would noticeably affect performance? I anticipate creating a site collection to manage this content by itself, but if there are known issues should storage reach a certain threshold, I can accept spreading this out over a few site collections but would want to know that before I recommend anything to our business unit. I'm aware of the recommendations for SharePoint 2013, but am unsure these limitations would still apply.Office 365: Add or remove account fron SharePoint Site collection administrators
When you have to manage Office 365 tenant, it could be useful to set or remove user account (or group) as Site collection administrator. The basic case for that request is for Support delegation or Technical service account This small PowerShell script can be used and adapt if required to do that change in the 2 ways (add or remove): [string]$username = "YourAdminAccount@yourtenant.onmicrosoft.com" [string]$PwdTXTPath = "C:\SECUREDPWDFOLDER\ExportedPWD-$($username).txt" [string]$CompteouGroupeAADavecGUIDO365= "c:0-.f|rolemanager|s-1-5-21-1575671886-733387139-3803724931-1933543" [string]$CompteIdentifiantSP201X= "i:0#.f|membership|myUserLogin@mydomain.com" [string]$Compteavecsimplelogin= "loginAdmin@yourtenant.onmicrosoft.com" function Load-DLLandAssemblies { [string]$defaultDLLPath = "" # Load assemblies to PowerShell session $defaultDLLPath = "C:\Program Files\SharePoint Online Management Shell\Microsoft.Online.SharePoint.PowerShell\Microsoft.SharePoint.Client.dll" [System.Reflection.Assembly]::LoadFile($defaultDLLPath) $defaultDLLPath = "C:\Program Files\SharePoint Online Management Shell\Microsoft.Online.SharePoint.PowerShell\Microsoft.SharePoint.Client.Runtime.dll" [System.Reflection.Assembly]::LoadFile($defaultDLLPath) $defaultDLLPath = "C:\Program Files\SharePoint Online Management Shell\Microsoft.Online.SharePoint.PowerShell\Microsoft.Online.SharePoint.Client.Tenant.dll" [System.Reflection.Assembly]::LoadFile($defaultDLLPath) } function ChangeUserStatusForSiteCollectionAdmin { Param( [string]$SiteCollURL, [string]$LoginToSet, [boolean]$ToSiteCollAdminorNot ) if ($ToSiteCollAdminorNot) { Set-SPOUser -Site $SiteCollURL -LoginName $LoginToSet -IsSiteCollectionAdmin $ToSiteCollAdminorNot; Write-Host " >>>>>>>>", $LoginToSet, " - is now part of Site Collection Collection admins" -foregroundcolor green; } else { try { $CheckUserList = $Null $CheckUserList = Get-SPOUser -Site $SiteCollURL -LoginName $LoginToSet Set-SPOUser -Site $SiteCollURL -LoginName $CheckUserList.LoginName -IsSiteCollectionAdmin $ToSiteCollAdminorNot; Write-Host " >>>>>>>>", $CheckUserList.LoginName, " - Set to Site Collection Collection admin: ", $ToSiteCollAdminorNot -foregroundcolor green; } catch { write-host " >>>> $LoginToSet ---Error info: $($_.Exception.Message)" -foregroundcolor red } } } cls Write-Host " ---------------------------------------------- " Load-DLLandAssemblies Write-Host " ---------------------------------------------- " $secureStringPwd = ConvertTo-SecureString -string (Get-Content $PwdTXTPath) $adminCreds = New-Object System.Management.Automation.PSCredential $username, $secureStringPwd Connect-SPOService –Url “https://yourtenant-admin.sharepoint.com” -credential $adminCreds -ErrorAction SilentlyContinue -ErrorVariable Err #Retrieve all site collection infos $sitesInfo = Get-SPOSite -Template "STS#0" -Limit ALL | Sort-Object -Property url | Select * [int]$i = 1; foreach ($site in $sitesInfo) { Write-Host "SiteColl Number:", $i, "- of:", $sitesInfo.Count; $i += 1; Write-Host "SPO Site collection:", $site.Url, "- Title:", $site.Title ChangeUserStatusForSiteCollectionAdmin $site.Url $Compteavecsimplelogin $false Remove-SPOUser -Site $site.Url -LoginName $Compteavecsimplelogin; #If you want to remove all reference to the account ChangeUserStatusForSiteCollectionAdmin $site.Url $CompteIdentifiantSP201X $false Remove-SPOUser -Site $site.Url -LoginName $CompteIdentifiantSP201X; #If you want to remove all reference to the account ChangeUserStatusForSiteCollectionAdmin $site.Url $CompteouGroupeAADavecGUIDO365 $true } You can use or adap it depending of your local need. Be careful with the "Group sites" which are not only SharePoint sites, but more a mix between many other components from Office 365 (SP, AAD, Exchange, ...), so that script is clearly not enough in that case. Fabrice Romelard [MVP] Reference source: https://techcommunity.microsoft.com/t5/SharePoint/Office-365-Add-accounts-into-the-Site-collection-administrators/m-p/58186#M5615 Original post in french: Office 365: Ajouter ou retirer des comptes utilisateurs des administrateurs de collections de site via PowerShell
