Microsoft Intune Reviews

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.

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

I use Microsoft Intune to check if laptops are compliant or not, and to check if applications are added to user profiles. Sometimes there are applications users cannot find in the Company Portal or on their laptops, so we try to add them to their profiles. We can check if there are issues with Windows updates and verify if they have the latest version. We can check by hostname or serial number of the laptop if a user's computer is compliant or has access to the enterprise company platform resources.

The best features of Microsoft Intune include helping to know if computers are configured correctly and if users have access to apps or the platform. It provides an excellent overview of all machines for the company and helps determine if those machines are facing issues. It is particularly helpful when laptops face issues with upgrading or migrating to Windows 10 or Windows 11.

Automation has room for improvement in Microsoft Intune for fixing some errors. The knowledge and database in support can also be improved. If errors aren't in the database, we need to check forums or Google to understand and troubleshoot them. The most important improvement needed for Microsoft Intune is to have a comprehensive database about what each error means exactly and what steps to take for troubleshooting.

I have been using Microsoft Intune for about four years.

The stability of Microsoft Intune rates at nine out of ten.

Microsoft Intune has saved approximately 30% of time.

Users are mostly satisfied with Microsoft Intune because it helps them understand what's happening on their laptops. For some issues, I can assist depending on Microsoft Intune access. When comparing Microsoft Intune with other tools, the pricing is acceptable and it's easy to use. I recommend Microsoft Intune; it should be used in companies using Windows. I rate Microsoft Intune eight out of ten.

On-premises

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

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

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 have hundreds of thousands of users, so we have to manage their devices, and Microsoft Intune plays an important role in managing those devices through deploying applications, operating systems, and security configurations. 

Microsoft Intune has transformed my organization. We are managing to scale the Intune deployment across all our regions efficiently. 

It works perfectly for our needs. Our organization's architecture is well-suited for Microsoft Intune. Given that we are a diverse organization, managing connectivity with our endpoints can be quite challenging. However, Microsoft Intune offers an ideal interface solution that meets our requirements.

It is a device management tool that includes all the features which were available in SCCM, such as OS deployment, user device enrollment, and Autopilot. These features are primarily important for us to do automated OS deployment.

As a user, I assess the user experience of Microsoft Intune to be seamless. Users have to log in with their email ID on the device itself, and the process is seamless. Their 365 is integrated, and Outlook is configured automatically.

Microsoft Intune is evolving. They are introducing new features every month. For instance, they integrated Copilot, among many other features added in terms of Apple and Chrome. These enhancements are being implemented gradually, and I believe they are actually improving the user experience.

Local administrators use this tool to connect with users, and they require a password to be reset or retrieved. It can be a bit inconvenient for them to log into Intune just to raise privileges and reset the password.

Their technical support can be improved. 

We have been using Microsoft Intune for Windows devices since 2021.

Microsoft Intune is stable and reliable. I did not find any anomalies with the solution that Microsoft has introduced. None of the market has reported downtime for longer periods, though they might have experienced something with very short notice, but they have not reported it.

It fits perfectly with the growing needs of my organization. 

When we raise a question or issue, it takes a longer time to resolve. I would rate the technical support a five out of ten.

Positive

We were using SCCM before Microsoft Intune. It was cost-effective to switch from SCCM to Microsoft Intune because it has no local infrastructure to manage. Earlier, we were paying to manage our SCCM across hundreds of primary and secondary servers globally.

I was the one who designed the solution for my organization. We only faced a challenge when trying to implement a hybrid solution because it wasn't feasible with our multiple forests. As a result, we had to discard the option for hybrid deployment. Instead, we decided to use pure Autopilot devices for the Entra join process. For the existing domain-joined devices, we opted for co-management. Ultimately, the primary authentication for these devices will remain with the domain, but they will operate in a hybrid state.

In terms of infrastructure costs, we were previously managing our SCCM across the entire group, which involved hundreds of primary and secondary servers for managing endpoints and distribution centers. When we calculate the total expenses, Microsoft Intune turns out to be quite cost-effective. In fact, entire regions have approached us to adopt Microsoft Intune, so I can see that the ROI is fully recoverable. 

We didn't have to pay anything for Microsoft Intune with our subscription.

We have not evaluated other options before choosing Microsoft Intune because it comes free with all our licenses distributed across our users.

I would rate Microsoft Intune a seven out of ten. There are many things they have to add.