With these prerequisites in place simply download and install the cmdlets from Microsoft: Once installed open the Share Point Online Management Shell by clicking . Unlike with Share Point on-premises, this is not a snap-in but a module, which is basically the new, better way of loading cmdlets.

In the preceding example we are using the “STS#0” template, however, there are other templates available for our use and we can discover them using the Get-SPOWeb Template cmdlet, as shown below: Name Title Locale Id Compatibility Level —- —– ——– —————— STS#0 Team Site 1033 15 BLOG#0 Blog 1033 15 BDR#0 Document Center 1033 15 DEV#0 Developer Site 1033 15 DOCMARKETPLACESITE#0 Academic Library 1033 15 OFFILE#1 Records Center 1033 15 EHS#1 Team Site – Share Point Onl…

1033 15 BICenter Site#0 Business Intelligence Center 1033 15 SRCHCEN#0 Enterprise Search Center 1033 15 BLANKINTERNETCONTAINER#0 Publishing Portal 1033 15 ENTERWIKI#0 Enterprise Wiki 1033 15 PROJECTSITE#0 Project Site 1033 15 COMMUNITY#0 Community Site 1033 15 COMMUNITYPORTAL#0 Community Portal 1033 15 SRCHCENTERLITE#0 Basic Search Center 1033 15 visprus#0 Visio Process Repository 1033 15 Once your Site Collection has been created you may wish to grant users access to the Site Collection.

To see the list of Site Collections associated with a subscription or to see the details for a specific Site Collection use the Get-SPOSite cmdlet. If this optional switch parameter is omitted then the SPOSite objects that will be returned will only have their properties partially set.

Now you might think that this is in order to reduce the traffic between the server and the client, however, all the properties are still sent over the wire, they simply have default values for everything other than a couple core properties (so I would assume the only performance improvement would be in the query on the server).

The capabilities are somewhat limited in that our abilities are limited to manipulating Site Collections, but it’s a start.

In this article I’ll walk through the available cmdlets and detail some examples of how to use them.First you may want to create a new Share Point group (if an appropriate one is not already present) and then you may want to add users to that group (or an existing one).To accomplish these tasks you use the New-SPOSite Group cmdlet and the Add-SPOUser cmdlet, respectively.You can see the difference in the values that are returned by looking at a Site Collection with and without the details: Locale Id : 1033 Lock State : Unlock Owner : s-1-5-21-3176901541-3072848581-1985638908-189897 Storage Quota : 1000 Storage Quota Warning Level : 0 Resource Quota : 300 Resource Quota Warning Level : 255 Template : STS#0 Title : Contoso Team Site Allow Self Service Upgrade : True When we’re ready to create a Site Collection we can use the New-SPOSite cmdlet.This cmdlet is very similar to the New-SPSite cmdlet that we have for on-premises deployments.The following shows the syntax for the cmdlet: Note that the cmdlet also takes in a -No Wait parameter; this parameter tells the cmdlet to return immediately and not wait for the creation of the Site Collection to complete.