Merge pull request #271015 from apduvuri/migratedoc-03042024

added the limitation in the known issue and added the migration service

Author: prmerger-automator[bot]

articles/postgresql/migrate/migration-service/concepts-known-issues-migration-service.md

@@ -39,6 +39,8 @@ Here are common limitations that apply to migration scenarios:
 
 - The migration service doesn't support superuser privileges and objects.
 
+- Azure Database for PostgreSQL - Flexible Server does not support the creation of custom tablespaces due to superuser privilege restrictions. During migration, data from custom tablespaces in the source PostgreSQL instance is migrated into the default tablespaces of the target Azure Database for PostgreSQL - Flexible Server.
+
 - The following PostgreSQL objects can't be migrated into the PostgreSQL flexible server target:
     - Create casts
     - Creation of FTS parsers and FTS templates

articles/postgresql/migrate/migration-service/concepts-user-roles-migration-service.md

@@ -16,7 +16,7 @@ ms.topic: conceptual
 > [!IMPORTANT]  
 > The migration of user roles, ownerships, and privileges feature is available only for the Azure Database for PostgreSQL Single server as the source. This feature is currently disabled for PostgreSQL version 16 servers.
 
-The service automatically provides the following built-in capabilities for the Azure Database for PostgreSQL single server as the source and data migration.
+The migration service automatically provides the following built-in capabilities for the Azure Database for PostgreSQL single server as the source and data migration.
 
 - Migration of user roles on your source server to the target server.
 - Migration of ownership of all the database objects on your source server to the target server.