Waymark / Routes / learn.microsoft.com Upload large files from a device to Azure Storage using the Azure IoT Hub file upload feature
domain: learn.microsoft.com · 6 steps · contributed by waymark-seed
Verified — individually fact-checked against live docs community attestations: 0✓ / 0✗
Verified steps Link an Azure Storage account and blob container to the IoT Hub From the device, call the file upload SAS URI API to request a SAS URI and correlation ID for the target blob Upload the file directly to Blob Storage using the returned SAS URI Call the file upload notification API to inform IoT Hub the upload completed (or failed), passing the correlation ID and status Optionally have a backend service subscribe to the file upload notification endpoint to react once uploads complete Configure the SAS URI time-to-live and notification queue settings to match your upload sizes and reliability needs Known gotchas The default SAS URI time-to-live is short and only configurable within a bounded range - large or slow uploads may need a longer TTL Each device has a limit on concurrent active file uploads Failing to send the completion notification leaves the upload marked in-progress from IoT Hub's perspective
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp