Hi PS •,
Welcome to Microsoft Q&A forum.
As I understand, you want to perform restoration of Azure SQL Managed Instance from one server to another in the same subscription.
Please refer to the below documentations which has detailed explanation on how we can perform restore of Azure SQL MI:
https://learn.microsoft.com/en-us/azure/azure-sql/managed-instance/recovery-using-backups?view=azuresql&tabs=azure-portal
https://learn.microsoft.com/en-us/azure/azure-sql/managed-instance/restore-sample-database-quickstart?view=azuresql
https://stackoverflow.com/questions/60427576/restoring-database-in-azure-managed-instance-from-one-subscription-to-another
Consider the following limitations when working with backups and Azure SQL Managed Instance:
- Geo-restore of a database can only be performed to an instance in the same subscription as the source SQL managed instance.
- SQL Managed Instance databases can only be restored to SQL Server 2022 (either on-premises, or on a virtual machine) if the source SQL Managed Instance has enrolled in the November 2022 feature wave.
- SQL Managed Instance databases are encrypted with TDE by default. When the source database uses a customer-managed key (CMK) as the TDE protector, to restore your database to an instance other than the source SQL Managed Instance, the target instance must have access to the same key used to encrypt the source database in Azure Key Vault, or you must disable TDE encryption on the source database before taking the backup.
- You can only track the progress of the restore process by using the sys.dm_exec_requests and sys.dm_operation_status dynamic management views.
- When service endpoint policies are enabled on Azure SQL Managed Instance, placing a service endpoint policy on a subnet prevents point-in-time restores (PITR) from instances in different subnets.
Let us know if you face any issue in doing the same.
Thanks