Service Principal Git Integration Fails When Added via AD Group but Works with Direct Assignment

Thankyou  GilbertQ   for Addressing the issue.

Hi chiranjeevira07   , 

Thank you for reaching out to Microsoft Fabric Community Forum,Based on the information provided, please verify the following steps.

1. Ensure the service principal is added directly to the Fabric workspace and has the required workspace role Admin Access.
2. Verify that the Azure DevOps cloud connection is configured correctly and is associated with the same service principal.
3. Confirm that Git integration is configured using the supported service principal authentication method.

   From your testing, the service principal works when added directly to the workspace but fails when its access is inherited through a Microsoft Entra ID (Azure AD) security group. At this time, Microsoft documentation does not explicitly state whether this scenario is supported or unsupported.

For reference, you can review the following Microsoft documentation:

• Git Integration with Service Principal - Microsoft Fabric | Microsoft Learn
•  Automate git integration with a service principal in Azure DevOps - Microsoft Fabric | Microsoft Learn
•  Get started with Git integration - Microsoft Fabric | Microsoft Learn

If the issue continues even after verifying the above, please  the Activity ID, Request ID, Correlation ID, Timestamp (UTC), Workspace ID, and Tenant ID, along with screenshots of the error and raise a support ticket 

Thanks,

Chaithanya.