Hi @Jamie Fraser Greetings! Welcome to Microsoft Q&A forum. Thank you for posting this question here.
The policy names you see in the shared link are only meant to used when creating an Enrollment group in Azure DPS through Azure portal. But the limitation here is that the Enrollment group creation from the portal only allows DPS to be linked with Azure IoT Hub but not IoT Central. Please find the below image for reference.
However, as the documentation states,
when setting the allocation policy using the DPS REST API, Azure CLI, and DPS service SDKs, they are referred to as follows:
hashed
,
geolatency
,
static
, and
custom
.
You can use the Microsoft.Azure.Devices.Provisioning.Service Namespace and create a ProvisioningServiceClient class and use the AllocationPolicy Enum defined in the namespace to create a static/custom allocation policy for IoT Central. Here is a link to documentation where you can find the implementation of DPS service SDKs
Kindly note that you would have to customize the samples provided in the GitHub repository and would need to create a custom solution that suits your needs. The Tutorial: Create and connect a client application to your Azure IoT Central application uses DPS device client to provision devices to IoT Central. You can modify the code to use DPS service client and test the custom allocation policies.
Hope this helps.
If the response helped, please do click Accept Answer and Yes for the answer provided. Doing so would help other community members with similar issue identify the solution. I highly appreciate your contribution to the community.