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
Hi -_RH_-
"I'm pretty sure the non-LTSC versions of Server they've released don't have CSP support either."
I agree with you, if this were the case also Azure Stack HCI, especially it is a cloud touched product, would support it but does not afaik. Hence Azure Stack HCI OS and Windows Server Datacenter Azure Edition do support Automanage, so their scope to manage Server OS and Client are still diverged, not only in terms of policies, but also in Terms of Security + Update Management. This is a model I am not agreeing with as it causes complexity for common to SMB and SMC for generic tasks. The target are corporations that have and can afford dedicated teams, and then it is fine also in terms of RBAC. I believe though, that this conception and weaknesses have been brought to attention already and I personally do not believe in a change here, solely as this would imply to redesign the whole Azure platform services, including on-premises via Arc. That's too much to ask.
If we wonder why non LTSC version and named Azure centric OS do not offer CSP, well they have no GUI. Allow me to name a detail, even though it is a command-line, you cannot join WS Core to Azure AD via dsregcmd.exe, while it is present (for unclear reason) in the GUI installation option. This could give you an impression about their heading in this regard. I do not want to speak for them or their design decisions though, just my 2 cents.
Hello Deleted 🙂
I think I follow what you're describing/speculating. It sounds like the forked management model plan is Client for customers, and Server primarily for... Microsoft itself (for Azure). Customers now also have access to those same Azure management tools (including on-premises via Azure Stack HCI and Arc), but while these controls may make sense for Microsoft's use, they don't really map that nicely to how customers manage their servers. They are a subset of GPO/SCCM/CSP controls, and unless this is some hidden thing I've not yet stumbled across, some things simply can't be done because of that gap, such as applying Conditional Access controls based on Compliance status.