Merge pull request #93099 from xyh1/patch-76

Update storage-blob-soft-delete.md

Author: PRMerger10

articles/storage/blobs/storage-blob-soft-delete.md

@@ -147,7 +147,7 @@ When you initially turn on soft delete, we recommend using a small retention per
 
 The following steps show how to get started with soft delete.
 
-### Azure portal
+# [Portal](#tab/azure-portal)
 
 To enable soft delete, navigate to the **Soft delete** option under **Blob Service**. Then click **Enabled** and enter the number of days you want to retain soft deleted data.
 
@@ -177,7 +177,7 @@ Once you undelete a blob's snapshots, you can click **Promote** to copy a snapsh
 
 ![](media/storage-blob-soft-delete/storage-blob-soft-delete-portal-promote-snapshot.png)
 
-### PowerShell
+# [Powershell](#tab/azure-powershell)
 
 [!INCLUDE [updated-for-az](../../../includes/updated-for-az.md)]
 
@@ -214,7 +214,7 @@ To find the current soft delete retention policy, use the following command:
    Get-AzStorageServiceProperty -ServiceType Blob -Context $account.Context
 ```
 
-### Azure CLI 
+# [CLI](#tab/azure-CLI)
 
 To enable soft delete, update a blob client's service properties:
 
@@ -228,7 +228,7 @@ To verify soft delete is turned on, use the following command:
 az storage blob service-properties delete-policy show --account-name mystorageaccount 
 ```
 
-### Python client library
+# [Python](#tab/python)
 
 To enable soft delete, update a blob client's service properties:
 
@@ -246,7 +246,7 @@ block_blob_service.set_blob_service_properties(
     delete_retention_policy=DeleteRetentionPolicy(enabled=True, days=7))
 ```
 
-### .NET client library
+# [.NET](#tab/net)
 
 To enable soft delete, update a blob client's service properties:
 
@@ -288,6 +288,8 @@ CloudBlockBlob copySource = allBlobVersions.First(version => ((CloudBlockBlob)ve
 blockBlob.StartCopy(copySource);
 ```
 
+---
+
 ## Are there any special considerations for using soft delete?
 
 If there is a chance that your data is accidentally modified or deleted by an application or another storage account user, turning on soft delete is recommended. Enabling soft delete for frequently overwritten data may result in increased storage capacity charges and increased latency when listing blobs. You can mitigate this additional cost by storing the frequently overwritten data in a separate storage account where soft delete is disabled.