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-mysql.md
+12-14Lines changed: 12 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,12 +6,12 @@ ms.author: malev
6
6
ms.service: service-connector
7
7
ms.topic: how-to
8
8
ms.custom: engagement-fy23
9
-
ms.date: 02/02/2024
9
+
ms.date: 03/14/2025
10
10
---
11
11
12
12
# Integrate Azure Database for MySQL with Service Connector
13
13
14
-
This page shows supported authentication methods and clients, and shows sample code you can use to connect Azure Database for MySQL - Flexible Server to other cloud services using Service Connector. This page also shows default environment variable names and values (or Spring Boot configuration) you get when you create the service connection.
14
+
This article covers supported authentication methods, clients, and sample code you can use to connect your apps to Azure Database for MySQL - Flexible Server using Service Connector. In this article, you'll also find default environment variable names, values, and configuration obtained when creating service connections.
@@ -27,7 +27,7 @@ Service Connector can be used to connect the following compute services to Azure
27
27
28
28
## Supported authentication types and client types
29
29
30
-
The table below shows which combinations of authentication methods and clients are supported for connecting your compute service to Azure Database for MySQL using Service Connector. A “Yes” indicates that the combination is supported, while a “No” indicates that it is not supported.
30
+
The table below shows which combinations of authentication methods and clients are supported for connecting your compute services to Azure Database for MySQL using Service Connector. A “Yes” indicates that the combination is supported, while a “No” indicates that it is not supported.
31
31
32
32
| Client type | System-assigned managed identity | User-assigned managed identity | Secret/connection string | Service principal |
@@ -42,16 +42,14 @@ The table below shows which combinations of authentication methods and clients a
42
42
| Ruby (mysql2) | Yes | Yes | Yes | Yes |
43
43
| None | Yes | Yes | Yes | Yes |
44
44
45
-
This table indicates that all combinations of client types and authentication methods in the table are supported. All client types can use any of the authentication methods to connect to Azure Database for MySQL using Service Connector.
46
-
47
45
> [!NOTE]
48
-
> System-assigned managed identity, User-assigned managed identity and Service principal are only supported on Azure CLI.
46
+
> System-assigned managed identity, user-assigned managed identity and service principal authentication is only supported on Azure CLI.
49
47
50
48
## Default environment variable names or application properties and sample code
51
49
52
50
Reference the connection details and sample code in following tables, according to your connection's authentication type and client type, to connect compute services to Azure Database for MySQL. For more information about naming conventions, check the [Service Connector internals](concept-service-connector-internals.md#configuration-naming-convention) article.
53
51
54
-
### System-assigned Managed Identity
52
+
### System-assigned managed identity
55
53
56
54
#### [.NET](#tab/dotnet)
57
55
@@ -65,7 +63,7 @@ Reference the connection details and sample code in following tables, according
@@ -240,7 +238,7 @@ Refer to the steps and code below to connect to Azure Database for MySQL using a
240
238
Refer to the steps and code below to connect to Azure Database for MySQL using a user-assigned managed identity.
241
239
[!INCLUDE [code sample for mysql system mi](./includes/code-mysql-me-id.md)]
242
240
243
-
### Connection String
241
+
### Connection string
244
242
245
243
> [!WARNING]
246
244
> 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.
@@ -257,7 +255,7 @@ Refer to the steps and code below to connect to Azure Database for MySQL using a
Copy file name to clipboardExpand all lines: articles/service-connector/how-to-integrate-postgres.md
+14-14Lines changed: 14 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,12 +6,12 @@ ms.author: malev
6
6
ms.service: service-connector
7
7
ms.topic: how-to
8
8
ms.custom: engagement-fy23
9
-
ms.date: 02/02/2024
9
+
ms.date: 03/14/2025
10
10
---
11
11
12
12
# Integrate Azure Database for PostgreSQL with Service Connector
13
13
14
-
This page shows supported authentication methods and clients, and shows sample code you can use to connect Azure Database for PostgreSQL to other cloud services using Service Connector. You might still be able to connect to Azure Database for PostgreSQL in other programming languages without using Service Connector. This page also shows default environment variable names and values (or Spring Boot configuration) you get when you create the service connection.
14
+
This article covers supported authentication methods, clients, and sample code you can use to connect your apps to Azure Database for PostgreSQL using Service Connector. In this article, you'll also find default environment variable names, values, and configuration obtained when creating service connections.
15
15
16
16
## Supported compute services
17
17
@@ -25,7 +25,7 @@ Service Connector can be used to connect the following compute services to Azure
25
25
26
26
## Supported authentication types and client types
27
27
28
-
The table below shows which combinations of authentication methods and clients are supported for connecting your compute service to Azure Database for PostgreSQL using Service Connector. A “Yes” indicates that the combination is supported, while a “No” indicates that it is not supported.
28
+
The table below shows which combinations of authentication methods and clients are supported for connecting compute services to Azure Database for PostgreSQL using Service Connector. A “Yes” indicates that the combination is supported, while a “No” indicates that it is not supported.
29
29
30
30
| Client type | System-assigned managed identity | User-assigned managed identity | Secret/connection string | Service principal |
@@ -40,16 +40,14 @@ The table below shows which combinations of authentication methods and clients a
40
40
| Ruby (ruby-pg) | Yes | Yes | Yes | Yes |
41
41
| None | Yes | Yes | Yes | Yes |
42
42
43
-
This table indicates that all combinations of client types and authentication methods in the table are supported. All client types can use any of the authentication methods to connect to Azure Database for PostgreSQL using Service Connector.
44
-
45
43
> [!NOTE]
46
44
> System-assigned managed identity, User-assigned managed identity and Service principal are only supported on Azure CLI.
47
45
48
46
## Default environment variable names or application properties and sample code
49
47
50
-
Reference the connection details and sample code in the following tables, according to your connection's authentication type and client type, to connect compute services to Azure Database for PostgreSQL. For more information about naming conventions, check the [Service Connector internals](concept-service-connector-internals.md#configuration-naming-convention) article.
48
+
Reference the connection details and sample code in the following tables, according to your connection's authentication type and client type. For more information about naming conventions, check the [Service Connector internals](concept-service-connector-internals.md#configuration-naming-convention) article.
51
49
52
-
### System-assigned Managed Identity
50
+
### System-assigned managed identity
53
51
54
52
#### [.NET](#tab/dotnet)
55
53
@@ -63,7 +61,8 @@ Reference the connection details and sample code in the following tables, accord
@@ -222,7 +222,7 @@ Refer to the steps and code below to connect to Azure Database for PostgreSQL us
222
222
Refer to the steps and code below to connect to Azure Database for PostgreSQL using a user-assigned managed identity.
223
223
[!INCLUDE [code sample for postgresql user mi](./includes/code-postgres-me-id.md)]
224
224
225
-
### Connection String
225
+
### Connection string
226
226
227
227
> [!WARNING]
228
228
> 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.
@@ -239,7 +239,7 @@ Refer to the steps and code below to connect to Azure Database for PostgreSQL us
![prmerger-automator[bot]](https://avatars.githubusercontent.com/u/22479449?v=4&size=40){kind=avatar}
0 commit comments