Microsoft Intune Reviews

I can provide a specific example of how I use Microsoft Intune in my daily work. Application deployment and device configuration represent key areas where I utilize Microsoft Intune. For example, in my daily work, I use Microsoft Intune to deploy applications, assign configuration profiles, and enforce compliance policies on corporate devices. When a new device is enrolled, I can ensure it automatically receives the required security settings and business applications. This helps standardize the environment and reduce the operational effort.

Microsoft Intune is especially valuable when you need to standardize and automate endpoint management at scale. In my work, I have also used it to solve more complex challenges, such as migrating devices from traditional management to modern management, for example, from on-premises to cloud-first. A unique aspect is the ability to combine Microsoft Intune with tools like Windows Autopilot instead of SCCM OSD deployment. You can use compliance policies and conditional access to build a more secure and consistent user experience.

From an operational efficiency perspective, Microsoft Intune has helped reduce the amount of manual work involved in device provisioning, application deployment, and policy enforcement. We don't always measure it with exact numbers, but the improvement is clear in day-to-day operations. For example, preparing a new device now takes much less effort than in more traditional management models because many activities are automated and standardized.

Conditional Access is valuable for us and for everyone because it allows connecting device compliance with access control. In practice, you can use it to ensure that only compliant and trusted devices can access corporate resources such as Microsoft 365 apps and other company services. For example, if a device is not compliant with the security requirements, such as encryption, password policy, or device health, access can be blocked or limited. This is extremely important in an environment because it helps enforce security without relying only on the user's identity.

One of the biggest advantages of Microsoft Intune is not only the management itself, but also how well it integrates with other Microsoft technologies. For example, when you combine Microsoft Intune with Microsoft Entra ID, Conditional Access, Windows Autopilot, and Microsoft Defender, you can build a much more automated and secure endpoint management model. From my perspective, this integration is one of the main reasons why Microsoft Intune is valuable in modern environments.

Microsoft Intune is a very strong platform, but there are still some areas where it could improve. In my personal opinion, reporting and troubleshooting could be more detailed, especially when dealing with complex scenarios. I also think some features could be more consistent across different platforms, and some administrative workflows could be simpler. Overall, the product is very good, but there is still room for improvement in visibility and usability.

For example, the user interface could be improved in some areas. Sometimes the admin experience is not as intuitive as it could be, especially when features are spread across different sections or when it takes too many steps to find a specific setting or troubleshooting detail. I also think support and feature consistency across operating systems could be stronger. Windows is clearly the most mature platform in Microsoft Intune, and while some capabilities on macOS, iOS, and Android can feel more limited or less consistent, depending on the specific scenario. Overall, there is room to improve usability, visibility, and cross-platform consistency.

I have been working with Microsoft Intune for more than 10 years, mainly in endpoint management, device compliance, security, and modern workplace projects.

Yes, overall I would say Microsoft Intune is stable. It is a mature cloud service and in my experience it performs reliably for everyday endpoint management tasks such as policy deployment, application delivery, compliance management, and device administration. Microsoft also provides service health and tenant status visibility, which helps administrators monitor incidents and planned changes. Of course, like any cloud platform, it can occasionally have service issues or rollout delays, so it is not perfect. But overall, I consider it a stable and dependable solution for modern endpoint management.

Microsoft Intune is highly scalable because it is well suited for organizations of different sizes, from smaller environments to very large enterprises. One of its main strengths is that as a cloud-native service, it can scale without the same infrastructure constraints you typically have, for example, in an on-premises solution. In my experience, it supports growth well, especially when combined with the broader Microsoft ecosystem for identity, security, and automation.

I would say the customer support is generally good. It is reliable overall, although the experience can vary depending on the complexity of the issue. Standard cases are usually handled well, while more complex scenarios may take longer to resolve, but overall the support experience is positive.

Before Microsoft Intune, we used SCCM or Microsoft Endpoint Configuration Manager. The main reason for the switch was the need to move toward a more modern, cloud-based management model. Microsoft Intune offered better support for remote management, modern provisioning, and mobile device management, and also the integration with services such as Entra ID, Conditional Access, and Autopilot. It also helped reduce the dependency on on-premises infrastructure and made endpoint management more flexible and scalable.

This is a very big question because it's not just technical. My advice would be to start with planning and know it configuration. First, define your device scenarios, ownership model, enrollment method, security requirement, and application strategy. Then, and only then, use a phased rollout with a smaller pilot group before scaling broadly because Microsoft's own deployment guidance recommends a phased approach and highlights the need to plan enrollment prerequisites and support scenarios yearly.

