ImportExportJobError, SQL72012, SQL72014, SQL72045.

When trying to Import .bacpac file via Azure Portal, it fails with below error:

  'code': 'ImportExportJobError',

  'message': 'The ImportExport operation with Request Id '' failed due to 'The ImportExport operation with Request Id '' failed due to 'Could not import package.\\nWarning SQL72012: The object [data_0] exists in the target, but it will not be dropped even though you selected the 'Generate drop statements for objects that are in the target database but that are not in the source' check box.\\nWarning SQL72012: The object [log] exists in the target, but it will not be dropped even though you selected the 'Generate drop statements for objects that are in the target database but that are not in the source' check box.\\nError SQL72014: Framework Mi'.'.'

The DAC framework hit a hard error and failed due to conflicts with existing system objects in the target database. The generated error does not show much information, except a Warning without enough detail to pinpoint the root cause.

⚠️ What the warnings mean (SQL72012)

The object [data_0] exists in the target, but it will not be dropped…

The object [log] exists in the target, but it will not be dropped…

Retrying the import from the portal doesn’t help—the job fails consistently with the same outcome.

To understand the exact cause of error, you can use SQLPackage.exe tool and follow steps below:

1. Download SqlPackage for Windows.
2. To extract the file by right clicking on the file in Windows Explorer, and selecting 'Extract All...', and select the target directory.
3. Open a new Terminal window and cd to the location where SqlPackage was extracted:

Import:

sqlpackage.exe /Action:Import /tsn:ServerName.database.windows.net /tdn:sqlimporttestDB /tu:sql-user /tp:password /sf:"C:\test\DB-file.bacpac" /d:True /df:C:\test\df.txt

TSN: Target server name, where the database will be imported.

Tdn: Target database name, the name of the new database that will be created.

Tu: user

Tp: password

Sf: source file, where the bacpac file is located.

d: diagnostic, this parameter will help us to obtain detailed information for the import/export process.

Df: where the diagnostic file will be saved and the name of it, please change the folder location to the same used on the source file.

Note: .bacpac file needs to be present locally on your machine for this command.

In the diagnostic file generated, we got a clear error indicating that Script "CREATE USER [EntraUser1@contoso.com] FOR EXTERNAL PROVIDER" failed to execute and only connections established with Entra accounts can create other Entra users.

Microsoft.Data.Tools.Diagnostics.Tracer Error: 0 : 2026-01-22T06:56:50 : Error encountered during import operation

 Exception: Microsoft.SqlServer.Dac.DacServicesException: Could not import package.

Error SQL72014: Core Microsoft SqlClient Data Provider: Msg 33159, Level 16, State 1, Line 1 Principal 'EntraUser1@contoso.com' could not be created. Only connections established with Active Directory accounts can create other Active Directory users.

Error SQL72045: Script execution error.  The executed script:

CREATE USER [EntraUser1@contoso.com] FOR EXTERNAL PROVIDER;

You’ll also notice the database gets created, but none of the schema or tables are deployed—leaving you with an online but completely blank database.

SSMS shows the same behavior, the database appears online after creation, but the import ultimately fails and the resulting database is empty.

When explicitly executing this script in database, you'll face the exact same error:

If the source database contains only Contained Entra users, you typically won’t see this issue. For contained users, the import job uses a different user-creation script—one that can be executed even when the import connection is established using SQL authentication.

CREATE USER [EntraUser2@contoso.com]
    WITH SID = 'User-SID-Here' , TYPE = E;

The issue occurs when the Exported database contains Entra Server logins and a corresponding User is created in the User Database.

To mitigate this issue:

• You need to initiate the Import request using Microsoft Entra Account since SQL Authentication account cannot create a user from an External Provider which is Microsoft Entra in this case.

• Make the Entra Users 'Contained' in User Database before exporting and then use SQL Authentication account for importing the DB.

The second option is especially useful if you prefer importing through the Azure portal but your Entra account has MFA enforced. In that case, using SQL authentication for the import workflow can be a practical path forward.

REFERENCES:

Import a BACPAC File to Create a Database in Azure SQL Database - Azure SQL Database & Azure SQL Managed Instance | Microsoft Learn

SqlPackage Import - SQL Server | Microsoft Learn