Skip to content

Commit 5051d2a

Browse files
committed
Address the warnings
1 parent a9e58e8 commit 5051d2a

File tree

4 files changed

+5
-5
lines changed

4 files changed

+5
-5
lines changed

articles/postgresql/migrate/migration-service/how-to-network-setup-migration-service.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -154,7 +154,7 @@ Completing these steps enables the Azure Database for PostgreSQL - Flexible Serv
154154

155155
## Scenario 8: Azure Database for PostgreSQL single server with private endpoint to Azure Database for PostgreSQL flexible server with private endpoint
156156

157-
Below are the essential networking steps for migrating from a Single Server with a private endpoint to a Flexible Server with a private endpoint in Azure PostgreSQL, including the integration of a runtime server's virtual network with private endpoint configurations.
157+
Below are the essential networking steps for migrating from a Single Server with a private endpoint to a Flexible Server with a private endpoint in Azure PostgreSQL, including the integration of a runtime server's virtual network with private endpoint configurations. For more information about the Runtime Server, visit the [Migration Runtime Server](concepts-migration-service-runtime-server.md).
158158

159159
- **Gather Private Endpoint Details for Single Server**
160160
- Access the Azure portal and locate the Azure Database for PostgreSQL - Single Server instance.
@@ -192,7 +192,7 @@ Below are the essential networking steps for migrating from a Single Server with
192192

193193
## Scenario 9: On-Premises, Azure VM, AWS RDS with private IPs to Azure Database for PostgreSQL flexible server with private endpoint
194194

195-
Below are the networking steps for migrating a PostgreSQL database from an on-premises environment, Azure VM, or AWS instance—all of which are configured with private IPs—to an Azure Database for PostgreSQL Flexible Server that is secured with a private endpoint. The migration ensures secure data transfer within a private network space, using Azure's VPN or ExpressRoute for on-premises connections and virtual network peering or VPN for cloud-to-cloud migrations.
195+
Below are the networking steps for migrating a PostgreSQL database from an on-premises environment, Azure VM, or AWS instance—all of which are configured with private IPs—to an Azure Database for PostgreSQL Flexible Server that is secured with a private endpoint. The migration ensures secure data transfer within a private network space, using Azure's VPN or ExpressRoute for on-premises connections and virtual network peering or VPN for cloud-to-cloud migrations. For more information about the Runtime Server, visit the [Migration Runtime Server](concepts-migration-service-runtime-server.md).
196196

197197
- **Establish Network Connectivity:**
198198
- For on-premises sources, set up a Site-to-Site VPN or ExpressRoute to connect your local network to Azure's virtual network.

articles/postgresql/migrate/migration-service/tutorial-migration-service-aws-offline.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -141,7 +141,7 @@ After selecting the databases, select the **Next: Summary**
141141

142142
The Summary tab summarizes all the source and target details for creating the validation or migration. Review the details and select the Start Validation and Migration button.
143143

144-
:::image type="content" source="media/tutorial-migration-service-aws-offline/04-portal-offline-select-migration-target-aws.png" alt-text="Screenshot of the summary migration page.":::
144+
:::image type="content" source="media/tutorial-migration-service-aws-offline/06-portal-offline-summary-aws.png" alt-text="Screenshot of the summary migration page.":::
145145

146146
### Monitor the migration
147147

articles/postgresql/migrate/migration-service/tutorial-migration-service-iaas-offline.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -248,7 +248,7 @@ To begin the migration, create a JSON file with the migration details. The JSON
248248
```
249249

250250
> [!NOTE]
251-
> When configuring the JSON properties for the migration to Azure Database for PostgreSQL Flexible Server, if your source environment is an Azure Virtual Machine, you can specify the source type using the `"sourceType":"AzureVM"` property. This helps the migration service understand the environment from which the data is being migrated.
251+
> When configuring the JSON properties for the migration to Azure Database for PostgreSQL Flexible Server, if your source environment is an Azure Virtual Machine, you can specify the source type using the `"sourceType":"AzureVM"` property. This helps the migration service understand the environment from which the data is being migrated.
252252
253253
- Run the following command to check if any migrations are running. The migration name is unique across the migrations within the Azure Database for PostgreSQL flexible server target.
254254

articles/postgresql/migrate/migration-service/tutorial-migration-service-iaas-online.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -246,7 +246,7 @@ To begin the migration, create a JSON file with the migration details. The JSON
246246
```
247247

248248
> [!NOTE]
249-
> When configuring the JSON properties for the migration to Azure Database for PostgreSQL Flexible Server, if your source environment is an Azure Virtual Machine, you can specify the source type using the `"sourceType":"AzureVM"` property. This helps the migration service understand the environment from which the data is being migrated.
249+
> When configuring the JSON properties for the migration to Azure Database for PostgreSQL Flexible Server, if your source environment is an Azure Virtual Machine, you can specify the source type using the `"sourceType":"AzureVM"` property. This helps the migration service understand the environment from which the data is being migrated.
250250
251251
- Run the following command to check if any migrations are running. The migration name is unique across the migrations within the Azure Database for PostgreSQL flexible server target.
252252

0 commit comments

Comments
 (0)