Microsoft Intune Reviews

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.

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.

I work with Microsoft Intune full-time as an integrator. I work on M365 portfolio applications, which are major use cases for Microsoft Intune. Microsoft Intune is for end device management where I handle Windows device management, AutoPilot enrollment, and policies and compliance management for the end devices.

Cloud-based device management is the best feature for me as it impacts my company the most; it is much easier than the previous Configuration Manager or SCCM. Administration and management can now be easily accomplished anywhere, anytime through the Microsoft Intune portal.

Two methods are available: I can accomplish all administration management through the portal, and the same thing can be accomplished using Microsoft Intune Management Shell, which is the command prompt and API.

Microsoft Intune brings all of my endpoint and security management tools into one place.

From a security standpoint, I can manage both BYOD devices and corporate devices; one will be Azure registered devices and another one is Entra ID joined devices. Joined devices will be the corporate devices where end-to-end complete security, compliance, and management is fully owned by the corporate. In the BYOD case, any device can be plugged in and registered to Microsoft Intune platform, which is compliant and compatible with corporate standards. Once that device is registered to Microsoft Intune, security, configuration, and compliance will be applied as per corporate requirements.

I am using Microsoft Intune Endpoint Privilege Management feature. This feature affects user productivity in the company because when a new user joins the company, the same device can be reused at a later time; I can wipe it or reset it, and the entire user profile and applications will be removed from the device so the same device can then be reused for new users.

I am using the advanced endpoint analytics in Microsoft Intune suite; it is another feature. Previously, logs and analytics were available from the local device perspective, but now everything from the end device is sent to the Microsoft Intune portal. Log Analytics and Endpoint Analytics workspaces can be configured to determine what datasets can be fetched by the portal. It is much easier depending on the requirement and need, and analytics requirements can be configured so everything is available in a central repository that can be easily monitored, viewed, and can also be integrated with Power BI for advanced reporting and data manipulation.

I work with Cloud PKI in Microsoft Intune. Many options are available, from the BIOS level to the operating system platform level; everything can be managed from the single, central portal which is Microsoft Intune. Many monitoring options and integration options are available to all the other M365 portfolio SaaS applications. Cloud PKI helps to manage the complexity of certificate infrastructure.

I have worked on UEFI and trust hierarchy based on end devices like laptops or desktops; I have a platform key certificate, PK certificate, and DB certificate. This is at the very core of any end devices and defines what applications can be installed or allowed to install on the end device, trusted by the PKI architecture, which is ideally a UEFI secure boot concept where only trusted applications can be installed onto the end device. Anything listed in the revoked DBX database, known malicious vulnerabilities, cannot be installed or will be blocked from getting installed on the devices.

I am using CoPilot in Microsoft Intune; it can be enabled or is available for the Microsoft Intune portal and all of the M365 application space. I can input my questions and CoPilot provides the best possible answers or methods on how the target can be achieved. I extensively use it for PowerPoint presentations; I provide some very basic inputs and CoPilot gives me a well-structured presentation in different formats. CoPilot is available in Microsoft Intune side, Word, Access, Excel, and everywhere CoPilot is enabled; it is next-generation AI that Microsoft is bringing. CoPilot helps to protect my environment by simplifying my IT and security operations. CoPilot helps with this simplification by identifying the content of the document, such as whether it is internal or confidential, whether it can be shared or if it is a restricted document.

Automations in Microsoft Intune can be more elaborated; KQL (Kusto Query Language) is available, but if multiple automation options were readily available, which would include PowerShell, KQL, JSON, and different interpreters like VS Code or Python readily available from Microsoft Intune, it would help administration and management much better.

I have been dealing with Microsoft Intune for almost four or five years.

Microsoft Intune is stable because since it is part of the Microsoft product suite, it provides 99.9999 SLA downtime.

I rate customer support from Microsoft as outstanding because anytime I can raise my concerns directly through the portal and I get a quick response from Microsoft.

