Microsoft Intune Reviews

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

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

We use Microsoft Intune for our mobile devices, including tablets and mobiles, across both iOS and Android. Our intention is to eventually use Intune to manage our laptop estate as well.

The integration into Azure stack and M365 stack is highly powerful. Additionally, no longer having to pay for a third-party MDM solution is a significant benefit. We also appreciate the conditional access rules and the basic Azure/M365 security scoring, which offer centralized control and the ability to manage policies from one point.

I would like more clarity on how Intune is migrating control from Active Directory group policies, especially as we move over to Windows 11. It seems inefficient to manage some settings in Active Directory and others in Intune.

I have used the solution for approximately just under two years.

I would rate the stability of Intune as a 10. We have not experienced downtime, bugs, or glitches. The only issues we encountered were during the initial setup.

I would rate the scalability of Intune as a 10. You can scale as much as needed based on the size of your tenants.

We use a third party for support instead of Microsoft directly. Our value-added reseller, who specializes in Intune, is excellent, and I rate them as a 10.

Positive

We previously used BlackBerry UEM. We switched to Microsoft Intune to bring our system under Microsoft and achieve more seamless integration. The cost is included in our licensing, eliminating the need for separate servers and complex configurations.

I have been in the IT field for 30 years, and the initial setup made me scratch my head, so we brought in a third party to help. The deployment stretched over several weeks.

We engaged a third party to help with the implementation.

Financially, we saved four to £5,000 a year on MDM licensing after switching from BlackBerry. The one-touch commissioning has also saved significant time by simplifying device configuration and maintenance.

We saved on licensing costs as Microsoft Intune is included in our existing licensing deal.

BlackBerry UEM

I recommend Intune but only once your M365 configuration is established to support it and after completing your Exchange Online migration. I rate the overall solution as a 10.

Public Cloud

Other

I have been working with Microsoft Intune for the last seven years. Before that, I worked on competitive platforms like MobileIron and Citrix Endpoint Management. These are MDM platforms, and when compared to them, Intune is one of the best solutions from Microsoft. I currently play a role as a Microsoft Intune architect, designing and implementing solutions for customers, managing iOS devices, and Android devices, and now it's growing in managing Windows devices. Previously, SCCM was used as an on-premise solution for clients, but now they are moving to Microsoft Intune as a cloud solution with better security and functions.

Windows Autopilot is one of the best features. It offers security and helps us know which device a user is using before it is enrolled. 

Autopilot has various features, making it easy to manage Windows devices. In the migration of existing SCCM devices to Microsoft Intune, we use Group Policy Analytics, which simplifies copying existing policies to Intune and reduces migration time significantly. 

Comparing iOS devices, DEP is an exceptional solution integrated with Microsoft Intune. It allows for better visibility and actions on devices. 

The Volume Purchase Program (VPP) from Apple is also beneficial as it reserves licenses for specific applications, which we can integrate with Intune.

In terms of improvements, regarding Windows devices, Microsoft needs to enhance options for copying existing policies to Intune. 

Some configurations are not available with Intune and exist in group policy, so they should be added to Intune immediately. Most customers are migrating from on-premise to cloud, and this should be a priority. 

The synchronization of devices takes a significant amount of time, between 15 minutes and two hours. Microsoft should work on reducing this sync time to improve efficiency.

I have been working with Microsoft Intune for the last seven years.

When a particular device issue is not resolved, I report it to Microsoft, who will take it over and add it in the next quality or feature updates. It will take time, but it will definitely be resolved.

Positive

I previously used MobileIron, a notable solution in the market. At that time, Microsoft Intune was not an option. MobileIron was one of the best solutions despite its high cost for users. Microsoft Intune is cost-effective, and integrating it with other Microsoft services, like Windows 10 and 11, is beneficial. I have also worked on Citrix Endpoint Management.

The redeployment of Intune is quite simple. Level four support is managed by Microsoft. Previously, with on-premise solutions, disaster recovery was essential. Microsoft Intune cloud environments should develop their own disaster recovery solutions.