Other

We have seen a return on investment, mainly in terms of time saving, operational efficiency, and improved standardization. We don't always measure it in very strict financial terms, but the value is clear in day-to-day operations. With Microsoft Intune, tasks such as device provisioning, policy deployment, application delivery, and compliance enforcement require less manual effort than in more traditional management models. This helps reduce administrative overhead and allows IT teams to focus more on higher value activities.

In my experience, the prices and licensing are reasonable, especially for organizations that are already invested in the Microsoft ecosystem. The value becomes clear when Microsoft Intune is used together with other Microsoft services because it is a part of a broader management and security platform. Setup costs can vary depending on the size of the environment and the complexity of the project, but in general, the cloud-based model helps reduce some of the infrastructure costs you would typically have with a more traditional solution. The main challenge I think is usually licensing complexity because understanding the different Microsoft bundles and plans can sometimes be less straightforward than the technical setup itself.

I didn't evaluate another option because the choice was mainly driven by the Microsoft ecosystem we were already using. Since we were already working with Microsoft technologies, Microsoft Intune was the most natural fit because of its integration with services such as Microsoft 365, Entra ID, Conditional Access, and other security and management tools.

Overall, my view is very positive. Microsoft Intune is a strong solution for modern device management. One of its biggest advantages is how well it integrates with the broader Microsoft ecosystem because it helps improve security and standardization. There are still some areas that could improve, such as reporting, but overall, I see it as a very valuable platform. I love Microsoft Intune. My overall review rating for Microsoft Intune is nine out of ten.

My use case for Microsoft Intune is for remote access and configuration management, and it primarily serves security purposes.

The lot of time we saved at deployment. 

Overall, the best features of Microsoft Intune are its ease of management and robust security protocols, which are what I value most about it and how it stands out. Copilot helps in keeping my environment protected by offering real-time assistance with security protocols and compliance checks.

Advanced endpoint analytics in Microsoft Intune help me to detect and remediate anomalies effectively.

Areas that have room for improvement in Microsoft Intune include network dependency, among other factors.

I have been using Microsoft Intune for some time, and my experience with it is extensive.

I would rate the stability of Microsoft Intune highly; I rarely experience downtime, bugs, or glitches. The stability is very high, with minimal issues.

I would rate the scalability of Microsoft Intune as an 8 from 1 to 10.

I would rate the technical support for Microsoft Intune as a 10 from 1 to 10.

The deployment of Microsoft Intune is generally easy, although I do encounter some complexities at times, and I have had challenges deploying it. Deploying Microsoft Intune is often a mixed experience; while it is easy, I have faced challenges at times.

The return on investment I have seen is about 20%. It has saved me time and resources, but quantifying a specific amount has been challenging.

I would compare Microsoft Intune favorably with other products and vendors on the market, emphasizing its integration capabilities and user experience.

Microsoft Intune is deployed in a hybrid model. I use it on Azure cloud, and the deployment time can vary, typically ranging from days to weeks. Approximately 100 users in Capgemini work with Microsoft Intune. My clients are primarily in the medium to enterprise business sector. The solution does require maintenance, and it is complex to maintain, especially regarding updates, patching, and releases. My thoughts on the pricing of Microsoft Intune are that it is fairly priced considering the features offered. From one to 10, I think Microsoft Intune is around a 5 in terms of being cost-efficient. I would rate the pricing of Microsoft Intune as a 5, where 1 is cheap and 10 is expensive. I am using the Enterprise Application Management feature, and it has been beneficial. I would definitely recommend Microsoft Intune to other users due to its features and support. My overall rating for this review is 9.

I mainly use Microsoft Intune for managing company devices and pushing apps and policies. It also helps us keep everything secure without too much manual work.

I used Microsoft Intune to roll out a new app to all company phones in one go. No manual install was needed. This saved a lot of time and everything was set up automatically for users.

We also use Microsoft Intune to enforce security policies such as screen lock and password rules on all devices. It keeps everything consistent and saves us from checking each device manually.

We mostly use remote wipe and device reset when a device is lost or someone leaves the company. It helps us protect data quickly without needing physical access to the device.

The best features are device management and app deployment. Everything can be controlled from one place. Additionally, the security policies and remote actions make it easy to keep devices safe without much effort.

The interface can be a bit complex to set up initially, so a simpler interface would really help. Additionally, better reporting and clearer logs would make troubleshooting easier.

