Applying Template: you need to connect to the target page not admin site

[ceitwitt]

While following the instruction to install pathways,

Connect-PnPOnline https://<tenant>-admin.sharepoint.com/ -Interactive

Invoke-PnPTenantTemplate -Path .\your-template-file.pnp -Parameters @{"SiteTitle"="<Title-of-your-target-site>";"SiteUrl"="/sites/<URL-of-your-target-site>"}

I got the response:

WARNING: The source site from which the template was generated had a base template ID value of SITEPAGEPUBLISHING#0, while the current target site has a base template ID value of TENANTADMIN#0. This could cause potential issues while applying the template.
Invoke-PnPSiteTemplate: Object reference not set to an instance of an object.

---

And documentation should have connecting as well to before invoke template

Connect-PnPOnline https://<tenant>.sharepoint.com/sites/<URL-of-your-target-site> -Interactive
right?

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: 25076df9-4f54-9a7b-6449-3cd696c66a42
• Version Independent ID: 25076df9-4f54-9a7b-6449-3cd696c66a42
• Content: Applying PnP Templates to SharePoint Sites
• Content Source: docs/solution-guidance/applying-pnp-templates.md
• Service: sharepoint-online
• GitHub Login: @VesaJuvonen
• Microsoft Alias: vesaj

[mkm17]

Hi @ceitwitt, It looks like the issue is caused by the reason you mentioned. Running the Invoke-PnPSiteTemplate command on an admin site connection (with site template ID TENANTADMIN#0) may cause an error because it is not the same site template ID as SITEPAGEPUBLISHING#0.

In the PnP PowerShell documentation, there is no information indicating that Invoke-PnPSiteTemplate requires a connection to the SP admin site (unlike in the case of Invoke-PnPTenantTemplate).

This part of the documentation should be updated. Thank you for pointing it out.

[Amey-MSFT]

Hello @ceitwitt,
Thank you for bringing this issue to our attention. Could you please confirm if the issue still persists for you?

[Amey-MSFT]

We are closing this issue for now. If the problem persists, feel free to reopen it or open a new one.