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/mariadb/concepts-data-access-security-private-link.md
+15-15Lines changed: 15 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: Private Link for Azure Database for MariaDB
2
+
title: Private Link - Azure Database for MariaDB
3
3
description: Learn how Private link works for Azure Database for MariaDB.
4
4
author: kummanish
5
5
ms.author: manishku
@@ -10,7 +10,7 @@ ms.date: 03/10/2020
10
10
11
11
# Private Link for Azure Database for MariaDB
12
12
13
-
Private Link allows you to connect to various PaaS services in Azure via a private endpoint. Azure Private Link essentially brings Azure services inside your private Virtual Network (VNet). The PaaS resources can be accessed using the private IP address just like any other resource in the VNet.
13
+
Private Link allows you to create private endpoints for Azure Database for MariaDB and so brings Azure services inside your private Virtual Network (VNet). The private endpoint exposes a private IP you can use to connect to your Azure Database for MariaDB database server just like any other resource in the VNet.
14
14
15
15
For a list to PaaS services that support Private Link functionality, review the Private Link [documentation](https://docs.microsoft.com/azure/private-link/index). A private endpoint is a private IP address within a specific [VNet](https://docs.microsoft.com/azure/virtual-network/virtual-networks-overview) and Subnet.
16
16
@@ -46,39 +46,39 @@ With Private Link, you can enable cross-premises access to the private endpoint
46
46
47
47
### Creation Process
48
48
49
-
Private Endpoints are required to enable Private Link. This can be done using the following how-to guides.
49
+
private endpoints are required to enable Private Link. This can be done using the following how-to guides.
Once the network admin creates the Private Endpoint (PE), the admin can manage the Private Endpoint Connection (PEC) to Azure Database for MariaDB.
56
+
Once the network admin creates the private endpoint (PE), the admin can manage the private endpoint Connection (PEC) to Azure Database for MariaDB. This separation of duties between the network admin and the DBA is helpful for management of the Azure Database for MariaDB connectivity.
57
57
58
58
* Navigate to the Azure Database for MariaDB server resource in the Azure portal.
59
-
* Select the Private endpoint connections in the left pane
60
-
* Shows a list of all Private Endpoint Connections (PECs)
61
-
* Corresponding Private Endpoint (PE) created
59
+
* Select the private endpoint connections in the left pane
60
+
* Shows a list of all private endpoint Connections (PECs)
61
+
* Corresponding private endpoint (PE) created
62
62
63
-

63
+

64
64
65
65
* Select an individual PEC from the list by selecting it.
66
66
67
-

67
+

68
68
69
69
* The MariaDB server admin can choose to approve or reject a PEC and optionally add a short text response.
70
70
71
-

71
+

72
72
73
73
* After approval or rejection, the list will reflect the appropriate state along with the response text
74
74
75
-

75
+

76
76
77
77
## Use cases of Private Link for Azure Database for MariaDB
78
78
79
-
Clients can connect to the Private endpoint from the same VNet, peered VNet in same region, or via VNet-to-VNet connection across regions. Additionally, clients can connect from on-premises using ExpressRoute, private peering, or VPN tunneling. Below is a simplified diagram showing the common use cases.
79
+
Clients can connect to the private endpoint from the same VNet, peered VNet in same region, or via VNet-to-VNet connection across regions. Additionally, clients can connect from on-premises using ExpressRoute, private peering, or VPN tunneling. Below is a simplified diagram showing the common use cases.
80
80
81
-

81
+

82
82
83
83
### Connecting from an Azure VM in Peered Virtual Network (VNet)
84
84
Configure [VNet peering](https://docs.microsoft.com/azure/virtual-network/tutorial-connect-virtual-networks-powershell) to establish connectivity to the Azure Database for MariaDB from an Azure VM in a peered VNet.
@@ -105,9 +105,9 @@ The following situations and outcomes are possible when you use Private Link in
105
105
106
106
## Deny public access for Azure Database for MariaDB
107
107
108
-
While Private Link allows access via private endpoint only, customer can use still use the public end points via [firewall rules](concepts-firewall-rules.md) and [VNet service endpoints](concepts-data-access-security-vnet.md) in such cases where they may need a mix of private and public connectivity. However, if you want to rely only on private endpoints for accessing their Azure Database for MariaDB, you can disable setting all public endpoints by setting the **Deny Public Network Access** configuration on the database server.
108
+
If you want to rely completely only on private endpoints for accessing their Azure Database for MariaDB, you can disable setting all public endpoints ([firewall rules](concepts-firewall-rules.md) and [VNet service endpoints](concepts-data-access-security-vnet.md)) by setting the **Deny Public Network Access** configuration on the database server.
109
109
110
-
When this setting is set to *YES* only connections via private endpoints are allowed to your Azure Database for MariaDB. When this setting is set to *NO* clients can connect to your Azure Database for MariaDB based on your firewall or VNet service endpoint setting. Additionally, once the value of the Private network access is set to customers cannot add and/or update existing ‘Firewall rules’ and ‘VNet service endpoint rule
110
+
When this setting is set to *YES*, only connections via private endpoints are allowed to your Azure Database for MariaDB. When this setting is set to *NO*, clients can connect to your Azure Database for MariaDB based on your firewall or VNet service endpoint settings. Additionally, once the value of the Private network access is set, you cannot add and/or update existing firewall and VNet service endpoint rules.
111
111
112
112
> [!Note]
113
113
> This setting does not have any impact on the SSL and TLS configurations for your Azure Database for MariaDB.
Copy file name to clipboardExpand all lines: articles/mariadb/concepts-ssl-connection-security.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,11 +22,11 @@ To learn how to enable or disable SSL connection when developing application, re
22
22
23
23
## TLS connectivity in Azure Database for MariaDB
24
24
25
-
Azure Database for MariaDB supports privacy and data integrity over communications as clients connect to your database server using Transport Layer Security (TLS). TLS is an industry standard protocol that ensures secure network connections between your database server and your client applications and helps adhere to compliance requirements.
25
+
Azure Database for MariaDB supports encryption for clients connecting to your database server using Transport Layer Security (TLS). TLS is an industry standard protocol that ensures secure network connections between your database server and client applications, allowing you to adhere to compliance requirements.
26
26
27
27
### TLS settings
28
28
29
-
Security conscious customers now have the ability to enforce the TLS version for the client connecting to their Azure Database for MariaDB. To use the TLS option, use the **minumumTlsVersion** option setting. The following values are allowed for this option setting:
29
+
Azure Database for MariaDB provides the ability to enforce the TLS version for the client connections. To use the TLS option, use the **Minimum TLS version** option setting. The following values are allowed for this option setting:
@@ -36,12 +36,12 @@ Security conscious customers now have the ability to enforce the TLS version for
36
36
| TLS1_2 | TLS version 1.2 and higher |
37
37
38
38
39
-
For example, setting this Minimum TLS setting version to TLS 1.0 means you shall allow clients connecting using TLS 1.0,1.1 and 1.2+. Alternatively, setting this to 1.2 means that you only allow clients connecting using TLS 1.2 and all incoming connections with TLS 1.0 and TLS 1.1 will be rejected.
39
+
For example, setting this Minimum TLS setting version to TLS 1.0 means your server will allow connections from clients using TLS 1.0,1.1, and 1.2+. Alternatively, setting this to 1.2 means that you only allow connections from clients using TLS 1.2 and all connections with TLS 1.0 and TLS 1.1 will be rejected.
40
40
41
41
> [!Note]
42
42
> Azure Database for MariaDB defaults to TLS being disabled for all new servers.
43
43
>
44
-
> Currently the TLS version supported for Azure Database for MariaDB are TLS 1.0, TLS 1.1, TLS 1.2.
44
+
> Currently the TLS versions supported byAzure Database for MariaDB are TLS 1.0, 1.1, and 1.2.
45
45
46
46
To learn how to set the TLS setting for your Azure Database for MariaDB, refer to [How to configure TLS setting](howto-tls-configurations.md).
Copy file name to clipboardExpand all lines: articles/mariadb/howto-deny-public-network-access.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: Deny Public Network Access in Azure Database for MariaDB using Azure portal
2
+
title: Deny Public Network Access - Azure portal - Azure Database for MariaDB
3
3
description: Learn how to configure Deny Public Network Access using Azure portal for your Azure Database for MariaDB
4
4
author: kummanish
5
5
ms.author: manishku
@@ -10,7 +10,7 @@ ms.date: 03/10/2020
10
10
11
11
# Deny Public Network Access in Azure Database for MariaDB using Azure portal
12
12
13
-
This article describes how you can configure an Azure Database for MariaDB server to deny all public configurations and allow only private endpoints to go through to enhance the network security.
13
+
This article describes how you can configure an Azure Database for MariaDB server to deny all public configurations and allow only connections through private endpoints to further enhance the network security.
14
14
15
15
## Prerequisites
16
16
@@ -24,9 +24,9 @@ Follow these steps to set MariaDB server Deny Public Network Access:
24
24
25
25
* In the [Azure portal](https://portal.azure.com/), select your existing Azure Database for MariaDB server.
26
26
27
-
* On the MariaDB server page, under **Settings** heading, click **Connection security** to open the connection security configuration page.
27
+
* On the MariaDB server page, under **Settings**, click **Connection security** to open the connection security configuration page.
28
28
29
-
* In the Deny Public Network Access, select **Yes** to enable deny public access for your MariaDB server.
29
+
* In Deny Public Network Access, select **Yes** to enable deny public access for your MariaDB server.
30
30
31
31

description: Learn how to set TLS configuration using Azure portal for your Azure Database for MariaDB
4
4
author: kummanish
5
5
ms.author: manishku
@@ -12,7 +12,7 @@ ms.date: 03/10/2020
12
12
13
13
This article describes how you can configure an Azure Database for MariaDB server to enforce connections for a minimum TLS version to go through and deny all connections with lower TLS version thereby enhancing the network security.
14
14
15
-
Security conscious customers now have the ability to enforce TLS version for connecting to their Azure Database for MariaDB. Customers now have a choice to set the minimal TLS version for their database server. For example, setting this Minimum TLS version to 1.0 means you shall allow clients connecting using TLS 1.0,1.1 and 1.2. Alternatively, setting this to 1.2 means that you only allow clients connecting using TLS 1.2 and all incoming connections with TLS 1.0 and TLS 1.1 will be rejected.
15
+
Customers now have the ability to enforce TLS version for connecting to their Azure Database for MariaDB by setting the minimal TLS version for their database server. For example, setting the minimum TLS setting version to TLS 1.0 means your server will allow connections from clients using TLS 1.0,1.1, and 1.2+. Alternatively, setting this to 1.2 means that you only allow connections from clients using TLS 1.2 and all connections with TLS 1.0 and TLS 1.1 will be rejected.
16
16
17
17
## Prerequisites
18
18
@@ -26,9 +26,9 @@ Follow these steps to set MariaDB server minimum TLS version:
26
26
27
27
* In the [Azure portal](https://portal.azure.com/), select your existing Azure Database for MariaDB server.
28
28
29
-
* On the MariaDB server page, under **Settings** heading, click **Connection security** to open the connection security configuration page.
29
+
* On the MariaDB server page, under **Settings**, click **Connection security** to open the connection security configuration page.
30
30
31
-
* In the **Minimum TLS version**, select **1.2** to deny connections with TLS version less than TLS 1.2 for your MariaDB server.
31
+
* In **Minimum TLS version**, select **1.2** to deny connections with TLS version less than TLS 1.2 for your MariaDB server.
32
32
33
33

0 commit comments