An Azure relational database service.
The article describes three approaches. The first is CREATE DATABASE ... AS COPY OF, which is particularly attractive for a large database because it avoids the lengthy BACPAC export/import process - configure connectivity to both servers, create a SQL login/user on the source with the required permissions, capture its SID, create the same login on the destination using that SID, and then execute CREATE DATABASE destination AS COPY OF sourceServer.sourceDatabase from the destination server. Azure performs the copy and you can monitor its progress through sys.dm_operation_status. The second option is active geo-replication, which involves creating a geo-secondary in another subscription and tenant and is might be the preferred choice when minimizing downtime is more important than simply making a copy, because changes can continue replicating until you are ready to cut over. However, cross-tenant geo-replication has limitations - particularly around Microsoft Entra-only authentication and private endpoints. The third option is SqlPackage BACPAC export/import, which works but is generally slower for a 1 TB database. To speed it up, you can try running SqlPackage from an Azure VM with SSD storage, accelerated networking, sufficient disk space, and preferably in the same region as the database.
If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.
hth
Marcin