Skip to content

Commit 16d9fa8

Browse files
committed
VNet style fix
1 parent c5eab2e commit 16d9fa8

File tree

3 files changed

+25
-18
lines changed

3 files changed

+25
-18
lines changed

articles/mysql/flexible-server/concepts-networking-vnet.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ In the above diagram,
3939

4040
1. Azure Database for MySQL flexible server instances are injected into a delegated subnet - 10.0.1.0/24 of virtual network **VNet-1**.
4141
2. Applications deployed on different subnets within the same virtual network can access the Azure Database for MySQL flexible server instances directly.
42-
3. Applications deployed on a different virtual network **VNet-2** don't have direct access to Azure Database for MySQL flexible server instances. Before they can access an instance, you must perform a [private DNS zone virtual network peering](#private-dns-zone-and-vnet-peering).
42+
3. Applications deployed on a different virtual network **VNet-2** don't have direct access to Azure Database for MySQL flexible server instances. Before they can access an instance, you must perform a [private DNS zone virtual network peering](#private-dns-zone-and-virtual-network-peering).
4343

4444
## Virtual network concepts
4545

articles/mysql/flexible-server/how-to-manage-virtual-network-cli.md

Lines changed: 19 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.service: mysql
77
ms.subservice: flexible-server
88
ms.custom: devx-track-azurecli
99
ms.topic: how-to
10-
ms.date: 9/21/2020
10+
ms.date: 1/18/2024
1111
---
1212

1313
# Create and manage virtual networks for Azure Database for MySQL - Flexible Server using the Azure CLI
@@ -17,11 +17,11 @@ ms.date: 9/21/2020
1717
Azure Database for MySQL flexible server supports two types of mutually exclusive network connectivity methods to connect to your Azure Database for MySQL flexible server instance. The two options are:
1818

1919
- Public access (allowed IP addresses)
20-
- Private access (VNet Integration)
20+
- Private access (virtual network integration)
2121

22-
In this article, we will focus on creation of MySQL server with **Private access (VNet Integration)** using Azure CLI. With *Private access (VNet Integration)*, you can deploy your Azure Database for MySQL flexible server instance into your own [Azure Virtual Network](../../virtual-network/virtual-networks-overview.md). Azure Virtual Networks provide private and secure network communication. In Private access, the connections to the Azure Database for MySQL flexible server instance are restricted to only within your virtual network. To learn more about it, refer to [Private access (VNet Integration)](./concepts-networking-vnet.md).
22+
This article focuses on creation of MySQL server with **Private access (virtual network Integration)** using Azure CLI. With *Private access (virtual network integration)*, you can deploy your Azure Database for MySQL flexible server instance into your own [Azure Virtual Network](../../virtual-network/virtual-networks-overview.md). Azure Virtual Networks provide private and secure network communication. In Private access, the connections to the Azure Database for MySQL flexible server instance are restricted to only within your virtual network. To learn more about it, refer to [Private access (Virtual Network Integration)](./concepts-networking-vnet.md).
2323

24-
In Azure Database for MySQL flexible server, you can only deploy the server to a virtual network and subnet during creation of the server. After the Azure Database for MySQL flexible server instance is deployed to a virtual network and subnet, you cannot move it to another virtual network, subnet or to *Public access (allowed IP addresses)*.
24+
In Azure Database for MySQL flexible server, you can only deploy the server to a virtual network and subnet during creation of the server. After the Azure Database for MySQL flexible server instance is deployed to a virtual network and subnet, you can't move it to another virtual network, subnet or to *Public access (allowed IP addresses)*.
2525

2626
## Launch Azure Cloud Shell
2727

@@ -33,7 +33,7 @@ If you prefer to install and use the CLI locally, this quickstart requires Azure
3333

3434
## Prerequisites
3535

