diff --git a/support/azure/azure-kubernetes/storage/file-share-mount-failures-azure-files.md b/support/azure/azure-kubernetes/storage/file-share-mount-failures-azure-files.md
index 2c7a0a8637..ac099d548c 100644
--- a/support/azure/azure-kubernetes/storage/file-share-mount-failures-azure-files.md
+++ b/support/azure/azure-kubernetes/storage/file-share-mount-failures-azure-files.md
@@ -1,8 +1,8 @@
 ---
 title: File share mounting failures for Azure Files
 description: Troubleshoot why your file share for Azure Files fails to mount as storage on your Azure Kubernetes Service (AKS) clusters.
-ms.date: 06/10/2022
-ms.reviewer: chiragpa, nickoman, v-leedennis
+ms.date: 10/23/2024
+ms.reviewer: chiragpa, nickoman, jaewonpark, v-leedennis
 ms.service: azure-kubernetes-service
 keywords:
 #Customer intent: As an Azure Kubernetes user, I want to troubleshoot why my file share fails to mount so that I can successfully use Azure Files for storage on my Azure Kubernetes Service (AKS) clusters.
@@ -16,6 +16,14 @@ This article discusses how to troubleshoot file share mounting failures for Azur
 
 Your storage account key has changed.
 
+## Symptom
+
+This can occur as various errors, but the following event mainly occur in pods.
+
+```
+Error: failed to generate container "56907e9807c6f4203c3aace8c5a6e3a75832cf07d3080a3869d355114657b54f" spec: failed to generate spec: failed to stat "/var/lib/kubelet/pods/xxxxxxxx-9fe6-46d7-b12e-339951b8d2f5/volumes/kubernetes.io~csi/pvc-xxxxxxxx-3b70-498c-b357-3488e1c1f429/mount": stat /var/lib/kubelet/pods/xxxxxxxx-9fe6-46d7-b12e-339951b8d2f5/volumes/kubernetes.io~csi/pvc-xxxxxxxx-3b70-498c-b357-3488e1c1f429/mount: host is down
+```
+
 ## Solution
 
 Manually update the `azurestorageaccountkey` field in an Azure file secret with your base64-encoded storage account key. To make this update, follow these steps:
@@ -34,6 +42,11 @@ Manually update the `azurestorageaccountkey` field in an Azure file secret with
 
 1. Change the `azurestorageaccountkey` field to use the new base64-encoded storage account key, and save the file.
 
+1. Redeploy your pods.
+
+> [!NOTE]
+> Simply deleting the pod and let it recreate again may not take effect. Be sure to redeploy the pod.
+
 After a few minutes, the agent node will retry the Azure File mount with the updated storage key.
 
 [!INCLUDE [Third-party disclaimer](../../../includes/third-party-disclaimer.md)]