Sometimes policies take a bit of time to sync, so faster updates would be beneficial. Also, better error messages would really help when something does not work as expected.

The setup and configuration can feel complex at times. Additionally, reporting and troubleshooting could be more clear and detailed.

I have been working in my current field for around five to six years.

Microsoft Intune is generally pretty stable for day-to-day use.

It scales really well. We have been able to manage more devices as the company grows without any major issues. Since it is cloud-based, it handles large numbers easily and we do not have to worry about infrastructure limits.

Customer support is decent overall. They usually respond and help resolve issues. Sometimes it can take a bit of time for complex cases, but nothing too frustrating.

We were using a basic manual setup and a few separate tools before. We switched to Microsoft Intune to have everything in one place and make management easier.

Take your time to understand the setup and policies in the beginning. It makes things much smoother later.

We have definitely seen a good return on investment with Microsoft Intune. It saved us a lot of time on manual tasks and reduced the need for extra tools. Overall costs went down as well.

Pricing was pretty reasonable since we already had it bundled with our Microsoft 365 license. Setup cost was minimal, mostly just time spent on configuration rather than any extra expenses.

We did look at a few options such as ManageEngine and Workspace ONE before deciding. However, we went with Microsoft Intune since it integrated better with our existing Microsoft setup and was easier to manage.

Microsoft Intune has been a solid and reliable tool for us. It has made device management and security much easier compared to before. I would rate this review a nine out of ten.

I am a mobile developer who has been involved in integrating Microsoft Intune SDK into applications. I can provide a general overview from both a developer perspective and a user perspective, as I have been using it corporately with Teams, Outlook, and other applications.

From the developer perspective, I have worked on integrating Microsoft Intune SDK into enterprise mobile applications. This work mainly involves implementing app protection policies, handling policy callbacks, and ensuring the app behaves correctly under compliance requirements.

Microsoft Intune helps enforce enterprise security policies at the application level. For example, when entering a mobile app, users might be required to enter an app PIN, and the system automatically encrypts the data. There are various other features like restricting copy-paste and enabling selective wipe of corporate data.

Microsoft Intune provides strong security controls, including strong application-level security, encryption, and data leakage prevention. A very important feature is the selective wipe capability. Whenever Microsoft Intune detects any rooted device or any tampering with the device, it involves both MAM (mobile application management) and MDM (mobile device management).

From the developer perspective, Microsoft Intune offers centralized policy management, which is another significant advantage because you can update everything remotely without changing the app.

From the user perspective, the experience is quite different because most controls are enforced seamlessly in the background. The primary advantage from the user perspective is the security aspect. Encryption and data protection happen in the background without requiring any manual effort, making the experience more seamless.

A lot of behavior depends on policies configured externally. It is not just that you code and then integrate the SDK. The Microsoft documentation about Microsoft Intune SDK is fairly structured, which is fine. The primary hurdle is the visibility gap between the Intune SDK and the Admin Portal. Improved logging or a 'Developer Mode' for policy simulation would help bridge the gap between the mobile implementation and the tenant-side configurations

There are many policy scenarios that are time-consuming and depend on external configurations. Additionally, the debugging process requires a test environment and dev environment, and getting access to those environments for debugging is challenging. It becomes difficult to determine where issues are occurring and why policies are not being enforced.

One major concern I have is user friction. When you enforce many policies and people log into apps like Microsoft Teams or Outlook, they encounter numerous MFA and other policies. Users feel friction due to additional authentication steps such as PIN or repeated login requirements.

From the user perspective, these restrictions can feel limiting. Blocking copy-paste or screenshots can sometimes feel limiting from a usability perspective. Another concern is limited visibility into why things happen. Users do not get full transparency because they see messages stating "Your device is blocked" or "You cannot access this right now," but the exact reason behind these messages lacks transparency. Additionally, many policies depend on device configurations and compliance. If the device is not compliant, users might lose access, which can be frustrating without clear guidance.

My suggestion for improvements would be better tooling for testing policy scenarios both locally and improved debugging support, which would make developers' work easier with Microsoft Intune.

I have been working as a mobile developer for one and a half years. I have been using Microsoft Intune for two to three years, dating back to university level where we had Teams, Outlook, and other applications. For corporate use, I have been using it for two years, and as a mobile developer, I have been using it for around one and a half years.

Microsoft Intune has been stable. Whenever we log into Teams, Outlook, or apps where we have integrated Microsoft Intune, the policies are getting enforced. However, sometimes when Azure AD  (Microsoft Entra ID) identifiers are not recognizable, the policies do not get enforced in very rare cases. This does not cause any application crash or a hard stop. It simply means that the identifiers are not identified and then policies are not enforced for that account at that point in time.

