Get-PnPTenantTemplate: Fixing scope name generation

[heinrich-ulbricht]

Type

• Bug Fix
• New Feature
• Sample

Related Issues?

N/A

What is in this Pull Request ?

While using Get-PnPTenantTemplate to extract a team I noticed that the scope names are sometimes incorrect. The following things happened:

• the resource already contained the leading https:// resulting in a scope name starting with https://https://
• the resource ended with / causing the scope name to end with ///.default

Sample error:

@erwinvanhunen And I replaced the // with / so right before the .default is always only one /.

Hope this makes sense. For me this fixed my problems.

[erwinvanhunen]

Thank you! While this should have been fixed on engine level already, an extra check doesn't hurt as such.