What do you mean? You have to create an app and then create the client secret in the app. This is what you did for the other test right?
Cheers.
OAuth2 - Microsoft setup
KevinTheJedi
For my other test, I am using Exchange online plan1 license, which I am able to do via Azure
Created App:
Enterprise applications | All applications
Then I registered under: App registrations
Then gave permission to API
That's where I generated Client secrets and was able to add Redirect URIs, etc...
I was trying to test with a personal account like outlook.com, but I am not sure where to go
KevinTheJedi
hmm, so I was able to set up on personal account app and created the secrets, but as far as permission, User.Read.All is grayed out
KevinTheJedi
I am working with MS365 support, they are asking which version of TLS are you using.
ramrajone Try un-ticking user.read and see if it will then allow you to select user.read.all. It might be one of those that only one can be selected. Just a shot in the dark.
Daedalus01
tried that, but no go
Version of TLS depends on what you have installed locally. You can check your openssl settings to confirm which version you are using (should be 1.2 which is the latest - but I cannot see your system).
Cheers.
KevinTheJedi
Well no go with MS365
MS side saying SMTP and IMAP working fine because I can send out email via PowerShell using SMTP protocol and setup Outlook using IMAP setting.
Double checked the API permission
This is what I have on the Ubuntu server 22.04:
grep -ir SSLProtocol /etc/apache2/*
/etc/apache2/mods-available/ssl.conf: SSLProtocol all -SSLv3
We are at the point, where it fails to fetch and send SMTP
I even added TXT record, but still no go
Same issue I have with my personal outlook account. Other peeps on the forum have everything setup and working with MS emails so you might want to review those threads and see how they got theirs working.
Just to note, I am 100% anti-windows. The only reason I use MS products at all is to test things like this. Their support is far from good and not helpful at all. Their documentation is horrendous and out of date all the time. So I tend to steer clear of windows if at all possible. I really don't know what's going on without talking to MS support but they haven't provided any sort of help in 2+ weeks so I'm at a loss here. We are going to create an official MS account so hopefully we'll be in a better position to test things like this in the future.
With all that said I know that MS + Modern Auth works with RC3 and the OAuth2 plugin (as other community members have confirmed) but I don't know where to tell you to look as I just don't know anything about MS products (and their docs aren't helpful).
Cheers.
KevinTheJedi
Well, I am checking all forums here, but without success setup, this setup I have is Test only, so I have been starting from fresh, documenting what's working so far.
If anyone using Ubuntu with Auth2 - Microsoft who got it working, please post your solution, so I and others having issues can double-check where is the missing point
note: I am Linux Ubuntu side, MS is great for larger corps with lots of $$$$, They are sticking to their own egg shell, I don't contact vendors unless things are out of my hand
Here is one of them:
Cheers.
KevinTheJedi
I have followed that guide, double checked all my settings, I will start fresh tomorrow with a new account, just to make sure I don't have anything cache or MS365 doesn't have something in the backend, that's causing an issue
@KevinTheJedi
I just tested one more thing and found little strange, not sure if this has anything to do with Auth2.0, probably not
On the same server where I have installed v1.17-RC3 with the LDAP plugin, I can only log in once, the user shows up in the user list, but can't log in again
So, I installed 1.16.3, and LDAP worked fine
I have done another fresh setup and still, I cannot get it to work
I can save the config and get the token, but when I try to enable the Fetching or SMTP, that's when I get error
I gave the following permissions:
I signed up for a O365 dev account and it’s not letting me access anything so I contacted MS support again. Waiting on their response. Once I have a working account we can better debug this.
Cheers.
5 days later
We now have a confirmed setup working with Microsoft. Please review my post below:
Cheers.
KevinTheJedi
Great job Kevin, I have tested config works now
I had changed only one thing
Default: mail to emailAddress
Email Address Attribute: *
Please consult your provider docs for the correct attribute to use
emailAddress
I am able to enable SMTP, create tickets via Portal,
only thing not working is mail Fetching, which I will fix later on
Thank you very much for your help
Yea rblake and I had to use EmailAddress so it seems specific to each tenant. Good thing we have the note to consult the provider's docs to see which attribute to use! 
Cheers.