You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I saw a lot of documents concerning the B2B part (it works fine), and no one about the consumer mailboxes.
I configured everything as expected (I think)
I can even can get the access/refresh token without any issue but the connexion fails.
Hi, we're having the same issue.
We are using a personal account to create the credentials, client ID and client secret.
I didn't understand well how you made it works.
grant_type=refresh_token doesn't seem to be valid.
For scopes:
openid offline_access email User.Read wl.offline_access wl.imap wl.emails https://outlook.office.com/IMAP.AccessAsUser.All
I don't understand where you set this. In the /token POST it accepts only .default
Hello,
I saw a lot of documents concerning the B2B part (it works fine), and no one about the consumer mailboxes.
I configured everything as expected (I think)
I can even can get the access/refresh token without any issue but the connexion fails.
Scope : openid email User.Read IMAP.AccessAsUser.All
(
openid offline_access email User.Read https://outlook.office.com/IMAP.AccessAsUser.All is not valid
and IMAP.AccessAsApp can't be added for consumer mailboxes
and https://outlook.office.com/Mail.ReadWrite does not help
)
URLs:
https://login.microsoftonline.com/consumers/oauth2/v2.0/authorize
https://login.microsoftonline.com/consumers/oauth2/v2.0/token
(I replaced values with XXX below)
Config :
[accounts] => Array
(
[default] => Array
(
[host] => outlook.office365.com
[port] => 993
[protocol] => imap
[encryption] => ssl
[validate_cert] => 1
[username] => [email protected]
[password] => XXX (the access token)
[authentication] => oauth
Debug :
OK The Microsoft Exchange IMAP4 service is ready. [XXX]
<< TAG1 NO AUTHENTICATE failed.
Same issue if I did it manually (openssl s_client -crlf -connect outlook.office365.com:993 ...)
The text was updated successfully, but these errors were encountered: