We would like to request support for Azure DevOps as a remote Git provider in the Version Control functionality of FME Flow.
One of our clients recently upgraded from FME Flow 2024.2.1 to FME Flow 2025.1.2. In the previous version, they were successfully using Azure DevOps Git repositories to manage workspace versioning. After the upgrade, they are no longer able to push changes to their remote repository. The UI reports: “There was a problem communicating with the REST API.”
And the backend logs show HTTP 500 errors when attempting to push.
- According to the documentation, only GitHub.com is officially supported.
- Azure DevOps is not listed, although it previously worked without issue.
- This limitation significantly impacts their ability to maintain version history and collaborate effectively.
Could you please consider:
- Adding official support for Azure DevOps Git repositories in FME Flow Version Control.
- Providing documentation or configuration guidance for Azure DevOps integration.
- Ensuring compatibility with common enterprise Git platforms beyond GitHub.com.
This feature would be highly valuable for organizations using Microsoft and would align FME Flow with broader enterprise DevOps practices.
Please let us know if this request will be considered for a future release and if so, in which upcoming release.
Thank you for your support!
Kind regards,
Joëlle Jansen-Soepenberg
FME Consultant
