Good day @scal74 Note: I cannot publish a full explanation since the QnA has a bug which prevent publishing answers which are not very short. I will split my short answer and put some part in the comment. Before discussion the error and what you can do, I have to clarify something since it seems like you have huge misconception about what bacpac is or isn't. **bacpak has nothing to do with restoring a database or with DR (Disaster Recovery) solution!** You cannot restore a database using bacpac. A DR solution provides a way to return to exact point-in-time from all aspects. For example, if you use backup and restore then you restored database will be exactly as it was in the point-of-time of the backup. If at that time the database was corrupted then the restored database will be the same with the same corruption, and if at the time of the backup there were uncommitted transactions in the log file then these will be in the backup file and will be restored... A bacpac is a copy of the schema and data, and nothing else. It does not take us to the point-in-time but provide simple information only about the schema and data in the time we created the file (and only the entities which we selected to store their data) **IT IS A HUGE DIFFERENT** so never speak about restoring a database using bacpac. what you do is a copy of the database. bacpac is a way to copy a database (schema / data) fully or partially. Back to the issue and what next... **Option 1** (best option): check if you have a backup of the database! Azure Databases are automatically backuped and you can restore the backup to a new database. Azure Databases create full backups every week, differential backups every 12-24 hours, and transaction log backups every 5 to 10 minutes. [You can read more about Azure automatic backup in this document][1]. In short: You do not have a direct control on the backup files, but you can use these files to restore the database to any point-in-time as long as the backup still exists. Notice that you can restore the backup as new database. **Option 2:** ONLY IF OPTION ! DOES NOT FIT... if you do not have any backup of the database which fit your needs, and the database is not online now or you must have a copy of whjat you have in specific time in the past (and you do not have the option to go back in time to re-create a good solution) - in short, you must use this specific bacpac file, then you can edit the bacpak file manually and remove the problematic entity from the bacpak file before you use it. by the way, Just few days ago on May 24, [I had a lecture at PASS organization local user group about this exact topic][2], but it is in Hebrew so I have no idea how useful it can be for you. It could provide you full understanding and explanation on what are your options and how tio "fix" the bacpac file. For future cases, you should pre-design your solution. There are multiple option which can help different scenario of copy data and schema, sync data, keep replication of the database, and so on For example these solutions are related to the topic, depending on your exact needs (This is one slide out of 2 which show the list of options and there are more options): ![9705-inside-bacpac-files-ronen-ariely-v01.png][3] [1]: https://docs.microsoft.com/en-us/azure/azure-sql/database/automated-backups-overview?tabs=single-database [2]: https://youtu.be/1VMUuXk7oFY [3]: /answers/storage/temp/9705-inside-bacpac-files-ronen-ariely-v01.png