Skip to content

Commit 02d235e

Browse files
Update chaos-studio-configure-customer-managed-keys.md
1 parent bc56669 commit 02d235e

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

articles/chaos-studio/chaos-studio-configure-customer-managed-keys.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,7 @@ When configured, Chaos Studio uses Azure Storage, which uses the CMK to encrypt
3232
- You need to use our *2023-10-27-preview REST API* to create and use CMK-enabled experiments only. There's *no* support for CMK-enabled experiments in our general availability-stable REST API until H1 2024.
3333
- Chaos Studio currently *only supports creating Chaos Studio CMK experiments via the command line by using our 2023-10-27-preview REST API*. As a result, you *can't* create a Chaos Studio experiment with CMK enabled via the Azure portal. We plan to add this functionality in H1 of 2024.
3434
- The storage account must have *public access from all networks* enabled for Chaos Studio experiments to be able to use it. If you have a hard requirement from your organization, reach out to your CSA for potential solutions.
35+
- Experiment data will appear in ARG even after using CMK. This is a known issue, but the visbility is limited to only the active subcription using CMK.
3536

3637
## Configure your storage account
3738

0 commit comments

Comments
 (0)