Positive

Before Microsoft Intune, I was using something called Configuration Manager, which is an on-premise solution. Configuration Manager is again Microsoft, the Microsoft Configuration Manager, which is an on-premise solution, not from the cloud. Now everything has been migrated, and everything is from the Azure cloud; Microsoft Intune is part of the Azure cloud solution.

I find Microsoft Intune quite affordable. I rate this solution nine out of ten.

The primary use case for using Microsoft Intune is to secure the endpoint and device management, along with a strong focus on enforcing compliance and enabling secure access within our corporate resources. When a new user joins, we use Windows Autopilot via Microsoft Intune to provision their laptop. As soon as the device connects to the internet, it automatically joins Microsoft Entra ID. Security policies are applied, and the required applications are also installed automatically. This is our real-time example of how we use Microsoft Intune.

The best feature of Microsoft Intune is its unified endpoint management. The second thing is the conditional access integration, as we can deeply integrate with Microsoft Entra ID. This is also one of the best features, along with its automated policy and device provisioning.

We rely on the automated provisioning feature the most, as it is really great for onboarding that we use frequently.

Microsoft Intune has positively impacted our organization by covering processes, improving security, and saving time. The centralized endpoint management is really helping us to reduce the administrative overhead, and it has made it easier to maintain consistency in the configuration part. We are able to onboard and deploy faster with the help of Autopilot and automated policy deployment, so it is really saving us time and money.

We have seen almost 40 to 60% faster deployment during onboarding, and time saving is a really big matter. It has saved us almost 50 to 60%.

Microsoft Intune is working well, and all the features are very useful and smoothly working without any significant frustrations or wishes for change. I think nine is a very good rating for this solution, and I kept one point out because I think in the future it requires improvement based on future scalability in the IT infrastructure.

I have been working in my current field for more than five years.

Microsoft Intune is very good and stable.

Microsoft Intune is really handling our organization's growth in terms of scalability.

The experience with customer support has been positive, and they are really technically rich.

We have not switched from a different solution before Microsoft Intune.

We have seen great time saving and also money saving as employees don't waste their time in deployment because of automation. It automatically onboards.

We have seen almost 40 to 60% faster deployment during onboarding, and time saving is a really big matter. It has saved us almost 50 to 60%.

My experience with pricing, setup cost, and licensing for Microsoft Intune was straightforward, and it is a very good experience.

We have not evaluated any other options before choosing Microsoft Intune.

If anyone is planning to implement Microsoft Intune, they should start with the identity and access design, plan their device enrollment properly, and start small before scaling up. This advice will be really helpful. I gave this solution a rating of nine out of ten.

I am a consultant and architect of Microsoft Intune, and previously I was also an internal customer of Microsoft, using Microsoft Intune.

I work with Microsoft Intune to manage cloud-only devices, mainly Windows, and this includes the migration process from hybrid join to cloud-only environments, enforcing policies via configurations and scripts, and implementing the RBAC model to set up permissions for different roles for customers.

Additionally, I implement macOS with iOS and iPadOS in fully managed mode and personally owned mode, such as BYOD. I am currently focusing on automation, attempting to build a solution that maintains governance, ensuring customers can focus on specific parts of Microsoft Intune and automate the monitoring of compliance of devices and their status.

I tried using Microsoft's Copilot in Microsoft Intune, specifically the Security Copilot, but I have not gained experience with real-world examples. I made an attempt to set up the onboarding agent diligently and managed the device offboarding process.

The most valuable feature of Microsoft Intune for me is its fully cloud-based nature, allowing me to work from anywhere, whether I am using my mobile phone, Windows, or macOS devices, so I can access it from any place at my convenience.

The specific feature that makes me choose Microsoft Intune over other tools is its integration with Microsoft services, specifically the connection with Entra ID, Azure, and collaboration tools. This is the main reason I recommend Microsoft Intune as the proper MDM solution for any company, although I am aware of alternatives such as Jamf or Zebra systems that cater to different needs.

