Azure Application Insight Encryption

[Ronnie-personal]

Based on the document, the data is encrypted, can we have more detail, is it encrypted using Microsoft Managed Key, and is the key scoped to a particular resource or to subscription or all subscriptions under on AAD tenant or entire Azure?

Does it support CMK encryption?

https://docs.microsoft.com/en-us/azure/azure-monitor/app/data-retention-privacy#is-the-data-encrypted
[Enter feedback here]

---

Document Details

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

• ID: c4cb6c8f-80a5-3a49-3cc1-e194e5b98b16
• Version Independent ID: ef9c64e5-466d-9be2-df6a-39de8c76b1ad
• Content: Data retention and storage in Azure Application Insights - Azure Monitor
• Content Source: articles/azure-monitor/app/data-retention-privacy.md
• Service: azure-monitor
• Sub-service: application-insights
• GitHub Login: @lgayhardt
• Microsoft Alias: lagayhar

[BryanTrach-MSFT]

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

[Ronnie-personal]

@BryanTrach-MSFT Any update on the issue? Thanks!

[BharathNimmala-MSFT]

@Ronnie-personal Apologies for delay in getting back to this thread

One of the capabilities with the new workspace-based Application Insights allows you to take advantage of Customer-Managed Keys (CMK) provides encryption at rest for your data with encryption keys that only you have access to.

For further details on Azure Monitor customer-managed key , please refer here.

Hope the information helps , we will also review with our document author to see how we can show the references of this in the document so that its easy discoverable. Please let us know if you have any further queries.

[BharathNimmala-MSFT]

@Ronnie-personal Hope the above information shared helps. Please review it and let us know if you have any further queries.

At this point it appears that there's no further edits or updates needed to the documentation mentioned in this issue. We will go ahead and close this issue for now, however if you have any further feedback on the document please tag us in your reply and will be happy to reopen the thread and continue the conversation. Thank you