Hello @LeonT !
Welcome to Microsoft QnA!
I can see your issue with SQL been there trust me !
First of all
have you seen the Limitations :
- Importing to a database in elastic pool isn't supported. You can import data into a single database and then move the database to an elastic pool.
- Import Export Service does not work when Allow access to Azure services is set to OFF. However you can work around the problem by manually running SqlPackage from an Azure VM or performing the export directly in your code by using the DacFx API.
- Import does not support specifying a backup storage redundancy while creating a new database and creates with the default geo-redundant backup storage redundancy. To work around, first create an empty database with desired backup storage redundancy using Azure portal or PowerShell and then import the .bacpac into this empty database.
- Storage behind a firewall is currently not supported.
- During the import process, do not create a database with the same name. The import process creates a new database of the specified name
Second , in my env it worked from the Sql Management Studio select deploy to Azure SQL .... it was the only way it worked correctly !
I hope this helps!
Kindly mark the answer as Accepted and Upvote in case it helped!
Regards