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
Copy file name to clipboardExpand all lines: articles/iot-dps/how-to-use-custom-allocation-policies.md
+14-2Lines changed: 14 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -113,12 +113,18 @@ In this section, you create an Azure function that implements your custom alloca
113
113
> [!NOTE]
114
114
> 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**.
115
115
116
+

117
+
116
118
4. On the **Summary** page, select **Create** to create the function app. Deployment may take several minutes. When it completes, select **Go to resource**.
117
119
118
120
5. On the left-hand pane of the **Overview** page, select **+** next to **Functions** to add a new function.
119
121
122
+

123
+
120
124
6. On **Azure Functions for .NET - getting started**, for the **CHOOSE A DEPLOYMENT ENVIRONMENT** step, select the **In-portal** tile, then select **Continue**.
121
125
126
+

127
+
122
128
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.
123
129
124
130
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
137
143
</Project>
138
144
```
139
145
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.
0 commit comments