tabs

Author: alexwolfmsft

articles/storage/common/migrate-azure-credentials.md

@@ -31,6 +31,8 @@ For local development, make sure you're authenticated with the same Azure AD acc
 
 Next you need to update your code to use passwordless connections.
 
+## [.NET](#tab/dotnet)
+
 1. To use `DefaultAzureCredential` in a .NET application, add the **Azure.Identity** NuGet package to your application.
 
    ```dotnetcli
@@ -56,6 +58,8 @@ Next you need to update your code to use passwordless connections.
 
    :::image type="content" source="../blobs/media/storage-quickstart-blobs-dotnet/storage-account-name.png" alt-text="Screenshot showing how to find the storage account name.":::
 
+---
+
 ### Run the app locally
 
 After making these code changes, run your application locally. The new configuration should pick up your local credentials, such as the Azure CLI, Visual Studio, or IntelliJ. The roles you assigned to your local dev user in Azure allows your app to connect to the Azure service locally.
@@ -153,6 +157,8 @@ If you connected your services using Service Connector you don't need to complet
 
 You need to configure your application code to look for the specific managed identity you created when it is deployed to Azure. In some scenarios, explicitly setting the managed identity for the app also prevents other environment identities from accidentally being detected and used automatically.
 
+## [.NET](#tab/dotnet)
+
 1. On the managed identity overview page, copy the client ID value to your clipboard.
 1. Update the `DefaultAzureCredential` object in the `Program.cs` file of your app to specify this managed identity client ID.
 
@@ -167,6 +173,8 @@ You need to configure your application code to look for the specific managed ide
                             }));
     ```
 
+---
+
 3. Redeploy your code to Azure after making this change in order for the configuration updates to be applied.
 
 ### Test the app