Skip to main content
Solved

oauth 2.0 instruction confusion

  • Oct 28, 2026 11:14 AM UTC
  • 2 replies
  • 62 views

parke372
Supporter
Forum|alt.badge.img+11

Hi all,

i’m trying to add a FME flow automation that uses IMAP as a trigger, going through these instructions:
https://support.safe.com/hc/en-us/articles/25407404506253-How-to-Connect-to-Microsoft-Exchange-Online-using-OAuth-2-0-Microsoft-Modern-Authentication#h_01HWPG1A9N334HV2CQHSS1092K

i’m not real clear about part 2 where it discusses setting up an emailer transformer - do i need to do that even if i am just trying to use FME Flow or is that for FME Form only? i’m kind of leaning towards only being for form, but we are trying to troubleshoot an issue so confirmation would be nice to have.

Best answer by j.botterill

If you're not using an Emailer transformer in a workspace, you don't need the Part 1/2 process of:

  • adding an Emailer transformer
  • creating the Microsoft Mail (safe.emailer) web service
  • creating the Microsoft Mail web connection
  • publishing an Emailer workspace to Flow
  • adding the FME Flow /fmeoauth redirect URI for that Emailer web service
  • creating a client secret for that Emailer connection

That section is effectively a separate SMTP/Emailer use case.

 

You want to check all of Part 3: FME Flow Automations.

For an Email - IMAP received trigger, Safe specifically says that Automations:

  • do not use the Emailer web service
  • still require a Microsoft Entra/Azure App Registration
  • do not require a client secret
  • require the delegated permission IMAP.AccessAsUser.All
  • require Allow public client flows = Yes
  • use the application's Client ID directly in the Automation trigger configuration.

Check your registered app

  • IMAP.AccessAsUser.All is a Delegated permission.
  • Admin consent has been granted.
  • Allow public client flows is enabled on the App Registration.
  • The mailbox account being used is actually permitted to authenticate without MFA/Conditional Access blocking it.
View original

2 replies

j.botterill
Evangelist
Forum|alt.badge.img+69
  • Evangelist
  • Best Answer
  • Oct 29, 2026 12:49 AM UTC

If you're not using an Emailer transformer in a workspace, you don't need the Part 1/2 process of:

  • adding an Emailer transformer
  • creating the Microsoft Mail (safe.emailer) web service
  • creating the Microsoft Mail web connection
  • publishing an Emailer workspace to Flow
  • adding the FME Flow /fmeoauth redirect URI for that Emailer web service
  • creating a client secret for that Emailer connection

That section is effectively a separate SMTP/Emailer use case.

 

You want to check all of Part 3: FME Flow Automations.

For an Email - IMAP received trigger, Safe specifically says that Automations:

  • do not use the Emailer web service
  • still require a Microsoft Entra/Azure App Registration
  • do not require a client secret
  • require the delegated permission IMAP.AccessAsUser.All
  • require Allow public client flows = Yes
  • use the application's Client ID directly in the Automation trigger configuration.

Check your registered app

  • IMAP.AccessAsUser.All is a Delegated permission.
  • Admin consent has been granted.
  • Allow public client flows is enabled on the App Registration.
  • The mailbox account being used is actually permitted to authenticate without MFA/Conditional Access blocking it.

parke372
Supporter
Forum|alt.badge.img+11
  • Author
  • Supporter
  • Oct 29, 2026 10:05 AM UTC

thanks! i thought so, but it’s nice to be 100% sure. my suspicion at this point is that one or more of the delegated permissions were not added when the client id was generated. i’m waiting to hear back from our team that does that.