KB485630: Impact of SMTP distribution with the new Microsoft’s policy for Exchange Online authentication

Background
In September 2021, Microsoft announced that effective October 1, 2022, they will begin disabling Basic authentication for Outlook, EWS, RPS, POP, IMAP, and EAS protocols in Exchange Online. SMTP Auth will also be disabled if it is not already being used by the customer .
SMTP AUTH will still be available when Basic authentication is permanently disabled on October 1, 2022. The reason SMTP will still be available is that many multi-function devices such as printers and scanners can't be updated to use modern authentication.
Reference: https://docs.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/deprecation-of-basic-authentication-exchange-online
Impact on the Distribution Service
No impact on the customers who have already been using email-related functionalities of the Distribution Service before Oct1, 2022
Has impact on the new customers or the registered customers who want to use it after Oct1, 2022, like Email subscription/Email notification will be affected.
Note:  The impact happen in the delivery stage and the direct impact is that the user can't not receive any email if the customer use the Microsoft email client.
Workaround
Disable smart host when configuring email in the Device Editor, by unchecking the ‘Always use Smart Host’ option.
Reference: https://community.strategy.com/article/KB31568-How-to-configure-Smart-Host-for-use-with-MicroStrategy?language=en_US
Note:

• SMTP: The Simple Mail Transfer Protocol (SMTP) is an internet standard communication protocol for electronic mail transmission. Mail servers and other message transfer agents use SMTP to send and receive mail messages.
  
• Smart Host: is an email server via which third parties can send emails and have them forwarded on to the email recipients' email servers.
  
• Smart host is acting as an intermediary server(the email sender) that sends out the email to the recipient (the email receiver: the email address that is attached to the user/device/contact). We(the client: Developer/Workstation) require the user's authorization to access the smart host server which is configured as IP Address /Server Name in the Smart Host section, by using the username/password provided in the Smart Host Authentication section and its the basic authentication that is not recommended to use in the future. By contrast, modern authentication is using bearer tokens from the Authorization server authorized by the user to access the host server.
  
• Disabling the smart host will not touch this authentication workflow and the distribution service will send out the email directly using an anonymous account, that's why these anonymous senders will be easily to be treated as spam emails by some email server.   
  
• Reference: https://community.Strategy.com/s/article/KB31568-How-to-configure-Smart-Host-for-use-with-Strategy