Windows Server as a REST API
Delegating access to Windows Server functions (e.g., create a DHCP reservation, modify a DNS record, provision a share, etc.) in a heterogeneous, modern, self-service environment is greatly hindered by available protocols. While RPC, CIM, psremoting/wsman/soap, et al. are technically open, they are far enough from modern mainstream app heterogeneous ease of use that they are practically Windows only.
Windows should provide a facility to easily expose Windows functions as simple REST-ish APIs accessible to any calling platform. JEA makes a great engine for executing delegated functions, so I would imagine using JEA or similar as the execution context, but with a REST-ish API in front of it to take requests and return results as JSON or whatnot.
This isn't a new idea (see https://blogs.msdn.microsoft.com/powershell/2014/09/29/simple-http-api-for-executing-powershell-scripts/ and https://technet.microsoft.com/en-us/library/hh880865(v=vs.85).aspx ), but currently it is difficult to implement. Windows should embrace this scenario and make it easier to configure and deploy with strong security assurances and clear guidance.
Aftab Hussain commented
This should also be mandated for all the core features of the OS, then get added to other Microsoft products, such as Exchange, SQL, etc. You've already done this for IIS, https://channel9.msdn.com/Blogs/Seth-Juarez/Microsoft-IIS-Administration-A-new-way-to-manage-IIS