The case of Get-SPOSite

If you use both the PnP cmdlets and the Microsoft Office 365 Management cmdlets, you might have noticed that both have an Get-SPOSite cmdlet. And those conflict. There are a few ways around that problem, but they are cumbersome. To resolve this, basically the only way is either them (Microsoft) or us (PnP) rename the Get-SPOSite cmdlet. So we sat down with the PnP Core team, looked at a few scenarios, and we came up with what I describe a bit below in this post. Continue reading

Changes to the PnP PowerShell Cmdlets Naming

Following the changes in the PnP Core Library naming, the PnP PowerShell Cmdlets have been renamed too. Besides that, we added another version of the PowerShell module too. Internal naming We renamed the internal project name and the namespaces from OfficeDevPnP to SharePointPnP Old OfficeDevPnP.PowerShell.Commands OfficeDevPnP.PowerShell.Tests OfficeDevPnP.PowerShell.Setup OfficeDevPnP.PowerShell.CmdletHelpAttributes OfficeDevPnP.PowerShell.CmdletHelpGenerator New SharePointPnP.PowerShell.Commands SharePointPnP.PowerShell.Tests SharePointPnP.PowerShell.Setup (deprecated/removed in the latest master branch) SharePointPnP.PowerShell.CmdletHelpAttributes SharePointPnP.PowerShell.CmdletHelpGenerator Packages on the PowerShell Gallery We also renamed the packages on the PowerShell Gallery to a more intuitive naming (we think): Continue reading

Multilingual Provisioning Templates with the Office 365 Developer Patterns and Practices Provisioning Engine

Somehow I don’t seem to be able to come up with short titles for my posts :-) A much requested feature was the ability to create a multi-language provisioning template. It turned out that the implementation of that wasn’t actually that complex, we had much of the plumbing already in place in the engine. The main question we had to ask ourselves was: how do we specify the various values for each language? Continue reading

Using an extensibility provider with the PnP Provisioning Engine

When you use the provisioning engine of the PnP Core project, you can provide an extensibility provider in your XML file. In order to use the Apply-SPOProvisioningTemplate cmdlet with an XML file that contains such a reference, it is important that you also load the assembly, otherwise the engine will fail to instantiate your provider and as a result, the provider will not be executed. An extensibility provider is nothing but a simple class: Continue reading

Getting started with the Office 365 Developer Patterns and Practices PowerShell Cmdlets

Update 2020-08-17: Updated post to reflect latest state Update 2018-03-14: Updated post to reflect latest state Update 2015-08-25: Updated links Update 2015-08-06: If you want to see the cmdlets in action, please check out this video on Channel 9. The Microsoft 365 PnP Powershell Cmdlets are a set of cmdlets specifically designed to provision and modify artifacts in Microsoft 365. In this way they differ a bit from the Microsoft SharePoint Online Management Shell provided by Microsoft which are mainly focused on administrative task towards SharePoint Online. Continue reading

Managing Document Sets with the OfficeDev PnP PowerShell cmdlets

I just released a couple of new cmdlets to manage document sets in SharePoint. While at the time of writing these cmdlets are not available in the master branch yet, you can still decide to download the dev branch from the GitHub site and compile that one. The cmdlets will be available in the master branch in the August release. The cmdlets work as described below: There are 4 cmdlets: Continue reading