Microsoft Intune Reviews

We opted for Microsoft Intune for endpoint management within our Microsoft solution bundle.

Intune unifies our endpoint and security management tools.

Managing our devices in a single solution helps our IT security operations.

The user experience is good, especially for SIS Administration.

Intune provides 90 percent visibility and IT control across device platforms.

Intune helps us secure our hybrid work.

Our information security team has been quite satisfied with our organization's security posture since deploying Intune.

Microsoft's E3 and S3 subscriptions keep us within their ecosystem and enhance our IT productivity, eliminating the need for third-party solutions.

With the implementation of Intune the risk of security breaches has been decreased.

Intune's unified platform has saved our organization money by eliminating redundant costs, like extra licenses and the need for multiple solutions for the same tasks.

Intune helped us consolidate vendors. This consolidation has improved our security posture.

It is important for us that Intune integrates with Microsoft 365 and Microsoft Security for both cloud and commonly managed devices.

Intune's unified endpoint management platform is invaluable.

Microsoft Intune is not user-friendly to manage and has room for improvement.

The detection and prevention of end-user data leaks from mobile devices can be improved.

I have been using Microsoft Intune for nine months. 

The first level of remote support is inadequate. While the E5 license grants access to advanced support, I've encountered instances where the technical support team deflects responsibility. For example, a recent issue with Microsoft not syncing properly with the cloud was attributed to Windows and redirected to another team. Due to Microsoft's overall responsibility for their products, I believe since it all falls under the umbrella of Microsoft, they should deal with it.

Positive

Once we create our tenants, the migration and synchronization of the users to the cloud services is straightforward.

We deployed the solution in phases and it took around three months to complete. Three people from our end were involved in the deployment.

Our Microsoft partner helped with the deployment.

We evaluated IBM, Ivanti, and Workspace ONE but our management decided to move away from third-party platforms to simplify and save costs.

I would rate Microsoft Intune a nine out of ten. Intune is missing a single-pane-of-glass, requiring us to jump through multiple portals to manage all our devices.

We have 3,000 users.

Microsoft Intune is a top-notch solution and I recommend it.

Hybrid 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

Microsoft Intune is used for Mobile Device Management. We enrolled our mobile devices as well as the mobile device solution for corporate devices. We have a lot of policies such as the compliance policy, and the conditional access-based policies for the corporate mobile user and we use the solution to assign their  Outlook Teams and other configurations for the organization. 

We use Intune to design compliance policies that apply to corporate devices and to wipe data from devices when users are terminated. Intune is also used for mobile-based solutions, but we have recently explored its capabilities by using the Autopilot feature. With Autopilot, Windows 10 devices can be reset and new versions of Windows 10 can be deployed from Intune.

Intune has many benefits from the Microsoft perspective. This solution can manage Windows 10 devices, app management, and provide security solutions. We don't need to worry about our network connection, and we'll be more secure with regular security patches and compliance. Since everything will be deployed through the internet and users will log in using the internet only, the risks have been mitigated. Security updates, security patching, and the application will be targeted from Intune. The location tracker will be available to track where the device is and the user's location. The user will be restricted from accessing certain applications using compliance policies. Conditional access policies will be based on the reason why the user needs access to the application.

Microsoft Intune is one of the best products in the industry for managing Windows devices. The solution has more feature restrictions. The conditional access policies also eliminate the dependency on the on-prem network for the devices. The solution also manages our security settings and a lot of other beneficial features such as Microsoft Purview which gives us the compliance portion. We can manage all aspects of our device from a single console, including M365 services. This allows us to configure data classification types, such as public, private, internal, confidential, and highly confidential.

The best feature is that we don't need to worry about downtime. We don't need to worry about the network connections of our office or the virtual private network. Everything is being done through the internet. Using Intune Autopilot, we can configure and deploy everything to the devices.

We need the capabilities of the Cloud Management Gateway (CMG) to be enhanced through Intune instead of Azure. I suggest that Microsoft consider this. If the user already has a subscription to Intune, they should not need to buy an additional subscription for Azure services.

The support needs improvement. When we need support, we don't get a response within the SLA because the support has been outsourced.

I have been using the solution for five years.

Microsoft Intune is a stable product. For the configuration, we could reach out to technical support, but other than that, we need not worry about anything. If we have configured the product correctly and we are not going to enhance any additional capabilities in Intune, then we need not worry about technical support.

The solution is extremely scalable. I give scalability ten out of ten.

