Forum Discussion
Support for M365 Apps (O365) on Windows 2022
First off I would like to thank everyone for the feedback and apologize for the delay in responding to this thread. Your feedback has made a difference, and sparked many internal discussions... we have customers running M365 on WS2016 and WS2019 today, and we want to enable staying current and secure being able to upgrade to WS2022.
<UPDATED EDIT> In response to your feedback we have announced support for M365 on Windows Server 2022, please see this link for additional information:
Windows Server end of support and Microsoft 365 Apps - Deploy Office | Microsoft Learn
Again, thank you for your feedback and passion!!
Elden Christensen
Principal Group PM Manager
Windows Server Development Team
asdasdadqwdq This is the Problem for us, too.
We have many small customer, who would not have that many Compute needs, to fill an Azure Stack HCI Node. So multitanancy would be helpful.
As far as I know, Citrix is Working on Support for Multi Tenant Windows 10/11 OnPrem.
With Multi tenant Support for Azure Stack we can switch our Workload from Terminalserver
to Multi User Client Operating Systems.
That would be a fair compromise for all, I think. And we have no trouble if the Next Server OS gets
Office 365 Apps
It is unclear to me why multi-user client is significantly different from terminal server, other than licensing. However, one thing that is sorely lacking in Server is Intune support, and this isn't really answered by Azure Stack HCI, either (Azure Security Center/Defender for Cloud =/= Intune, and it makes little sense to spin up/maintain/skill up on a non-cloud Config Manager for cloud-first orgs). Want to apply Conditional Access Compliance policies for Server? Can't do it. The technical answer I've heard is "CSP support doesn't exist in Server," but that kind of skirts the question, as it's coming from the company that could easily choose to add it.
Deleted That misses the point: Microsoft could simply choose to provide CSP support in anything they want: they make all the Windows versions, including the LTSC versions. I don't think it's that simple anyway, as I'm pretty sure the non-LTSC versions of Server they've released don't have CSP support either.
-_RH_- "It is unclear to me why multi-user client is significantly different from terminal server, other than licensing. [...]no Intune, CSP (Policies) support.
That's quite easy to answer. It is not only Windows Server that is in question but also all Windows Client LTSC versions. Mind Windows Server is also an LTSC version, while less dominantly named in the product.
This causes constraints, technically, to support products and techniques coming from Azure PGs.
Actively seeing this on the matter how much of work it is to bring winget to Windows Server, while possible, but not yet supported. It is on the roadmap for winget but it is clear that LTSC as a definition and missing dependencies makes it harder to implement.
I personally do not like the clear split of management of WS and Clients aswell. Especially for SMB there are no "server" and seperate "client" teams, opposed to enterprises.
- Bernd Dausch Until now, yes, but it was only recently that Server support for O365 was in question.
100% agreed regarding cost vs. VDI. There are some workloads for which terminal server is a better solution. The alternative seems to be multi-user client, but as server and client still use the same core and the process of modularization of the OS has gone far, the main difference from Microsoft's standpoint seems to be licensing. However, from a customer's standpoint, as many here have pointed out, there are many practical implications (or perhaps more to the point, many impractical implications). the Windows Client OS has always Support for Office 365.
so no need to wait if the pressure from the customers to microsoft is high enough
to get support for the next server Version.
and it is cheeper for the customers then VDI. And esier for us to maintain for us