Skip to content

Commit a8a933c

Browse files
Merge pull request SharePoint#5991 from ngcatalin/ngcatalin/issue5960
Updated "PnP Provisioning Tenant Templates" page - "Create the Azure Function" section
2 parents a9ab758 + 6d60ce7 commit a8a933c

File tree

4 files changed

+20
-4
lines changed

4 files changed

+20
-4
lines changed
Loading
Loading
Loading

docs/declarative-customization/site-design-pnp-provisioning.md

Lines changed: 20 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Calling the PnP provisioning engine from a site script
33
description: Build a complete SharePoint site design using the PnP provisioning engine
4-
ms.date: 06/05/2020
4+
ms.date: 07/04/2020
55
localization_priority: Priority
66
---
77

@@ -172,12 +172,28 @@ Copy the following provisioning template XML to a new file and save the file as
172172
1. Go to the [Azure Portal](https://portal.azure.com).
173173
1. Choose **+ Create a resource**.
174174
1. Search for **Function App** and create a new function app. In the **Storage** field, select **Use existing**, and select the storage account that you created earlier. Set the other values as required.
175-
1. Currently Function apps are created with the V2 runtime which does not support PowerShell functions. Change the runtime of the function app to V1 by navigating selecting **Platform features**, **Function app settings** and change the Runtime version from **~2** to **~1**.
176-
1. Create a new function: **Functions** > **New function**.
175+
1. Within the Function App select **Configuration** > **Function runtime settings** and change the runtime version from **~3** to **~1**.
176+
177+
![Screenshot of the Azure portal with the Function runtime settings screen highlighted](images/pnpprovisioning-runtime-settings.png)
178+
179+
> [!NOTE]
180+
> Function Apps based on the runtime version ~3 or ~2 only support PowerShell Core as programming language. At this moment, PnP PowerShell cmdlets can be only executed under PowerShell (and not on PowerShell Core).
181+
>
182+
> First, to make available Powershell at the level of the Function App, the runtime version has to be set to **~1**.
183+
>
184+
> Secondly, PowerShell can be only activated from the **classic experience** of the Azure Portal, by enabling the **Experimental Language Support**, at the level of the Function App.
185+
>
186+
> Read more about [Azure Functions runtime versions.](https://www.microsoft.com/download/details.aspx?id=35588)
187+
188+
1. Temporarly switch the Azure Function App's user interface to the **classic experience** from the current experience. Select **Overview** in the left-hand navigation and select **Switch to Classic experience** as shown in the following figure.
189+
190+
![Screenshot of the Azure portal with the Function runtime settings screen highlighted](images/pnpprovisioning-switch-classic-experience.png)
191+
192+
1. Create a new Azure Function **Functions** > **New function**:
177193

178194
![Screenshot of the Azure portal with the New function option highlighted](images/pnpprovisioning-create-function.png)
179195

180-
1. Turn on experimental language support:
196+
1. Enable **Experimental Language Support**:
181197

182198
![Screenshot of the Azure portal with the Experimental Language Support switch highlighted](images/pnpprovisioning-experimental-features.png)
183199

0 commit comments

Comments
 (0)