Merge pull request #312896 from MicrosoftDocs/main

Auto Publish – main to live - 2026-03-10 10:00 UTC

Author: learn-build-service-prod[bot]

articles/storage-mover/cloud-to-cloud-migration.md

@@ -24,6 +24,7 @@ Before you begin, ensure that you have:
 - An AWS account with access to the Amazon S3 bucket from which you want to migrate.
 - An [Azure Storage account](../storage/common/storage-account-create.md) to use as the destination.
 - A [Storage Mover resource](storage-mover-create.md) deployed in your Azure subscription.
+- A [private connection setup on Azure](migrations-requiring-private-connections.md), if your AWS source data is in a Virtual Private Cloud (VPC).
 
 ## Limits
 
@@ -32,7 +33,6 @@ The Cloud-to-Cloud Migration feature in Azure Storage Mover has the following li
 - Each migration job supports the transfer of 500 million objects.
 - A maximum of 10 concurrent jobs is supported per subscription. If you need to run more than 10, you can do so by creating a support request.
 - Azure Storage Mover doesn't support automatic rehydration of archived objects. Data stored in AWS Glacier or Deep Archive must be restored before migration. Migration jobs should only be initiated after the data is fully restored.
-- Private Networking is currently not supported. However, Azure Storage Mover's Cloud-to-Cloud feature securely transfers data by limiting S3 access to trusted Azure IP ranges. This approach ensures secure, controlled connectivity over the public internet.
 
 ## Create a multicloud connector for AWS
 

articles/storage-mover/cloud-to-cloud-private-network-configs.md

@@ -103,10 +103,6 @@ SD-WAN and firewall NVAs can terminate VPN tunnels, perform inspection, and appl
 
 SD-WAN NVAs are commonly licensed as either pay-as-you-go (PAYG) or bring-your-own-license (BYOL). Vendor support varies by deployment option.
 
-PAYG: Pay as you go
-
-BYOL: Bring your own license
-
 #### Example deployment (FortiGate NVA in Azure)
 
 **Select a topology** (single VM, active/passive, or active/active) based on availability and throughput requirements.
@@ -206,7 +202,16 @@ After creating the Direct Connect resource, create a private connection in Stora
 4. Only private connections in **Approved** state can be selected.
 5. Remaining job steps are the same as a public S3-to-Blob migration.
 
+## Architecture
+### Cloud-to-cloud Migration flow (private networking)
+
+:::image type="content" source="./media/cloud-to-cloud-networking/cloud-to-cloud-private-networking.png" alt-text="Screenshot of cloud-to-cloud private networking architecture." lightbox="./media/cloud-to-cloud-networking/cloud-to-cloud-private-networking.png":::
+
+Above diagram shown with private networking to AWS but same applies for other private networking scenarios.
 
+### Cloud-to-cloud Migration flow (public S3 bucket to Azure Blob)
+
+:::image type="content" source="./media/cloud-to-cloud-networking/cloud-to-cloud-public.png" alt-text="Screenshot of cloud-to-cloud public workflow." lightbox="./media/cloud-to-cloud-networking/cloud-to-cloud-public.png":::
 
 
 ## Troubleshooting
