SMTP: Allow Modern Authentication

Good morning,

With Basic Authentication being depreciated by Microsoft how do I go about configuring your service to work with our Microsoft365 email?

Thanks so much!

Hello Jesse,

Thanks for reaching out to Jotform Support. I'm quite not familiar with Microsoft's Basic Authentication, but could you explain a bit more about your question so we can check if it's something possible with Jotform?

Once we hear back from you, we'll be able to advise.

Lorenz,

Hi! This week, Microsoft has deprecated all the "Basic Auth" logins on the Office/Microsoft 365 accounts nation (world?) wide. Forcing each to use "Modern Authentication".

We're finding our account which Jotform uses to connect to our SMTP instance on O365 to fail. I've verified the login is valid and all should be good. Except, I'm getting 'test failed' when I go to send a test from the account settings page.

What are other customers needing to do? There should be a bunch of us in this same boat.

Thank so much!

Hello Jesse,

Thank you so much for the clarification, I now have an idea what you are referring to. It looks like Modern Authentication(0Auth) doesn't require sharing of password data, and uses authentication tokens rather, which is not inline with our current SMTP setting requirements, which asks for a password. I don't think this is supported yet with our current SMTP settings. I've gone ahead and escalated this to our Developer Team as a feature request. When or if it's developed depends on their workload, how viable it is, and how many other users request it. If there are any updates, we’ll circle back to this thread and let you know. 

In the meantime, please let us know if you have any other questions.

What are your other O365 customers doing now? If it's working for them then we'd like to do the same thing. Surely we're not the only ones in this particular boat. *grin*

Thanks!

Hello Jesse,

Thanks for getting back to us. Unfortunately, there's no workaround as of now. I will send a note to my team to about this feature implementation as I understand how important this is. Rest assured that we’ll get back to you with an update as soon as we have one.

Let us know if there’s anything else we can help you with. 

As it stands, your service is completely inoperative to us. What has me flabbergasted is this deprecation of the Basic Auth service by Microsoft wasn't a surprise. It's been in the works for years. Microsoft has been constantly notifying the world it was coming and gave a solid timeline and even a 1-time extension for folks to get their systems in order. For this to happen, with no workaround, is unacceptable.

A solution needs to be provided ASAP or we'll have no choice to but change providers. I realize our $39 a month subscription isn't substantial, but I can't help but feel there's hundreds of other customers similarly affected. Hopefully this entices prompt resolution.

Hi Jesse,

Thank you for patiently waiting. We’re working on a solution as fast as we can and I will make a follow-up on our team. Rest assured that we’ll get back to you with an update as soon as we have one.

Thanks for your patience and understanding. We appreciate it.

Can you offer your suggestions on what else we can do to continue to use our branded email to send out notifications to customers?

Hi Jesse,

Thank you for reaching out to Jotform Support. I'm sorry that this is happening. Unfortunately, there's no workaround as of now. I don’t have an update yet. I know that it’s taking some time to resolve this. I’ve marked this as a Priority and reached out to our Assgined Team again. 

We’ll let you know as soon as there is an update. Thanks for your patience and understanding.