You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/service-connector/how-to-integrate-storage-blob.md
+11-9Lines changed: 11 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,16 +1,16 @@
1
1
---
2
2
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.
4
4
author: maud-lv
5
5
ms.author: malev
6
6
ms.service: service-connector
7
7
ms.topic: how-to
8
-
ms.date: 03/14/2025
8
+
ms.date: 02/03/2026
9
9
---
10
10
11
11
# Integrate Azure Blob Storage with Service Connector
12
12
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 methodsand 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.
14
14
15
15
## Supported compute services
16
16
@@ -24,7 +24,7 @@ Service Connector can be used to connect the following compute services to Azure
24
24
25
25
## Supported authentication types and client types
26
26
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.
28
28
29
29
| Client type | System-assigned managed identity | User-assigned managed identity | Secret / connection string | Service principal |
@@ -60,7 +60,7 @@ Authenticating with a system-assigned managed identity is only available for Spr
60
60
61
61
#### Sample code
62
62
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.
64
64
[!INCLUDE [code sample for blob](./includes/code-blob-me-id.md)]
65
65
66
66
### User-assigned managed identity
@@ -85,13 +85,14 @@ Authenticating with a user-assigned managed identity is only available for Sprin
85
85
86
86
#### Sample code
87
87
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
+
89
90
[!INCLUDE [code sample for blob](./includes/code-blob-me-id.md)]
90
91
91
92
### Connection string
92
93
93
94
> [!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.
95
96
96
97
#### SpringBoot client
97
98
@@ -112,7 +113,7 @@ Refer to the steps and code below to connect to Azure Blob Storage using a user-
112
113
113
114
#### Sample code
114
115
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.
116
117
[!INCLUDE [code sample for blob](./includes/code-blob-secret.md)]
117
118
118
119
### Service principal
@@ -139,7 +140,8 @@ Authenticating with a service principal is only available for Spring Cloud Azure
139
140
140
141
#### Sample code
141
142
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
+
143
145
[!INCLUDE [code sample for blob](./includes/code-blob-me-id.md)]
0 commit comments