Hello @kamilmark,
Thank you for reaching out to us. I’m sorry to hear that you are encountering difficulties while configuring your Office 365 connection within FluentSMTP.
Regarding the multi-tenant configuration, I would like to clarify that in the current Azure interface, the option labeled “Accounts in any organizational directory (Any Entra ID tenant – Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)” is the correct equivalent to what you are looking for. Selecting this option should function exactly as the previous multi-tenant setup did.
Could you please attempt the configuration again using this specific setting?
I also appreciate you bringing the outdated tutorial to our attention. I have already forwarded your feedback to our documentation team so they can prioritize updating the guide to reflect the latest Azure interface changes.
In the meantime, if you encounter any specific error messages during the token generation process or when attempting to send test emails after selecting the correct tenant option, please share those details with me. This will allow us to investigate further and ensure we get your O365 connection up and running smoothly.
I look forward to your update.
Hello @ibrahimsharif, thank you for the replay.
What you described was clear. The problem is that when we selected the option you mentioned, a message popped up (the one on the second screen) saying it wasn’t a verified publisher, and MS admin said he couldn’t proceed any further.
-
This reply was modified 1 month, 3 weeks ago by
kamilmark.
Hello @kamilmark,
Thank you for reaching back out and sharing those details from your client’s IT team. I completely understand the concern—seeing a “not a verified publisher” warning during an integration process can be quite alarming, especially when dealing with Microsoft’s security protocols.
I would like to clarify that you can safely ignore that warning message. We have not encountered any functional interruptions or blocks in the connection process due to this notification.
Because the app is being registered within your client’s own Azure organization and you are essentially authorizing a connection to your own website’s environment, this process remains secure. The warning is a standard Microsoft prompt for apps that have not undergone the formal third-party verification process, but it does not prevent you from successfully configuring the connection.
Please advise your client’s IT administrator that they can proceed with the authorization despite the warning, as it is a common expected behavior when setting up custom app registrations in Azure for FluentSMTP.
Regarding your note about the Azure interface, we are currently working on updating our documentation to reflect the latest UI changes. We appreciate your patience while we get those refreshed.
Please let me know if they hit any other roadblocks after clicking through that warning, and I will be happy to assist further!
