Configure network connectivity for Microsoft Azure SQL Managed Instance sources

This page describes how to configure network connectivity for Microsoft Azure SQL Managed Instance sources for homogeneous migrations to Cloud SQL for MySQL migrations with Database Migration Service. There are several methods you can use:

You can also use a reverse-SSH tunnel, but this approach requires creating additional Virtual Machines (VMs) to host the necessary network components.

Configure Private Service Connect interfaces

To use private connectivity with Private Service Connect interfaces for Microsoft Azure SQL Managed Instance sources, follow these steps:

  1. Set up direct connectivity with Cloud VPN from Google Cloud to your source VPC.

    Depending on your network architecture, you might need to set up additional VPN gateways in your system. For more information, see Create HA VPN connections between Google Cloud and Azure in the Cloud VPN documentation.

  2. Create a destination Cloud SQL instance enabled for Private Service Connect. See Create a Private Service Connect-enabled instance in the Cloud SQL documentation.
  3. Configure Private Service Connect for outbound connectivity on your instance. At a high level, this process involves:
    1. Creating a network attachment in the VPC network where you set up your Cloud VPN. Note that the subnet range reserved for the network attachment must be within RFC 1918 range.
    2. Assigning the network attachment to your destination Cloud SQL for MySQL instance.

    For the full process, see Configure outbound connectivity in the Cloud SQL documentation.

  4. At a later stage, when you create the source connection profile enter the private IP of your Microsoft Azure SQL Managed Instance source.
  5. When you create the migration job select PSC interface for your connectivity method.

Configure VPC peering

To use private connectivity with Virtual Private Cloud peering for Microsoft Azure SQL Managed Instance sources, follow these steps:

  1. Set up direct connectivity with Cloud VPN to your Microsoft Azure SQL Managed Instance source.

    For more information, see Create HA VPN connections between Google Cloud and Azure in the Cloud VPN documentation.

    Ensure the Virtual Private Cloud network is configured for private services access. For more information, see Configure private services access.

  2. Make sure your destination Cloud SQL instance is configured to use a private IP with Private Service Access (PSA) and peered with the VPC where you have your Cloud VPN. For more information, see Use private IP in the Cloud SQL documentation.
  3. At a later stage, when you create the source connection profile enter the private IP of your Microsoft Azure SQL Managed Instance source.
  4. When you create the migration job select VPC Peering for your connectivity method.

Configure IP allowlist connectivity

To use the public IP allowlist connectivity method for Microsoft Azure SQL Managed Instance sources, follow these steps:

  1. Enable public IP for your destination Cloud SQL instance. Enable public IP in the Cloud SQL documentation.

    If you are migrating to a new destination instance, make sure to create the destination with a public IP enabled.

  2. Configure your source Microsoft Azure SQL Managed Instance to allow public network access from the public IP of your destination Cloud SQL instance.

    For more information, see Change public network access in the Microsoft documentation.

  3. At a later stage, when you create the source connection profile use your instance's fully qualified server name for the source database IP.

    For more information about how to view the connection details of your Microsoft Azure SQL Managed Instance instance, see Get server connection information in the Microsoft documentation.

  4. When you create the migration job select IP allowlist for your connectivity method.

What's next