diff --git a/deploy/example/storageclass-blobfuse.yaml b/deploy/example/storageclass-blobfuse.yaml
index c710d822e..bfdb62654 100644
--- a/deploy/example/storageclass-blobfuse.yaml
+++ b/deploy/example/storageclass-blobfuse.yaml
@@ -5,7 +5,7 @@ metadata:
   name: blob-fuse
 provisioner: blob.csi.azure.com
 parameters:
-  skuName: Premium_LRS  # available values: Standard_LRS, Premium_LRS, Standard_GRS, Standard_RAGRS
+  skuName: Premium_LRS  # available values: Standard_LRS, Premium_LRS, Standard_GRS, Standard_RAGRS, Standard_ZRS, Premium_ZRS
 reclaimPolicy: Delete
 volumeBindingMode: Immediate
 allowVolumeExpansion: true
diff --git a/deploy/example/storageclass-blobfuse2.yaml b/deploy/example/storageclass-blobfuse2.yaml
index e6b6391f1..c968a68a1 100644
--- a/deploy/example/storageclass-blobfuse2.yaml
+++ b/deploy/example/storageclass-blobfuse2.yaml
@@ -5,7 +5,7 @@ metadata:
   name: blob-fuse
 provisioner: blob.csi.azure.com
 parameters:
-  skuName: Premium_LRS  # available values: Standard_LRS, Premium_LRS, Standard_GRS, Standard_RAGRS
+  skuName: Premium_LRS  # available values: Standard_LRS, Premium_LRS, Standard_GRS, Standard_RAGRS, Standard_ZRS, Premium_ZRS
   protocol: fuse2
 reclaimPolicy: Delete
 volumeBindingMode: Immediate
diff --git a/docs/driver-parameters.md b/docs/driver-parameters.md
index 9bcde90a3..12f0cf972 100644
--- a/docs/driver-parameters.md
+++ b/docs/driver-parameters.md
@@ -19,7 +19,7 @@
 
 Name | Meaning | Example | Mandatory | Default value
 --- | --- | --- | --- | ---
-skuName | Azure storage account type (alias: `storageAccountType`) | `Standard_LRS`, `Premium_LRS`, `Standard_GRS`, `Standard_RAGRS` | No | `Standard_LRS`
+skuName | Azure storage account type (alias: `storageAccountType`) | `Standard_LRS`, `Premium_LRS`, `Standard_GRS`, `Standard_RAGRS`, `Standard_ZRS`, `Premium_ZRS`  | No | `Standard_LRS`
 location | Azure location | `eastus`, `westus`, etc. | No | if empty, driver will use the same location name as current k8s cluster
 resourceGroup | Azure resource group name | existing resource group name | No | if empty, driver will use the same resource group name as current k8s cluster
 storageAccount | specify Azure storage account name| STORAGE_ACCOUNT_NAME | No | If the driver is not provided with a specific storage account name, it will search for a suitable storage account that matches the account settings within the same resource group. If it cannot find a matching storage account, it will create a new one. However, if a storage account name is specified, the storage account must already exist.