New minimum Outlook for Windows version requirements for Microsoft 365
Published Aug 27 2021 09:00 AM 410K Views

*Update added on 11/4/2021

**Update added on 1/12/2022

***Update added on 3/1/2022
****Update added on 3/23/2022

 

We are quickly approaching the November 1st deadline when the minimum version requirements for connecting Outlook for Windows to Office 365/Microsoft 365 services will change. So, we thought we’d share more information on why we’re doing that. 

 

After November 1, 2021, only Outlook 2013 Service Pack 1 (with latest fixes) and later will be able to connect to Microsoft 365 services. It’s worth noting here that Outlook 2007, 2010, and Office 2013 versions earlier than 15.0.4971.1000 *and Office 2016 versions earlier than 16.0.4600.1000 aren’t supported now, but we know some customers just can’t quit them. 

 

Current status

 

Since our Message Center post last fall, we’ve seen a drop in the usage of the unsupported versions of Outlook for Windows – great job! If you’re still running older versions, please start working on a plan to move by November 1st. 

 

Our Customer Support team is actively reaching out to tenants that have the most usage on Outlook 2007 and 2010 to help them meet the deadline. If you have questions or concerns about getting all users off these unsupported builds, please reach out to your support teams. 

 

*As announced, the block will start rolling out on November 1st for users on Outlook 2007 and will proceed in a phased rollout. 

 

**The block has started rolling out for Outlook 2010 users on January 11, 2022 and will proceed in a phased rollout. 

 

***The block has started rolling out for Outlook 2013 users (on versions earlier than 15.0.4971.1000) on February 28, 2022 and will proceed in a phased rollout. 

 

****The block will start rolling out for Outlook 2016 MSI users (on versions earlier than 16.0.4600.1000) & Outlook for Microsoft 365 users (on versions earlier than 16.0.8321.1000) on March 28, 2022 and will proceed in a phased rollout.

 

**User experience in Outlook

 

Outlook users will see the following error message in Outlook, when they experience the block that we are rolling out: “Your Microsoft Exchange administrator has blocked the version of Outlook that you are using. Contact your administrator for assistance.” 

 

New Outlook requirements blog image.png

 

Please note that once Outlook 2007 or Outlook 2010 is blocked from connecting to Exchange Online, we are unable to restore the ability to connect. Users can immediately start using Outlook on the web through a browser on their Windows (or any other) device. Outlook on the web connects to Exchange Online and allows the user to interact with their email, contacts, calendar, groups, public folders and tasks. 

 

In order to connect to Exchange Online using Outlook for Windows, the device must be upgraded to a supported version of Outlook for Windows as outlined below.

 

Customers can also immediately obtain a free 1-month trial of Microsoft 365 Apps for business, which includes the Outlook desktop client to use with their existing Exchange Online subscription. 

 

Outlook for iOS and Android and Outlook for Mac are other recommended options on mobile devices to connect to Exchange Online and utilize the feature-set offered in our service for mobile users. 

 

***Outlook 2013 users should see the following error when attempting to connect to a mailbox in Exchange Online using an out of support build of Outlook 2013 after the block is enabled:

 

User experience in outlook.jpg 

****Outlook 2016 users should see the following error when attempting to connect to a mailbox in Exchange Online using an out of support build of Outlook 2016 after the block is enabled:

 

New minimum outlook blog - new error message.jpg

 

Why are we blocking old versions? 

 

Older versions of Outlook, such as Outlook 2007 and 2010 are incompatible with the following upcoming service changes, which is prompting this controlled block: 

  • Support for basic authentication is ending to increase the security of Microsoft 365 by relying on modern authentication protocols, which are not only more secure, but also provide compliance and policy controls to help you manage your data. 
  • We’re working on adding support for HTTP/2 in Microsoft 365. HTTP/2 is a full duplex protocol, which decreases latency through header compression and request multiplexing. On the service side, we’ll be able to better prioritize requests and more effectively push data to clients. 

