Skip to content

Commit 411bff2

Browse files
committed
added images for create function/function app
1 parent 318dab4 commit 411bff2

8 files changed

+14
-2
lines changed

articles/iot-dps/how-to-use-custom-allocation-policies.md

Lines changed: 14 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -113,12 +113,18 @@ In this section, you create an Azure function that implements your custom alloca
113113
> [!NOTE]
114114
> By default, **Application Insights** is enabled. If you want to, you can disable it by selecting the **Monitoring** tab and selecting **No** for **Enable Application Insights**.
115115
116+
![Create an Azure Function App to host the custom allocation function](./media/how-to-use-custom-allocation-policies/create-function-app.png)
117+
116118
4. On the **Summary** page, select **Create** to create the function app. Deployment may take several minutes. When it completes, select **Go to resource**.
117119
118120
5. On the left-hand pane of the **Overview** page, select **+** next to **Functions** to add a new function.
119121
122+
![Add a function to the Function App](./media/how-to-use-custom-allocation-policies/create-function.png)
123+
120124
6. On **Azure Functions for .NET - getting started**, for the **CHOOSE A DEPLOYMENT ENVIRONMENT** step, select the **In-portal** tile, then select **Continue**.
121125
126+
![Select the portal development environment](./media/how-to-use-custom-allocation-policies/function-choose-environment.png)
127+
122128
7. On the next page, for the **CREATE A FUNCTION** step, select the **Webhook + API** tile, then select **Create**. A function named **HttpTrigger1** is created, and the portal displays the contents of the **run.csx** code file.
123129
124130
8. Reference required Nuget packages. To create the initial device twin, the custom allocation function uses classes that are defined in two Nuget packages that must be loaded into the hosting environment. With Azure Functions, Nuget packages are referenced using a function.host file. In this step, you save and upload a function.host file.
@@ -137,7 +143,13 @@ In this section, you create an Azure function that implements your custom alloca
137143
</Project>
138144
```
139145
140-
2. On the **HttpTrigger1** function, expand the **View Files** tab on the right side of the window. Select **Upload** and browse to the **function.proj** file you saved previously and select **Open** to upload the file.
146+
2. On the **HttpTrigger1** function, expand the **View Files** tab on the right side of the window.
147+
148+
![Open view files](./media/how-to-use-custom-allocation-policies/function-open-view-files.png)
149+
150+
3. Select **Upload** and browse to the **function.proj** file you saved previously and select **Open** to upload the file.
151+
152+
![Select upload file](./media/how-to-use-custom-allocation-policies/function-choose-upload-file.png)
141153
142154
9. Replace the code for the **HttpTrigger1** function with the following code and click **Save**:
143155
@@ -284,7 +296,7 @@ In this section, you'll create a new enrollment group that uses the custom alloc
284296
285297
1. Still on the [Azure portal](https://portal.azure.com), open your Device Provisioning Service instance.
286298
287-
2. Select the **Manage enrollments** tab, and then click the **Add enrollment group** button at the top of the page.
299+
2. Select **Manage enrollments** on the left pane, and then click the **Add enrollment group** button at the top of the page.
288300
289301
3. On **Add Enrollment Group**, enter the following information, and click the **Save** button.
290302
44.9 KB
Loading
11.1 KB
Loading
14.1 KB
Loading
38.1 KB
Loading
32.2 KB
Loading
4.29 KB
Loading
36.6 KB
Loading

0 commit comments

Comments
 (0)