Microsoft Intune Reviews

I am an IT consultant, and I mainly advise my customers on how to implement Microsoft 365 solutions like Microsoft Intune within small and large companies.

First of all, the integration with the rest of Microsoft's products is a major win. Secondly, it comes from a vendor for which we manage most of the operating systems, which is a big plus. 

As a software-as-a-service, it is updated monthly, meeting all the new functionality provided by the operating system vendors. If I don't have an endpoint management solution, I must go to each computer individually to harden systems, install software and data. 

Comparing this to having an endpoint management solution, the efficiency gain may be up to 80%.

The biggest challenge Microsoft has with its own product is supporting all the versions of its own product as well. A major challenge is making all the products work within device management solutions like Intune. It would be beneficial if Microsoft removed support for older products much earlier in the process. 

However, given that they have paying customers, it's not something they can easily do. Ideally, we would have a product capable of managing the latest versions of the operating systems without having to deal with outdated systems.

I have been using the product actively for about five to seven years.

Customer service is not really good. I would give it a six out of ten. The main issue is the time it takes to get someone involved who truly understands what the product does and what the real issue is. I do realize that my support requests are the more advanced ones. 

Getting used to working with a product like Intune is easier if I'm already familiar with other Microsoft products, as many companies are. The adoption rate is quite fast. Other vendors provide good solutions as well. Ultimately, it depends on what I am accustomed to. If I have worked for 20 years with VMware technology, then adopting the VMware endpoint management solution might be easier than switching to Microsoft Intune.

It really saves time and resources. As mentioned earlier, I need not go to each machine to update it and install software when using a device management solution. The efficiency gain might be between 60% to 80% compared to other products. If compared to another product I am accustomed to, the results may vary.

As a consultant, I advise customers and help them implement it. In addition, I offer a service where customers purchase configuration updates from me on a subscription basis. I ensure the Intune environment and other products remain up-to-date. 

Microsoft is doing a good job in this area, and many customers who ask for my help already pay for the license. Cloud PKI has similar issues, where other vendors provided that functionality before. Customers who needed it previously adopted third-party solutions. 

Now, Cloud PKI has been available for a year, serving as a good alternative provided by Microsoft, although many customers continue to stick with solutions they had already adopted. 

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

We use Microsoft Intune for mobile device management, which includes both endpoint and mobile devices.

The feature I find most valuable in Microsoft Intune is being able to configure policies and push them directly to mobile phones.

Being able to remotely wipe mobile phones in case they are stolen or misplaced is very important for us.

We're hoping we'll be able to deploy patches quickly once fully deployed. 

It's a cloud solution and you can easily scale. 

Currently, I have not seen any areas I want to improve in Microsoft Intune. We haven't gone far into using it. We still rely mostly on SCCM. We are trying to transition mobile device management and endpoint management from SCCM to Microsoft Intune, so we are still in the process of doing that. I haven't actually explored all the functionality of Microsoft Intune. Probably when we do that, I will have more to say about it.

A feature I would want to see added in Microsoft Intune is the ability to manage other non-Microsoft devices.

I have been using Microsoft Intune for probably three years.

Microsoft Intune has been stable and reliable.

It is a cloud solution, and you can easily scale as your needs grow.

Whenever we have had challenges, we were able to get Microsoft support on time. Not all technicians are knowledgeable of the Microsoft solution, so they have to work on that as well. Some technicians are good and give you the best support you can get, but some of them are not there yet.

Neutral

It has always been Microsoft solutions prior to adopting Microsoft Intune.

Microsoft Intune is deployed on the Azure cloud. I wasn't part of the deployment as it was already in use when I came to the company. 

The question about return on investment with Microsoft Intune would probably be for the Solutions Manager, as they manage all the solutions and would understand if there has been a return on investment. I don't have any access to numbers around that. Once we're done fully migrating, I'll have a better sense of ROI in terms of time savings.

We're not using CoPilot and INtune. The Copilot we use currently is just for Office 365.

I am also not currently using Enterprise Application Management in Microsoft Intune.

Advanced endpoint analytics is tied to Defender for Endpoint.