Microsoft has outsourced its technical support so if we raise a ticket with severity, the technical support team may not be able to respond to us within the timeframe or the standard we expect. Sometimes we get the call within four hours. Sometimes we won't get that call for a day or more. The service side is pathetic now. To get support from Microsoft, we need to have our TAMs in place and then we need to submit the ticket. If we have already aligned a TAM for the tickets, we get support from Microsoft.

Neutral

Previously we were using Microsoft Configuration Manager. The Microsoft Configuration Manager is the dedicated server for managing devices on-prem. We need to make sure the device is on the same network through which the policy is getting replicated. The dependencies with that server as well as with the network are important, and the devices need to be online on the network. Using Intune as a backup solution, if the device is not on the network or if the device owner is not in the location but it has an internet connection, then we can deploy all our physical solutions onto the devices. We are using both, the Microsoft Endpoint Configuration Manager as well as Intune, since a couple of policies are still only being managed with the Configuration Manager.

The initial setup is straightforward. Once we have subscribed to the license, we will receive our tenant ID and organization ID. We can then access the portal and configure whatever we want. To save the configuration, we must enable it from the portal itself. The Azure Ready Connect GUI console makes it easy to join devices to Azure and to create and deploy conditional access policies.

We have four or five global administrator access levels in our organization. The most limited level is for the global administrator, who can be limited to one person. We need to involve them to enter the password while configuring the CMG, and then the Microsoft support in case we are missing any configuration during the installation or managing Microsoft Intune.

We deployed across more than 10 to 15 countries. The solution is used in India, the US, and England.

We have seen a return on investment using Microsoft Intune. We can save money by establishing our management point and cloud distribution point in Azure. Cloud support is an additional cost. We have to pay Microsoft for the VM, which doesn't act as a management point and the cloud distribution point for the endpoint. Endpoints are the on-prem devices.

Earlier, Microsoft used to give the license using the MSDN subscription, now the subscription part uses the M365 E3/E5. Existing E5 license holders for M365, Intune, and Azure, receive a free license.

If we're only upgrading to Windows 10 for the monthly security patches, Ivanti has Patch Now. Patch Now is a solution that gives us the same set of capabilities as IBM BigFix, but Intune has enhanced capabilities. Ivanti Patch Now is another product similar to the Microsoft Configuration Manager console and we have to make sure the device is on the on-prem network itself. Intune is a cloud-based solution that does not require the device to be on-prem. Everything is in the cloud, including device tracking, writing, and initiating remote connections.

I give the solution a ten out of ten.

I manage the endpoints for the implementation strategy and use the desktops or Windows for migration. I'm not from the mobile device management team, but I can give presentations on how the devices will work in the Autopilot zone with Intune. I'm also familiar with conditional access policies and what needs to be in place for a successful migration.

We have 35,000 end-users.

Maintenance is minimal. There have been no reports of any outages from the cloud perspective, meaning that any downtime is from Microsoft itself. However, on-prem systems may experience challenges. We don't need to worry about downtime and all the systems will still be operational.

New customers are definitely going to reach out to Microsoft for purchasing all the products. Microsoft will have its own lab. They will give us the live demo from the lab, but that won't be a feasible solution. We should check and bring that solution to our environment. It would be good if we can create our own test environment and then ask Microsoft to perform all those configurations and just train our engineer about the Intune part. We will know all the legacy parts of our environment which could impact when we are moving our devices to Intune, either the legacy app, legacy hardware, whether those devices are supported, the TPM, the Tested Platform Module, the BitLocker configuration, everything we need to understand before we move our device to Intune.

Public Cloud

Microsoft Azure

We use Intune for security or endpoint inside the company and especially for many customers we have.

Microsoft Intune has helped us by improving our security posture, leading to fewer security problems, and helping us understand where we have issues. 

Intune's compliance features are valuable because they allow for immediate visibility into ongoing situations. The solution is very easy to use. We haven't implemented Microsoft Copilot but will adopt it next year. It will be interesting to use natural language to interact with Intune.

It would be interesting to integrate the server side of Intune. Some group policy updates we have on the Windows Server side and possibly some on the client side could also be included.

I have been using Microsoft Intune for about two years.

Microsoft Intune is very stable.

The scalability of Microsoft Intune is good. We don't have large customers, so we haven't seen any issues with scalability.

I rate Microsoft support nine out of 10. Customer service and technical support are good. The technical support from Microsoft and Infineon Technologies is also good. The quality and professionalism of the people are really good, although sometimes we need to escalate to get the right content and answers.

Positive

We previously used a solution from an older competitor that is now defunct.

