Outlook
A family of Microsoft email and calendar products.
2,960 questions
Outlook Android App cannot add new account after TLS Configuration
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(153.6, 93%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBS%3C/text%3E%3C/svg%3E)
Bilgi İslem Admin
0
Reputation points
I had not enabled extended protection over On Premise Exchange 2016 server. Because it gave TLS requirement errors. So, I applied TLS registry settings (following the page https://learn.microsoft.com/en-us/exchange/plan-and-deploy/post-installation-tasks/security-best-practices/exchange-tls-configuration?view=exchserver-2016)"learn.microsoft.com") to the second member of our Exchange server 2016 DAG to see if there will be an issue.
After configuring registry settings and restarting the server, one problem occured: Adding new exchange account over Android outlook application started to fail. It says "Connection to server timeout" when trying to add new exchange account. The problem was not there before restarting the server. I installed last updated application but did not solve. We tried 3 or 4 different accounts and android phones. Has anyone encountered such an error?
Exchange Server update information: 2016 Cu23 installed March 2024 Update.
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(112.00000000000001, 24%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJM%3C/text%3E%3C/svg%3E)
JimmyYang-MSFT 48,871 Reputation points Microsoft Vendor2024-03-29T07:15:41.9966667+00:00 Do you have any operations when you applied TLS registry settings?
According to your description, it recommends you check if you have enable TLS 1.2 and disable 1.1 and 1.0. If you have Load balancer, check if tls 1.2 is only enabled on that.
In addition, please try to revert the TLS settings to see if this issue can be fixed.
Considering that your problem is complicated, we also recommend that you open a ticket. The engineer will collect the activesync log and backend http proxy log to give you more suggestion about this issue.
Sign in to comment