Public Preview: Support database-level managed identity (including FIC) in Create Database Scoped Credential T-SQL
- Feed
- Azure Updates · original
- Microsoft id
577491- Availability
- Preview: October 2026
- Tags
- Databases, Feature, Hybrid + multicloud
- First captured by us
- Microsoft last modified
Description
With database-level managed identity in Azure SQL Database, you can use a user-assigned managed identity for each database to query files in Azure Blob Storage and Azure Data Lake Storage Gen2 through external tables and OPENROWSET. You can authenticate these queries without storing shared access signature (SAS) tokens or relying on a shared server-level identity.
By assigning separate identities and storage permissions to your databases, you can limit each database to the data it needs—for example, granting your HR database access to HR files and your finance database access to finance files. This helps you isolate access across databases on the same logical server and reduces secret-management overhead, while retaining familiar T-SQL queries over external data.
Learn more.
Quoted from Azure Updates (source). Reproduced for reporting and archival purposes.
What Microsoft changed
We have seen one version of this item so far. If Microsoft edits it, the earlier version stays here with the difference highlighted.