Forum Discussion

JAnder's avatar
JAnder
Helper II
9 months ago
Solved

Create Git Credentials for DevOps Repo

We work in a multi-tenanted environemt so we have over 100 workspaces. For this reason, we manage most tasks through the Rest APIs with a service principal. This means the principal also owns everyth...
Need Help
  • v-karpurapud's avatar
    v-karpurapud
    8 months ago

    Hi JAnder 

    As of now the Fabric CLI does not provide a way to create a new Azure DevOps Git integration or configure Azure DevOps credentials under a service principal. While the CLI supports service principal authentication, it ultimately calls the same public REST APIs as the SDK and therefore inherits the same limitation: the initial Git credential setup for Azure DevOps must be performed interactively through the Fabric UI under a user identity.
    The CLI can still be valuable after the Git connection has been created in the UI, as it enables automation for tasks such as syncing, checking Git connection status, and managing workspace configurations across multiple tenants in a scriptable and consistent way. However, it cannot replace or bypass the UI-based credential configuration step.

    Regards,

    Microsoft Fabric Community Support Team.

KevinChant's avatar
KevinChant
Super User
9 months ago

Have you considered leveraging the Fabric CLI to do this instead? So that it can authenticate with each tenant first and then use the fab API commands for you.

JAnder's avatar
JAnder
Helper II
8 months ago

KevinChant Are there any docs or can you elaborate a little? If I could run the commands against a CLI to set up the integations and have them owned by the principal that would be good, but I thought we needed to use either UI or API for that.

  • v-karpurapud's avatar
    v-karpurapud
    Community Support
    8 months ago

    Hi JAnder 

    As of now the Fabric CLI does not provide a way to create a new Azure DevOps Git integration or configure Azure DevOps credentials under a service principal. While the CLI supports service principal authentication, it ultimately calls the same public REST APIs as the SDK and therefore inherits the same limitation: the initial Git credential setup for Azure DevOps must be performed interactively through the Fabric UI under a user identity.
    The CLI can still be valuable after the Git connection has been created in the UI, as it enables automation for tasks such as syncing, checking Git connection status, and managing workspace configurations across multiple tenants in a scriptable and consistent way. However, it cannot replace or bypass the UI-based credential configuration step.

    Regards,

    Microsoft Fabric Community Support Team.