search

pnp / PnP-Sites-Core

Microsoft 365 Dev PnP Core component (.NET) targeted for increasing developer productivity with CSOM based solutions.
Other
415 stars 642 forks source link

Office 365 Groups provisioning: Access Denied after provisioning Content Types #1189

Open PaoloPia opened 7 years ago

PaoloPia commented 7 years ago

Please refer to this item: https://github.com/SharePoint/PnP-Provisioning-Schema/issues/183

maxali commented 6 years ago

Same problem here.

Apply-PnPProvisioningTemplate : Access denied. You do not have permission to perform this action or access this resource.

Apply-PnPProvisioningTemplate -Path ./Template.xml throws error even after template is applied to site.

Problem occurs only on Modern Sites (O36 Groups).

ghost commented 6 years ago

Hi - I'm seeing the same issue. I've attached my template. My template performs the following: 1) Remove all web parts from home page except for Document Library web part 2) Creates 2 site content types and adds one of them to the Documents library 3) Includes 2 folders and 2 sample documents in the Document library 4) Replaces SiteIcon.jpg and SiteIcon.png in Site Assets with updated logos

RIMProjectTemplate.zip

dharm-4 commented 5 years ago

Hi,

I am facing same issue during Apply-PnpProvisioningTemplate. After so long still there is no reply or solution for this error.

Steps to reproduce this error, Create SubSite - (Site1 in RootSite) Create New Columns in Site1 (at subsite level not root web level) Create Custom Content Types (same subsite level) Get-PnpProvisioningTemplate for Site1 Create New SubSite - (Site2) Apply-PnpProvisioningtemplate in Site2

it will create one Content Type in new subsite and then throw the same error "Access Denied".

Looking forward for your response for this issue.