From f1a10c71ffd9d50c4af9b11d708068afe41f9ba7 Mon Sep 17 00:00:00 2001 From: Hiroshi Yoshioka <40815708+hyoshioka0128@users.noreply.github.com> Date: Wed, 23 Oct 2024 00:19:18 +0900 Subject: [PATCH] =?UTF-8?q?Update=20how-to-manage-virtual-network-portal.m?= =?UTF-8?q?d=20(Typo=20"flexible=20server"=E2=86=92"Flexible=20Server")?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit https://github.com/MicrosoftDocs/azure-databases-docs/blob/main/articles/mysql/flexible-server/how-to-manage-virtual-network-portal.md #PingMSFTDocs --- .../how-to-manage-virtual-network-portal.md | 26 +++++++++---------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/articles/mysql/flexible-server/how-to-manage-virtual-network-portal.md b/articles/mysql/flexible-server/how-to-manage-virtual-network-portal.md index 1e9eae18d6..1a16add738 100644 --- a/articles/mysql/flexible-server/how-to-manage-virtual-network-portal.md +++ b/articles/mysql/flexible-server/how-to-manage-virtual-network-portal.md @@ -14,27 +14,27 @@ ms.topic: how-to [!INCLUDE[applies-to-mysql-flexible-server](../includes/applies-to-mysql-flexible-server.md)] -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: +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: - Public access (allowed IP addresses) - Private access (virtual network integration) -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](/azure/virtual-network/virtual-networks-overview). 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). +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](/azure/virtual-network/virtual-networks-overview). 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). >[!Note] ->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)*. +>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)*. ## Prerequisites -To create an Azure Database for MySQL flexible server instance in a virtual network, you need: +To create an Azure Database for MySQL Flexible Server instance in a virtual network, you need: - A [Virtual Network](/azure/virtual-network/quick-create-portal#create-a-virtual-network) > [!Note] - > The virtual network and subnet should be in the same region and subscription as your Azure Database for MySQL flexible server instance. + > The virtual network and subnet should be in the same region and subscription as your Azure Database for MySQL Flexible Server instance. -- To [delegate a subnet](/azure/virtual-network/manage-subnet-delegation#delegate-a-subnet-to-an-azure-service) 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. +- To [delegate a subnet](/azure/virtual-network/manage-subnet-delegation#delegate-a-subnet-to-an-azure-service) 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. -## Create an Azure Database for MySQL flexible server instance in an already existing virtual network +## Create an Azure Database for MySQL Flexible Server instance in an already existing virtual network 1. Select **Create a resource** (+) in the upper-left corner of the portal. 2. Select **Databases** > **Azure Database for MySQL**. You can also enter **MySQL** in the search box to find the service. @@ -44,7 +44,7 @@ To create an Azure Database for MySQL flexible server instance in a virtual netw 6. In the **Connectivity method**, select **Private access (VNet Integration)**. Go to **Virtual Network** section, you can either select an already existing *virtual network* and *Subnet* that is delegated to *Microsoft.DBforMySQL/flexibleServers* or create a new one by clicking the *create virtual network* link. > [!Note] > Only virtual networks and subnets in the same region and subscription will be listed in the drop down.
- > The chosen subnet will be delegated to *Microsoft.DBforMySQL/flexibleServers*. It means that only Azure Database for MySQL flexible server instances can use that subnet.
+ > The chosen subnet will be delegated to *Microsoft.DBforMySQL/flexibleServers*. It means that only Azure Database for MySQL Flexible Server instances can use that subnet.
:::image type="content" source="./media/how-to-manage-virtual-network-portal/vnet-creation.png" alt-text="Vnet-integration"::: @@ -52,14 +52,14 @@ To create an Azure Database for MySQL flexible server instance in a virtual netw > [!NOTE] > Private DNS zone names must end with `mysql.database.azure.com`.
> If you do not see the option to create a new private dns zone, please enter the server name on the **Basics** tab.
- > After the Azure Database for MySQL flexible server instance is deployed to a virtual network and subnet, you cannot move it to Public access (allowed IP addresses).
+ > After the Azure Database for MySQL Flexible Server instance is deployed to a virtual network and subnet, you cannot move it to Public access (allowed IP addresses).
:::image type="content" source="./media/how-to-manage-virtual-network-portal/private-dns-zone.png" alt-text="dnsconfiguration"::: -8. Select **Review + create** to review your Azure Database for MySQL flexible server configuration. +8. Select **Review + create** to review your Azure Database for MySQL Flexible Server configuration. 9. Select **Create** to provision the server. Provisioning can take a few minutes. ## Next steps -- [Create and manage Azure Database for MySQL flexible server virtual network using Azure CLI](./how-to-manage-virtual-network-cli.md). -- Learn more about [networking in Azure Database for MySQL flexible server](./concepts-networking.md). -- Understand more about [Azure Database for MySQL flexible server virtual network](./concepts-networking-vnet.md#private-access-virtual-network-integration). +- [Create and manage Azure Database for MySQL Flexible Server virtual network using Azure CLI](./how-to-manage-virtual-network-cli.md). +- Learn more about [networking in Azure Database for MySQL Flexible Server](./concepts-networking.md). +- Understand more about [Azure Database for MySQL Flexible Server virtual network](./concepts-networking-vnet.md#private-access-virtual-network-integration).