Hi Jay,
you're right at the start of the migration and the tool won't even let you select your source server. this is a known limitation with the azure database migration service.
the azure database migration service is primarily designed for migrating from on premises databases or other clouds to azure. its support for moving data between two azure postgresql flexible servers, especially within the same subscription, is limited and often doesn't work as expected in the portal wizard.
for your specific scenario of moving from one flexible server to another, you should use a different method. the most reliable and recommended approach is to use logical replication with pg_dump and pg_restore.
first, use pg_dump with the --verbose --format=custom options to create a backup file of your source database. this creates a highly compressed, portable dump.
then, use pg_restore with the --verbose --clean --no owner --no privileges options to restore this dump into your target flexible server. this will copy all the schema and data.
this method gives you full control and is the standard way postgresql databases are moved, even within azure.
the database migration service tool is the wrong tool for this job. use the native postgresql pg_dump and pg_restore utilities to migrate your data between the two flexible servers.
regards,
Alex
and "yes" if you would follow me at Q&A - personaly thx.
P.S. If my answer help to you, please Accept my answer