@@ -276,3 +281,5 @@ For BGP between Azure and AWS, follow: [Tutorial - Configure a BGP-enabled conne
 
 
 
+
+

articles/storage-mover/media/cloud-to-cloud-networking/cloud-to-cloud-private-networking.png

@@ -91,7 +91,7 @@ Create a YAML manifest file such as `storageclass.yaml`. Use the names and varia
 apiVersion: storage.k8s.io/v1
 kind: StorageClass
 metadata:
-  name: azuresan-encrypted
+  name: azuresan-csi-encrypted
 provisioner: san.csi.azure.com
 reclaimPolicy: Delete
 volumeBindingMode: Immediate
@@ -124,7 +124,7 @@ spec:
   resources:
     requests:
       storage: 1Gi
-  storageClassName: azuresan-encrypted
+  storageClassName: azuresan-csi-encrypted
 ```
 
 Apply the manifest to create the PVC.

articles/storage-mover/media/cloud-to-cloud-networking/cloud-to-cloud-public.png

@@ -55,13 +55,14 @@ Azure Container Storage is a cloud-based volume management, deployment, and orch
   Example:
 
   ```azurecli
-  az aks update -n <cluster-name> -g <resource-group> --enable-azure-container-storage ephemeralDisk,elasticSan
+  az aks update -n <cluster-name> -g <resource-group> --enable-azure-container-storage ephemeralDisk elasticSan
   ```
 
   **Behavior:**
   - Installs the installer plus the selected CSI driver(s).
   - Creates default storage class objects if none exists.
-  - Supports comma-separated storage types.
+  - Default storage class names are `local-csi` for `ephemeralDisk` (local NVMe) and `azuresan-csi` for `elasticSan` (Azure Elastic SAN).
+  - Supports multiple storage types.
 
   Supported storage types for version 2.1.0 and later: `ephemeralDisk` (local NVMe) and `elasticSan` (Azure Elastic SAN).
 
@@ -70,7 +71,8 @@ Azure Container Storage is a cloud-based volume management, deployment, and orch
   The extension configuration supports the same flows as Azure CLI:
 
   - **Installer-only (choose storage later):** Set `enable-azure-container-storage` to `true`. Create a storage class later to trigger driver installation.
-  - **Installer + storage type(s):** Set `enable-azure-container-storage` to a storage type value such as `ephemeralDisk`, `elasticSan`, or a comma-separated list like `ephemeralDisk,elasticSan`. This installs the installer and the selected CSI drivers.
+  - **Installer + storage type(s):** Set `enable-azure-container-storage` to a storage type value such as `ephemeralDisk`, `elasticSan`, or a list like `ephemeralDisk elasticSan`. This installs the installer, the selected CSI drivers, and creates a default storage class.
+    Default storage class names are `local-csi` for `ephemeralDisk` (local NVMe) and `azuresan-csi` for `elasticSan` (Azure Elastic SAN).
 
   Supported storage types for version 2.1.0 and later: `ephemeralDisk` (local NVMe) and `elasticSan` (Azure Elastic SAN).
 

articles/storage/container-storage/configure-encryption-for-elastic-san.md

@@ -106,7 +106,7 @@ Run the following command to create a new AKS cluster and install Azure Containe
 az aks create -n <cluster-name> -g <resource-group> --node-vm-size Standard_L8s_v3 --enable-azure-container-storage ephemeralDisk --generate-ssh-keys
 ```
 
-This command installs the installer, deploys the `ephemeralDisk` driver, and creates a default storage class. You can install and use both local NVMe and Elastic SAN by providing comma-separated values such as `ephemeralDisk,elasticSan`.
+This command installs the installer, deploys the local NVMe CSI driver, and creates a default storage class called `local-csi`. You can install and use both local NVMe and Elastic SAN by providing a list such as `ephemeralDisk elasticSan`.
 
 ## Install Azure Container Storage on an existing AKS cluster
 
@@ -128,7 +128,7 @@ Run the following command to enable Azure Container Storage on an existing AKS c
 az aks update -n <cluster-name> -g <resource-group> --enable-azure-container-storage elasticSan
 ```
 
-This command installs the installer, deploys the Elastic SAN CSI driver, and creates a default storage class. You can install and use both local NVMe and Elastic SAN by providing comma-separated values such as `ephemeralDisk,elasticSan`.
+This command installs the installer, deploys the Elastic SAN CSI driver, and creates a default storage class called `azuresan-csi`. You can install and use both local NVMe and Elastic SAN by providing a list such as `ephemeralDisk elasticSan`.
 
 ::: zone-end
 
@@ -286,6 +286,16 @@ When it completes, the cluster has the Azure Container Storage installer compone
 
 ## Verify installation
 
+### Connect to the AKS cluster
+
+Before running the verification commands, make sure your local kubeconfig is set to the target cluster:
+
+```azurecli
+az aks get-credentials --resource-group <resource-group-name> --name <cluster-name>
+```
+
+If you manage multiple clusters, add `--overwrite-existing` to replace an existing context or use `--context` to set a unique context name.
+
 ### Verify installer (installer-only mode)
 
 After an installer-only enable, verify that the installer is present:
@@ -313,8 +323,8 @@ Example output:
 
 ```output
 NAME                    PROVISIONER               RECLAIMPOLICY   VOLUMEBINDINGMODE      ALLOWVOLUMEEXPANSION   AGE
-azuresan                san.csi.azure.com         Delete          Immediate              false                  4d7h
-local                   localdisk.csi.acstor.io   Delete          WaitForFirstConsumer   true                   4d5h
+azuresan-csi            san.csi.azure.com         Delete          Immediate              false                  4d7h
+local-csi               localdisk.csi.acstor.io   Delete          WaitForFirstConsumer   true                   4d5h
 ```
 
 ### Verify driver installation

articles/storage/container-storage/container-storage-faq.md

@@ -85,7 +85,7 @@ Create a YAML manifest file such as `storageclass.yaml`, then use the following
 apiVersion: storage.k8s.io/v1
 kind: StorageClass
 metadata:
-  name: azuresan
+  name: azuresan-csi
 provisioner: san.csi.azure.com
 reclaimPolicy: Delete
 volumeBindingMode: Immediate
@@ -113,9 +113,9 @@ Alternatively, you can create the storage class using Terraform.
       config_path = "~/.kube/config"
     }
 
-    resource "kubernetes_storage_class_v1" "azuresan" {
+    resource "kubernetes_storage_class_v1" "azuresan_csi" {
       metadata {
-        name = "azuresan"
+        name = "azuresan-csi"
       }
 
       storage_provisioner    = "san.csi.azure.com"
@@ -140,7 +140,7 @@ If you need a different initial capacity than the default 1 TiB, set the `initia
 apiVersion: storage.k8s.io/v1
 kind: StorageClass
 metadata:
-  name: azuresan
+  name: azuresan-csi
 provisioner: san.csi.azure.com
 reclaimPolicy: Delete
 volumeBindingMode: Immediate
@@ -177,7 +177,7 @@ If you don't already have Azure Container Storage installed, [install it](instal
    apiVersion: storage.k8s.io/v1
    kind: StorageClass
    metadata:
-     name: azuresan
+     name: azuresan-csi
    provisioner: san.csi.azure.com
    reclaimPolicy: Delete
    volumeBindingMode: Immediate
@@ -225,7 +225,7 @@ If you don't already have Azure Container Storage installed, [install it](instal
    apiVersion: storage.k8s.io/v1
    kind: StorageClass
    metadata:
-     name: azuresan
+     name: azuresan-csi
    provisioner: san.csi.azure.com
    reclaimPolicy: Delete
    volumeBindingMode: Immediate
@@ -246,14 +246,14 @@ kubectl apply -f storageclass.yaml
 Verify that the storage class is created:
 
 ```azurecli
-kubectl get storageclass azuresan
+kubectl get storageclass azuresan-csi
 ```
 
 You should see output similar to:
 
 ```output
-NAME       PROVISIONER          RECLAIMPOLICY   VOLUMEBINDINGMODE   ALLOWVOLUMEEXPANSION   AGE
-azuresan   san.csi.azure.com    Delete          Immediate           true                   10s
+NAME           PROVISIONER          RECLAIMPOLICY   VOLUMEBINDINGMODE   ALLOWVOLUMEEXPANSION   AGE
+azuresan-csi   san.csi.azure.com    Delete          Immediate           true                   10s
 ```
 
 ## Create a persistent volume claim
@@ -273,7 +273,7 @@ A persistent volume claim (PVC) automatically provisions storage based on a stor
      resources:
        requests:
          storage: 1Gi
-     storageClassName: azuresan
+     storageClassName: azuresan-csi
    ```
 
 1. Apply the manifest to create the PVC.
@@ -360,7 +360,7 @@ Use the following YAML manifest to create a default Elastic SAN storage class:
 apiVersion: storage.k8s.io/v1
 kind: StorageClass
 metadata:
-  name: azuresan
+  name: azuresan-csi
 provisioner: san.csi.azure.com
 reclaimPolicy: Delete
 volumeBindingMode: Immediate
@@ -376,7 +376,7 @@ kubectl apply -f storageclass.yaml
 Verify the storage class:
 
 ```azurecli
-kubectl get storageclass azuresan
+kubectl get storageclass azuresan-csi
 ```
 
 ### Create an Elastic SAN volume
@@ -410,7 +410,7 @@ spec:
   accessModes:
     - ReadWriteOnce
   persistentVolumeReclaimPolicy: Retain
-  storageClassName: azuresan
+  storageClassName: azuresan-csi
   csi:
     driver: san.csi.azure.com
     volumeHandle: #{rg}#{san}#{vg}#{vol}
@@ -443,7 +443,7 @@ spec:
     requests:
       storage: 5Gi
   volumeName: pv-san
-  storageClassName: azuresan
+  storageClassName: azuresan-csi
 ```
 
 Apply the manifest to create the PVC.

articles/storage/container-storage/install-container-storage-aks.md

@@ -69,15 +69,15 @@ For more information, refer to [Best practices for ephemeral NVMe data disks in
 
 If you don't already have Azure Container Storage installed, [install it](install-container-storage-aks.md).
 
-Azure Container Storage (version 2.x.x) presents local NVMe as a standard Kubernetes storage class. Create the `local` storage class once per cluster and reuse it for both generic ephemeral volumes and persistent volume claims.
+Azure Container Storage (version 2.x.x) presents local NVMe as a standard Kubernetes storage class. Create the `local-csi` storage class once per cluster and reuse it for both generic ephemeral volumes and persistent volume claims.
 
 1. Use your favorite text editor to create a YAML manifest file such as `storageclass.yaml`, then paste in the following specification.
 
     ```yaml
     apiVersion: storage.k8s.io/v1
     kind: StorageClass
     metadata:
-      name: local
+      name: local-csi
     provisioner: localdisk.csi.acstor.io
     reclaimPolicy: Delete
     volumeBindingMode: WaitForFirstConsumer
@@ -109,9 +109,9 @@ Alternatively, you can create the storage class using Terraform.
       config_path = "~/.kube/config"
     }
 
-    resource "kubernetes_storage_class_v1" "local" {
+    resource "kubernetes_storage_class_v1" "local_csi" {
       metadata {
-        name = "local"
+        name = "local-csi"
       }
 
       storage_provisioner    = "localdisk.csi.acstor.io"
@@ -134,19 +134,19 @@ Alternatively, you can create the storage class using Terraform.
 Run the following command to verify that the storage class is created:
 
 ```azurecli
-kubectl get storageclass local
+kubectl get storageclass local-csi
 ```
 
 You should see output similar to:
 
 ```output
-NAME    PROVISIONER                RECLAIMPOLICY   VOLUMEBINDINGMODE      ALLOWVOLUMEEXPANSION   AGE
-local   localdisk.csi.acstor.io    Delete          WaitForFirstConsumer   true                   10s
+NAME       PROVISIONER                RECLAIMPOLICY   VOLUMEBINDINGMODE      ALLOWVOLUMEEXPANSION   AGE
+local-csi  localdisk.csi.acstor.io    Delete          WaitForFirstConsumer   true                   10s
 ```
 
 ## Create and attach generic ephemeral volumes
 
-Follow these steps to create and attach a generic ephemeral volume using Azure Container Storage. Make sure Azure Container Storage is [installed](install-container-storage-aks.md) and the `local` storage class exists before you continue.
+Follow these steps to create and attach a generic ephemeral volume using Azure Container Storage. Make sure Azure Container Storage is [installed](install-container-storage-aks.md) and the `local-csi` storage class exists before you continue.
 
 ### Deploy a pod with generic ephemeral volume
 
@@ -178,7 +178,7 @@ Create a pod using [Fio](https://github.com/axboe/fio) (Flexible I/O Tester) for
              spec:
                volumeMode: Filesystem
                accessModes: ["ReadWriteOnce"]
-               storageClassName: local
+               storageClassName: local-csi
                resources:
                  requests:
                    storage: 10Gi
@@ -211,7 +211,7 @@ While generic ephemeral volumes are recommended for ephemeral storage, Azure Con
 > [!NOTE]
 > Azure Container Storage (version 2.x.x) uses the new annotation `localdisk.csi.acstor.io/accept-ephemeral-storage: "true"` instead of the previous `acstor.azure.com/accept-ephemeral-storage: "true"`.
 
-Make sure Azure Container Storage is [installed](install-container-storage-aks.md) and the `local` storage class you created earlier is available before deploying workloads that use it.
+Make sure Azure Container Storage is [installed](install-container-storage-aks.md) and the `local-csi` storage class you created earlier is available before deploying workloads that use it.
 
 ### Deploy a stateful set with persistent volumes
 
@@ -259,7 +259,7 @@ spec:
           localdisk.csi.acstor.io/accept-ephemeral-storage: "true"
       spec:
         accessModes: ["ReadWriteOnce"]
-        storageClassName: local
+        storageClassName: local-csi
         resources:
           requests:
             storage: 10Gi
@@ -289,8 +289,8 @@ You should see output similar to this example:
 
 ```output
 NAME          STORAGE_CLASS   CAPACITY    NODE
-csisc-2pkx4   local           1373172Mi   aks-storagepool-31410930-vmss000001
-csisc-gnmm9   local           1373172Mi   aks-storagepool-31410930-vmss000000
+csisc-2pkx4   local-csi       1373172Mi   aks-storagepool-31410930-vmss000001
+csisc-gnmm9   local-csi       1373172Mi   aks-storagepool-31410930-vmss000000
 ```
 
 If you encounter empty capacity output, confirm that a StorageClass for `localdisk.csi.acstor.io` exists. The `csistoragecapacities.storage.k8s.io` resource is only generated after a StorageClass for `localdisk.csi.acstor.io` exists.
@@ -309,10 +309,10 @@ az aks nodepool scale --cluster-name <cluster-name> --name <nodepool-name> --res
 
 To clean up storage resources, you must first delete all PersistentVolumeClaims and/or PersistentVolumes. Deleting the Azure Container Storage StorageClass doesn't automatically remove your existing PersistentVolumes/PersistentVolumeClaims.
 
-To delete a storage class named `local`, run the following command:
+To delete a storage class named `local-csi`, run the following command:
 
 ```azurecli
-kubectl delete storageclass local
+kubectl delete storageclass local-csi
 ```
 
 ## See also

articles/storage/container-storage/use-container-storage-with-elastic-san.md

@@ -108,7 +108,7 @@ Create a new PVC that uses the volume snapshot as a data source.
    spec:
      accessModes:
        - ReadWriteOnce
-     storageClassName: azuresan
+     storageClassName: azuresan-csi
      resources:
        requests:
          storage: 100Gi