You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Azure is pushing the Managed Identities for access to Storage Containers/Blobs now. Your product automatically appends a required credential, rightfully assuming a SAS token.
The new Managed Identities method, the MI is added without SQL Server knowledge. A credential is still created but while performing the backup a @credential is not needed, simply the URL.
Could you add this feature through a Parameter or other detection method?
It seems, on any managed instance version it forces the @credential to match the URL name, but in this case does not find a SAS method and the Azure MI rejects the backup. When Managed Identities is setup via Code or the Portal a @credential is not required and in this case fails.
Azure is pushing the Managed Identities for access to Storage Containers/Blobs now. Your product automatically appends a required credential, rightfully assuming a SAS token.
The new Managed Identities method, the MI is added without SQL Server knowledge. A credential is still created but while performing the backup a @credential is not needed, simply the URL.
Could you add this feature through a Parameter or other detection method?
It seems, on any managed instance version it forces the @credential to match the URL name, but in this case does not find a SAS method and the Azure MI rejects the backup. When Managed Identities is setup via Code or the Portal a @credential is not required and in this case fails.
Background Information:
https://techcommunity.microsoft.com/t5/azure-sql-blog/how-to-take-secure-on-demand-backups-on-sql-managed-instance/ba-p/3638369
The text was updated successfully, but these errors were encountered: