SQL Server & Data

Azure SQL Database Adds Public Preview for Database-Level Managed Identity

Azure SQL Database introduces a public preview supporting database-level managed identity in Create Database Scoped Credential T-SQL. Developers can now utilize a user-assigned managed identity per database to query cloud storage.

What changed From the source

A new public preview has been announced for Azure SQL Database that introduces support for database-level managed identity. This capability extends to Federated Identity Credentials (FIC) within Create Database Scoped Credential T-SQL statements.

With this update, administrators and developers can configure a user-assigned managed identity specifically for individual databases. This identity enables authentication when querying files residing in Azure Blob Storage and Azure Data Lake Storage Gen2.

  • Support added for database-level managed identity in Azure SQL Database.
  • Applies to Create Database Scoped Credential T-SQL.
  • Enables querying files via external tables and OPENROWSET.

At a glance · SQL Server & Data

What changedWhy it mattersWho should careUpgrade and migration considerations

Why it matters Analysis

This feature improves how database workloads authenticate against Azure storage services by removing the need to embed credentials directly into database scripts or configuration files. Utilizing user-assigned managed identities per database offers tighter security boundaries and simplifies credential lifecycle management for cloud-native data architectures.

  • Reduces secret management overhead by leveraging Azure managed identities.
  • Improves least-privilege security posture at the individual database level.

Who should care Analysis

Database administrators, backend engineers, and cloud architects working with Azure SQL Database, external tables, or OPENROWSET queries against Azure Blob Storage and Azure Data Lake Storage Gen2 should evaluate this preview. Teams looking for enhanced security controls for data ingestion and querying pipelines will find this particularly relevant.

  • Cloud architects designing secure data integration pipelines.
  • Developers managing Azure SQL Database external data sources.

Upgrade and migration considerations Analysis

Because this functionality is currently in public preview, it may not be suitable for production environments without thorough testing. The source material does not specify exact migration steps, timelines for general availability, or potential breaking changes, so teams should monitor official Azure documentation before adopting this feature in production workloads.

  • Feature is currently in public preview.
  • Migration steps and general availability dates are not specified by the source.

Sources and further reading

Original: “Public Preview: Support database-level managed identity (including FIC) in Create Database Scoped Credential T-SQL”, Azure Updates, published 30 Oct 2026, retrieved 30 Oct 2026. This article was drafted with AI assistance from the official source and passed automated fact and quality checks. Spotted a mistake? See our corrections policy.