My assessment of the user experience of Microsoft Intune is that it is sometimes good and sometimes poor, depending on Microsoft's infrastructure. There have been outages affecting not only Microsoft Intune but also connected services such as Entra ID, which can be frustrating, especially when demonstrating features to customers and encountering issues.

While there are many aspects that can be improved, such as log visibility and the accessibility of detailed information, I recognize that Microsoft Intune does have room for improvement.

Other areas of Microsoft Intune that could be improved include the enrollment process for Windows devices, which remains quite simple. Customers have expressed a desire for more customization options during enrollment, such as adding custom steps. This capability was possible in the previous Microsoft Endpoint Configuration Manager, leading to questions about why Autopilot does not offer the same functionality.

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

I assess the stability and reliability of Microsoft Intune as being in good shape. It is evolving continually every month with new capabilities and fixes, which is beneficial for all users. I see a promising roadmap ahead, indicating that it is well-managed by Microsoft.

The stability and reliability of Microsoft Intune are crucial for me and my customers, as many of us rely heavily on Microsoft services. Any disruptions greatly impact operations, but fortunately, Microsoft has effective SLAs for its services, so we are not faced with hypothetical scenarios regarding poor performance.

In terms of scalability, I find Microsoft Intune to be an excellent tool for managing devices, designed for simplicity, making it user-friendly from an administrative perspective. With capabilities for scripting and application configuration, it works well for managing hundreds to thousands of devices.

While it supports macOS and iOS, the inclusion of Linux support would enhance its capabilities, considering Linux devices often lack visibility in IT management.

I have communicated with Microsoft Intune's technical support a few times, and my experience has been that I first need to explain my case to L1 support, which can be time-consuming before reaching someone with the necessary expertise, such as product management.

The worst experience involved a limitation related to Windows 11's multi-kiosk capability, which Microsoft confirmed was by design. Conversely, my best experience involved quick communication with a senior-level contact regarding a governance issue in Czech Republic, which was resolved efficiently.

Based on my experience with technical support, I would rate them a six out of ten.

Before adopting Microsoft Intune, I had the opportunity to work with Jamf, which focused on Apple devices, but I have not used other similar tools.

I participated in the initial setup and deployment of Microsoft Intune in different environments, including my own, and I found that the deployment was straightforward. Microsoft's documentation provided clear guidance, which I appreciated.

As for return on investment with Microsoft Intune over the years, I find it difficult to quantify because there remains a need for personnel to manage Microsoft Intune, from L1 to L3 support. It appears that it does not reduce staffing costs, and while AI may offer different advantages, Microsoft Intune alone does not alleviate staffing expenses.

Currently, I do not use Microsoft Intune Suite's Cloud PKI and have only theoretical knowledge about it, as I have not had the opportunity to implement it with a real customer or personally interact with it.

I am not currently using the enterprise application management features of Microsoft Intune Suite due to the strength of the global Microsoft Intune community and the abundance of existing tools such as Enterprise App Management, making it difficult to persuade customers to adopt it.

I also do not use the advanced endpoint analytics in Microsoft Intune Suite, although I understand its KQL language and data usage, similar to the enterprise application management features. Customers are not utilizing it.

Regarding Microsoft Intune's pricing and licensing, I find the default option, particularly Microsoft Intune Plan 1 included in most Microsoft licenses, to be reasonable for managing devices.

However, I consider Microsoft Intune Suite, which includes features such as Cloud PKI and Advanced Analytics, to be quite expensive, making it difficult to justify the cost to customers with large user bases, although I am pleased that Microsoft Intune Suite will be offered partially in E3 and fully in E5, which is a positive development.

Before choosing Microsoft Intune, I did not evaluate other options because Microsoft is so prevalent in the industry.

My overall rating for this product is eight out of ten.