We did not use an integrator, reseller, or consultant for the deployment because we are an integrator.

Our customers have seen a significant return on investment because they now understand and see where the problems are on the endpoints without needing to search the entire company.

We know the pricing is good because customers are not complaining about it.

We directly switched to Microsoft Intune after receiving good feedback from customers.

I would rate Intune eight out of 10. Some features could be added, but it is a rock-solid solution.

Hybrid Cloud

Other

We operate call centers and provide our agents with laptops that they use from their home environment or home offices. We use Microsoft Intune to manage those laptops remotely. This remote management accounts for 99 percent of our use cases.

Microsoft Intune has effectively managed our patching needs, resulting in very few system-wide issues. While a small number of laptops occasionally fail to receive updates, the vast majority are patched successfully without manual intervention.

Microsoft Intune has enabled us to effectively manage our laptops, which is crucial for our involvement in civilian federal projects. The platform allows us to maintain a necessary security patch level and address any bugs that may arise, ensuring our devices are always secure and functional. Implementing Intune provides a cost-effective solution that would otherwise be prohibitively expensive.

Our Intune users, the IT group and system administrators, are happy with the system and have not reported any complaints.

The most valuable feature of Microsoft Intune is patching-related capabilities. This is because patches are constantly being released, and it requires us to stay current with bug-related and security-related patches, which is critical for our day-to-day operations. Intune's support in this area is crucial for us to maintain our laptops at a certain security patch level.

A more incisive reporting tool with automated progress updates and graphical representation would be beneficial, as the current manual method lacks efficiency and visual clarity.

I have been using the solution for about a year.

The stability of Microsoft Intune is ten out of ten. It has been very stable for us.

The scalability of Microsoft Intune is ten out of ten. Although we are not the largest company, it has never presented any scalability issues for us.

The customer service is above average. We have an Azure engineer on staff who handles troubleshooting. Although we have not had any major issues.

Positive

The initial setup is straightforward. We manage everything in-house with just a few commands needed before deploying laptops, never having to reconsider our processes.

We do everything ourselves without using a reseller or consultant.

We have never operated without Microsoft Intune, but it is apparent that it offers significant cost reductions. Operating without it would likely be prohibitively expensive, indicating a ninety-nine percent reduction in cost with Intune.

The alternative to Intune, sending out replacements for every issue, is prohibitively expensive. In contrast, Intune's pricing is reasonable considering its benefits and the high costs it helps avoid.

We evaluated other options that are tool-specific. For instance, our call center platform from NICE's CXone, has built-in Copilot-like capabilities. Nevertheless, Copilot remains our primary focus as it covers our entire spectrum of needs.

I rate Microsoft Intune nine out of ten.

We recently started using Copilot and find its support features very attractive. Our call center agents are internal customers who, like any customer, need occasional assistance with various issues. Copilot could benefit both IT and non-IT departments by providing faster service, self-guided troubleshooting, and access to relevant resources. For example, if an agent has an HR question, needs help with benefits, or experiences a technical issue like audio problems with their laptop, Copilot could guide them with self-service options or provide helpful files. This would empower our agents to resolve issues independently and efficiently. Our initial analysis suggests Copilot may have the potential to protect our environment, though our assessment is ongoing and we haven't begun implementation. Preliminary findings indicate it will be a valuable tool.

Public 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 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

You can use Intune to manage devices for any size project, from a small business to an enterprise-level project. You can manage hundreds of thousands of devices. Intune can manage on-prem and cloud services. We are working with large enterprises mostly.

Intune encompasses all devices, applications, and policies that can be deployed within an organization through a single portal. In the event of an outage, it simplifies the management and resolution of issues or policy adjustments. It allows for the management of security profiles, applications, and devices from one portal across any operating system platform.

Consolidating everything in one location enhances the efficiency and productivity of IT administrators. Since adopting Intune, our IT team's productivity has increased by 20 to 30 percent. Additionally, the integration of Copilot has further improved our efficiency by 5 to 10 percent.

However, there are exceptions. Certain applications cannot be deployed easily via Intune. Win32 deployment is necessary for these, which can be challenging as it demands extensive testing to release a custom package from Intune. More innovation is needed to deploy custom applications, which would greatly benefit us. For most enterprise scenarios, application deployment is relatively straightforward.

Hybrid environments call for innovation, particularly with hybrid enrollments using GPO. While most autopilot hybrid scenarios and co-management run smoothly, I have encountered issues with hybrid GPO enrollments due to their complexity.

