如何自定义Azure Function URL并实现多IoT设备共用HTTP触发函数

Got it, let's break this down step by step to get your Azure Function set up exactly how you want it—with dynamic device handling and the URL format you specified.

To get that https://<functionapp>.azurewebsites.net/api/<function>/{device_id}?code=xxxxx format, you just need to define a route parameter in your HTTP trigger. In C#, you can do this directly with the Route property on the HttpTrigger attribute:

[FunctionName("IoTHttpTrigger")]
public static async Task<IActionResult> Run(
    [HttpTrigger(AuthorizationLevel.Function, "get", "post", Route = "IoTHttpTrigger/{device_id}")] HttpRequest req,
    string device_id, // This binds directly to the {device_id} in the route
    ILogger log)

• The Route = "IoTHttpTrigger/{device_id}" part tells Azure Functions to expect a device_id value in the URL path.
• AuthorizationLevel.Function ensures the request requires the function's access code (the ?code=xxxxx part) for security—perfect for IoT device requests.

For the device key, the most seamless approach is to fetch it directly from Azure IoT Hub using the IoT Hub SDK, since you’re already working with IoT devices. Here’s how to do it:

Step 1: Install Required NuGet Package #

Add the Microsoft.Azure.Devices NuGet package to your Function project—this gives you access to the tools needed to interact with the IoT Hub device registry.

Step 2: Securely Store IoT Hub Credentials #

Store your IoT Hub connection string in the Function App’s Application Settings (never hardcode it!)—name it something like IOT_HUB_CONNECTION_STRING. You can set this in the Azure Portal under your Function App > Configuration > Application settings.

Step 3: Full Working Code Example #

using Microsoft.Azure.Devices;
using Microsoft.Azure.WebJobs;
using Microsoft.AspNetCore.Http;
using Microsoft.Extensions.Logging;
using System.Threading.Tasks;
using Microsoft.AspNetCore.Mvc;

[FunctionName("IoTHttpTrigger")]
public static async Task<IActionResult> Run(
    [HttpTrigger(AuthorizationLevel.Function, "post", Route = "IoTHttpTrigger/{device_id}")] HttpRequest req,
    string device_id,
    ILogger log)
{
    log.LogInformation($"Processing request for device: {device_id}");

    // Pull IoT Hub connection string from app settings
    var iotHubConnectionString = System.Environment.GetEnvironmentVariable("IOT_HUB_CONNECTION_STRING");
    if (string.IsNullOrEmpty(iotHubConnectionString))
    {
        return new BadRequestObjectResult("IoT Hub connection string not configured");
    }

    // Initialize RegistryManager to fetch device details from IoT Hub
    var registryManager = RegistryManager.CreateFromConnectionString(iotHubConnectionString);
    var device = await registryManager.GetDeviceAsync(device_id);

    if (device == null)
    {
        return new NotFoundObjectResult($"Device {device_id} not found in IoT Hub");
    }

    // Extract dynamic device values
    var deviceKey = device.Authentication.SymmetricKey.PrimaryKey; // Use SecondaryKey if needed
    var iotHubUri = "your-iot-hub-name.azure-devices.net"; // Or pull this from app settings too!

    // Initialize DeviceClient with dynamic credentials
    var deviceClient = DeviceClient.Create(iotHubUri, new DeviceAuthenticationWithRegistrySymmetricKey(device_id, deviceKey));

    // Add your IoT logic here (send messages, update twin, etc.)
    // ...

    await deviceClient.CloseAsync();
    return new OkObjectResult($"Successfully processed request for device {device_id}");
}

If you prefer storing device keys outside IoT Hub (e.g., for custom auth workflows), you can:

• Store each device’s key in Azure App Configuration with a key pattern like Devices:{device_id}:Key
• Or use Azure Key Vault with secrets named device-{device_id}-key
• Then use the respective SDKs (Azure App Configuration or Azure Key Vault) to fetch the key by device_id in your Function.

• Secure Secrets: Never hardcode connection strings or keys—always use Application Settings or Key Vault.
• Permissions: If using RegistryManager, assign the IoT Hub Data Registry Reader role to your Function App’s Managed Identity (more secure than using a connection string).
• Access Code: Find your function’s access code in the Azure Portal under your Function App > Your Function > Keys tab. Devices must include this code in the code query parameter.

内容的提问来源于stack exchange，提问作者user2022284