36-
You'll need to sign in to your account using the [az login](/cli/azure/reference-index#az-login) command. Note the **ID** property, which refers to **Subscription ID** for your Azure account.
36+
You need to sign in to your account using the [az login](/cli/azure/reference-index#az-login) command. Note the **ID** property, which refers to **Subscription ID** for your Azure account.
3737

3838
```azurecli-interactive
3939
az login
@@ -46,7 +46,8 @@ az account set --subscription <subscription id>
4646
```
4747

4848
## Create an Azure Database for MySQL flexible server instance using CLI
49-
You can use the `az mysql flexible-server` command to create the Azure Database for MySQL flexible server instance with *Private access (VNet Integration)*. This command uses Private access (VNet Integration) as the default connectivity method. A virtual network and subnet will be created for you if none is provided. You can also provide the already existing virtual network and subnet using subnet ID. <!-- You can provide the **vnet**,**subnet**,**vnet-address-prefix** or**subnet-address-prefix** to customize the virtual network and subnet.--> There are various options to create a Azure Database for MySQL flexible server instance using CLI as shown in the following examples.
49+
50+
You can use the `az mysql flexible-server` command to create the Azure Database for MySQL flexible server instance with *Private access (virtual network integration)*. This command uses Private access (virtual network integration) as the default connectivity method. A virtual network and subnet are created for you if none is provided. You can also provide the already existing virtual network and subnet using subnet ID. <!-- You can provide the **vnet**,**subnet**,**vnet-address-prefix** or**subnet-address-prefix** to customize the virtual network and subnet.--> There are various options to create an Azure Database for MySQL flexible server instance using CLI as shown in the following examples.
5051

5152
>[!Important]
5253
> Using this command will delegate the subnet to **Microsoft.DBforMySQL/flexibleServers**. This delegation means that only Azure Database for MySQL flexible server instances can use that subnet. No other Azure resource types can be in the delegated subnet.
@@ -55,29 +56,36 @@ You can use the `az mysql flexible-server` command to create the Azure Database
5556
Refer to the Azure CLI [reference documentation](/cli/azure/mysql/flexible-server) for the complete list of configurable CLI parameters. For example, in the following commands you can optionally specify the resource group.
5657

5758
- Create an Azure Database for MySQL flexible server instance using default virtual network, subnet with default address prefix.
59+
5860
```azurecli-interactive
5961
az mysql flexible-server create
6062
```
61-
- Create an Azure Database for MySQL flexible server instance using already existing virtual network and subnet. If provided virtual network and subnet does not exists then virtual network and subnet with default address prefix will be created.
63+
64+
- Create an Azure Database for MySQL flexible server instance using already existing virtual network and subnet. If provided virtual network and subnet don't exist, then virtual network and subnet with default address prefix are created.
65+
6266
```azurecli-interactive
6367
az mysql flexible-server create --vnet myVnet --subnet mySubnet
6468
```
6569
66-
- Create an Azure Database for MySQL flexible server instance using already existing virtual network, subnet, and using the subnet ID. The provided subnet should not have any other resource deployed in it and this subnet will be delegated to **Microsoft.DBforMySQL/flexibleServers**, if not already delegated.
70+
- Create an Azure Database for MySQL flexible server instance using already existing virtual network, subnet, and using the subnet ID. The provided subnet shouldn't have any other resource deployed in it and this subnet are delegated to **Microsoft.DBforMySQL/flexibleServers**, if not already delegated.
71+
6772
```azurecli-interactive
6873
az mysql flexible-server create --subnet /subscriptions/{SubID}/resourceGroups/{ResourceGroup}/providers/Microsoft.Network/virtualNetworks/{VNetName}/subnets/{SubnetName}
6974
```
75+
7076
> [!Note]
7177
> The virtual network and subnet should be in the same region and subscription as your Azure Database for MySQL flexible server instance.
7278
<
73-
- Create an Azure Database for MySQL flexible server instance using a new virtual network, subnet with non-default address prefix.
79+
- Create an Azure Database for MySQL flexible server instance using a new virtual network, subnet with nondefault address prefix.
80+
7481
```azurecli-interactive
7582
az mysql flexible-server create --vnet myVnet --address-prefixes 10.0.0.0/24 --subnet mySubnet --subnet-prefixes 10.0.0.0/24
7683
```
77-
Refer to the Azure CLI [reference documentation](/cli/azure/mysql/flexible-server) for the complete list of configurable CLI parameters.
7884
85+
Refer to the Azure CLI [reference documentation](/cli/azure/mysql/flexible-server) for the complete list of configurable CLI parameters.
7986
8087
## Next steps
88+
8189
- Learn more about [networking in Azure Database for MySQL flexible server](./concepts-networking.md).
8290
- [Create and manage Azure Database for MySQL flexible server virtual network using Azure portal](./how-to-manage-virtual-network-portal.md).
83-
- Understand more about [Azure Database for MySQL flexible server virtual network](./concepts-networking-vnet.md#private-access-vnet-integration).
91+
- Understand more about [Azure Database for MySQL flexible server virtual network](./concepts-networking-vnet.md#private-access-virtual-network-integration).

articles/mysql/flexible-server/how-to-manage-virtual-network-portal.md

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -6,20 +6,19 @@ ms.author: sunaray
66
ms.service: mysql
77
ms.subservice: flexible-server
88
ms.topic: how-to
9-
ms.date: 9/21/2020
9+
ms.date: 1/18/2024
1010
---
1111

1212
# Create and manage virtual networks for Azure Database for MySQL - Flexible Server using the Azure portal
1313

1414
[!INCLUDE[applies-to-mysql-flexible-server](../includes/applies-to-mysql-flexible-server.md)]
1515

16-
1716
Azure Database for MySQL flexible server supports two types of mutually exclusive network connectivity methods to connect to your Azure Database for MySQL flexible server instance. The two options are:
1817

1918
- Public access (allowed IP addresses)
20-
- Private access (VNet Integration)
19+
- Private access (virtual network integration)
2120

22-
In this article, we will focus on creation of MySQL server with **Private access (VNet Integration)** using Azure portal. With Private access (VNet Integration), you can deploy your Azure Database for MySQL flexible server instance into your own [Azure Virtual Network](../../virtual-network/virtual-networks-overview.md). Azure Virtual Networks provide private and secure network communication. With private access, connections to the MySQL server are restricted to your virtual network. To learn more about it, refer to [Private access (VNet Integration)](./concepts-networking-vnet.md#private-access-vnet-integration).
21+
This article focuses on creation of MySQL server with **Private access (VNet Integration)** using Azure portal. With Private access (virtual network integration), you can deploy your Azure Database for MySQL flexible server instance into your own [Azure Virtual Network](../../virtual-network/virtual-networks-overview.md). Azure Virtual Networks provide private and secure network communication. With private access, connections to the MySQL server are restricted to your virtual network. To learn more about it, refer to [Private access (virtual network Integration)](./concepts-networking-vnet.md#private-access-virtual-network-integration).
2322

2423
>[!Note]
2524
>You can deploy your Azure Database for MySQL flexible server instance into a virtual network and subnet during server creation. After the Azure Database for MySQL flexible server instance is deployed, you cannot move it into another virtual network, subnet or to *Public access (allowed IP addresses)*.
@@ -61,5 +60,5 @@ To create an Azure Database for MySQL flexible server instance in a virtual netw
6160
## Next steps
6261

6362
- [Create and manage Azure Database for MySQL flexible server virtual network using Azure CLI](./how-to-manage-virtual-network-cli.md).
64-
- Learn more about [networking in Azure Database for MySQL flexible server](./concepts-networking.md)
65-
- Understand more about [Azure Database for MySQL flexible server virtual network](./concepts-networking-vnet.md#private-access-vnet-integration).
63+
- Learn more about [networking in Azure Database for MySQL flexible server](./concepts-networking.md).
64+
- Understand more about [Azure Database for MySQL flexible server virtual network](./concepts-networking-vnet.md#private-access-virtual-network-integration).

0 commit comments

Comments
 (0)