Azure-docs: BYOK Encryption status and Creation via ARM template

[pnarsi]

A couple of questions on this this feature:

1) Is this a preview feature or is it GA and usable for production use
2) Can we use a ARM template to specify the BYOK at the time of deployment? I don't see anything in the latest ARM template that suggests that we can: https://docs.microsoft.com/en-us/azure/templates/microsoft.devices/2020-03-01/iothubs

---

Document Details

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

• ID: e75acdea-dda0-2c68-7642-523d636b8ce7
• Version Independent ID: 377c59c2-6531-f7b0-b4b6-14f71fd25e3c
• Content: Azure IoT Hub data encryption at rest via customer-managed keys
• Content Source: articles/iot-hub/iot-hub-customer-managed-keys.md
• Service: iot-hub
• GitHub Login: @ash2017
• Microsoft Alias: asrastog

[ash2017]

Please contact us through Microsoft support https://azure.microsoft.com/en-us/support/create-ticket/ to see if this is available in your region for use.

[SatishBoddu-MSFT]

Hello @pnarsi

Please let us know if you need further help in this matter or we good to close this issue?

[pnarsi]

@SatishBoddu-MSFT I have asked our Microsoft rep to assist in following up on this. Ideally however this should be documented on this docs page somewhere i.e. if supported it should be documented here otherwise it should be called as not supported.

[AshokPeddakotla-MSFT]

@pnarsi Thanks for the further feedback. We will review and update the doc as necessary. Meanwhile as suggested, kindly follow up with support for further help. Do let us know if you have any further queries.

[pnarsi]

Thanks @AshokPeddakotla-MSFT. I have followed up offline with my Microsoft reps and have got answers to my questions.

[SatishBoddu-MSFT]

Thank you @pnarsi for the response. Please let us know if we are good to close this issue?

[AshokPeddakotla-MSFT]

Good to hear that you got the answers. 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.