Skip to content

Commit 8b77010

Browse files
committed
us gov for cmk transition caveat
1 parent c675f3d commit 8b77010

File tree

1 file changed

+8
-3
lines changed

1 file changed

+8
-3
lines changed

articles/azure-netapp-files/configure-customer-managed-keys.md

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -79,14 +79,16 @@ Azure NetApp Files customer-managed keys is supported for the following regions:
7979
* UAE North
8080
* UK South
8181
* UK West
82-
* US Gov Arizona
83-
* US Gov Texas
84-
* US Gov Virginia
82+
* US Gov Arizona*
83+
* US Gov Texas*
84+
* US Gov Virginia*
8585
* West Europe
8686
* West US
8787
* West US 2
8888
* West US 3
8989

90+
\* The ability to transition existing volumes to customer-managed keys isn't currently supported for US Gov regions.
91+
9092
## Requirements
9193

9294
Before creating your first customer-managed key volume, you must set up:
@@ -367,6 +369,9 @@ Azure NetApp Files supports the ability to move existing volumes using platform-
367369
368370
Encryption key transition for Azure NetApp Files is currently in preview. Before using this feature for the first time, you need to register it.
369371
372+
>[NOTE]
373+
>Transitioning volumes to customer-managed keys isn't currently supported for US Gov regions.
374+
370375
1. Register the feature:
371376
372377
```azurepowershell-interactive

0 commit comments

Comments
 (0)