[Feature Request] Restore of Azure SQL DBs via Entra ID identities

[timm.vollborn]

Hello Veeam R&D Team,

we set up Veeam Backup for Azure to backup / restore Azure workloads. Generally this works fine, however regarding Azure SQL DBs / Azure SQL Managed Instance SQL DBs we are only able to back them up, but are unable to restore them using Entra ID identities (service principal / admin user). When trying to run the restore option for Azure SQL DBs / Azure SQL Managed Instance SQL DBs there is simply no possibility to select an Entra ID service principal / admin user.

Together with the Veeam technical support (Case # 07574048), we were able to implement a workaround (restore using local SQL admin user), but for a more secure and modern approach, it would be great, if it were possible to use Entra ID identities to restore Azure SQL DBs / Azure Managed Instance SQL DBs so that admin users can be created / managed solely through Entra ID as an IAM-solution.

Best regards,
Timm

[nielsengelen]

Hi Timm,

We'll do some research on this and report back once we know more if there is a workaround or if this is something we'll have to consider for a future release.

[lyudmila.ezerskaya]

Hi!
Currently, in Veeam Backup for Microsoft Azure, Entra ID users cannot be used for SQL backups and restores.

We’ve added this as a feature request and will research the possibility of supporting it in future releases.

[timm.vollborn]

Hi Lyudmila,

thanks for the info, sounds good.

Best regards
Timm

[CarlosEsteves]

Is there any update on this feature request ?

[nielsengelen]

Hi,

This is still on the roadmap for a future improvement.

[bsmith25]

Hello

We have a customer who is backing up Azure SQL Databases using Veeam. The Databases are backing up fine; however, we have hit an issue with being unable to restore the data, as there are Entra ID entities within the databases, which causes the restore to fail

It seems stupid that the databases can be backed up perfectly fine, yet you have no option of restoring the data if Entra is used.

I'm raising a request to look at supporting Entra ID for Azure SQL databases

[PetrM]

Hi Ben and Welcome to Veeam R&D Forums!

Could you please clarify what method are you using to protect the databases? Are you talking about Veeam Backup for Microsoft Azure?

Thanks!

[nielsengelen]

Hi Ben,

I’ve merged your post with the ongoing topic about this. It is still on the roadmap to implement this.

[bsmith25]

Yes Veeam Backup for Microsoft Azure we are using

[navinr]

Hi Veeam,
We'd like to add a +1 for this request.
Our case number is 08132200. We were able to backup Azure SQL DBs with Entra ID objects however restoration to a new location resulted in the following errors:

Error SQL72014 (Msg 33159, Level 16, State 1): Principal '[User ID]' 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 [[User ID]] FOR EXTERNAL PROVIDER;

The backup taken using Veeam Backup for Azure completes successfully however we're unable to restore the backup.
Can this be looked into with some urgency please?

[nielsengelen]

Hi Navin,

Entra ID support is planned for our upcoming release which will be available very soon. For now, there is no direct workaround available.

[navinr]

Is there an ETA for the Entra ID support? We're at the tail end of deploying a Veeam solution with Veeam Vault for our customer and this has become a showstopper.