You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* update open source PNP includes to include URLs to project home
* add includes for open source pnp projects
- added include for PnP Provisioning Engine
- added include for PnP Sites Core
* add open source support disclaimer for PnP PowerShell
* add open source support disclaimer for O365 CLI
* add open source disclaimer for PnP Provisioning Framework, Schema & Engine
* add open source disclaimer for PnPJS
* Address build report errors
* add open source disclaimer
- add disclaimer to ALM APIs for PnP CSOM
* add includes for open source pnp projects
- added include for PnP Provisioning Engine
- added include for PnP Sites Core
* add open source support disclaimer for PnP PowerShell
* add open source support disclaimer for O365 CLI
* update ALM API
- fix broken submission
Co-authored-by: Vesa Juvonen <[email protected]>
Copy file name to clipboardExpand all lines: docs/declarative-customization/site-design-o365cli.md
+2-3Lines changed: 2 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -1,16 +1,15 @@
1
1
---
2
2
title: SharePoint site design - Office 365 CLI commands
3
3
description: Use the Office 365 CLI to create, retrieve, and remove site designs and site scripts.
4
-
ms.date: 10/23/2018
4
+
ms.date: 06/05/2020
5
5
localization_priority: Priority
6
6
---
7
7
8
8
# SharePoint site design: Office 365 CLI commands
9
9
10
10
Use the Office 365 CLI to create, retrieve, update, and remove site designs and site scripts to new and existing modern site collections from any platform.
11
11
12
-
> [!NOTE]
13
-
> Office 365 CLI is an open-source tool with active community providing support for it. There is no SLA for the open-source tool support from Microsoft.
Copy file name to clipboardExpand all lines: docs/declarative-customization/site-design-pnp-provisioning.md
+21-22Lines changed: 21 additions & 22 deletions
Original file line number
Diff line number
Diff line change
@@ -1,13 +1,13 @@
1
1
---
2
2
title: Calling the PnP provisioning engine from a site script
3
3
description: Build a complete SharePoint site design using the PnP provisioning engine
4
-
ms.date: 03/24/2020
4
+
ms.date: 06/05/2020
5
5
localization_priority: Priority
6
6
---
7
7
8
8
# Calling the PnP provisioning engine from a site script
9
9
10
-
Site designs offer a great way to standardize the look and feel of your site collections. However, you can't do some things with site designs, like add a footer to every page. You can use the PnP provisioning engine to create a template that you can use to provision an Application Customizer to a site. This Application Customizer can then update your page design, for example to register a footer on every page.
10
+
Site designs offer a great way to standardize the look and feel of your site collections. However, you can't do some things with site designs, like add a footer to every page. You can use the PnP provisioning engine to create a template that you can use to provision an Application Customizer to a site. This Application Customizer can then update your page design, for example to register a footer on every page.
11
11
12
12
This article describes how to create a site design that applies a PnP provisioning template to a site. The template will add an Application Customizer to render a footer.
13
13
@@ -24,28 +24,27 @@ The steps in this article use the following components:
24
24
25
25
You'll use these components to trigger the PnP provisioning code after you create the site and apply the site design.
26
26
27
-
> [!NOTE]
28
-
> PnP Provisioning Engine is an open-source solution with active community providing support for it. There is no SLA for the open-source tool support from Microsoft.
To set up app-only access, you need to have two different pages on your tenant—one on the regular site, and the other on your SharePoint administration site.
33
32
34
-
1. Go to following URL in your tenant: `https://[yourtenant].sharepoint.com/_layouts/15/appregnew.aspx` (you can go to any site, but for now pick the root site).
33
+
1. Go to following URL in your tenant: `https://[yourtenant].sharepoint.com/_layouts/15/appregnew.aspx` (you can go to any site, but for now pick the root site).
35
34
36
-
2. Next to the **Client Id** and **Client Secret** fields, choose the **Generate** button.
35
+
2. Next to the **Client Id** and **Client Secret** fields, choose the **Generate** button.
37
36
38
-
3. Enter a title for your app, such as **Site Provisioning**.
37
+
3. Enter a title for your app, such as **Site Provisioning**.
39
38
40
-
4. In the **App Domain** box, enter **localhost**.
39
+
4. In the **App Domain** box, enter **localhost**.
41
40
42
-
5. In the **Redirect URI** box, enter **https://localhost**.
41
+
5. In the **Redirect URI** box, enter **https://localhost**.
43
42
44
43
45
44
46
-
6. Choose **Create**.
45
+
6. Choose **Create**.
47
46
48
-
7. Copy the values for **Client Id** and **Client Secret** because you will need them later.
47
+
7. Copy the values for **Client Id** and **Client Secret** because you will need them later.
49
48
50
49
<br/>
51
50
@@ -67,7 +66,7 @@ Next, trust the app, so that it has the appropriate access to your tenant:
67
66
68
67
## Create the Azure Queue storage
69
68
70
-
In this section, you will use Azure Queue storage to receive messages from Power Automate. Every time a message shows up in the Queue storage, an Azure function is triggered to run a PowerShell script.
69
+
In this section, you will use Azure Queue storage to receive messages from Power Automate. Every time a message shows up in the Queue storage, an Azure function is triggered to run a PowerShell script.
71
70
72
71
To set up the Azure Queue storage:
73
72
@@ -83,7 +82,7 @@ To set up the Azure Queue storage:
83
82
84
83
## Create the flow
85
84
86
-
To put a message in the queue, you need to create a flow.
85
+
To put a message in the queue, you need to create a flow.
87
86
88
87
1. Go to the [Power Automate](https://flow.microsoft.com) site, sign in, and choose **Create from Blank** at the top of the page.
89
88
1. Choose **Search hundreds of connectors and triggers** to select your trigger.
@@ -110,7 +109,7 @@ To put a message in the queue, you need to create a flow.
110
109
}
111
110
}
112
111
}
113
-
```
112
+
```
114
113
115
114
1. Select **+ New Step** and choose **Add an action**.
116
115
1. Search for **Azure Queues** and select **Azure Queues - Put a message on a queue**.
@@ -186,14 +185,14 @@ Copy the following provisioning template XML to a new file and save the file as
186
185
187
186
188
187
189
-
1. Name the function **ApplyPnPProvisioningTemplate**.
188
+
1. Name the function **ApplyPnPProvisioningTemplate**.
190
189
1. Enter the name of the queue you created earlier.
191
-
1. Choose **Create**. An editor where you can enter PowerShell cmdlets will open.
190
+
1. Choose **Create**. An editor where you can enter PowerShell cmdlets will open.
192
191
193
192
Next, you'll upload the PnP PowerShell module so that you can use it in the Azure Function.
194
193
195
194
> [!NOTE]
196
-
> The Storage account must be in the same region as of Azure Function App, because the resources that talk to one another should be co-located in the same region. This is a requirement for Azure Functions.
195
+
> The Storage account must be in the same region as of Azure Function App, because the resources that talk to one another should be co-located in the same region. This is a requirement for Azure Functions.
197
196
198
197
## Upload the PnP PowerShell module for your Azure Function
199
198
@@ -205,7 +204,7 @@ You'll need to download the PnP PowerShell module so that you can upload it for
@@ -313,7 +312,7 @@ The **Add-SPOSiteDesign** cmdlet associates the site design with the team site.
313
312
314
313
## Verify the results
315
314
316
-
After you created your Azure Queue storage, you created the app ID for app-only access, the Azure Function, and the site design. You then triggered the Power Automate flow from the site design.
315
+
After you created your Azure Queue storage, you created the app ID for app-only access, the Azure Function, and the site design. You then triggered the Power Automate flow from the site design.
317
316
318
317
To test the results, create a new site. In your SharePoint tenant, select **SharePoint** > **Create Site** > **Team Site**. Your new site design should show up as a design option. Notice that the site design is applied after the site is created. If you configured it correctly, your flow will be triggered. You can check the run history of the flow to verify that it ran correctly. Note that the footer might not show up immediately; if you don't see it, wait a minute and reload your site to check again.
Copy file name to clipboardExpand all lines: docs/declarative-customization/site-design-pnppowershell.md
+2-3Lines changed: 2 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -1,16 +1,15 @@
1
1
---
2
2
title: SharePoint site design - PnP PowerShell cmdlets
3
3
description: Use PnP PowerShell cmdlets to create, retrieve, and remove site designs and site scripts.
4
-
ms.date: 01/18/2019
4
+
ms.date: 06/05/2020
5
5
localization_priority: Priority
6
6
---
7
7
8
8
# SharePoint site design: PnP PowerShell cmdlets
9
9
10
10
Use PnP PowerShell cmdlets to create, retrieve, update, and remove site designs and site scripts to new and existing modern site collections.
11
11
12
-
> [!NOTE]
13
-
> PnP PowerShell is an open-source solution with active community providing support for it. There is no SLA for the open-source tool support from Microsoft.
First, we will create the marketing site that will serve as a hub site that other sites can associate with. The intent is that any sites that are marketing-oriented will be part of the hub site. This applies common navigation and branding across the associated sites, enables team members to search across all the sites associated with the single hub site, and takes advantage of other hub site features.
Copy file name to clipboardExpand all lines: docs/features/hub-site/hub-site-o365cli.md
+2-3Lines changed: 2 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -1,16 +1,15 @@
1
1
---
2
2
title: Office 365 CLI commands for SharePoint hub sites
3
3
description: Use Office 365 CLI to create and manage SharePoint hub sites.
4
-
ms.date: 6/18/2019
4
+
ms.date: 06/05/2020
5
5
localization_priority: Priority
6
6
---
7
7
8
8
# Office 365 CLI commands for SharePoint hub sites
9
9
10
10
Use the Office 365 CLI commands to create and manage SharePoint hub sites.
11
11
12
-
> [!NOTE]
13
-
> Office 365 CLI is an open-source tool with active community providing support for it. There is no SLA for the open-source tool support from Microsoft.
Copy file name to clipboardExpand all lines: docs/features/site-footer.md
+2Lines changed: 2 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -34,6 +34,8 @@ Set-PnPFooter -Enabled:$false
34
34
> [!NOTE]
35
35
> Above PowerShell scripts assumes that you have already installed PnP PowerShell cmdlets for your environment and you are not using multi-factor authentication. You can install PnP PowerShell cmdlets to your computer by opening PowerShell console in administrative mode and executing following command: `Install-Module SharePointPnPPowerShellOnline`. If you are using multi-factor authentication, you can enable MFA login by updating the `Connect-PnPOnline` line as follows: `Connect-PnPOnline -Url "<SiteURL>" -UseWebLogin`.
Site owner can control the footer visibility using the **Change the look** functionality of the site, which exposes the different user interface configuration options.
0 commit comments