Update 6/11/2025: We updated the timeline of this deprecation mentioned in this post.
Exchange Online will permanently remove support for Basic authentication with Client Submission (SMTP AUTH) gra...
Updated Jun 12, 2025
Version 4.0
Blog Post
"Did some testing today; it works fine to use the Azure Communication Service. The biggest issue might be the actual username and password configuration on the printer/scanner.
The username is a construct of the following three segments: <Azure Communication Services Resource Name>.<Entra Application ID>.<Entra Tenant ID>. The Azure Communication Services Resource Name is a global name in Azure and can be fairly short; mine was 12 characters. However, the other two are GUID-like, so my username became 86 characters long.
The secrets for an Azure app are also very complex, which can be a challenge for some devices. The length is 40 characters and very complex.
It might be easier to use SendGrid SaaS in Azure for this."
Jörgen Hjärtenflo
Manish-StrategicPMMicrosoft
I posted an update here - Exchange Online to retire Basic auth for Client Submission (SMTP AUTH) | Microsoft Community Hub
ACS team is working on addressing this issue, and customers will be able to add custom usernames (shorter custom usernames)
We ran into the same issue, we have some "old" devices which cannot handle a 80 character username.
Peter
- Manish-StrategicPM
I posted an update here - Exchange Online to retire Basic auth for Client Submission (SMTP AUTH) | Microsoft Community Hub
ACS team is working on addressing this issue, and customers will be able to add custom usernames (shorter custom usernames)
