Forum Discussion
Microsoft Fabric API Authentication & Deployment Issue | Azure DevOps Pipeline
Hi Sukiazure007 ,
Thank you for the update.
1. To prevent manual token generation, utilize certificate-based authentication or Managed Identity rather than a service account.
Please ensure the application is correctly registered in Microsoft Entra ID.
Please assign Workspace.ReadWrite.All and Workspace.GitUpdate permissions.
Reference: Apps & service principals in Microsoft Entra ID - Microsoft identity platform | Microsoft Learn
2. After deploying from Git, the connections still point to the DEV environment instead of updating dynamically.
Grant the Connections.ReadWrite.All permission to the registered application.
After deploying from Git, use the Connections API to update connection settings dynamically.
If permission issues persist, verify the role assignments in the Fabric Admin Portal under Manage Workspaces.
I hope this helps streamline token generation and automate connection updates after deployment.
Dear Team,
Apologies for the delayed response. Currently, I am using the service account for the updateFromGit process, and while the deployment itself is successful, we are facing two key challenges:
- Access Token Issue – The pipeline requires a manually generated access token each time. Despite MFA being disabled, it seems interactive login is not supported, causing an automation bottleneck.
- Connection Configuration Post-Deployment – After deployment from Git, all connections are still pointing to the DEV environment. We plan to use the Connections API to update them dynamically, but we are facing permission restrictions. Adding Connections.ReadWrite.All should help resolve this.?
Could you please advise on potential solutions for both issues? Your support would be greatly appreciated.
Hi Sukiazure007 ,
Thank you for the update.
1. To prevent manual token generation, utilize certificate-based authentication or Managed Identity rather than a service account.
Please ensure the application is correctly registered in Microsoft Entra ID.
Please assign Workspace.ReadWrite.All and Workspace.GitUpdate permissions.
Reference: Apps & service principals in Microsoft Entra ID - Microsoft identity platform | Microsoft Learn
2. After deploying from Git, the connections still point to the DEV environment instead of updating dynamically.
Grant the Connections.ReadWrite.All permission to the registered application.
After deploying from Git, use the Connections API to update connection settings dynamically.
If permission issues persist, verify the role assignments in the Fabric Admin Portal under Manage Workspaces.
I hope this helps streamline token generation and automate connection updates after deployment.
Thanks, #02 - Will test with the permission Connections.ReadWrite.All and update here in couple of days. #01 --> Git - Update From Git - REST API (Core) | Microsoft Learn --> As per the article service principal are not supported for this API, still will i able to automate this process in pipeline?
Hi Sukiazure007 ,
1. To avoid manual token generation, please use certificate-based authentication or Managed Identity instead of a service account.
Ensure that the application is properly registered in Microsoft Entra ID.
Reference: Apps & service principals in Microsoft Entra ID - Microsoft identity platform | Microsoft Learn
Please assign Workspace.ReadWrite.All and Workspace.GitUpdate permissions.
2. Upon deployment from Git, the connections still point to the DEV environment instead of updating dynamically.
Please grant the Connections.ReadWrite.All permission to the registered application.
After deploying from Git, use the Connections API to update connection settings dynamically.
If permission issues persist, verify the role assignments in the Fabric Admin Portal under Manage Workspaces.
I hope this helps streamline token generation and automate connection updates after deployment.