Microsoft Intune is scalable because you can include it in a variety of apps. As the application users increase and everything else related grows in size, Microsoft Intune is capable of handling all those scales.

We integrate the SDK and then configure the policies. We have a separate team responsible for looking into the configurations in the Azure portal, checking the effects, and managing the endpoint. As developers, we do not have access to that portal. A separate team handles those responsibilities.

As a developer, I focused on the implementation of the Microsoft Intune SDK. While our architecture team decided on the solution, I have researched other SDKs like those from VMware or MobileIron to understand industry standards for app protection policies. We found that Intune’s tight coupling with Microsoft Entra ID conditional access made it the most logical fit for our enterprise environment.

From the user perspective, Microsoft Intune enables access to corporate data and apps even on personal devices, which is convenient. The selective wipe feature builds user trust because only corporate data is removed while personal data remains untouched.

Users get a consistent experience across devices because the policies are centrally managed.

My use case with Microsoft Intune is mostly hardening our devices, but I'm also using it to set up some ASR rules. I think because we set up Windows LAPS, which required creating a new role, I would say I would stay with hardening and ASR rules.

With Microsoft Intune, we're using Autopilot and it makes deployment much easier. We are currently starting to use the Company Portal feature in Microsoft Intune.

In my five years of experience with Microsoft Intune, I appreciate that its behavior is different than other MDMs. I would say that we're setting up hardening on our Windows devices and because Microsoft Intune is a Microsoft product, it behaves much better than other MDMs on Windows.

It's really the beginning phase. When I worked at Samsung, I set up some managed Play Store, and it was pretty easy because you could upload or import your application and add it to the Microsoft Intune console and it appears in the Microsoft Manage Store. The process is probably the same right now.

App discovery sometimes works with Microsoft Intune. I think sometimes it's missing something, but in general, I would say it's pretty easy to find what I need.

Microsoft Intune is customizable. I know there are some custom settings that can be set, but it requires ADMX creation. That's why it would be much easier to use. There's a lot of API, and I think there is space for some additional features, not just some, but a lot of additional ones.

Microsoft Intune saves me time with automations, running processes, and access by about fifty percent, because I don't have to set up everything via registry editor.

Regarding JAMF, I would say JAMF is only good for Apple devices, as it's an Apple product, and the same is true for Microsoft Intune. Everything works perfectly with Microsoft using its own product. I would say right now that Microsoft Intune is one of the best solutions. I'm not a big fan of the IBM solution or Citrix. Regarding VMware, I haven't used it for three or four years.

I think it would be good to have many more policies in Microsoft Intune and stop using remediation scripts. It would be much more helpful.

I've been using Microsoft Intune for over five years.

I would rate the stability of Microsoft Intune a nine because there are no outages or issues. There are really not many issues within my whole career with Microsoft Intune.

I rate scalability a nine. It's pretty feasible.

My whole team is saying that they would rate technical support a three or four out of ten. Sometimes, I think it's good to mark it as a six because sometimes they are waiting for an issue to be resolved somehow, and sometimes we are able to overcome our issue. I would say five because sometimes after our support ticket, they change their documentation. Instead of helping us, they just change a few words in their documentation. They send us documentation saying to check it because it's by design.

I mean, they don't help us at all sometimes. They're just sending documentation and changing documentation and then sending us the article that says to check it. In their article, they described that it's a behavior and it won't be changed. This is how it should behave.

Positive

With Microsoft Intune, the user experience was difficult at the very beginning because I worked at Samsung and I enrolled Android devices. I have to say that Microsoft Intune was one of my least favorite MDMs because I just didn't get used to its UI. But that was the very beginning. I think now it's pretty easy, and I would say this is a really good MDM.

The initial deployment of Microsoft Intune is pretty easy to start. It really depends on how much I have to deploy because some environments need some additional things. But it usually takes days.

I'm not the one who is doing maintenance.

Our company was bought by another, and we're currently trying to persuade them to use Microsoft Intune with an E5 license. I think I will definitely recommend to them that it's worth it to use Microsoft Intune.

We currently have an E5 license, and using all of those features was really good. I'm not the one who's actually buying it. I think it should always be lower than its current price. It's really hard for me to say how it compares to other prices.

I don't use the advanced endpoint analytics in Microsoft Intune. We actually don't use it much because Microsoft Defender is taking care of it mostly. There's Defender for Endpoint.

