All Microsoft related mail accounts were shifted to Outlook.com earlier in 2017, as a part of their upgrade process. As a mandatory part of the migration, users would have to reconnect their Outlook 2013 and Outlook 2016 desktop email clients to Outlook.com. Not doing so, would mean that the syncing of the emails would stop.
If you face problems after upgrading and reconnecting Microsoft Outlook desktop client to Outlook.com web app, on your Windows PC, then this post will help you troubleshoot the issue.
Troubleshoot issues with Outlook.com migration
Despite the advantages of the upgrade, nothing is perfect at the beginning. The migration hasn’t been flawless and users have reported a few problems. Let us take a look at them.
Email account name shows up as outlook_[long series of characters]@outlook.com
A serious issue reported with those who migrated to Outlook.com is that the name of the email account shows up as outlook_[long series of characters]@outlook.com in the Folder Pane. It causes a problem because the recipients receive a mail with outlook_[long series of long series of characters]@outlook.com as the sender’s email ID. Now when the sender responds to that email ID, which obviously is not your, the mail bounces back.
This problem is particular to users using the Outlook client on Windows and it works fine with Outlook.com.
To resolve it, go to account.live.com/names/Manage and set your Outlook.com email ID as your primary alias. Remove all other email ID’s.
Repeated credential prompts on Outlook for Outlook.com connected accounts
While repeated credential prompts is a known issue with Outlook clients (for all later versions), if it occurs after the migration to Outlook.com, it might be a problem with the 2-step verification. Before trying the usual steps like using the SARA Tool to fix Outlook & Office 365 problems, deleting Windows credentials, rebuilding the profile, etc., check if you have created an App Password to add the account in Outlook.
Outlook crashes after migration to Outlook.com
While no sure shot resolution has been found for this issue, Microsoft has advised users to create a new Outlook profile. To create a new Outlook profile. If this doesn’t resolve the issue, use the SARA tool for the rest of the troubleshooting.
Unable to send emails from 3rd party email ID’s when connected to Outlook.com primary account
When the user’s Outlook for Window is set with Outlook.com as its primary account, the user won’t be able to send emails with third party email ID’s likeGmaill, yahoo, etc. This is a feature of the design. The best workaround would be to change the primary account. However, the user could send emails with @Outlook, @Live and @Hotmail email IDs. The purpose behind this setup is clearly to promote the use of Microsoft’s own products.
Recipients receive a winmail.dat file attachment along with the mail
This issue is under investigation. The recipient receives a file titled winmail.dat along with the usual mail. Though not resolution has been mentioned by Microsoft yet, it is known that it doesn’t happen when the mail is sent from Outlook.com. This could be used as a workaround meanwhile.
Company’s name missing in contacts upon syncing to server
While no resolution has been mentioned for the same, one best thing that could be done is to add the details of the crucial contacts on Outlook.com (the site) itself. Or we could try to sync Outlook to the server again if it works.
The sender’s email gets added to the ‘To’ field automatically while sending the mail
When adding multiple recipients to a mail, the sender’s own email ID gets added to the ‘to’ field automatically. It’s a known bug, the solution of which is yet to be found. The best that could be done as a workaround for the present is to delete the surplus email ID manually.
Unable to send email to a Contact Group in Outlook
When attempting to send a mail to a contact group, Outlook gives the error “An unexpected error has occurred.”
Microsoft has not been able to find a fix for this as of present, but the contact list could be expanded and the email could be sent to the list of IDs.
From field always shows Outlook.com account’s email ID
For those who have multiple accounts associated with their Outlook 2013 or Outlook 2016 for Windows, the from field always defaults to their Outlook.com email ID when they try to send emails from their other accounts.
Since the issue is with the built and there doesn’t seem to be a fix, a couple of workarounds could be tried.
In case the issue doesn’t bother much and the user uses his/her personal accounts rarely, the ‘from’ field could be changed every time before sending the mail.
If you need a long term workaround for this problem, create an empty Outlook Data File and restart the Outlook for Windows client.
A few things to be noted when migrating to Outlook.com
- Multiple devices: If a user has multiple devices, all devices using Outlook for Windows desktop client would have to be re-connected to Outlook.com.
- Mobile phones: Mobile phones do not use the same client as desktops. Thus they do not need to be re-connected to Outlook.com.
- Mac systems: Mac systems do not use the Outlook for Windows client. Thus they do not need to be re-connected to Outlook.com. This procedure is only for Outlook for Windows desktop clients.
- Data transfer: All data stored on the server would be migrated to Outlook.com. However, drafts and outbox would probably get deleted since they are stored on the system locally. You could back them up if needed.
- Auto-complete addresses: Anything that happens to these lists would be similar to the action upon re-building a new Outlook profile. In usual cases, Outlook.com would pick up email addresses from the list of ID’s you have mailed to.
While no product is perfect, Microsoft is working hard towards making this transition as smooth as possible for its users.
See this post if you receive a The operation failed, An object cannot be found message.