Skip to content

Commit 7ebe849

Browse files
Merge pull request #311290 from v-thpra/tjp-lf-servconnect-002
Q&M: Light Freshness - Service Connector - TJP002
2 parents 671aedd + 501f2e6 commit 7ebe849

1 file changed

Lines changed: 11 additions & 9 deletions

File tree

articles/service-connector/how-to-integrate-storage-blob.md

Lines changed: 11 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,16 @@
11
---
22
title: Integrate Azure Blob Storage with Service Connector
3-
description: Integrate Azure Blob Storage into your application with Service Connector
3+
description: Learn how to integrate Azure Blob Storage into your application with Service Connector by using the supported authentication methods and clients.
44
author: maud-lv
55
ms.author: malev
66
ms.service: service-connector
77
ms.topic: how-to
8-
ms.date: 03/14/2025
8+
ms.date: 02/03/2026
99
---
1010

1111
# Integrate Azure Blob Storage with Service Connector
1212

13-
This article covers supported authentication methods, clients, and sample code you can use to connect your apps to Azure Blob Storage using Service Connector. In this article, you'll also find default environment variable names, values, and configuration obtained when creating service connections.
13+
In this article, we cover the supported authentication methods and clients that you can use to connect your apps to Azure Blob Storage using Service Connector. For each supported method, we provide sample code and describe the default environment variable names, values, and configuration obtained when creating a service connection.
1414

1515
## Supported compute services
1616

@@ -24,7 +24,7 @@ Service Connector can be used to connect the following compute services to Azure
2424

2525
## Supported authentication types and client types
2626

27-
The table below shows which combinations of authentication methods and clients are supported for connecting your compute services to Azure Blob Storage using Service Connector. A Yes indicates that the combination is supported, while a “No” indicates that it is not supported.
27+
The following table shows which combinations of authentication methods and clients are supported for connecting your compute services to Azure Blob Storage using Service Connector. A *Yes* indicates that the combination is supported, while a *No* indicates that it isn't supported.
2828

2929
| Client type | System-assigned managed identity | User-assigned managed identity | Secret / connection string | Service principal |
3030
|--------------------|----------------------------------|--------------------------------|----------------------------|-------------------|
@@ -60,7 +60,7 @@ Authenticating with a system-assigned managed identity is only available for Spr
6060

6161
#### Sample code
6262

63-
Refer to the steps and code below to connect to Azure Blob Storage using a system-assigned managed identity.
63+
To connect to Azure Blob Storage using a system-assigned managed identity, refer to the following steps and sample code.
6464
[!INCLUDE [code sample for blob](./includes/code-blob-me-id.md)]
6565

6666
### User-assigned managed identity
@@ -85,13 +85,14 @@ Authenticating with a user-assigned managed identity is only available for Sprin
8585

8686
#### Sample code
8787

88-
Refer to the steps and code below to connect to Azure Blob Storage using a user-assigned managed identity.
88+
To connect to Azure Blob Storage using a user-assigned managed identity, refer to the following steps and example code.
89+
8990
[!INCLUDE [code sample for blob](./includes/code-blob-me-id.md)]
9091

9192
### Connection string
9293

9394
> [!WARNING]
94-
> Microsoft recommends that you use the most secure authentication flow available. The authentication flow described in this procedure 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 other more secure flows, such as managed identities, aren't viable.
95+
> Microsoft recommends that you use the most secure authentication flow available. The authentication flow described in this procedure requires a high degree of trust in the application, and carries risks that aren't present in other flows. You should only use this flow when other more secure flows, such as managed identities, aren't viable.
9596
9697
#### SpringBoot client
9798

@@ -112,7 +113,7 @@ Refer to the steps and code below to connect to Azure Blob Storage using a user-
112113

113114
#### Sample code
114115

115-
Refer to the steps and code below to connect to Azure Blob Storage using a connection string.
116+
To connect to Azure Blob Storage using a connection string, refer to the following steps and sample code.
116117
[!INCLUDE [code sample for blob](./includes/code-blob-secret.md)]
117118

118119
### Service principal
@@ -139,7 +140,8 @@ Authenticating with a service principal is only available for Spring Cloud Azure
139140

140141
#### Sample code
141142

142-
Refer to the steps and code below to connect to Azure Blob Storage using a service principal.
143+
To connect to Azure Blob Storage using a service principal, refer to the following steps and sample code.
144+
143145
[!INCLUDE [code sample for blob](./includes/code-blob-me-id.md)]
144146

145147
## Next steps

0 commit comments

Comments
 (0)