I use Microsoft Copilot for additional questions. If there are some difficulties in enrollment or configuration, it's always good to ask Copilot and it helps navigate me to the proper troubleshooting. I would rate this product an eight overall.

I have used almost all features that Microsoft Intune provides for my use case, whether it is configuration management, remote access, or endpoint management.

The most valuable aspect of Microsoft Intune to me is the simplicity of the UI. It is not difficult for me to explain to my juniors how things work, and the admin console is well organized. For example, if I need to go to applications, I can navigate to Apps, then Windows apps or other apps. The organization is excellent.

The API is the best feature of Microsoft Intune. The Graph API is exceptional. I use Microsoft Graph API extensively through Python, PowerShell, or C# .NET SDK, and it is very effective.

It definitely saves considerable time with the new device provisioning process. Since the API is flexible and powerful, I have automated many activities that have saved hours of work. I would not say resources were saved, but hours were saved.

Microsoft Intune could be faster with client to server communication. Whenever I push something, it takes time. Sometimes it takes more than one hour to deploy on the Windows side, for example. Since Windows is a Microsoft product and Microsoft Intune is also a Microsoft product, it should be much faster, but it is too slow compared to other MDM solutions.

Speed is the main concern for people. Apart from these issues, there are definitely many things that could be proposed at the feature level.

Advanced discovery is an area where there is room for improvement. It provides whatever schema is designed in the backend, but when they say advanced, I should be able to fetch whatever I want. That is not the case. The feature has been added and they continue to add more. Perhaps in the future, they will provide additional functionality that can be utilized. The issue is that I can get reporting, but I cannot utilize the same reporting to convert it into a query for Azure AD groups to handle remediations or fix problems based on that data. I am not sure whether this is in the pipeline, but they have many research and development people, so they might be considering it.

I have been using Microsoft Intune for nine years and twenty-four days.

For stability, I would rate it nine point nine out of ten.

I would not rate it ten out of ten because nothing is perfect, but it is nine point nine out of ten for scalability.

I would rate the technical support at seven out of ten.

Microsoft outsourced the support to a third-party vendor, and they are not very effective. They are not good at handling issues, and they take too much time. I have to explain the same issues to multiple engineers, and they have a very rigid template. They do not think outside the box; they think only from the template perspective. That kind of approach drags out the issue even if it is not significant. I have given direct feedback to Microsoft on this, and support needs to be improved.

Positive

I worked with Jamf and I currently work with Jamf. One advantage of Jamf is that it is very fast compared to Microsoft Intune when it comes to client and server communication. Whenever I deploy anything, it reaches the device within a minute, but Microsoft Intune deployment is too slow.

Compared to other solutions in the market, Microsoft Intune is almost free because it is part of the Microsoft 365 E3 or E5 suite, which is why people do not complain much about the speed. In parallel, Jamf charges more than seventy USD per device per year. Microsoft Intune is a very cost-effective solution.

Initial deployment is very easy.

If somebody has good or even moderate knowledge and experience, they can set up the tenant and make it ready to use at a basic level within two or three hours.

Approximately thirty-three percent of ticket automation has been achieved. If I receive one hundred tickets, I now receive around seventy, so thirty percent of the tickets are automated. I am planning to increase this further to reach fifty percent this year.

I would definitely recommend Microsoft Intune to other administrators because this MDM tool provides the capability to manage Android, iOS, Windows, Mac, and now they have added Linux support. All these platforms can be managed from a single console, and I do not have to buy additional device-based licenses. It works on user-based licenses, and one user can use multiple types of devices without paying much. Other features such as application management are available, and it integrates well with conditional access to identify real-time threats during sign-in. Microsoft Intune is a very effective solution from my understanding, and I definitely would recommend it. The overall review rating I would give is nine point five out of ten.

I started my career with Microsoft Intune, so I am very close to it, and all aspects are fine except for the speed issue. For this reason, I would rate it nine point five out of ten.

My final rating is nine out of ten.

I work exclusively with Microsoft products, and we use the E3 license for Office, for the Microsoft portal, which includes some security solutions, SharePoint, and Office applications. Microsoft Intune is mandatory in our business. I work with Microsoft Intune as an integrator, user, and administrator.

The major purpose for using Microsoft Intune is enforcing policies, controlling onboarding processes of computers, and enforcing privacy and data link prevention. I am using Microsoft Copilot in Microsoft Intune. I am using the Enterprise Application Management feature in Microsoft Intune Suite.

