updated file

Author: flang-msft

articles/redis/dotnet.md

@@ -1,21 +1,33 @@
-## Microsoft.Azure.StackExchangeRedis Sample Application
+---
+title: "Quickstart: Use Azure Managed Redis in .NET Core"
+description: In this quickstart, learn how to use Azure Managed Redis in a .NET console app
+ms.date: 01/30/2026
+ms.topic: quickstart
+ms.devlang: csharp
+zone_pivot_groups: redis-type
+appliesto:
+    - ✅ Azure Managed Redis
+# Customer intent: As a .NET developer, new to Azure Managed Redis, I want to create a new dotnet app that uses Azure Managed Redis.
+---
+
+# Quickstart: Use Azure Redis in .NET Core
+
+This is a .NET 8 console application that demonstrates how to connect to **Azure Managed Redis** using **Microsoft Entra ID**  authentication. The core value proposition is **passwordless authentication** with automatic token refresh, providing a secure and modern approach to Redis connectivity.
 
-### Overview
+## Skip to the code on GitHub
 
-This is a .NET 8 console application that demonstrates how to connect to **Azure Managed Redis** using **Microsoft Entra ID** (formerly Azure Active Directory) authentication. The core value proposition is **passwordless authentication** with automatic token refresh, providing a secure and modern approach to Redis connectivity.
+Clone the repo [Microsoft.Azure.StackExchangeRedis](https://github.com/Azure/Microsoft.Azure.StackExchangeRedis/tree/main/sample) on GitHub.
 
-### Required NuGet Packages
+## Required NuGet Packages
 
 | Package | Purpose |
-|---------|---------|
+|||
 | `Microsoft.Azure.StackExchangeRedis` | Extension library that adds Entra ID authentication to StackExchange.Redis |
 | `Azure.Identity` | Provides `DefaultAzureCredential` and other Azure identity implementations |
 | `StackExchange.Redis` | The underlying Redis client (pulled in as a dependency) |
 | `Microsoft.Extensions.Logging.Console` | Console logging for diagnostics |
 
----
-
-### Authentication Methods
+## Authentication Methods
 
 The extension supports multiple identity types, each with a corresponding `ConfigureForAzure*()` extension method:
 
@@ -29,8 +41,6 @@ The extension supports multiple identity types, each with a corresponding `Confi
 
 5. **Service Principal (Certificate)** — Client ID + Tenant ID + X.509 certificate for higher security.
 
----
-
 ### How `DefaultAzureCredential` Works Locally
 
 When developing locally, `DefaultAzureCredential` will attempt to authenticate using:
@@ -41,9 +51,7 @@ az login
 
 This signs you into the Azure CLI with your Microsoft Entra ID account. The SDK detects your cached credentials and uses them to obtain tokens. Your Entra ID user must be configured as a **Redis User** on the Azure Managed Redis resource via the **Data Access Configuration** blade in the Azure portal.
 
----
-
-### Key Implementation Patterns
+## Key Implementation Patterns
 
 **Connection Configuration:**
 
@@ -72,9 +80,7 @@ await database.StringSetAsync("key", "value");
 var value = await database.StringGetAsync("key");
 ```
 
----
-
-### Token Lifecycle & Automatic Re-authentication
+## Token Lifecycle & Automatic Re-authentication
 
 The extension handles the OAuth2 token lifecycle automatically:
 
@@ -85,15 +91,13 @@ The extension handles the OAuth2 token lifecycle automatically:
 You can subscribe to token events for observability:
 
 | Event | Purpose |
-|-------|---------|
+|-||
 | `TokenRefreshed` | New token acquired |
 | `TokenRefreshFailed` | Token refresh failed (still using old token) |
 | `ConnectionReauthenticated` | Connection successfully re-authenticated |
 | `ConnectionReauthenticationFailed` | Re-auth failed for a connection |
 
----
-
-### RESP3 vs RESP2 Protocol
+## RESP3 vs RESP2 Protocol
 
 The sample uses **RESP3** (`Protocol = RedisProtocol.Resp3`) because:
 
@@ -102,48 +106,43 @@ The sample uses **RESP3** (`Protocol = RedisProtocol.Resp3`) because:
 - Pub/sub connections close when their token expires, causing brief interruptions.
 - RESP3 multiplexes everything on one connection, avoiding these disruptions.
 
----
-
-### Azure Prerequisites
+## Azure Prerequisites
 
 1. **Create an Azure Managed Redis** instance.
 2. **Enable Microsoft Entra ID authentication** under "Data Access Configuration."
 3. **Add your identity as a Redis User** with the appropriate permissions (Data Owner, Data Contributor, etc.).
 4. **Run `az login`** locally to authenticate with your Entra ID account.
 
----
-
-### Redis Basics Refresher
+## Redis Basics Refresher
 
 | Concept | Description |
-|---------|-------------|
+||-|
 | `ConnectionMultiplexer` | Singleton, thread-safe connection pool to Redis—create once, reuse for the app lifetime. |
 | `IDatabase` | Interface for executing commands (`StringGet`, `StringSet`, `HashGet`, etc.). |
 | Endpoint format | `endpoint:10000` (TLS) for Azure Managed Redis. |
 | Commands | Redis is single-threaded per key—atomic operations like `INCR`, `SETNX` avoid race conditions. |
 
----
-
-### Running the Sample
+## Running the Sample
 
 ```powershell
 az login
 cd sample
 dotnet run
 ```
 
-Enter your Redis endpoint (e.g., `myredis.redis.azure.net`), choose authentication method **1** (DefaultAzureCredential), and watch the `+` characters print every second as commands succeed. Let it run for 60+ minutes to verify automatic token refresh works.
+Enter your Redis endpoint (e.g., <myredis.redis.azure.net:1000>), choose authentication method **1** (DefaultAzureCredential), and watch the `+` characters print every second as commands succeed. Let it run for 60+ minutes to verify automatic token refresh works.
 
----
-
-### Production Considerations
+## Production Considerations
 
 | Setting | Sample Value | Production Value |
-|---------|--------------|------------------|
+||--||
 | `AbortOnConnectFail` | `true` | `false` (retry on startup) |
 | `BacklogPolicy` | `FailFast` | `Default` (queue commands during transient failures) |
 | Connection lifetime | Demo loop | Singleton via DI (`IConnectionMultiplexer`) |
 
----
-
 This sample provides a complete reference implementation for secure, passwordless Entra ID authentication in any .NET application that uses Azure Managed Redis.
+
+## Related content
+
+- [Connection resilience](best-practices-connection.md)
+- [Best Practices Development](best-practices-development.md)