This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreDid you hear? There's a new SQL AI Developer certification (DP-800). Start preparing now and be one of the first to get certified. Register now
Microsoft Fabric Workspace Identity is positioned as a secure, secretless authentication mechanism for Fabric workloads. However, Fabric Notebooks currently cannot acquire Azure Resource Manager (ARM) access tokens (https://management.azure.com) using Workspace Identity via notebookutils.credentials.getToken().
This limitation prevents Fabric notebooks—whether executed interactively or via pipelines—from calling ARM APIs for essential operations such as:
The behavior is consistent across execution modes and identity contexts and appears to be a by-design restriction, as ARM is not a supported token audience today.
The only functional workaround is to:
While technically viable, this approach:
This limitation significantly restricts real-world enterprise scenarios, including:
Customers adopting Fabric as a unified analytics and orchestration platform expect parity with Azure managed identity patterns, including secure ARM access without client secrets.
Enable native ARM token acquisition using Fabric Workspace Identity, for example:
This would align Fabric Workspace Identity with Azure Managed Identity capabilities and unlock critical governance and automation scenarios.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.