Open NicolasKheirallah opened 4 years ago
Same behavior here too
Same behavior here too, any updates on this?
I see the same problem. 3.22.2006.0 worked for me but not 3.25.2009.1
Who at microsoft do I need to contact about this? I have a premium subscription with them and I keep getting bounced around between the SharePoint team, Azure Team, and Office 365 team.
PnP is a community project,I recommend you downgrade to 3.22.2006 for now
At 3.22.2006 my provisioning template is not set correctly. It works locally at 3.24 and 23.25 - but these versions won't go on Azure. Does anybody know if there's going to be an update soon?
Last one I was able to run in Azure is: 3.23.2007.0
I just tried this for the first time today and got the same error...I am running 3.26.2010.0. Is there any fix other than running a lower version of PnP?
If you have a question and are not reporting a bug, please go to:
https://github.com/pnp/pnp-powershell/discussions
Reporting an Issue or Missing Feature
Bug in newest PnP
Expected behavior
Tested a older version (3.17) and it worked as it should, 3.25 doesn't
Actual behavior
Steps to reproduce behavior
1.Create an azure function for powershell 2.Create a folder called module under your function using kudu: "D:\home\site\wwwroot\ApplyPnPProvisioningTemplate\modules"
Which version of the PnP-PowerShell Cmdlets are you ?
What is the version of the Cmdlet module you are running?
(you can retrieve this by executing
Get-Module -Name sharepointpnppowershell* -ListAvailable
)How did you install the PnP-PowerShell Cmdlets?