Skip to main content
Question

FME Flow 2025 upgrade and SharePointOnlineConnector authorisation

  • December 23, 2025
  • 3 replies
  • 81 views

scottmacdonald
Contributor
Forum|alt.badge.img+2

We recently upgraded to FME Flow 2025 but now all of our FME processes with SharePointOnlineConnectors are failing.

We have to keep going into FME Flow Connections and Parameters>Web Connections and re-authorise the Microsoft SharePointOnline connection. Is there a way to keep it authorised?

This is causing dozens of processes to fail daily because we keep having to re-authorise the connection.  I have been upgrading transformers and re-publishing the workbenches to FME Flow but wondered if this was an issue for anyone else and if there were any further suggestions.

Thanks in advance

Scott

3 replies

timatsafe
Safer
Forum|alt.badge.img+4
  • Safer
  • December 24, 2025

Hi ​@scottmacdonald,

If you can please submit a ticket so that our team can look into this further, that would be great!

When submitting your ticket, please provide the following (if available):

- Details about the environment used (e.g. platform and OS version, FME Flow deployment, any other dependencies, etc.)
- Any relevant log files (e.g. translation logs, job logs, fmeserver.log, etc.)
 

 


scottmacdonald
Contributor
Forum|alt.badge.img+2
  • Author
  • Contributor
  • January 5, 2026

Thanks for your reply and recommendation to submit a ticket.

Our processes were failing to connect to SharePoint however we managed to get them running again by upgrading all transformers (to FME 2025) and re-publishing the workbench to FME Flow (without ticking Emailer) and then re-authorised the SharePoint connection.

If you upgrade FME Flow then upgrade the FME Form workbenches and transformers as well and re-publish to FME Flow

 


ebygomm
Influencer
Forum|alt.badge.img+46
  • Influencer
  • January 5, 2026

What version of FME did you upgrade from?

We have a sharepoint connector in a workspace in a dev environment that was written in 2024 and it has remained running post upgrade to 2025.