Recently, Microsoft has decided to postpone disabling Basic Authentication in Exchange Online for those customers still actively using it until the second half of 2021. In the meantime, Microsoft will continue to disable Basic Authentication for newly created tenants by default. Starting in October 2020 they will also start to disable Basic Authentication in tenants that have no recorded usage. This means that applications that are using Basic Authentication to connect to Exchange Online might face authentication failures when adopted by a customer who is new to Exchange Online or has not used Basic Authentication applications before.
For more details refer the below link (published in April 2020) :
After setting all required configurations , Many of you facing issue while generating the refresh token and some other exceptions\ Errors while implementing this scenario.
The purpose of this blog is to collect right information about the PI\PO Mail Adapter OAuth configuration and traces and to improve the troubleshooting of PI issues in Mail Adapter OAuth scenarios to identify the exact logs.
Latest XPI_Inspector needs to be installed in your PI\PO system.
Refer the Note 2010715 - How to deploy/undeploy the XPI INSPECTOR
Steps to Collect XPI OAuth Logs:
Open XPI_ Inspector : http://host:50X XX/xpi_inspector/index.jsp
Select Example 100 and add below log locations depend on your case
Refresh Token Generation Issue:
For all Mail Adapter OAuth issues:
1)Above log locations in XPI will help you to get the exact issue where it is happening Mail Adapter OAuth scenarios,
2)Before raising any OAuth related incidents to SAP , you can collect the above logs and attach them to the Ticket to speed up the resolution.
The above steps will help you to get proper logs\traces for PI\PO Mail Adapter with OAuth 2.0 authentication with Office365.