Storage Account with MS Entra ID not working with external repositories

[harbinger]

Hi all

Since 12.1 brought the feature to use MS Entra ID Account for storage account authentication I've been switching the old SAS Keys to the new method and for a VBR Repository it's working great so far.
I wanted to get rid of the old SAS credentials and disable the SAS option on the storage accounts but I've noticed they're still being used for the external Repositories which are configured on the VBA Appliance which I've connected to the VBR Server. I'm not even able to select these new credentials when wanting to connect the external repository to VBR, only the old credentials with SAS Key are available. As far as I know VBA is also using the Entra ID App to connect to storage accounts, or is this a known limitation for the external repositories? I cannot seem to find anything about this restriction in the official documentation: https://helpcenter.veeam.com/docs/backu ... ml?ver=120

Best Regards
Philipp

[Mildur]

Hi Philipp

I believe it was not yet implemented for external repositories. Let me discuss it with the team.

Best,
Fabian

[WestieDave]

Looking to do exactly the same so I can remove shared key access from the Storage accounts in Azure - given that MS do not recommend this for security. Currently the external repo storage account and the worker storage accounts are set to use shared key, and it would be great if I could switch these too.

We're on 12.3.2 and I've moved across the backup Repo OK but external repo still does not recognise or allow the Entra ID credentials.

Is there any update on whether this will happen in 12 or is it only available in 13?

Thanks.

[nielsengelen]

Hi,

This is indeed not available yet but is planned for a future version of v13. I cannot provide a specific ETA yet though.