![AWS OpsWorks [EOL] vs. Microsoft Intune report](https://www.peerspot.com/assets/media/images/icons/pdf-c33db68f.svg){kind=icon}
![AWS OpsWorks [EOL] Logo](https://images.peerspot.com/image/upload/c_scale,dpr_3.0,f_auto,q_100,w_64/ecwtjjlwilx2g4qujp0d5nz7cwsn.jpg?_a=BACAGSGT)
![AWS OpsWorks [EOL] Logo](https://images.peerspot.com/image/upload/c_scale,dpr_3.0,f_auto,q_100,w_30/ecwtjjlwilx2g4qujp0d5nz7cwsn.jpg?_a=BACAGSGT){kind=small}
![AWS OpsWorks [EOL] Logo](https://images.peerspot.com/image/upload/c_scale,dpr_3.0,f_auto,q_100,w_40/ecwtjjlwilx2g4qujp0d5nz7cwsn.jpg?_a=BACAGSGT){kind=small}
Regarding what I dislike about Microsoft Intune and its downsides, I would say that more Mac controls are needed because we have limited Mac and Linux control. When comparing controls and policies between Windows, Mac, and Linux, Windows has almost everything you can think of, while Mac and Linux have limited types of control. You cannot implement certain things on Mac and Linux that you can on Windows. The limited controls are a major issue. Additionally, if Microsoft could find a way to embed servers into Microsoft Intune, that would be beneficial. Microsoft Intune is not really designed for servers or Windows servers. It is more tailored towards Windows 11 and Windows 10 operating systems. Windows servers are not fully supported. Enterprise organizations usually have both servers and endpoints, which are users' workstations. For servers, most people look for other solutions such as SCCM, which is Configuration Manager. However, SCCM is what Microsoft Intune is trying to replace. Both SCCM and Microsoft Intune belong to Microsoft. Microsoft is trying to transition organizations into Microsoft Intune, the native cloud solution. However, because this update is still in process, servers are not fully compatible with Microsoft Intune and cannot be managed by it. The current policy that has emerged from issues with clients is what they call co-management, which is relatively new, and I do not know if adoption is significant. Many legacy or older customers who have been using these products for decades still have SCCM. When it is time for them to manage their Windows devices, they use what is called cloud attach. Cloud attach is a term whereby your SCCM is connected to your Microsoft Intune. Most people do not know about it, but I have deployed it for several organizations. Cloud attach and co-management work together so that your device is in SCCM, but some policies are pushed from Microsoft Intune. It is like two different solutions working hand in hand. That is what they call co-management. Microsoft Intune does not bring all of your endpoint and security management tools into one place, which is the goal and how it should be. However, as I mentioned, servers are not included. If we talk about end users, Microsoft Intune does bring all your devices together. In a typical enterprise environment, you have end users with workstations, laptops, company-issued phones, and bring your own devices. You can create policies for all of these. However, for the backend, your servers do not have much coverage. Servers are not really covered by Microsoft Intune in that way.
