diff --git a/en/azure/blobservice/blob-service-immutable.md b/en/azure/blobservice/blob-service-immutable.md
index 78609ce84..7aca507a4 100644
--- a/en/azure/blobservice/blob-service-immutable.md
+++ b/en/azure/blobservice/blob-service-immutable.md
@@ -18,9 +18,10 @@
1. Log in to the Microsoft Azure Management Console.
2. Find the search bar at the top and search for "Storage accounts".
3. Select the "Storage account" by clicking on the "Name" link to access the configuration changes.
-4. In the left navigation panel click on "Containers" under "Data Storage"
-5. In the Containers List, select the container by clicking on the triple dots (...) on the extreme right and select "Access Policy".
-6. In the "Access Policy" panel check the "Permissions" associated with the "Blob". If the "Blob" allow full (racwdl) read, add, create, write, delete, or list permissions then the selected "Blob" is not properly configured in blob services to protect critical data against deletion.
-7. To change permissions in the "Access Policy" panel, click on triple dots (...) at the right and select "Edit".
-8. Uncheck the "Add/Write/Detele/List" policies under the "Permissions" and click on the "OK" button to make the changes.
-9. Repeat steps number 5 - 8 to ensure data immutability is properly configured in blob services to protect critical data against deletion.
+4. In the "Data Management" Section, Click on the "Data protection" tab. Enable the Soft delete for blobs or containers based on your required level and save.
+5. Now, in the left navigation panel click on "Containers" under "Data Storage"
+6. In the Containers List, select the container by clicking on the triple dots (...) on the extreme right and select "Access Policy".
+7. In the "Access Policy" panel, create immutable blob storage access policy in the containers (time-based or legal hold).
+8. To create a policy with container scope, don't check the box for Enable version-level immutability and click save.
+9. Repeat steps number 5 - 8 to ensure data immutability is properly configured in blob services to protect critical data against deletion.
+
diff --git a/resources/azure/blobservice/blob-service-immutable/step4.png b/resources/azure/blobservice/blob-service-immutable/step4.png
index 6379cd4bb..468884cad 100644
Binary files a/resources/azure/blobservice/blob-service-immutable/step4.png and b/resources/azure/blobservice/blob-service-immutable/step4.png differ
diff --git a/resources/azure/blobservice/blob-service-immutable/step5.png b/resources/azure/blobservice/blob-service-immutable/step5.png
index ebbaca7c3..6379cd4bb 100644
Binary files a/resources/azure/blobservice/blob-service-immutable/step5.png and b/resources/azure/blobservice/blob-service-immutable/step5.png differ
diff --git a/resources/azure/blobservice/blob-service-immutable/step6.png b/resources/azure/blobservice/blob-service-immutable/step6.png
index 469dc0f81..ebbaca7c3 100644
Binary files a/resources/azure/blobservice/blob-service-immutable/step6.png and b/resources/azure/blobservice/blob-service-immutable/step6.png differ
diff --git a/resources/azure/blobservice/blob-service-immutable/step7.png b/resources/azure/blobservice/blob-service-immutable/step7.png
index e51a8eb52..42db21bb9 100644
Binary files a/resources/azure/blobservice/blob-service-immutable/step7.png and b/resources/azure/blobservice/blob-service-immutable/step7.png differ
diff --git a/resources/azure/blobservice/blob-service-immutable/step8.png b/resources/azure/blobservice/blob-service-immutable/step8.png
deleted file mode 100644
index 4b89bd748..000000000
Binary files a/resources/azure/blobservice/blob-service-immutable/step8.png and /dev/null differ