Azure-docs: Deploy modules without access to subscription

[MarekLani]

Is it possible to deploy new modules to IoT Edge device without having access to Azure subscription where the related IoT Hub is running? I would expect to have possibility to deploy modules (using deploy manifest) to edge device using IoT Hub manage key.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: ed3eb802-31f2-6c9c-7c8d-17b88f33f7c6
• Version Independent ID: fb1ea209-a141-85ef-c9b4-113d69536892
• Content: Deploy modules from command line - Azure IoT Edge
• Content Source: articles/iot-edge/how-to-deploy-modules-cli.md
• Service: iot-edge
• GitHub Login: @kgremban
• Microsoft Alias: kgremban

[Alberto-Vega]

@MarekLani Thanks for the feedback! We are currently investigating and will update you shortly.

[Alberto-Vega]

@MarekLani I'm assigning the issue to the content author to help and evaluate the feedback

[kgremban]

@MarekLani Can you clarify what you mean by "using IoT Hub manage key"? I know that IoT Hub allows you to Control access to IoT Hub with scoped permissions, but that doesn't sound like what you're describing. Are you thinking about a scenario where a 3rd party module developer would want to push updates to their customer's devices?

[MarekLani]

@kgremban yes this is what I meant. Basically having possibility to deploy modules without any need of accessing customer's subscription.

[kgremban]

Thank you for the extra info. Currently that functionality doesn't exist in IoT Edge. You can update your container and increment its version, then tell your customers to just update their deployment manifests with the new version. You can write up the feature request and provide it as feedback to the product team to consider in their planning: https://feedback.azure.com/forums/907045-azure-iot-edge

[MarekLani]

@kgremban thanks I added feedback: https://feedback.azure.com/forums/907045-azure-iot-edge/suggestions/37761754-allow-upstream-iot-hub-event-hub-to-be-different, but I gave it a second thought. The requirement of being signed in to azure subscription in order to manage IoT Edge device might not be a problem. What might be desired is that Edge Device allows upstream IoT Hub to be different as management one. Scenario: Edge device is managed and operated by company A, but data collected by Edge Device should be provided to company B. Ofc it is possible to have a separate module connecting to second IoT Hub, but this solution would not utilize Edge routing.

[kgremban]

Thanks for making that request, Marek. @Alberto-Vega-MSFT could you #please-close this issue because it's about features that aren't available in the product currently.

[BryanTrach-MSFT]

@MarekLani We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.