We are happy to announce that User Managed Identity support for Auditing Azure SQL Database is now Generally available.
Auditing for Azure SQL database has started supporting User Managed Identity. Auditing can be configured to Storage account using two authentication methods, managed identity, and storage access keys. For managed identity you can use system managed identity or user managed identity. To know more about UMI in azure refer here.
To configure writing audit logs to a storage account, select Storage when you get to the Auditing section. Select the Azure storage account where logs will be saved, you can use two storage authentication types i.e., managed identity and storage access keys.
For managed identity, we support system and user managed identity.
By default, it picks primary user identity assigned to the server, and if there is no user identity, it will create system assigned identity and use it for authentication.
select the retention period by opening Advanced properties. Then click Save. Logs older than the retention period is deleted.
UMI gives User flexibility to create and maintain their own UMI for a given tenant. UMI can be used as server identities for Azure SQL. UMI is managed by the user, compared to SMI, which identity is uniquely defined per server, and assigned by the system.
For more information about UMI, please refer to User-assigned managed identity (UMI) in Azure AD for Azure SQL - Microsoft Community Hub
https://techcommunity.microsoft.com/t5/azure-sql-blog/user-managed-identity-support-for-auditing-azu...