Once we are done fully migrating to Microsoft Intune, I will compare that with what we currently do with SCCM. Currently, with our Microsoft Intune, it is limited in the sense that it focuses more on mobile device management and less on other endpoint management. Once we have fully transitioned into endpoint management, I can compare and see how it helps in terms of patch management and deployment.

On a scale of one to ten, I rate Microsoft Intune an eight out of ten.

Public Cloud

Microsoft Azure

Our current use cases for the solution involve consulting and implementing for many customers. Primarily, the majority of our customers are India-based, but we have a few customers in the US. We essentially help them with all their device management, end-to-end, including mobile device management.

We are mainly using CoPilot in Microsoft Intune for configuration and from a productivity point of view. Additionally, we want to standardize many of these processes so we do not have to reinvent the wheel when we go to different customers. This is the context in which we are using CoPilot to help us speed up in terms of reusable objects that we can generate and then deploy across customers.

It is an ideal solution for customers who are a Microsoft-shop. The ecosystem plays a big role, and there is support for a variety of devices. I do not see any problem because Microsoft Intune supports all sorts of devices and platforms, but if their ecosystem is much more Microsoft, it is even easier for us from a configuration and implementation point of view.

We are using the enterprise application management feature in Microsoft Intune. We support end-to-end, and we have customers ranging from small to mid-size and large enterprises. Depending on the customer's needs, it may change, but we do use it. Enterprise application management in Microsoft Intune primarily helps in terms of throughput and productivity.

We can cater to more customers with the limited capacity that we have. We do not have to hire many more engineers, especially with CoPilot and other tools. Also, standardizing some of these deployment options across customers helps us to scale easily.

The most valuable feature of Microsoft Intune is that it is more of a one-stop shop, providing an easier experience. The seamless experience and remote management for customers from our office with our engineers are the most convenient aspects. It increases productivity and helps us to scale and expand.

The user experience of Microsoft Intune is very good. For the last eight years, we have been using it effectively. It is probably one of the best experiences. I do not have any complaints or problems. My team quickly gets through it, and they understand it easily. Training becomes easier, especially when people move out and then get new people onboarded. It is a seamless experience.

So far, I have not heard any complaints because it is a pretty mature product. From my level of analysis, the feature I would prefer to see added to Microsoft Intune is extensive support. Anything that helps to diagnose the problem and solve it would be useful. Helping the engineers, especially with CoPilot, with ready or out-of-the-box solutions would make life a lot easier because that helps us reduce tickets and respond faster. They can support engineers to do their job better and in a much more proactive way. They can also suggest solutions so that we do not have to waste time. Being more proactive is essential.

I have been using Microsoft Intune for more than eight years.

Microsoft Intune is very stable. I have not experienced any downtime, crashes, or performance issues with Microsoft Intune at all.

Microsoft Intune scales with our growing needs. We are mostly catering to our customers, and scaling is never a problem. We have worked with customers with over 100,000 employees, so it performs exceptionally.

We support the entire M365 end-to-end, and Microsoft Intune is a part of that. We support all features and capabilities around Microsoft Intune. My team is technical. We give L1, L2, and L3 support, and we only escalate to L4, L5 when needed, which is a very limited situation. This happens only when new features and products are released, such as CoPilot, which we have not experienced before. Generally, my team is self-sufficient.

Positive

Its deployment is seamless. We have on-premises and cloud deployments. The cloud provider is Azure.

We have seen a return on investment. There are more revenue generation opportunities for us and productivity. Those are the two key aspects, along with customer satisfaction.

We have data points and metrics to calculate our return on investment, as we continuously track our internal stats, especially on the support side. We have to report back from the reports point of view, so we have many internal stats around it.

My experience with the pricing, setup costs, and licensing of Microsoft Intune has been good. As a partner, we always look for how we can generate more revenue from a consulting point of view, but I do not see any complaints from the customer side regarding pricing, so they are satisfied with it.

We have been using Microsoft Intune for a long time. We are a Microsoft partner, so we will stick with them.

I would rate Microsoft Intune an eight out of ten.

I use Microsoft Intune for mobile device management. My team is specifically responsible for managing mobile devices. Recently, we migrated all our devices to Intune from AirWatch. At my company, we are also utilizing Intune to manage desktops, laptops, and MVD devices.

One valuable feature of Microsoft Intune is the enrollment process, which is user-based, making it easier to manage compared to AirWatch. Additionally, the integration with Azure and other Office 365 apps is seamless. Another beneficial aspect is that Intune brings all endpoint and security management tools into one place, allowing us to streamline management and have a single point of view. Mobile users have found the enrollment process seamless, and the Company Portal displays required apps effectively.

There is room for improvement in the reporting capabilities, specifically app reporting. It is challenging to report which apps are installed on which device. Also, there needs to be more granularity in pulling up stale records. I cannot control mobile devices separately or create separate policies, which Microsoft mentioned they are working on.

I have been using Microsoft Intune for a little more than two years now.

The migration to Intune took some time to show benefits, as we started about two years ago and are finishing the migration now. Initially, there were challenges due to differences between Workspace ONE and Intune, requiring adjustments to internal policies.

From an end-user perspective, mobile users have had a good experience, with enrollment being seamless. However, there are concerns with inconsistent device syncing, as there are times when synchronization with Intune takes longer than expected.

My experience with customer service is that once I reach higher-level support, the service is good. However, intermediate levels of support haven't been very successful, so I often escalate to get higher-level engineers involved.

Neutral

I used AirWatch, which is now called Workspace ONE from VMware, before switching to Microsoft Intune due to better pricing with Intune, as it is included with an E5 license.

The initial setup of Microsoft Intune was made easier as I had previously been using it on the desktop side. However, there were challenges due to differences with Workspace ONE, but after addressing those, everything went smoothly.

My entire team was involved in the implementation, with at least three people working on it.

The pricing was much better with Microsoft Intune, as it is included with an E5 license, requiring no additional hardware purchases, which was a deciding factor for us to switch.

Overall, I would rate the solution a seven on a scale of one to 10. The more mature features of Workspace ONE mean it offers better functionality in some cases, but Microsoft Intune’s pricing and integration with our existing licenses make it more appealing financially.

Other

We primarily use Microsoft Intune for deploying Windows patches, security patches, and various software applications such as Office and Zoom. It serves as a deployment tool to manage updates and application installations on user machines.

One of the most valuable features of Microsoft Intune is the detection and remediation script capability. This allows us to detect issues on user machines and run remediation scripts based on these detections. This functionality has greatly helped us resolve issues more efficiently. Having all endpoint and security management tools in one place through Intune has streamlined operations and improved compliance, almost reaching 99%.

There is room for improvement in the remediation and detection modules, which are currently about eighty percent fully functional. There could be enhancements to address issues faced due to cloud or internet connectivity problems. These improvements would enhance precision and reliability.

I have been using Microsoft Intune for approximately one year.

I was part of the deployment discussion, and the process was complex and challenging. It required a lot of coordination across teams, such as security and stakeholders, for whitelisting and setup. However, once everything was configured, the tool performed effectively.

Microsoft Intune is very stable, although there is always room for improvement. I would rate its stability nine out of ten.

Being a Microsoft product, scalability is not an issue. Microsoft Intune can be scaled up or down as per requirements, making it highly scalable. I would rate its scalability ten out of ten.

The customer service and support from Microsoft is prompt and effective. If there are issues, we can raise requests, and they respond quickly. I would rate their service nine out of ten.

Positive

Previously, we used SCCM. However, Microsoft Intune offers better features, such as automatic remediation and improved deployment efficiencies, which is why we transitioned from SCCM to Intune.

The initial setup was complex and required considerable collaboration with security and other teams to complete necessary configurations.

The administration and implementation of Microsoft Intune were handled by a separate team. I initially joined the team to learn about its use and how to resolve issues.

In the long term, Microsoft Intune is cost-effective as it helps in monitoring software licenses and usage, allowing the uninstallation of unused applications to save license costs. It's about twenty percent more effective than SCCM.

The pricing of Microsoft Intune is costlier than SCCM in the short term, but it becomes less expensive in the long run due to features that allow better management of software licenses.

Before choosing Microsoft Intune, we did not evaluate any other alternatives. I consider Intune to have little competition in its category.

Microsoft Intune is a mandatory tool for companies due to its role as a deployment and security management backbone. It is evolving rapidly and will surpass other automation tools. I would rate Microsoft Intune nine out of ten.

Hybrid Cloud

Other

We use Microsoft Intune to manage mobile devices and distribute software. It helps us securely manage multiple vendors and operating systems.

Intune makes our organization more secure and flexible. We can onboard new employees faster and more securely. We are a governmental organization with strict regulations, and Intune helps us comply with those requirements.

The most valuable feature for us is mobile device management because it allows us to use multiple vendors and operating systems securely. I don't use Intune directly. My teams have used it, and I don't get any complaints about the user experience. 

Intune Suite's enterprise application management has made my life a little more difficult because now I know the kind of applications circulating in my organization. On the other hand, we started a program to fix the problem, and Intune helps us by providing us with insights.

Copilot helps because you can use the prompt to ask questions about the Intune-managed environment. That shortens the time we spend on reporting and that kind of stuff. Our analysis will be more efficient.

We would like to see the ability to use multiple personas on a device, similar to Samsung Knox, included in future updates.

I have used Intune for the two years I have worked for my company, but the company has been using it for longer. 

Intune's scalability is excellent. We are not a large company—only around 2,000 employees— and Intune handles our needs well.

Customer service used to be better, but as we are nearing the end of the contract, the focus on investing in us as a customer has diminished. It is what one would expect in such a situation.

Positive

Deploying Intune was difficult for me, but we have a deployment manager who handles it. 

We used multiple consultants, including Capgemini and KPN. Our experience with Capgemini has been positive due to a long-term relationship.

It is hard to quantify the ROI in hard metrics, but using Intune allows faster onboarding, increased flexibility, and more insight into device and software usage.

We are a governmental organization, so we can get discounts. Considering our environment, we get good value. 

I rate Microsoft Intune eight out of 10. Microsoft Intune fits well into our architecture, and they are developing new features like Copilot. It has contributed to the seamless integration with our existing setup.

Hybrid Cloud

Our primary use case for Microsoft Intune is endpoint management across our enterprise, particularly for Windows and mobile endpoints.

Intune simplifies compliance. The ability to manage software updates and policies on endpoints has helped us meet contract requirements.

We like Intune's mobile device management features. When we migrated from another solution to Intune, onboarding our mobile devices was straightforward. Intune is pretty transparent for the end user. They have a customer portal, and I've never had complaints about it. 

The enterprise application management feature allows us to identify systems outside our standard security baseline and limit their access to company resources until they are updated and approved.

The interface is not as modern as some competitors in terms of single pane of glass visibility across the entire landscape. It has a very Azure vibe and may not be as graphically appealing as other products.

I have used Intune for around two years.

There are no complaints about the stability. It works one hundred percent of the time.

There are no concerns about scalability, especially coming from an on-premises solution. We no longer need additional hardware and infrastructure.

I rate Microsoft support eight out of 10. We haven't needed support much, but what we've gotten has been good. 

Positive

Previously, we used MobileIron for mobile devices, which is our primary use case for Intune. We switched to Intune mainly because it was included in our standard E5 license, providing cost savings and managing everything under a single pane of glass.

The initial setup was straightforward with minimal support required from Intune's side.

No external integrator, reseller, or consultant was used. All implementation was handled in-house.

We have seen a small return from the native integration with our Microsoft systems and Intune's reporting. 

With our standard E5 agreement with Microsoft, there have been no pricing concerns. Introductory professional services, like a fast-track service, were included with our E5 membership, and there have been no additional costs.

We evaluated Workspace ONE and Jamf for mobile management but stuck with Intune because it's included in our license.

I rate Microsoft Intune eight out of 10. It's a great solution, but there is room for it to become a more polished product.

Public Cloud

We usually use Microsoft Intune to manage our devices and add security layers to protect access to all company resources.

The main benefit for us with Microsoft Intune is centralized management of all devices, allowing us to apply one policy across the company from one location.

What I like the most about Microsoft Intune is its ability to manage mobile devices. Through integration with System Center, it can also manage desktops and laptops. We also appreciate how easy it is to manage everything from the console.

The enterprise application management feature lets you manage, deploy, or uninstall applications from Intune. It also enables us to automate updates. The Cloud PKI feature helps us manage security keys on all company devices. 

Intune should improve the management of non-Microsoft devices. It would be better to manage Mac, Android, and other non-Microsoft operating system devices within the same Intune interface.

I have been using Microsoft Intune for almost five years now.

I rate Microsoft Intune nine out of 10 for stability.

We are not a huge company to check the scalability part. However, when discussing with our customers across the region, it seems fine, especially with the integration with System Center.

I rate Microsoft support nine out of 10. We have not used customer support, but it seems okay. If something happens, we open a case and receive assistance.

Positive

While I didn't perform the initial deployment, I know it's easy to roll out Intune across all devices. 

From the device perspective, particularly for desktops, it automates application deployment and secures all the devices. Importantly, when someone leaves the company, it helps protect document access on their devices. Onboarding and offboarding users is a great asset in terms of ROI.

We are partners, so we receive some discount. However, from the customer's perspective, Microsoft Intune's pricing is competitive with non-Microsoft technology, and the price is good compared to other market competitors.

I rate Microsoft Intune nine out of 10.

Public Cloud

We use Microsoft Intune to manage mobile devices for our parent company and our independent subsidiaries. These devices are not directly corporate-owned but belong to individuals or subsidiaries with whom we work. We enroll both their and our corporate devices in Intune to manage policies, ensure optimal security settings through compliance reviews, and deploy a VPN client for secure access to our internal network resources.

Microsoft Intune has provided valuable insight into the status of our independent computers, which previously lacked a management agent and had no standardized security policies. We could not enforce password expiration policies, hardened passwords, or even minimum password requirements, with some users relying on six-character passwords. By enrolling these devices in Intune, we have enforced more robust security measures, such as a minimum eight-character password length, and gained visibility into device compliance to ensure adherence to best security practices for data protection.

The Intune user experience is good, especially with the many improvements made to the web interface over the years. It has always been designed as a simpler interface than Configuration Manager, and Microsoft has done a good job in achieving this goal.

Dynamic groups are more efficient than static groups, which require manually adding members. This was cumbersome, especially when onboarding new people, as it necessitated manually adding them to the appropriate groups. Dynamic groups allow us to set conditions for automatic membership, eliminating the need for user intervention or manual review and ensuring a seamless workflow.

Microsoft Intune's app deployment presents challenges for non-MSI and non-store apps, particularly EXEs, requiring the use of a Win32 wrapper tool and adding overhead to the process. Additionally, deploying device-specific installers, such as VPN clients, is complicated by the inability to target users directly, necessitating knowledge of device names that may not be readily available. Furthermore, the web interface lacks detailed information for MDM-enrolled devices, such as the user's UPN, requiring the use of Graph Explorer API and necessitating Global Admin consent to access device properties. Enhancing app deployment, enabling user-targeted device application deployment, and improving the web interface, particularly for MDM-enrolled devices, by providing comprehensive device information and customizable columns, would significantly streamline Intune's usability.

Microsoft Intune should enhance flexibility and features to better match the granularity available in systems like SCCM.

I have been using Microsoft Intune for over five years.

Microsoft Intune has been stable, and I have not noticed any specific stability issues. While we've encountered problems with other services like Exchange, Intune has remained unaffected.

Scaling Intune is challenging due to the various device types we manage. Our parent company's mobile devices were already enrolled, and we've added our independent Windows devices, with plans to include corporate devices soon. A key hurdle is the lack of visibility into user attributes in Intune, hindering our ability to create dynamic groups effectively. Ideally, we want to automatically segregate devices based on user properties like primary use, but currently, dynamic groups seem limited to device properties. This forces manual group assignment after user enrollment, which is inefficient and reliant on user notification. Improved dynamic group functionality, particularly the ability to leverage user attributes, would significantly streamline device management.

Customer support has been reasonable overall. However, there have been cases, such as issues with BitLocker recovery keys, where support was less effective, leading to multiple hand-offs and delays.

Neutral

Before Intune, the independent devices were unmanaged without any agent. For corporate devices, we previously used SCCM.

The initial deployment of Microsoft Intune was fairly straightforward, despite a few challenges due to our unusual configuration of two on-premise domains syncing to our Azure tenant. This dual user sync caused issues because some users remained on the older domain, leading to conflicts when automated systems modified on-premise account attributes. These modifications triggered Azure to switch the sync to the other account, resulting in login failures for users with cached credentials from the old account. While we've mostly identified the cause and the fix, we still encounter this issue occasionally.

The deployment was handled in-house. Our organization benefited from having skilled personnel and guidance from our parent company.

The return on investment includes successfully distributing applications like a VPN client and Office 365. As a result, independent devices now have better application access, encouraging even non-enrolled entities to request Intune enrollment.

We considered Tanium for managing independent devices, but it's a comprehensive endpoint management tool with more functionality than we needed. Management felt it would introduce unnecessary overhead. Since all our corporate devices are currently managed with Intune, adding independent devices would require segregation. Ultimately, we opted for Intune due to its ease of use, allowing us to create targeted policies from scratch.

I would rate Microsoft Intune a seven out of ten.

Public Cloud

Microsoft Azure

My use case for Microsoft Intune involves working in the breaking fixed line.  I receive tickets when customers encounter errors or have doubts about the tool. I can explain the tool to clients, or I'll analyze the error. For example, if someone tries to use BitLocker but their device doesn't encrypt, I start my analysis of the policy the client created and try to fix the error.

The best features of Microsoft Intune are Windows Update rings. This is superior because you can schedule updates for quality, security, or OS system updates. It is beneficial because we can schedule work hours or after work hours to implement the updates. It helps me better understand client issues and increase my response time to deliver solutions to problems.

The areas that have room for improvement in Microsoft Intune include the Autopilot process. The ESP profile could be easier to use as many clients complain about it because if we don't deploy the ESP, the Autopilot doesn't work properly. These two configurations should be together when you create the Autopilot profile rather than separated.

Another tool that needs modifications is script deployments. When trying to deliver PowerShell scripts in the organization to apply wallpapers, it's very complicated to see if they return errors or how they show in the devices. Changing that would help significantly.

I have used Microsoft Intune for a year and three months. I have been working for three years in the Microsoft line support. Before Microsoft Intune, I was the Exchange engineer from the support line too.

I have experienced downtime, bugs, and glitches. I rate it a seven because when we have bugs or instability in Microsoft Intune, we need to wait for the backend from Microsoft Intune to resolve issues and we can't deliver solutions to clients because we need to wait for action plans and related processes.

In my organization, I am the only one who works with Microsoft Intune. When I need to use my environment to test, I create approximately 20 users and start to deploy. In my role, I receive tickets from organizations that have thousands of devices requiring issue resolution in Microsoft Intune.

From one to ten, I would rate the technical support at a 10.

I cannot compare Microsoft Intune with other solutions or vendors on the market because the only time I saw Microsoft Intune work with another solution was when I received a ticket about Mac OS where the organization used MDM Jamf to manage devices and started using Microsoft Intune. They tried to migrate to Microsoft Intune. This is the only collaboration I have seen between Jamf and Microsoft Intune.

Microsoft Intune saves eight hours per day. During my work hours, I use my time to study and run tests on configurations I'm curious about and try them out in my environment.

The pricing for Microsoft Intune is very reasonable because organizations can pay without complaints. Microsoft Intune isn't sold standalone only. Organizations can buy Microsoft 365 Business Premium, which includes Microsoft Intune with the license. It's a reasonable price to use Microsoft Intune.

I recommend Microsoft Intune to other users because it's a great tool to manage the environment. You can use it on one machine to deliver it to others. When you enroll these devices, the IT professional's life becomes easier to manage these machines because we can do everything remotely. I would rate Microsoft Intune overall as a nine out of ten.

Public Cloud

Microsoft Azure