The biggest benefit for me in Microsoft Intune is control. I can control my users and what they can do, and enforce the policies that I want to enforce. It is a great tool to control and put structure, to take the organization to the place I want to take it.

Microsoft Intune changes my ability when it comes to app discovery, deployment, and automatic updating. If I were to give it a score, I would give it eighty percent.

I do see that Microsoft Intune is saving me a significant amount of time. I think it allows me to do one hundred percent more within my time.

I would assess the user experience of Microsoft Intune as not user-friendly in general. It may cause some problems or require more time for training because it seems that Microsoft is doing their best to confuse me with menus that move to a different location every other day. However, there is a lot of knowledge online, so it is doable.

The information Microsoft Copilot provides is of concerning quality. It could be so much better if it would take me to the correct menu that I am looking for instead of giving me instructions to places that do not exist anymore. It is not something that I would recommend somebody to use.

Microsoft Copilot in Microsoft Intune is absolutely useless for protecting my environment.

I do not have any other areas for improvements that I have not mentioned or anything more that could be enhanced.

I have been dealing with Microsoft Intune for six to seven years.

I have not experienced any downtime, crashes, or performance issues with Microsoft Intune. Overall, I could say that Microsoft Intune is very stable.

As for scalability, I find Microsoft Intune scales very well with the growing needs of my company. I do not see any limitations, and it is not expensive to scale, so it is very flexible.

I have interacted with technical support from Microsoft. My experience is neutral because it is easier to contact ChatGPT to find answers. Based on my interactions with support in the past, I would give them six points from zero to ten, where ten points is the best. I give them six because it is hard to find them, and then it is hard to understand what they say usually because of accent issues with people coming from India or Africa or elsewhere, which I respect, but it is hard to understand for me.

Positive

Before Microsoft Intune, I was using another product for the same purpose that I forgot its name, but it was awful.

My experience with the deployment of Microsoft Intune is that it was straightforward. The deployment part is not complex.

I bought Microsoft Intune directly from Microsoft.

The pricing is reasonable.

I replaced the product with something else, but I forgot what it was. The reason for replacement was that I think Microsoft Intune is better and it is integrated inside our environment. It is much easier to connect it to the environment than to bring a third party and connect it.

I try to use Microsoft Copilot, but it is uncomfortable. It seems that ChatGPT usually knows better what to do, and the last time that I used it, I used it to find how to get rid of it. I give this review a rating of eight.

My main use case for Microsoft Intune is centralized endpoint and mobile device management. I use it to manage Windows laptops and mobile devices, enforce security and compliance policies, deploy applications remotely, and monitor endpoint security across the organization. It also helps me support remote users and maintain better control over corporate devices through cloud-based management.

In my day-to-day work, I use Microsoft Intune to manage company laptops and mobile devices remotely. For example, when a new employee joins, I use Microsoft Intune to enroll the device, apply security compliance policies, push required applications such as Microsoft Office and VPN software, and configure device restrictions automatically. I also use it to enforce password policies, enable device encryption, manage application access, and ensure only compliant devices can access company resources through conditional access for mobile device management. I use Microsoft Intune to control corporate email access on Android and iOS devices and remotely wipe company data if a device is lost or an employee leaves the organization.

Overall, my main use case with Microsoft Intune has been improving centralized device management and strengthening endpoint security. It has simplified day-to-day administrative tasks, particularly for remote users in a hybrid work environment. The automation capabilities for policy deployment, software installation, and compliance management have helped reduce manual effort and improve operational efficiency across the organization.

The best features of Microsoft Intune are centralized device management, compliance policy enforcement, and seamless integration with the Microsoft ecosystem. Some features I use most are remote device management and monitoring, application deployment and automatic updates, compliance and security policy enforcement, conditional access integration with Microsoft 365, mobile device management for Android and iOS, endpoint security configuration from a single console, and remote wipe and device reset capabilities for lost or inactive devices. These features have helped me manage endpoints more efficiently, improve security, and support remote users without heavily depending on premises infrastructure.

The feature I rely on the most in Microsoft Intune is compliance policy management integrated with conditional access. It helps ensure that only secure and compliant devices can access company resources such as email, Teams, and internal applications. I rely on these features daily because they improve endpoint security without requiring manual verification from the IT team. It automatically checks device compliance such as encryption status, antivirus health, password policies, and operating system updates before granting access. This has been very useful for managing remote users and maintaining security standards across the organization.

