We currently use Azure DevOps pipeline to manage our CI/CD, much like https://learn.microsoft.com/en-us/fabric/cicd/deployment-pipelines/pipeline-automation-fabric .
However, because not all Fabric REST Api's support Service Principal authentication, our CI/CD Pipeline has to use a service user account (with disabled MFA) to authenticate our requests to e.g. trigger a deployment https://learn.microsoft.com/en-us/rest/api/fabric/core/deployment-pipelines/deploy-stage-content?tab... .
Unfortunately the next version Azure Connect-AzAccount will no longer support MFA from July 2025 - see Upcoming breaking changes in Azure PowerShell | Microsoft Learn .
The impact of multifactor authentication on Azure PowerShell in automation scenarios | Microsoft Lea... is that this change will prevent it's use in automation tasks, and so users need to switch to using either a service principal, managed identity, or a federated identity.
Currently Service Principal authentication is not supported for the key Fabric REST Api calls needed for our CI/CD pipeline, for example deploying to stages, scheduling pipelines, invoking notebooks.
Please advise how we can prevent our automation pipelines breaking later this year?
We would expect service principals to have to be supported at some point in the future for deployment pipeline and for running notebooks and pipelines, but because I haven't been able to find this on e.g. What's new and planned for Fabric Data Engineering in Microsoft Fabric - Microsoft Fabric | Microsof... we now need urgently need clarity on the timescale.
on:
Case Sensitivity ragrdless of the connection type ...
frithjof_v
on:
Lakehouse SQL Analytics Endpoint snapshots