Skip to content

Commit f2cd715

Browse files
committed
Clarify
1 parent 69975ab commit f2cd715

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

articles/iot-dps/concepts-custom-allocation.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ The following sections provide more detail about the custom allocation request a
4040

4141
## Manage function keys
4242

43-
Custom allocation policies use function keys to authenticate calls to Azure Functions. The behavior of key management differs based on whether you configure the custom allocation policy through the Azure portal or programmatically.
43+
Custom allocation policies use function keys to authenticate calls to Azure Functions where the authorization level is set to `Function`. The behavior of key management differs based on whether you configure the custom allocation policy through the Azure portal or programmatically.
4444

4545
### Function keys in the portal
4646

@@ -56,6 +56,8 @@ When you create an enrollment programmatically using the DPS API, you need to ma
5656

5757
Before you create the individual or group enrollment, retrieve the function key from your function. For more information, see [Get your function access keys](../azure-functions/function-keys-how-to.md#get-your-function-access-keys). Then, include the function key in the **webhookUrl** field of the **CustomAllocationDefinition**.
5858

59+
For more information, see [Azure Functions HTTP trigger > Access key authorization](../azure-functions/functions-bindings-http-webhook-trigger.md#api-key-authorization).
60+
5961
## Custom allocation policy request
6062

6163
DPS sends a POST request to your webhook on the following endpoint: `https://{your-function-app-name}.azurewebsites.net/api/{your-http-trigger}`

0 commit comments

Comments
 (0)