It can be a challenge to stay current, but there are many reasons why staying current is a good idea: 

  • Security fixes will protect your devices against known vulnerabilities. 
  • Reliability – over the last five years we’ve eliminated 75% of crashes in Outlook! 
  • Updated versions have all the coolest new features to make your life easier! 

 

*Reporting

For tenant admins who would like to know what versions of Outlook are active in their tenant, the Email apps usage report provides a full list of all users and Outlook versions in use within a tenant organization. For more information, see Microsoft 365 Reports in the admin center - Email apps usage. 


Upgrade guidance
 

 

Continue the conversation by joining us in the Microsoft 365 Tech Community! Whether you have product questions or just want to stay informed with the latest updates on new releases, tools, and blogs, Microsoft 365 Tech Community is your go-to resource to stay connected!

111 Comments
Copper Contributor

Hello - It was mentioned (here: https://docs.microsoft.com/en-us/deployoffice/endofsupport/microsoft-365-services-connectivity )that Visio and Project are also affected by this change.  How?What versions of those are affected? For MSI and click to run versions?  Our more recent installs of Visio and Project are baked into the O365 office suite.  But we do have older versions (e.g. project 2010/13) of these two apps that used the MSI based installer.

Copper Contributor

Will any other applications or devices (i.e. Android or iOS mobile devices running built-in mail apps) be affected by this? Or is the impact really only targeted somehow to old Outlook versions? If so, how is that being accomplished? By UserAgent string or something similar?

@net-1994, thanks for your question!

 

The article you referenced has been updated to clarify which versions are supported for connecting to Microsoft 365 (and Office 365) services. The section titled, "Additional information about connectivity to Microsoft 365 services" states:

  • The following versions of Project are supported for connecting to Microsoft 365 (and Office 365) services:
    • Project Online Desktop Client
    • Project Professional 2021 and Project Standard 2021
    • Project Professional 2019 and Project Standard 2019
    • Project Professional 2016 and Project Standard 2016
  • The following versions of Visio are supported for connecting to Microsoft 365 (and Office 365) services:
    • Visio desktop app that comes with a Visio Plan 2 subscription
    • Visio LTSC Professional 2021 and Visio LTSC Standard 2021
    • Visio Professional 2019 and Visio Standard 2019
    • Visio Professional 2016 and Visio Standard 2016

- Microsoft 365 Team

Copper Contributor

Thanks for the extra information.  What about Visio or Project 2010 or 2013 versions?  I don't think they connect or use any O365 services, but I could be wrong....

@AJohnstone765,

 

Thanks for your question. 

 

The block will only affect Outlook. When Outlook communicates to the server it says, "I am Outlook and I am build XX.X.XXXXX.XXXXX," and the server can then check if the user is using an appropriate build.

 

- Microsoft 365 Team 

Copper Contributor

In the post Basic Authentication and Exchange Online – February 2021 Update by the Exchange Team back in Feb 2021 Microsoft announced among other things that, "The first change is that until further notice, we will not be disabling Basic Auth for any protocols that your tenant is using. When we resume this program, we will provide a minimum of twelve months notice before we block the use of Basic Auth on any protocol being used in your tenant."

 

Is the content of that post still accurate?

 

Thanks.

Community Manager

@Balance58

 

As your question is regarding a separate blog post that you referenced, which was posted in the Exchange community and written by the Exchange team, it is recommended that you post your question on that blog article's comment thread to ensure you get an accurate response from the Exchange team. 

 

Thanks, 

 

Meenah 

Community Manager

Copper Contributor

Meenah, thanks for your reply. You referenced the exact same post in the first bullet under "Why are we blocking old versions?"  Given that, wouldn't my question be fair game for this thread?

 

Thanks.

@Balance58

 

The Exchange team published an updated blog article in June regarding Basic Auth and Exchange Online: Basic Authentication and Exchange Online – June 2021 Update - Microsoft Tech Community

 

In it The Exchange Team stated, "As we’ve said before, we’re only currently planning to turn off Basic Auth for those customers who are not using it. For customers that use still Basic for some or all the affected protocols*, we are not touching authentication settings for those protocols (for the time being)...We have been busy analyzing Basic Auth usage data for our customers and now have a solid understanding of who uses it and who does not. And we’re going to start turning it off for those who are not using it.

 

The process is: We’ll randomly select customers with no usage in any, or all affected protocols, send them a Message Center post informing them that in 30 days we’re going to turn off Basic Auth. 30 days later, we’ll turn it off and send another Message Center post to confirm it was done."

 

For additional information regarding this update, please reference the blog post linked above. 

 

- Microsoft 365 Team

Copper Contributor

That is very helpful. Thank you.

 

Just to be crystal clear (and sorry for not asking this sooner): Does that mean that users who are currently using Outlook 2010 or prior will continue to be able to connect past November 1?

Copper Contributor

@Balance58, I'm not a MS employee, so take this with a grain of salt, but i think the answer is 'no'. Old Outlook versions will be specifically prevented from connecting starting 11/1. See the question i asked earlier that a MS employee answered. They're going to use a UserAgent string (or equivalent) to detect and block those older versions. So they're not really disabling an authentication method this round. Just specific client versions.

Copper Contributor

@AJohnstone765, thanks for your response. It would not surprise me at all if you are correct but I hope MS will respond with a definitive confirmation that this is really, really going into effect on November 1, or not. LOTS of users are still running older versions, in many cases for compatibility with other (really old) applications. I'm not making excuses for their deferred maintenance, but the change will not just be a matter of upgrading Office for those users and November 1 is soon. 

Brass Contributor

@Microsoft_365_Team please add support for modern authentication in Outlook with POP/IMAP.

Now this is not available, but this functionality is very much needed!

 

Silver Contributor

I should share that several organizations have been working on migrating to the latest version of Microsoft Office.

However, due to the COVID-19 and financial situation, they forced to stay we older version.

I request Microsoft extend support for older version of Microsoft Office and give more time for recovery from the COVID-19, so companies would have resources for upgrade.

Copper Contributor

Anyone know of a programmatic way to determine if there are still old, soon to be unsupported Outlook clients, within the tenant?  The report through the web admin portal, and the Graph API, do not appear to report actual version numbers just "Outlook 2013" and "Outlook 2016", etc. I get that the goal should be to get rid of all the old software but limiting our ability to report on data MS does have (each client reports back what version is being used) doesn't help the situation.

Copper Contributor

This is why we run Exchange on prem and don't settle for this Exchange Online nonsense... Microsoft can pull the plug on you whenever it feels like it, leaving you with no recourse. We'll decide if basic auth is allowed or not, that's not for Microsoft to dictate to us, thank you very much.

Copper Contributor

1 week to go.

 

Microsoft Team, can you confirm that "After November 1, 2021, only Outlook 2013 Service Pack 1 (with latest fixes) and later will be able to connect to Microsoft 365 services" will be enforced?

 

Thanks.

Copper Contributor

@mprentice , check out this Microsoft doc for information on finding legacy authentication apps - https://docs.microsoft.com/en-us/azure/active-directory/fundamentals/concept-fundamentals-block-lega... 

It is still rudimentary but provides some good information.

 

Regards

Copper Contributor

I'm trying to understand whether or not this will impact migrations from Exchange 2010 to Exchange Online (O365).

 

Will we need to migrate to Exchange 2013+ and then onboard users to O365 EO from there?

Copper Contributor

@cheetos As long as the users are running new enough Outlook then it won't impact the migration from Exch 2010 to ExchOnline.  If the users are still running Outlook 2013 or old Outlook 2016, then they will be affected.  This is a client workstation issue, not a server issue.

Copper Contributor

@mprentice Excellent. Thanks for the clarification. I was not able to find anything on the server side either, so figured I'd check in to see if others had sourced information.

Copper Contributor

Microsoft, again being arbitrary and capricious.  In this case, I am an Exchange-only customer.  I have no interest in Microsoft TELLING ME what clients they will allow to connect to their exchange server, and that to use their precious Exchange hosting product, I have to update all my clients, at massive cost.   Easier to just move onto an alternative hosting service, one that will likely be willing to support my Office 2010 clients forever, FOREVER, until the end of time.  I don't care that Office 2010 is "not supported", hell Microsoft does NOT support stuff when it is "supported.

And in this case, the notifications DID NOT HAPPEN.  I woke up, had my service renew (3 days ago), and today, after paying for it, it no longer works because Microsoft decided that they want more money for clients.  NOT FOR ANY OTHER REASON!!!!!   All other excuses from Microsoft are just that, excuses.  Now, actively looking for a new Exchange Server hosting service.  Microsoft Online (Azure) completely has lost its way.  

Copper Contributor

Hi, please include in this article the required Windows OS versions.

Some customers still use Windows 7/8 in combination with Office2kX. They consider being supported by this. 

You have to have both, Office and Windows OS versions supported.

Copper Contributor

Does anyone know if this blocking will affect Outlook for companies that have a self-hosted Exchange Server?

Copper Contributor

Office 2013 versions earlier than 15.0.4971.1000
We have a slightly newer version 15.0.5059.1000 and it doesn't work.  What do we need to do to make this version work again?

Copper Contributor

I recently ran into this inability to connect. I am curious how come I able still able to connect to
my free Microsoft Email mailbox via Exchange mode; The connection modes looks very similar via the Outlook 2010 control panel applet. So I am thinking if the Outlook 2010 version is able to connect to the Free Email mailbox I am sure there is a way to utilize it to connect to my paid outlook Email mailboxes via Exchange mode Or may utilize the IMAP connection instead.

 

Anyone that as accomplished a configuration where they are still able to utilize the Outlook 2010 application either via IMAP etc would be helpful to me as I am not ready to shell out $150 a year just to continue check my Email via my preferred application that is working just fine for 
my home use. If Microsoft would offer a non-subscription based offering of Office I would consider that cost over the next 10+ years.

Copper Contributor

> I recently ran into this inability to connect. I am curious how come I able still able to connect to
my free Microsoft Email mailbox via Exchange mode; The connection modes looks very similar via the Outlook 2010 control panel applet. So I am thinking if the Outlook 2010 version is able to connect to the Free Email mailbox I am sure there is a way to utilize it to connect to my paid outlook Email mailboxes via Exchange mode Or may utilize the IMAP connection instead.

 

> Anyone that as accomplished a configuration where they are still able to utilize the Outlook 2010 application either via IMAP etc would be helpful to me as I am not ready to shell out $150 a year just to continue check my Email via my preferred application that is working just fine for 
my home use. If Microsoft would offer a non-subscription based offering of Office I would consider that cost over the next 10+ years.

 

It still works for me, though I'm sure I'm jinxing myself by saying that. I know Microsoft loves nothing more than to find something working well for somebody and break it. That's all they've done for the last 10 years.

I use Outlook 2010 to manage my calendar, contacts, and tasks primarily; occasionally but rarely for email itself; I use the Thunderbird-based MailNews client for that. Outlook as a client has always sucked for email, but it's really good for Exchange stuff and syncing calendar, etc. via Exchange protocol. That's what I don't want to lose out on.

Copper Contributor

I have a problem opening my outlook app on my desktop. As stated as problem "your Microsoft exchange administrator has blocked has blocked the version of outlook your using. Please contact your administrator assistance". 

What should I do here?

Copper Contributor

So if I am understanding correctly my options for Windows is either upgrade to Outlook 2019 or go to 365?  How long will Outlook 2019 be compatible?

 

Copper Contributor

Hi I'm running Outlook at part of Office Standard 2016

Discovered that Outlook is now blocked after getting this error message:

 

melctrees_1_0-1649141107048.png

I'm unable to locate KB 4051890

mentioned as a fix in the above article or find required version 16.0.4600.1000

 

My configuration:

 

Edition Windows 10 Home
Version 21H2
Installed on ‎16/‎10/‎2020
OS build 19044.1620
Experience Windows Feature Experience Pack 120.2212.4170.0

 

Processor Intel(R) Pentium(R) CPU N3710 @ 1.60GHz 1.60 GHz
Installed RAM 4.00 GB (3.90 GB usable)
Device ID 1FC0BC8D-E8A7-4AE5-9FC2-3A9250B222FD
Product ID 00325-80195-81435-AAOEM
System type 64-bit operating system, x64-based processor
Pen and touch Touch support with 10 touch points

 

My laptop won't run Windows 11.

 

What do I need to do to get Outlook working again? I don't want to purchase any updates that either won't work on my machine or won't work in the near future.

 

Thank you for your assistance

 

Microsoft

@melctrees_1 Sorry, I'm not sure what may be going on when you say you're not able to locate that KB article. Here's what I'd suggest in your case, that'd help you upgrade to the latest version of Office/Outlook 2016. Can you please go here and download and install the latest update: March 1, 2022, update for Office 2016 (KB5002160) (microsoft.com) - This would resolve the connectivity issue for you. Let us know how it goes for you.

Microsoft

@lpaulus It all depends on which version of Outlook for Windows you are using. Support for Outlook 2013 expires next year on 11 April 2023 (see: Outlook 2013 - Microsoft Lifecycle | Microsoft Docs), and Outlook 2016 & 2019, both will be out of support on Oct. 14, 2025 (see: Outlook 2016 - Microsoft Lifecycle | Microsoft Docs & Outlook 2019 - Microsoft Lifecycle | Microsoft Docs). Outlook as part of an M365 subscription will remain automatically updated as you move into future, so that'd be the best option if you never want to be bothered about being out of support, ever in future. Hope this helps.  

Microsoft

@StevenTater There could be 2 other reasons why Outlook 2013 may not be working for you. First being the use of Basic auth & its upcoming retirement. I'd highly recommend you to work thru the instructions in this article to enable Modern auth in your org and then switch the auth mechanism in use by Outlook 2013 to Modern auth, see: Enable Modern authentication for Office 2013 on Windows devices - Microsoft 365 admin | Microsoft Do.... Second being the use of Windows 7 as operating system, where Outlook 2013 is in use. If use of TLS 1.1 or 1.2 is not enabled at the OS system level, then you will see connectivity issues in Outlook 2013, check out this article for more info and solution: Outlook stops connecting on Windows 7 and legacy Windows versions (microsoft.com). Hope this helps!

Microsoft

@ScottLumos No, this requirement only applies to customers having mailboxes in M365 Exchange online service. It does not apply to any customers, who run/manage Exchange servers in their orgs (on-premises).

Copper Contributor
Second being the use of Windows 7 as operating system, where Outlook 2013 is in use. If use of TLS 1.1 or 1.2 is not enabled at the OS system level, then you will see connectivity issues in Outlook 2013, check out this article for more info and solution: Outlook stops connecting on Windows 7 and legacy Windows versions (microsoft.com). Hope this helps!

"Fake news"...

I have no problem at all using Outlook 2010 on my Windows 7 PC with the Exchange protocol (which I use for calendar and contacts and tasks, but not email so much).

I have no plans to "downgrade" either of them to anything newer.

Of course, I'm sure Microsoft is doing all they can to break whatever still works... knock on wood...

Microsoft

@JZapata_SwO All versions of Office/Outlook come with their own set of system requirement, you can look those up easily on Wikipedia. Windows operating systems have their own lifecycle, you can look that up on Microsoft Lifecycle website (Search Product and Services Lifecycle Information - Microsoft Lifecycle | Microsoft Docs). Windows 7 & 8 both are out of support, see: Windows 7 end of support and Office (microsoft.com) & Windows 8 end of support and Office (microsoft.com)   

Microsoft

@InterLinked1 What I wrote above and you have quoted specifically applies only to Exchange Online in M365, a service run/managed by Microsoft. If you have your own Exchange server (on-premises) then it does not apply to you, you should be able to use Outlook 2010 on Windows 7 to connect to a mailbox on your on-premises Exchange server. Hope this clarifies.

Copper Contributor
@InterLinked1 What I wrote above and you have quoted specifically applies only to Exchange Online in M365, a service run/managed by Microsoft. If you have your own Exchange server (on-premises) then it does not apply to you, you should be able to use Outlook 2010 on Windows 7 to connect to a mailbox on your on-premises Exchange server. Hope this clarifies.

I'm not using Exchange on prem. It's a personal @outlook.com account.

Granted, I haven't tried adding a new account since this happened. But existing accounts do seem to continue to work. I'm using an "unsupported" Outlook and "unsupported" Windows and yet it works. So don't be fooled by the official Microsoft line into giving up the software you want to use. If you believe in software choice, by all means continue using Outlook 2010/Windows 7, because you can and it (at least in some cases) still works with Exchange.

 

Hopefully by the time it inevitably hits the fan, I can spin up my own on prem Exchange 2010 server, but I'm trying to delay that as long as possible. It's just sad that Microsoft is emulating Apple now and, like them, force obsolescing anything it can't sell to people anymore.

Copper Contributor

Dear Team, We are unable to locate KB 4051890, we are using MS Office 2016 Standard (16.0.4266.1001) with Windows 11, Request you to please support.

 

 

Thanks,

Ravindra Ruthan

Copper Contributor

Running Outlook 2010, attempted to add a new exchange email yesterday, (my email provider changed from a POP to Exchange) crashed my Outlook, now I get the usual error dialog box and Outlook 2010 will not open.  I am currently downloading M365, but my real question is this;  How do I now salvage my Outlook 2010 emails, folders, contacts, etc. now that I cannot get Outlook 2010 to even open so that I can export them??  HELP Please!!

Copper Contributor

Users were using pea on so for connecting to exchange online suddenly it stopped in 24 of April

Copper Contributor

ok

Copper Contributor
Copper Contributor

Dear Team

  in one of the pc i have uninstalled Office2016 Pro due to the  Outlook error Code """"outlook requires update before it can start.click learn more for update instructions
Current Verstion :16.0.4266.1001 """ issue is not installed im having valum license and its effected more that 11 system 

 

 Find the error Screenshot and help use download the new version  of Office2016 Pro 64bit application 

Microsoft

@Vedamurthy I'd suggest to please call in for Support to get assistance with your issue, see: Get support - Microsoft 365 admin | Microsoft Docs 

Copper Contributor

Hi, 

For Outlook eDM in html and mobile responsive, can M365 version 16 be able to accommodate? And can render properly on mobile devices? 

Copper Contributor

By Robbing long time users who had already paid for Outlook 2010, into a FORCED Upgrade to Office 365, is laying down the groundwork for a multimillion-dollar Civil Lawsuit against Microsoft.  Looking forward to seeing management who came up with this amoral idea, at eventually getting fired.

Copper Contributor
I doubt anyone at Microsoft will ever face any repercussions for this. After all, to them, this is "progress"... It's not Outlook 2010 that's broken, it's Microsoft Exchange Online and their non standards compliant services. This will just force people to their senses to mistrust the cloud (if they trusted it at all to begin with) and run Exchange on-premises where Microsoft can't pull trash like this.
Copper Contributor

The last couple of comments have given me such a laugh... I didn't realize this was jokes forum. Thank you, very entertaining. 

Copper Contributor

After receiving an email from Microsoft yesterday July 15, 2022, alerting me to the fact I access Outlook.com via Office 2007, I started to panic regarding the drop dead deadline of Aug. 15, 2022 for a change is needed.  I'm a simple home person running a Desk Top PC with Windows 10 and MS Office 2007 for my primary email management.   I have been always using this type of program going back +20 years when I had "Outlook Express", really old.   I have checked with my computer shop and after reading most of the background, I'm wondering if it is possible for me to go to Office 2013, or Office 2016, either or latest versions as specified?   I don't feel as a "home individual" I should have to go to "365" in a paying mode of either choice there.    My computer guy had set me up with Office 2007 years ago when I was running Windows 7.  We continued this Office 2007 when I went to Windows 10.   So, we have discussed using either Office 2013 latest, or Office 2016 latest.   "What say you"???

 

Version history
Last update:
‎Mar 24 2022 10:16 AM
Updated by: