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.

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.

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.

Microsoft Intune has been used in organizations ranging from US entities to Indian companies, with onboarding of systems in numbers ranging from 300 to over 7,000. We migrated from on-premise Active Directory to Microsoft Intune during COVID for remote work support.

As a user, I believe that Microsoft Intune is a superior tool that addresses many issues compared to previous methods, such as using a local Active Directory. As an administrator, I have a broader view of the system, allowing me to monitor whether users are online or offline, track their last activity, and manage various aspects effectively. This is a significant improvement over older methods, where we often had to inform users that certain activities were not approved due to insufficient access levels.

Microsoft Intune streamlines remote system access and management without a physical environment. I started my career in Active Directory configuration and Group Policy. In those roles, we provided systems to end users. When users went home and encountered issues such as password changes or other policy problems, troubleshooting those issues became quite challenging without physical access to the systems. However, using Azure and Intune has helped us resolve most of these issues. With these tools, we no longer need a physical infrastructure to manage systems, as we can push policies remotely and maintain control over the devices. This capability is a significant advantage of the cloud environment, as it allows us to streamline processes and provide remote access without reliance on physical setups.

Additionally, Microsoft Intune gives us a broader perspective, enabling us to manage policies for both users and systems through cloud portals. This approach allows us to deliver solutions much more quickly than the methods we previously used.

Reporting remains an issue, with challenges in providing comprehensive reports. For instance, while we can generate detailed reports for individual users—such as examining sign-up, sign-in, or audit logs—we struggle to produce aggregate reports for the organization. For example, if a user encounters issues logging into the system, we can monitor that specific case and provide detailed information. However, if the organization wants to know about multiple users experiencing problems with multi-factor authentication (MFA), we cannot compile a comprehensive report that highlights how many users faced this issue or identify the overall cause, such as a policy change. This limitation in Microsoft Intune is a significant drawback; we cannot produce overall reports on an organizational level. 

Another issue is that when configuring and deploying Microsoft Intune, some processes experience delays due to the cloud environment or other structural elements like the local area network and internet dependencies. I believe that if Microsoft Intune could operate through both agent-based and non-agent-based approaches, it would improve communication between cloud services and local systems. For example, the policies could first be downloaded to local systems, and once everything is ready, the deployment could occur. Currently, with Windows updates, we have control over when to deploy them, and we can see the status of the deployment, whether successful or failed. A more effective approach would be to allow for manual deployment initiation rather than automatic triggers. By implementing this, we could validate that the updates are properly downloaded and available on the local systems before proceeding with deployment. This streamlined process would enhance our ability to manage updates effectively.

Pricing can be challenging for startups or smaller companies. While larger companies have budgets for cybersecurity, smaller ones may struggle with recurring costs of cloud-based solutions like Microsoft Intune.

I have been using Microsoft Intune for five to six years.

We haven't encountered any specific session outages or similar issues, but one drawback of this cloud environment is that we cannot accurately inform the end-user or management about when the exact policy will be applied and when the results will be visible. The nature of cloud deployment means that the rethinking process can take about 30 to 45 minutes, and in some cases, it can take a few days, as we've experienced.

Regarding scalability, there are no issues. We successfully scaled from 4,000 to over 10,000 employees without major changes. I don't foresee any significant issues in this regard.

While we encountered some initial problems during the early days of deployment, the frequency of these issues has decreased. Most troubleshooting can now be handled on our end. I would rate them an eight out of ten.

Positive

We previously managed 4,000 to 6,000 systems globally using Active Directory before migrating to Microsoft Intune during COVID.

The initial deployment and installation are quite comparable to other tools, but it offers more flexibility, especially since most systems operate on Windows. While the deployment or configuration might take a few days, once we finalize the planning phase, the onboarding process becomes much smoother. We can effectively onboard the system with or without user assistance. A significant advantage is that we can complete migrations remotely, minimizing user dependency. For context, we previously used Active Directory to manage 4,000 to 6,000 systems globally. We migrated to Microsoft Intune and other security solutions during the COVID-19 pandemic, when many organizations transitioned to remote work. During that time, we began the migration process, which included transferring user profiles. Typically, it took about 38 to 45 minutes to migrate a system from on-premises Active Directory to cloud-based Intune, assuming the user had minimal data in their profile. If the profile contained more data, the migration time could vary, but the average was still around 45 minutes for one system.

Regarding maintenance, while new deployments may not require a specialized person on-site, ongoing security improvements or updates to organizational policies need to be handled carefully. These adjustments are not something that a Level 1 engineer can manage alone. Proper planning and execution by specialized engineers are essential to implement these changes effectively.

On the pricing side, the cost for tools like Microsoft Intune can be challenging for early-stage companies that cannot afford such expenses. For smaller companies, the comparison often leads them to choose a local Active Directory, as it involves a one-time cost for purchasing and configuring servers. With Windows Server's built-in Active Directory feature, there are no additional costs for customizing policies. In contrast, Intune is a cloud-based solution that requires a recurring monthly payment. Moreover, the price increases with every additional endpoint, which wasn't the case before.

This cost structure could pose challenges for startups that are struggling financially. However, companies aiming for a fully secure environment and those with a dedicated cybersecurity budget can plan to implement Intune effectively. In summary, I would say that Microsoft Intune is the best product for established companies. It can be quite difficult for new companies without a cybersecurity budget to manage the associated costs.

I would rate Microsoft Intune a ten 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.