Skip to content

Commit c28f392

Browse files
committed
integrate-azure-cache-for-redis-with-service-connector
1 parent 5bbb2e0 commit c28f392

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/service-connector/how-to-integrate-redis-cache.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ You can use Service Connector to connect the following compute services to Azure
2424

2525
## Supported authentication and client types
2626

27-
Find out which combinations of authentication methods and clients are supported for connecting your compute service to Azure Cache for Redis using Service Connector in the following table. "Yes" means that the combination is supported, while "No" means that it's not supported.
27+
The following table shows which combinations of authentication methods and clients are supported for connecting your compute service to Azure Cache for Redis using Service Connector. "Yes" means that the combination is supported, while "No" means that it isn't supported.
2828

2929
| Client type | System-assigned managed identity | User-assigned managed identity | Secret / connection string | Service principal |
3030
|--------------------|----------------------------------|--------------------------------|----------------------------|-------------------|
@@ -68,7 +68,7 @@ The following steps and code show you how to use a user-assigned managed identit
6868
### Connection string
6969

7070
> [!WARNING]
71-
> We recommend that you use the most secure authentication flow available. The authentication flow described here requires a very high degree of trust in the application, and carries risks that are not present in other flows. You should only use this flow when more secure flows, such as managed identities, aren't viable.
71+
> We recommend that you use the most secure authentication flow available. The authentication flow described here requires a very high degree of trust in the application, and carries risks that aren't present in other flows. You should only use this flow when more secure flows, such as managed identities, aren't viable.
7272
7373
#### [.NET](#tab/dotnet)
7474

0 commit comments

Comments
 (0)