Intune is a leading secure solution in the Indian market. It allows the creation of any conceivable security policy. With the addition of Purview and DLP modules and integration with Microsoft Defender for Endpoint, security has never been a concern, and our security posture is nearly impeccable.

Intune has also facilitated vendor consolidation. It is our primary recommendation for an MDM solution because it offers the productivity and features that would otherwise require integration of multiple solutions from other vendors. The industry is now transitioning from on-premises Intune to cloud-based management.

Intune enables the deployment of any security solution. Although it does not integrate, it allows for the deployment of a wide range of security measures.

I appreciate how Intune consolidates everything in one location. For instance, it allows the setup of conditional access for applications and devices directly within Intune. The segregation feature within Intune devices is also beneficial. Devices can be categorized by Windows, iOS, iPadOS, macOS, and Android, and sorted by platform, eliminating the need to navigate the devices section.

The app management feature has seen significant improvements. Initially, navigating the app section was quite challenging, but now, all my concerns have been addressed. It's possible to deploy or manage any application, with reports and app-protection policies accessible in the same section, which is quite convenient.

I would rate the user experience at nine out of 10. Having utilized various MDM solutions from Microsoft, Cisco, and VMware, I find Intune to be superior. We employ Microsoft Defender for Endpoint and DLP policies in Purview, along with multiple security policies such as baselines and BitLocker for encryption. This integration simplifies the administration of security features from other tools in one place.

The most sophisticated analytics we've utilized are group policy analytics. As a consultant, I often handle multiple migrations, primarily from on-premises to the cloud. Group policy analytics are particularly useful in these scenarios as we migrate on-premises policies. If Intune lacks support, we must either start anew or seek alternatives.

Copilot is beneficial as it supports various CSPs or policies. Despite extensive use, one cannot be fully versed in everything about Intune. Whenever there's confusion, Copilot is a valuable resource to clarify and ensure the feasibility of creations within Intune. Copilot assists in profile creation and assignment considerations.

My perspective on tools like Copilot is that they are artificial; the intelligence aspect is still emerging in the AI industry. Nevertheless, Copilot is a well-maintained and informed tool.

Microsoft currently restricts deployment to PowerShell or XML scripts, so it would be beneficial to support additional scripts such as command scripts, C languages, or TypeScript to enhance systematic compliance.

While the UI has been updated, it could be made more accessible. Navigating to a specific section in Intune requires multiple clicks through different areas before arriving at the intended destination, indicating the UI could benefit from further improvement.

The process of application discovery and deployment is relatively seamless. Nonetheless, there is room for enhancement in the reporting aspect. Intune still lacks comprehensive reports, and notably, its failure reporting does not succinctly communicate the full extent of an error.

I have used Intune for more than six and a half years. 

I rate Intune 10 out of 10 for stability.

With Linux and Chrome OS now supported, the scalability has reached 100 percent. Every device or endpoint operating on our OS can be enrolled in Intune. 

I would rate Microsoft support as four out of ten. Support is an area where Microsoft could significantly improve. I had an issue with Microsoft Azure recently, and after raising a ticket, it took two and a half weeks to receive a response. There is a need for enhanced support across all their product offerings.

Neutral

We have utilized Cisco Meraki, VMware Workspace ONE, and Jamf for managing Apple devices. However, Intune stands out among these options because it overcomes application deployment limitations that others have. While some support only Apple or Windows devices, Intune excels in compatibility, supporting Android as well. Moreover, Intune can implement more security policies than any other MDM solution available.

Hybrid enrollment is typically complex, yet cloud autopilot simplifies the process considerably. It's possible for anyone to grasp cloud deployment within five to ten minutes. While the most intricate enrollments, involving thousands of devices, may take two to three weeks, a cloud-based deployment can be accomplished in approximately one week.

This was completely in-house.

Intune is considered moderately priced. It is available as part of a bundle with Microsoft 365 E3 or E5 licenses. While the E5 licenses are somewhat costly, Intune offers some more affordable solutions.

Yes, we evaluated Cisco Meraki and VMware workspace One.

I give Microsoft Intune a rating of nine out of ten. Intune stands out as one of the top solutions in the market, and its capabilities are expanding with the integration of cloud PCs, Chrome OS, and Linux systems. For any large enterprise, I endorse both Intune and Defender.

The recent CrowdStrike outage, which is the largest in IT history, affected only systems without Microsoft Defender but with CrowdStrike. This incident underscores the importance for enterprises to transition towards deploying Intune and Defender for enhanced security.

Public Cloud

Microsoft Azure