Support for M365 Apps (O365) on Windows 2022

[rtravni42]

We have a large number of Windows Server 2016 with M365 Apps (O365) and need to upgrade these servers now (end of support for WS2016 is Jan 2022).
The next server product to install for us would be Windows Server 2022, unfortunately there is no support for M365 apps (O365).
In general, it looks like the support of M365 Apps for Server OS will be discontinued 2025.

RE2OqRI (microsoft.com) 

We want to get a statement from Microsoft as to whether Microsoft intends to support M365 Apps (O365) on Windows Server 2022 at some point.
Now we have to make a strategic decision.
The time is not long until 2025!
The way is not to AVD or Microsoft Azure HCI, but the way is away from the concept of application (or desktop) "remoting" and thus we as customers are no longer available for AVD and Windows 365!

[#2]

Thank you Elden. We can't all move to Azure Virtual desktop and Windows 10 multi-session; Office 365 (or even if it has to be, the LTSC version) works very well on remote desktop servers for us and many others today, and we don't see why we can't or shouldn't continue using it for the foreseeable future. Surely, the pace of change in mature products such as Office and Windows can't be so fast that we need to be on such quickly changing base products. And corporations don't WANT a quickly-changing base product either, they want stability. So maybe there is a fundamental conflict here but I do hope you will listen to what your customers really want out of the products, they are really good when they work. 🙂

[#3]

That's very good news. Does this mean we can already deploy this? Or is there no official support yet? When is this to be expected?

[#4]

Not supported in production yet, just being transparent that your voice is heard and we are working on it... and opening the door to please go try it out and give feedback to help us get this over the finish line. Thanks!

[#5]

@EldenChristensen :

Hi, 

This is good news. Thanks very much

Regards 

Reinhard 

[#6]

Does this also mean that there will be O365 support beyond October 2025 on the server platform because O365 will then be hosted on WS2022?

Reinhard Travnicek

[#7]

@rtravni42 we're facing same problem - strategic decisions how to handle onPrem RDS with M365 cannot wait until 2025. Provide multi-session Win10/11 for onPrem or keep RDS alive!

Really appreciate @EldenChristensen looking into this! Keep going!

[#8]

Awesome news Elden, this is definitely something that is still required for many of us as we are not ready to move to the cloud yet and because on-premise requirements will always exist up to some extent. Glad to see that Microsoft listen to its community and adapt their guidelines/support policy based on it.

[#9]

Hi @EldenChristensen , very good news! We all ask ourselves in Germany the question whether a possible support release goes beyond the year 2025? That would make us all very happy.
Regards Marius

[#10]

Same question here in Canada! We need support beyond 2025.

[#11]

@F_Neumann just for awareness there is another on-prem option, Azure Virtual Desktop is coming to Azure Stack HCI.  This will allow running Windows 10 and Windows 11 Enterprise multi-session virtual desktops on-prem.  It's currently in preview:

Azure Virtual Desktop for Azure Stack HCI (preview) - Azure | Microsoft Docs

Thanks!
Elden

[#12]

Hi Elden,

As far is i know there is no Multi Tenant for Azure Stack HCI. So no Option for Service Providers to transfer there Business to Windows 11 Enterprise multi user if there are needs to stay in their Datacenter.

So is there Support for Office 365 on Windows Server after 2025 or a Multitenant Option for Azure Stack HCI to put multiple Customers on a Azure Stack HCI Cluster.

Best Regards,

Bernd

[#13]

Dear @EldenChristensen please keep in mind, within your internal discussions, that in case Microsoft would decide to support M365 Apps on Windows Server 2022, this would be a welcome change for some scenarios.

On the other hand, and quite importantly, Microsoft should consider this decision would be the second time that the support of M365 Apps revoked from Windows Server would be reinstated later. As it happened with Windows Server 2019.

Back then the decision was a good one for several reasons:

- WS 2016 has bugged servicing stack taking ages to patch

- WS 2019 has several improvements to start and search / indexing making it easier to implement RDS or Citrix based multi-session use. Next to said servicing improvements and other things.

- the alternatives to cope with the revoke weren't up to par and not that versatile as they appear now in terms of technical excellence and licensing.

If Microsoft would change this decision and support M365 apps on Windows Server 2022, this would absolutely destroy the credibility to plan budgets and lifecycles based on roadmaps published by the Office team.

This time there is little reason, as many functional and cost effective alternatives to RDS exist. 

In terms of licensing, starting from October 1st which Microsoft supposed to loosen the VDI licensing requirements and make it easy to either host VDI on-premises on any hypervisor or in Azure using Windows 10/11 Pro / Ent while user are licensed with M365 E3/E5/Fx etc.

Alternatively, hosting Azure Virtual Desktop on Azure Stack HCI on-premises will be a great option. 

Even external hosting M365 apps within SPLA and on shared hardware could become an option starting from October 1st without QMTH provider requirements.

So before taking any u-turn, please consider these announced licensing changes, and rate their effectiveness, in addition to feedback from customers and / or partners to revert to "status quo".

Thanks for your time and consideration!

[#14]

@EldenChristensen 

Yeah, but again you forgot Support for Multitanant Scenarios.

Sorry to say this, but all your team is delivering are peaces, not a working model for broad markets.

1) Get Multitanancy to ASHCI Sceranios

2) Get Support for M365 on Server 2022 BUT also be clear what the restrictions are

3) Get clear about the end of support for M365 in remote scenarios in 2025 and stay with your decision before everyone will put ton of investments into it and you rethink it in 2024... 

SO make your homework, for all partners, not just for the enterprice customers....

[#15]

@kwester-ebbinghaus-businesswhy are you so against Microsoft supporting M365 apps on Windows Server? There aren't as many good alternatives to RDS as you claim, especially for those of us using on-prem hosting that is not Azure Stack HCI.  We shouldn't be forced to run MS virtualization either in their cloud or on-prem to run M365 apps.

I'm not saying MS shouldn't change their M365 apps system requirements to start to require newer versions of Windows Server sooner rather than later when they go out of support, I think that's a reasonable ask, as they already did with 2012R2 which still receives security updates but can't support latest M365 apps.  BUT we want RDS on WS to continue to be supported for running them, it is stable, it is performant and less resource-intensive than many different W10 desktops.

[#16]

Well as always it depends. We have things like memory compression and dynamic memory and thin provisioning + Dedup on storage level. At least all of this is included in the licensing cost for Azure Stack HCI or even traditional Hyper-V. So VDI could be quite effective, and more performant compared to RDS, but at least also more secure and flexible.

For me it is no pain that M365 and 2012R2 are not supported, as simply WS 2012R2 is not supported for mainstream, as well as WS 2016 is no longer supported.

I am well aware of the awkward situation when you are trying to open a support ticket with Microsoft and the qualified OS is in extended support.

It is nothing for everyday business. Let alone you have a potential cross product issue, like you might think it is your Windows Server causing FSLogix issue, or OneDrive or M365 apps.

My point is Microsoft should stop supporting M365 from any Windows Server as it is by now.
It is a Server OS, not a user OS, albeit they are quite similar. WS vNext (maybe released around 2023-2024) seems to the Windows 11 GUI, which is welcome in some parts and consistency but still suprising to me.

For RDS, if you really need it the same way, you could step back to the Office LTSC version and licensing.

One reason the Office Team keeps trying to avoid supporting M365 on any LTSC serviced Windows OS, including Windows Server, is the non-matching support matrix of both products. No matter if you are using M365 on deferred or current channels.

Please look forward for the licensing changes coming October 1st, which should offer alternatives for these not seeing the need to switch to AVD on AzureStackHCI on-premises but need to host VDI on-premises.

[#17]

There are no plans to auppprt on-prem, is basically what is being stated here. Yes? Interesting decision to throw away all those dark site, grey site and black site dollars.

[#18]

My current hypervisors can do all that too (with RDS on VMs, no one is on physical anymore) cheaper than Azure HCI, and in some cases it's unnecessary due to RDS hosting multiple users in one OS, so code is only loaded once, why do we need memory dedupe in that case anyway?
If I felt Microsoft would guarantee always releasing an LTSC of Office that would connect to 365 services, I'd feel better about M365 apps not being supported on Server, but I have the feeling (and don't tell me I'm crazy and it will never happen - people are wrong about those things all the time) that Microsoft will eventually say "sorry, no more Office LTSC, you gotta run 365 and if that means you gotta run on Azure VD then I guess that's your problem!" That's a situation we DON'T want to happen.

[#19]

I feel you, and agree it is quite uncertain what happens with Office LTSC, especially since Office 2022 LTSC release is quiet.
Just want to make clear that AzureStackHCI + AVD would be one option. Not intended to say it is the option.
"no one is on physical anymore"
In my posts and replies I always assume we are talking about virtualized workloads, too.

Repeating myself wait for October and check licensing terms before further decisions and conclusions on the matter. We need to have it written (and stable) in the product terms what is going to happen.

[#20]

@EldenChristensen 

we have been using Server 2022 with Office 365 since the beginning of 2022. We have made Server 2022 a thermal server and installed Office there. This can be used as a remote app or as a full terminal server. At one customer we also have a Server 2022 with Office 365 Apps for Enterprise for testing. This customer has been using this for about 2 months with no problems.

[#21]

Great news! Thank you for the feedback, keep it coming!!!