Another aspect I appreciate about Microsoft Intune is its ease of integration with other Microsoft security solutions. Features such as automated policy deployment, remote troubleshooting, and centralized visibility make day-to-day administration more efficient. It has also helped me reduce manual configuration efforts and maintain consistent security policies across all managed devices.

Microsoft Intune has positively impacted my organization by improving centralized endpoint management, security, compliance, and support for remote users. It has reduced manual administrative work by automating device enrollment, policy deployment, and application management. The platform has also helped strengthen security by ensuring only compliant devices can access company resources. Remote troubleshooting and cloud-based management have improved operational efficiency, particularly for a hybrid work environment where users are working from different locations. Overall, Microsoft Intune has helped me manage devices more efficiently while maintaining better security and compliance standards across the organization.

Microsoft Intune could be improved in several areas. The initial setup and policy configuration can be complex for a new administrator, particularly when managing multiple device platforms and integrating with other Microsoft security solutions. Troubleshooting and reporting could also be more user-friendly. Sometimes it takes time to identify the exact reason behind policy failures or device compliance issues because the logs and error messages are not always very clear. Another area for improvement is faster policy synchronization and more detailed reporting dashboards. Support for advanced management features on non-Windows devices such as Mac OS and Linux could also be enhanced further. Overall, the platform is strong, but simplifying administration and improving visibility will make it even better.

I would also appreciate simple troubleshooting tools and more detailed real-time reporting to help administrators resolve issues faster in Microsoft Intune.

I have been working in my current field for fourteen years.

My advice to organizations planning to use Microsoft Intune is to first understand their endpoint management and security requirements clearly before deploying. Proper planning for compliance policies, device enrollment methods, application deployment, and conditional access configuration is very important for a smooth implementation.

Since adopting Microsoft Intune, I have seen noticeable improvements in endpoint management and operational efficiency. Manual device configuration time has reduced significantly because policy applications and security settings are deployed automatically through Microsoft Intune. I have also reduced the number of support tickets related to device configuration and remote user onboarding. Tasks that previously took hours, such as provisioning a new laptop or applying security configuration, can now be completed much faster through automated deployment. Another major improvement has been better compliance visibility and faster responses to non-compliant devices. The centralized management approach has helped my IT team monitor and manage endpoints more effectively while supporting users working remotely from different locations.

In my experience, the AI-driven security-related capabilities in Microsoft Intune provide good governance and endpoint protection, particularly when integrated with Microsoft security solutions such as Defender and conditional access. The platform helps enforce compliance policies, monitor device health, and automate security actions based on the risk level. Features such as compliance enforcement, access control, and automated remediation help strengthen governance and reduce security risks across managed devices. However, I believe there is still room for improvement in terms of more advanced AI-driven analytics, clearer security insights, and simplified policy recommendations for administrators.

In my experience, the AI-driven recommendations and security insights in Microsoft Intune are generally accurate and reliable for identifying compliance issues, risky devices, and security-related events. The integration with Microsoft security services helps provide consistent visibility across endpoints. However, there are situations where alerts or recommendations require manual verification to avoid false positives or policy conflicts. Overall, the output is reliable for day-to-day endpoint management and security monitoring, but administrators still need to review and validate critical actions before implementation.

My organization's relationship with Microsoft is that of a customer and end-user of the solution. I would rate this review as eight out of ten.

I manage around 3,000 Windows devices across different countries. Before that, I used Microsoft Intune as a consultant at Cluster Reply, working with customers including IVECO Group. Over time, I have also worked with related tools including Autopilot, Autopatch, and Entra ID.

I value Windows Autopilot in Microsoft Intune the most. Devices set themselves up when turned on for the first time, eliminating the need for manual imaging. Windows Autopatch is another feature I use extensively to automate Windows updates across different groups of devices in a safe and phased way. Remediation scripts are also a feature I use frequently because they allow me to execute small scripts that automatically detect and fix configuration problems on devices.

Using Microsoft Intune has helped my organization save time through automatically executing actions remotely on devices. This is a great advantage because we do not need to go physically to each device and execute actions manually. We can use Microsoft Intune to automatically execute them instead.

I use advanced endpoint analytics in Microsoft Intune to verify the health status of our devices. With advanced endpoint analytics, we can identify devices that are in a bad health status and determine the boot status of the devices, including how long they take to start and turn on. This feature provides several other capabilities that are very helpful for IT administrators.

Microsoft Intune is an easy solution for IT administrators, and I would recommend it, though this depends on the organization. There are a few areas where Microsoft Intune still needs improvement. For example, app packaging, policy conflicts, and reporting require attention.

