PrepareSystemTables: Pending Preparing DAC metadata in the SQL Server instance '
PrepareSystemTables: Success Preparing DAC metadata in the SQL Server instance '
CreateDatabase: Pending Creating database 'eGovRestored'
CreateDatabase: Success Creating database 'eGovRestored'
ScriptDACObjects: Pending Preparing deployment script
ScriptDACObjects: Success Preparing deployment script
CreateLogin: Pending Creating login 'COMPANY\USER_NAME'
CreateLogin: Warning Creating login 'COMPANY\USER_NAME'
CreateDatabaseObjects: Pending Creating schema objects in database 'eGovRestored
CreateDatabaseObjects: Failure Creating schema objects in database 'eGovRestored
' Microsoft.SqlServer.Management.Common.ExecutionFailureException: An exception
occurred while executing a Transact-SQL statement or batch. ---> System.Data.Sql
Client.SqlException: 'COMPANY\USER_NAME' is not a valid login or you d
o not have permission.
I don't understand why it is trying to login using the COMPANY\USER_NAME when I have provided it the username and password for SQL Azure DB.
That message pops up because when the DAC framework exports your database, it carries the logins with it. When importing, DAC will attempt to create a login that requires integrated security in SQL Azure. SQL Azure does not support integrated
security and therefore emits an error. Your .bacpac can still import successfully even after that error, however, that login will not be created.
Also, the latest version of the EXE is available here along with some references to additional resources: