I won't go back to using POP/IMAP because that cannot sync calendar or contacts. Several friends and family members are using this setup. It's currently still working in my phone but that will also stop Outlook is the first application affected, the rest will stop working by the end of the month. I have the same problem with my personal email address (that has previously worked fine with Hotmail/) for many many years.Īccording to MS Support they are disabling activesync support. Small % of users, I am pretty sure that this will still be a very large actual number of users, so this is not a small trivial issue, but one which could be a blocker to the use of by a large number of people (and small businesses and How can we escalate this issue as it appears to need a fix on the side, and maybe on the Outlook 2013/2016 side as well, to mean than relatively non-technical people can get reconnected without these sorts of issues. I have tried to discuss this with the helpdesk, but did not manage to get anywhere before the link dropped - and did not have the time to start the whole discussion again. using EWS/Office 365 connection rather than EAS) using these personal email accounts?
Given that itself allows for the personal domain (outside the control of Microsoft) to be used for logon, receiving mail and sending mail - when will the connection from Outlook 2013 and (specifically in our case 2016, as we have Office 365 Home)īe fixed so that we can connect with full functionality (i.e.
Talked about in the original email announcements - although I don't understand how this would be broken without affecting ALL other clients connecting to such as the Windows 10 and Windows 10 Mobile mail, calendar and people apps. I have found a setup using EAS and using the server *seems* to be working (not sure how I got there, but think it was from an autodiscover session somehow), but I am not clear if this will also be affected by the potential problems
If you follow the instructions as per other users, and use an alias, it comes back with a non-specific email address in Outlook (completely unusable when you have multiple accounts you use) and sending from the alias (or worse, the non-specificĪddress) rather than the personal domain, which is setup as the default send address in (and works everywhere else).
The accounts in question are all fine, tested from and from the Windows 10 and
However, once you restart Outlook it ALWAYS comes up with the error "The name cannot be matched to a name in the address list" and then deletes the created account. (showing as MicrosoftAccount\.) and shows the account being successfully configured, requiring Outlook be restarted. When trying to reconnect following the recent announcements, we have setup the autodiscover CNAME record in the DNS for each of the domains, and when connecting from Outlook to setup the account again, it finds the service, prompts for the username/password We use forwarding from the hosting company and a send only account for outbound mail, to ensure that email is to/from these accounts and not "on behalf of.". and Outlook 2013/2016 (using Exchange Active Sync) for many years. Our family has a number of personal domains setup through a domain hosting company (#.me.uk and #.uk) and we have been using this successfully with There seems to be a major issue with the new connection process for Outlook 2013/2016.