Reporting in Microsoft Intune presents challenges because the built-in reports are often too basic. For detailed data, you usually need to set up Log Analytics and write custom queries. Policy conflicts are another concern, as when two policies target the same setting, it is not always clear which one takes precedence. This can cause unexpected behavior. App packaging is also an area for improvement, as packaging Win32 apps for Microsoft Intune is more manual and time-consuming compared to SCCM, Configuration Manager, which is an on-premise tool.

I have been using Microsoft Intune for over four years.

I would rate the stability as seven. In my opinion, it can be improved because sometimes we experience bugs in the portal, which is why we prefer to interact with PowerShell to automatically perform our tasks.

I would rate the technical support for Microsoft Intune as eight.

I have used Workspace ONE in a few projects. I prefer Microsoft Intune because it is more user-friendly than Workspace ONE, and it is easier to deploy devices and patch managed devices with Microsoft Intune.

Deploying Microsoft Intune is really easy. Compared to SCCM Configuration Manager, Microsoft Intune trades some low flexibility and control for cloud-native scale and simplicity. SCCM still wins for complex software deployment scenarios, but Microsoft Intune is a good upgrade that is easy to deploy without any need for a VPN.

I would say Microsoft Intune saves us about forty percent.

It is a little expensive for organizations using Microsoft Intune. I am aware that Microsoft increased the cost of the E3 and E5 licenses starting from July, and I think that this pricing is a bit expensive.

I use Security Copilot in Microsoft Intune to troubleshoot issues. For example, Copilot is really helpful for understanding policy conflicts because it allows me to understand the root cause of the issue. I also use it to identify non-compliant devices and determine how to remediate them, either by understanding how not to patch the devices or by using an existing catalog rather than a remediation script.

Microsoft Intune provides good integration with other products. For example, it integrates with the HP Portal Company to manage the BIOS settings of the devices and their updates, and it integrates with Configuration Manager and Entra ID. This integration provides a good experience with other products.

My feedback is positive, and I would recommend Microsoft Intune to others. I would say that Microsoft Intune is absolutely the right choice for any organization that is already invested in the Microsoft 365 ecosystem and wants a unified cloud-native endpoint management approach. I give this product an overall rating of nine out of ten.

My use case for Microsoft Intune is to secure data and manage apps on devices such as Windows, Macs, and Android mobiles, effectively managing both organizational devices.

The best features in Microsoft Intune include secure authentication, which I find very favorable, and the fact that we can remotely push applications. For instance, if a user needs any application installed on their device, they will raise a ticket, and we will push the application from Microsoft Intune, which will automatically appear on the device in 30 to 45 minutes, making it easy for users to download. The interface is user-friendly, allowing us to easily find options for apps and devices, and we can quickly locate user details and asset information.

Our company's relationship with Microsoft Intune is that HCL is using it to provide services, and we are from administration supporting the end users, equipped with admin rights and a certificate to do so, and we configure and push applications to their Windows devices.

The enterprise application management feature helps in app discovery, deployment, and automatic updating, as updates are automatically identified within the interface, allowing us easy access to application security groups.

I do use the Cloud PKI feature.

I use Copilot to easily identify corrections needed, for example, if we need to send an email, it will automatically correct it in a formal way, and it also helps provide instant troubleshooting assistance.

I use advanced endpoint analytics for managing secure data and controlling apps from the console.

Microsoft Intune helps to easily detect and remediate anomalies in endpoints; it is very straightforward to identify all issues through the interface.

There is room for improvement in Microsoft Intune's understanding and user experience as the interface is easy to navigate for deploying applications and finding user information, but I think there should be a reduction in dependency on on-premises infrastructure and focus on artificial intelligence and automation to improve further.

I have been using the solution since 2022, with my experience lasting until 2025 onwards.

I absolutely use Copilot.

I utilize the enterprise application management feature.

Negative

The deployment for Microsoft Intune is easy; everything can be understood easily, and we can deploy everything without challenges, making it user-friendly.

It only takes 30 to 45 minutes to deploy Microsoft Intune.

In my opinion, the pricing for Microsoft Intune is somewhat expensive, but I do believe it is a reasonable price.

I would compare Microsoft Intune very favorably, and I can confidently refer end users to use it.

My deployment model for Microsoft Intune is entirely cloud-based and is on Azure Cloud.

Mostly, we have nearly 2,000 end users using the solution.

The solution requires maintenance; we mostly deploy applications and drivers, and if there are any patches, we can also deploy them from Microsoft Intune.

I would rate this review a 10 out of 10.