isabella232 / geographically-provisioning-iot-devices-on-azure

This repository details how to provision your IoT devices based on their location using Azure.

Geographically Provisioning IoT Devices on Azure

The goal of this repository is to explain how you can implement IoT device geo-provisioning with Azure IoT Hub, Device Provisioning Service (DPS), Functions and Maps. Using these Azure services, you will learn how to control an IoT device’s provisioning based on their location.

The corresponding Tech Community blog that fully explains this architecture can be found here.

Getting Started

Prerequisites

1. Create an Azure IoT Hub
2. Create an Azure IoT Hub Device Provisioning Service (DPS)
   • Ensure the IoT Hub from step 1 has been linked to this DPS
3. Create an Azure Function App
   • Ensure the Runtime Stack and Version settings have been set to .NET and 6
4. Create an Azure Maps account
5. Install the .NET 6.0 SDK on your local machine

Demo

To run the demo, follow these steps:

1. Obtain your Azure Maps account's Primary Key
   • You can find the value of this key in the Azure Portal under the Authentication blade of your Azure Maps account or by using the Azure CLI script below:

     az maps account keys list -n "mapsAccountName" -g "resourceGroupName" -o tsv --query primaryKey

2. Update the subscriptionKey variable's value in the run.csx file, under the Azure Function Code folder, with the Primary Key value from step 1.
3. From the Azure portal, create an HTTP Trigger function in your Azure Function App.
4. Replace the HTTP Trigger function's default code with the code in the run.csx file.
5. Create an Individual Enrollment with a Custom Allocation Policy that uses your Azure Function App and the HTTP Trigger function from step 4.
6. Run the below commands locally, from within the root folder of this project:

   cd GeoProvisioningSample
   
   dotnet build
   
   dotnet run -- --DpsIdScope "replaceMeWithDPSScopeID" --DeviceId "replaceMeWithEnrollmentRegistrationId" --DeviceSymmetricKey "replaceMeWithEnrollmentPrimaryKey" --IPAddress "replaceMeWithEitherAPublicIPv4ORIPv6Address"

   • For now, this demo is configured to only allow provisioning devices with a public IPv4 or IPv6 address from the United States (US).

Resources

• Azure IoT Hub Device Provisioning Service | Overview

• Azure IoT Hub Device Provisioning Service | Custom Allocation Policy

• Azure Functions | Overview

• Azure Maps | Overview

• Azure Maps | Geolocation - Get IP To Location

• Azure Maps | Search - Get Search Address Reverse

• Azure IoT Hub | Overview

• Azure IoT Hub | Deployment Stamps