My main use case for Microsoft Intune is its central endpoint management and supporting both universal correct access release and conditional access, while supporting remote and hybrid users with cloud-based device management.

Microsoft Intune has improved our organization by providing faster device setup, better security and compliance, easy centralized management, support for remote users, and reduced IT workload.

We have seen clear improvement in daily operations such as centralized management, where all devices are managed from one console, eliminating the need to handle systems individually. Actions are faster, such as pushing app updates or policies to all users at once, which leads to fewer configuration mistakes because everything is centralized. This results in faster support and fewer repeated issues, improved security, and overall less manual work for the IT team, along with faster issue resolution and a more consistent and secure user environment.

An employee is onboarding and a new user receives a company laptop. When a user logs in with company credentials, the device automatically enrolls into Microsoft Intune Autopilot. The required apps, Office, VPN, and security tools are installed automatically, and security policy encryption and antivirus compliance are applied automatically.

One significant aspect of Microsoft Intune is the automation; all devices follow the same configuration and security baseline, resulting in less manual work due to automated policies and app deployment. It not only manages devices but also enforces uniform setup, security, and reduces optional support across the organization.

Centralized device management is one of the best features Microsoft Intune offers, allowing me to manage all Windows, macOS, Android, and iOS devices from one console and apply policy settings and detection easily.

With Microsoft Intune, applying policy and detecting device status are very straightforward and save a lot of daily effort in real work, including one-time policy applied to all devices, automatic compliance detection, and quick troubleshooting features that save the most time. Compliance is automatically enforced; if a device is not compliant, such as lacking encryption, antivirus, or having an outdated OS, Microsoft Intune automatically flags it and restricts access. If a user disables antivirus, the device becomes non-compliant, and Microsoft Intune detects it automatically, blocking access to the company app until the user fixes it.

One more important point about Microsoft Intune features is the level of automation and integration. Automation includes policy and app deployment where most tasks run automatically, and integration with other security tools combines identity and enterprise security while providing flexibility to support both corporate devices and BYOD with app protection policies.

There are some areas of improvement for Microsoft Intune, including faster policy sync so changes can apply quicker, a simpler interface, better reporting with more details and clear insight, improved troubleshooting, clearer error messages and logs, and stronger support for macOS and Linux, alongside better cross-platform features.

A few more practical points on Microsoft Intune include more real-time control, better patch update control, stronger automation, and a single unified portal. Overall, improving real-time control, automation, and user experience would make daily operations much smoother.

I have been using Microsoft Intune for the last one to two years.

Microsoft Intune is now stable.

Microsoft Intune is highly scalable and designed for enterprise environments.

Customer support is good and properly supported; one-time support is also good.

Previously, we were using no solution, and it was mainly manual work.

Before choosing Microsoft Intune, we evaluated two alternatives: VMware Workspace ONE and Microsoft Endpoint Central and SCCM Configuration Manager. I chose Microsoft Intune because it is fully cloud-based and offers better integration with Microsoft 365 and Azure, making it easier for remote and hybrid environments.

I am a reseller of the company.

We have seen a clear ROI with Microsoft Intune; time saved has reduced device setup from three to five hours to thirty minutes, and there is a workload reduction of around twenty to thirty percent less manual effort from the IT team. Cost savings include lower support and infrastructure costs with no imaging servers; the biggest gain is automation leading to less manual work and faster deployment.

My experience with Microsoft Intune has been generally good, but with a lot of complexity. Pricing is reasonable if you already use Microsoft 365 and can be an add-on. The setup cost is low since it is cloud-based, with no hardware or infrastructure needed, and licensing is flexible but sometimes confusing due to multiple plans and bundles.

My advice to others considering Microsoft Intune includes some simple tips: plan before deployment, start with the pilot, keep policies simple, use Autopilot, and learn the basics of Azure AD security for better management since Autopilot saves time in device setup. I rate this product an eight out of ten.