Update ws with incoming repo wh change with SPN not working

[datawithb]

I have a blocker on a automation project we are trying to implement for a customer, in the documentation it is unclear if a SPN can utilize the GIT API to update a incoming change. Some pages on Microsoft Learn suggest that you can and some says that you cant. In the reddit post a Microsoft employee suggests that this should be working 4 months ago, so is this a bug that has not been picked up yet or can someone from Microsoft bring som clarity regarding this?

This is the error I am getting when trying to update the ws with a SPN in postman: 

This is the endpoint: Git update endpoint learn page 

This section potentially says that an update is possible: https://learn.microsoft.com/en-us/rest/api/fabric/articles/item-management/item-management-overview

This clearly says that its not possible: https://learn.microsoft.com/en-us/fabric/data-warehouse/service-principals#limitations

Microsoft fabric subreddit with similar thread where Microsoft employee says it should be working: Microsoft Fabric subreddit wh issue

[V-yubandi-msft]

Hi @datawithb ,

May I know the status of your issue? Have you shared your requirement in the Ideas forum. If not yet, please do the team reviews submitted ideas and considers them for future updates based on community demand.

Thank you.

[V-yubandi-msft]

Hi @datawithb ,

May I know if your issue has been resolved, or if you still need any additional details? Please let us know if you need any further assistance.
 

Thank you.

[datawithb]

Hello! No this issue is not resolved. This is still something that needs to be added for automation purposes twoards a warehouse object. We have other dependencies + different structure, so a dacpac solution wont work. 

[V-yubandi-msft]

Hi @datawithb ,
At the moment, Service Principals aren’t supported for Warehouse Git operations or item updates  this is confirmed in the official Fabric documentation.

We understand that using dacpac isn’t ideal since you have continuous version control in place. I’d recommend sharing this scenario in the Fabric Ideas forum so the product team can review it for future updates.
Link: Fabric Ideas - Microsoft Fabric Community

Regards,
Yugandhar.

[KevinChant]

One workaround for thisis to update your Warehouse with a state-based (dacpac) deployment instead. Which will also help you keep your Warehouse updates isolated in case you perform updates you suspect will introduce braking changes.

I hope this helps.

[datawithb]

Hello Kevin! Thanks for you reply. This would make sense if we did not have version controll activated at all times against our prod and dev workspaces. 

[V-yubandi-msft]

Hi @datawithb ,

Thanks for providing the detailed context.
According to the current documentation here: Fabric Service Principals – Limitations.

Service Principals are not yet supported for Warehouse Git or item updates. Other Fabric items, such as Lakehouses, Notebooks, or Data Pipelines, may support Service Principals.

The reference in the Item Management API overview to updates being possible applies to Fabric items in general, but not all resource types currently support SPNs.

For your information, the Reddit link you shared isn’t accessible.

At this time, the official Microsoft documentation should be considered the reliable source.

Regards,
Yugandhar.