Overall, Microsoft Intune covers more than seventy percent of the market. I have worked on numerous projects within a consulting company, most of which involved Microsoft Intune. It is one of the leading products for MDM solutions.

PKI is typically managed by a separate team, though on-premise PKI is fine. Microsoft provides solutions like SCEP for certificate distribution, which another team can manage. Certificate distribution and authentication, such as MFA, can be defined on the Internet with SCEP to distribute certificates to end users. For example, WiFi authentication can use certificate-based methods. My overall product rating is nine out of out.

Hybrid Cloud

Microsoft Azure

I use Microsoft Intune to Autopilot our devices and manage various configuration policies mainly on Windows PCs. It helps in efficiently deploying company configurations remotely.

Intune has streamlined our onboarding process. Most of our workforce is remote, and there typically isn't an office where they can pick up the devices. It's easy to ship them to any address and configure them remotely. 

The Autopilot feature is the most valuable because it saves significant time on managing devices. We can ship devices globally, and users can set them up on their own. It's convenient.

The user experience is pretty solid. We've gotten great feedback on the onboarding process and replacing devices. Every employee on the Windows PC has gone through Intune's Autopilot process.

Microsoft Intune could improve in reporting data for endpoints and fleets. Enhanced capabilities to run queries and gather specific device data to identify trends or issues would be beneficial. The feature parity for MacOS and handling devices from an MDM perspective is not comprehensive. Consolidation of these functionalities within Intune would simplify processes and finances.

I have used Microsoft Intune for about four years.

Microsoft Intune is very stable. I cannot recall any significant service outages in the last few years.

Microsoft Intune is scalable and handles our workload efficiently. Although our organization is not very large, we foresee continuing with Intune as it supports scalability effectively.

We do not utilize Microsoft customer service and technical support since it is generally a waste of time.

We used SCCM before, and now we are in a hybrid state, co-managing with SCCM and Microsoft Intune. The primary reason for the switch was the convenience of joining devices to our environment over the Internet.

 Microsoft Intune's initial setup was straightforward. It took some effort to configure it to a finalized version. Like every other piece of technology, it's constantly undergoing configuration changes. From an out-of-the-box perspective, it's super-easy to set up, but, you know, you have to continue iterating on it over time.

The implementation was primarily conducted by my team, especially my endpoint administrator on the Windows side.

Factoring in the setup time, we've saved about 1,000 hours in the last couple of years.

We spend a lot of money on Intune licensing, and some of our users have to be double licensed just because of how our dev and corporate environments are segmented.

I rate Microsoft Intune eight out of 10. Offering the same features for MacOS would make it a 10.

Public Cloud

Microsoft Azure

We use Microsoft Intune to enroll devices in our environment, install software, and monitor security patches.

In the past, our cumbersome OSD installation model using images made it difficult for IT to track installations and required users to visit the help desk for reinstallation. However, with Intune, employees can now conveniently manage installations themselves.

I have no complaints about the Intune user experience.

I appreciate Intune's Autopilot feature, which allows us to enroll devices and install applications to meet corporate requirements seamlessly.

I would like to see Intune improve its handling of hybrid domain joins. We continue to experience issues with machines losing their hybrid domain join status.

I have been using Microsoft Intune for several years now.

Intune's stability has been generally good, although recent issues caused devices to stop checking in and become unmanageable. We hope this is resolved before we begin redeployment.

Intune's scalability appears satisfactory, as we have not experienced any scaling issues.

Support has become more challenging to navigate over the past couple of years. It takes some effort to engage the right level of support, but once the right person is contacted, support works well.

Neutral

Before Intune, we used the OSD image approach. We switched to Intune for end-user ease of use and to lessen the burden on support teams.

The initial setup was fairly straightforward.

We did the implementation in-house ourselves.

We did not evaluate other solutions because Intune was included with our Microsoft 365 solution.

Overall, I like Intune as a solution and would rate it nine out of ten. The rating isn't a ten because we haven't enrolled our entire environment in it yet, but so far, it looks promising. It might reach a ten at some point.

We have over 50,000 employees and 75,000 machines.

On-premises

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