Update POST.md

docs/en/Community-Articles/2023-03-16-Migration-Abp.io-Azure/POST.md

@@ -16,7 +16,7 @@ The decision to move to the cloud was made to eliminate the disadvantages of the
 
 ### Before Moving to Azure
 
-Before migrating to Azure, we decided to switch our database from MSSQL to PostgreSQL on-premise first. This gave us the opportunity to test and fine-tune the migration process before making the final switch to Azure.You can check the details of database migration from this article [Migrating from MS-SQL to Postgresql](https://github.com/abpframework/abp/blob/dev/docs/en/Community-Articles/2023-03-15-Migration-Mssql-Postgresql/POST.md).
+Before migrating to Azure, we decided to switch our database from MSSQL to PostgreSQL on-premise first. This gave us the opportunity to test and fine-tune the migration process before making the final switch to Azure.You can check the details of database migration from this article [Migrating from MS-SQL to Postgresql](https://community.abp.io/posts/migrating-from-mssql-to-postgresql-lbi5anlv).
 
 Before moving to Azure, the platform was tested in the staging environment. The staging environment was created on Azure to test the migration process. The staging environment was created with the same resources as the production environment. The staging environment was used to test the migration process and to optimize the migration process. The staging environment was also used to test the migration of the data from the old platform to Azure. The migration of the data from the old platform to Azure was tested several times to ensure that the migration process was successful.