Microsoft has set the final date for the Deprecation of Basic Authentication in Exchange Online (Office365) to October 1st, 2022.
VCC:
This will impact you only if:
- You are using Exchange Online as your email server, and
- You are using one of the following VCC modules/features
- ERMS module: no emails can be received or sent anymore
- ‘IVR voicemail to email’: no emails will be sent
- ‘Scheduled Email Reports’: no emails will be sent
How can you solve this?
- Microsoft has provided a one-time option to extend the use of ‘Basic’ authentication to end of December 2022, see article.
- Impacted customers should make sure these steps are executed in September!
- To enable ‘Oauth’ authentication as an alternative for ‘Basic’ authentication, VCC will release 2 Service Packs:
- VCC 19.2.1.3 – planned for mid-September: enables ‘Oauth’ authentication for ERMS
- VCC 19.2.1.4 – planned for early-October: enable ‘Oauth’ authentication for ‘IVR voicemail to email’ and ‘Scheduled email reports’
- Customers using Exchange Online should upgrade to these Service Packs before the extended deadline of end December 2022.
You will find more information in the documentation here.
APAS:
This will impact you only if:
- You are using Exchange Online as your email server, and
- You are using one of the following APAS modules/features
- Exchange Presence/Calendar
- Exchange Directory
How can you solve this?
- Microsoft has provided a one-time option to extend the use of ‘Basic’ authentication to end of December 2022, see article.
- Impacted customers should make sure these steps are executed in September!
- APAS 6.4.1 will be released mid-September 2022, and will support ‘Oauth’ authentication
- Customers using Exchange Online should upgrade to APAS 6.4.1 before the extended deadline of end December 2022.
You will find more information in the documentation here.
ELSBETH:
Customers using ELSBETH PowerContact are generally not negatively affected by this change. In their announcement, Microsoft has clarified that SMTP AUTH (authenticated SMTP), which PowerContact uses to send e-mails, is unaffected by the change.
Please make sure that you do not activate multi-factor authentication for the user account that is being used for sending mail as that will break SMTP AUTH. Please note that SMTP connections to Office365 are encrypted which keeps the account credentials safe.
Customers using appointment synchronisation should use the “MicrosoftGraphService” component of ELSBETH PowerContact, which is designed for Office365 Exchange. The “SynchronizationService” component of ELSBETH PowerContact is designed for on-premises Exchange Servers only.
