Microsoft Intune Reviews

We've experimented with and deployed Autopilot for building and deploying software through Intune, utilizing Intune policies to modify Azure AD joined systems, now referred to as Entra joined. This covers the entire scope of Intune that we've explored and implemented.

We are a consulting company with extensive experience in deploying Intune. We utilize Intune for hybrid join Entra machines. For clients who have the necessary licenses, while Intune is not a full-fledged Remote Monitoring and Management solution, it can serve as an effective replacement for RMM if you are a Managed Service Provider.

While more mature tools exist for securing hybrid work and protecting data on BYOD and company devices, Intune is a viable option for clients who want to leverage MDM with their Premium or E3 license, especially if cost is a major concern. Despite some challenges with Samsung Knox and iOS devices, Intune has shown improvement, and these issues are less frequent. As Microsoft doesn't have a native phone, limitations are inevitable.

The Mobile Device Management in Intune is a valuable feature.

Microsoft recently separated Defender into Security. Intune does not centralize all endpoint and security management tools into one place. It used to be more centralized.

The Microsoft support has been subpar for some time now. Troubleshooting issues often require us to involve a partner, which isn't an ideal or easily manageable solution given the challenges with Microsoft support. We need a reliable partner, but that partnership might still require Microsoft's assistance.

We've faced significant pushback with Copilot as our clients aren't seeing a favorable cost-benefit analysis. Many are opting for ChatGPT Enterprise instead of integrating Copilot into their workflows. We initially expected significant value from Copilot, but Microsoft's pricing is excessive, and the product itself is not exceptional. It remains quite rudimentary in its current state.

Microsoft should not rely on partners to fix issues. While users can open tickets with Microsoft, they often cannot resolve the problems themselves and must engage a partner. This is not an à la carte solution. Perhaps when Copilot eventually becomes available, it will address this. It's not Intune's fault, as it is used frequently.

I have been using Microsoft Intune for ten years.

The technical support is not good.

Negative

We tried numerous solutions prior to Intune, but Microsoft's inclusion of it within their licensing model incentivized us to adopt it. Since we were already paying for the license, it made sense to leverage its full potential and maximize our investment.

If you're subscribing to Premium or E3, there are no additional costs for Intune, it's included. However, with lower-tier plans, you don't get the full suite of security features. Depending on your specific licenses, you might have some level of Advanced Threat Protection, Endpoint Detection Response, or other Defender tools, but not the complete package. Generally, for around 300 users, you get decent protection with Defender for desktop and server – it's a good value. But with E5 licenses, you're at the enterprise level, and you get what you pay for, so expect add-ons. I don't think Microsoft would position Intune as a primary security product anymore, given their recent cloud changes and the focus on Defender. Intune is useful for patching, but it's not a comprehensive security solution in itself. That's why Microsoft has rebranded their security offerings under security.microsoft.com.

I rate Intune six out of ten.

Many of our clients with premium or E3 or above licenses use Intune because it's included in their Microsoft solution. They prefer to leverage a Microsoft product over a third-party alternative. Additionally, Intune allows us to maximize the value of our clients' existing licenses. Therefore, if a client has a premium license, has under 300 users, or is on E3 or above, there's no reason to use another solution when Intune is readily available.

Microsoft recently transitioned from Intune to Endpoint, then back to Intune. Additionally, they moved certain security aspects of Purview into a separate deployment, as is the case with their ATP Defender Suite. This shift signifies a move away from a single, unified management interface to a more distributed model.

We use the enterprise application management feature to roll out apps. While there are better tools available for app discovery, deployment, and automatic updating, Intune's inclusion in the Microsoft bundle keeps costs down. Although Intune may not be the ideal solution for automated application deployment or MDM, its integration with Microsoft licenses makes it a worthwhile option, especially with the expectation of future improvements from Microsoft.

We use the Advanced Endpoint Analytics but it is no longer in Intune. It's been moved over to the security portal for Defender.

The endpoint analytics feature, which helps proactively detect and remediate anomalies and endpoints, is now part of Microsoft Defender formerly known as Advanced Threat Protection. Gartner rates it very highly. To perform threat hunting, we need the appropriate licensing, such as a P2 Defender license. This functionality is not available within Intune. We are transitioning from the older Advanced Threat Protection to the newer Microsoft Defender platform. Previously, configuration was done through Intune, but now we manage it through the Microsoft security site.

My advice for any organization that is already paying for a Premium or above Microsoft license is to deploy Intune because it makes financial sense. Intune is not a bad tool but if they run into any issues, the Microsoft support is no good so they need to rely on a good partner to help resolve the issue.

Microsoft cannot fully replicate the functionality of a Remote Monitoring and Management tool. However, it could incorporate certain RMM features into its existing products or develop new tools that complement RMM solutions.

By implementing Intune, we are exposing aspects of our infrastructure to the cloud that traditionally would remain on-premises. This means relying heavily on Microsoft's infrastructure and security. As we saw a few years ago with the Department of Justice's issues, which were clearly Microsoft-related, placing all our trust in one provider can lead to potential problems. However, despite these concerns, we have not encountered any security issues with Intune to date. But at the end of the day, we are maximizing our license.

Intune deployment is straightforward if you're well-prepared, whether for a hybrid setup or a purely Azure-based one. Packaging new apps is generally well-documented, but troubleshooting can be trickier. There are helpful PowerShell scripts available, though they might not be easy to find.

I was using Intune with a customer. I had a long-term contract with a mining company, and then I moved to another organization. I am now in a different company. They all are large organizations. They are moving to the cloud, and Intune is one of the tools they are going to utilize.

In my previous job, Intune was being used for the cloud environment. We migrated fully from on-premises SCCM to cloud-only managed. We were utilizing all the benefits of Intune for cloud management, such as Windows updates, encryption, configuration, replacement of GPOs, etc. Moving away from the SCCM to Intune was a part of my previous job.

It is a modern tool. It is a cloud-based or software-as-a-service tool that gives you centralized management at one location. You have good dashboards. You have pretty much everything at a single location. You can manage different settings in one place. It is about manageability. It also gives you access from any place. It is a cloud solution, so as long as you have connectivity, you can do pretty much everything.

Intune brings all of the endpoint and security management tools into one place, but it is a lengthy process because I have been working for large organizations. They have been heavily dependent on on-premise services for years or decades, so the transition always takes time, but it is pretty successful. It is a good tool, but in security, there are dependencies, so it takes time for the transition to be successful. We have been using different security baselines and CIS or NAS methodology. It is a difficult process. Especially when you do GPO migration, not all settings are yet directly supported in Intune. Sometimes, you have to do a bit of workaround, power shell settings, and registry settings. It is tricky, but it is a key area for a successful transition.

Intune does not yet provide full endpoint visibility and IT control across device platforms. There is still a significant gap between all the systems we used on-premise and Intune. It is probably going to take time for Microsoft to fill the gap. Sometimes, you have to use third-party products, and sometimes, you have to use workarounds. It is a tricky one, but Microsoft is moving in the right direction, slowly but surely.

In terms of user experience, users do not use Intune. From the user perspective, it is about the performance and the impact, and there are some analytical tools to measure performance, reliability, etc. The built-in reporting is pretty good.

Intune affects IT productivity. From the IT operations perspective, things are much more simplified. The transition also enforces some cleanups, optimization, etc. It is definitely a great improvement for the IT organization.

Intune itself has probably not reduced the risk of security breaches, but there are many add-ons. There are many security products from Microsoft that integrate with Intune and Azure. Its reporting is great. By having the right knowledge and the right understanding, you can utilize this. There are some security baselines that you can utilize in Intune, which are coming out of the box. Microsoft is providing its own products for security, and this is probably an area we should explore.

Intune helps to save costs. As a part of the transition from on-premises to Intune, you can decommission your legacy infrastructure such as SCCM and domain controllers.

Intune has helped to consolidate vendors. It is one product, and Microsoft is trying to fill all the gaps with the add-ons. Microsoft is constantly adding functionality pretty much on a monthly basis. Utilizing a single vendor or single tool set is always good. This consolidation affects the licensing costs. When you have a single vendor, you have more options for contract negotiation, license discounts, etc.

It is very important that the capabilities of the Intune Suite are integrated with Microsoft 365 and Microsoft Security for both cloud and co-managed devices. You have a single pane and the same toolset. It is always good to utilize a single product.

It is a modern desktop management tool. It is a replacement for SCCM and GPOs. When organizations are moving away from the AD to Azure AD, especially for devices, it is very useful. It is helpful for managing devices anytime and any place without requiring dependency on the local networks.

There is still a gap between SCCM and Intune, especially in the reporting, inventory, and software deployment areas. For people using SCCM, Intune seems to be very simple. It is a good thing, but sometimes, it is a bad thing. There is a significant gap, especially for large organizations in terms of functionality. Microsoft still has a lot to do.

I have been working with Intune for about 5 years. I am an endpoint management specialist. I am using it pretty much daily.

I would rate it an 8 out of 10 for stability. It is still under development, so there are issues. Sometimes, settings are not consistently applied everywhere, so they give unexpected results. It is probably because of the learning curve and also the ongoing development. Sometimes, there are bugs or some mistakes. It is a cloud environment, and sometimes, some settings are not applied. It is a matter of time. It will get fixed.

It is very scalable. It is practically unlimited.

I have been working with companies with different numbers of users and devices. In one company, there were 40,000 devices, and in another one, there were 300,000. The number of users is more than the number of devices because the companies I have been working with have different shifts, so they are sharing devices. That is why there are more users than devices. The average is 35,000.

The first and the second lines of support are quite poor. They redirect end users to publicly available documentation, which is not very useful because usually, the first thing you do is to check what is available publicly before you raise the ticket. Their support is not very good. I would rate their support a 6 out of 10.

Neutral

I have been mostly using SCCM. The move to Intune was a part of the cloud transition. Most companies are moving not only the MDM solution but all kinds of services to the cloud. Intune is just one of them. It covers one of the areas.

Its deployment and maintenance are easy. I would rate it a 9 out of 10 for both. It is generally deployed on a public cloud.

The number of people required for maintenance depends on the size of the organization. One person is never good enough because you need to consider various time zones, people going on leave, etc. 

Intune comes with the licensing that is common for large organizations. However, Microsoft has recently released many add-ons that are very expensive, especially for large organizations or corporations. They are not very happy. They are not willing to buy them. That is the problem. Microsoft should probably work on the strategy for pricing for the add-ons.

They probably did not evaluate other options. A lot of organizations are trying to use one vendor, and they have been using Microsoft for a long time. Intune seems to be the most complete as compared to others. I have been doing some research recently for a company, and I have been going through some Gartner reports. Intune is clearly number one in this area.

To those evaluating this solution, I would advise to be aware of the fact that this is a product that is still being developed. There are many features that are not available yet, especially as compared to a product like SCCM which has been on the market for many years. Do not expect everything to be available straight away. 

I have not used Intune much for BYO devices. The companies I have been working with do not allow that. They either provide their own hardware, such as laptops or desktops, or virtual desktops such as cloud PCs. They either have Azure virtual desktop or Windows 365, so I do not have much experience with BYO devices.

I have also not used Intune's Endpoint Privilege Management feature. It is probably a new functionality that is not free. For large organizations, it is a significant cost, so they are reluctant to go in this direction. They might use it in the future.

Because of its scalability and future-proofing, I would rate Intune a nine out of ten.

We use Microsoft Intune for managing mobile devices. We considered purchasing another solution but ultimately decided to leverage the tools already available within our Microsoft product portfolio.

Microsoft Intune helps us achieve better predictability and a more secure mobile device environment.

Intune consolidates all our endpoint management tools into a single platform. This simplifies our software footprint. We began with mobile devices and are now expanding to personal computers and beyond. While the process may seem ongoing, it reflects the continuous growth of our endpoint management needs.

Intune is user-friendly. Supporting users doesn't require a huge effort. We've even created a self-service portal and instructions to help them install and manage their devices independently. We centrally manage policies and other configurations. This approach eliminates the need for users to bring their devices to service for initial setup, even for mobile devices. It's all about centralized management. When we provide company devices, everything is managed in one place with consistent policies. Software updates are also streamlined. Compared to older Microsoft tools, Intune offers a significant improvement. Updating software and maintaining the system is much easier with Intune.

Our overall security posture is good. We have implemented all of Microsoft's recommended security baselines. As a result, we use Microsoft Defender for Endpoint to protect both our desktops and mobile devices.

Overall, Microsoft Intune has positively impacted productivity within our organization. Several routine tasks that previously required manual intervention are now automated. This includes administrative functions, monitoring processes for functionality, and even interacting with processes that previously demanded significant manual effort.

By integrating Azure Active Directory Conditional Access with Microsoft Intune, we achieved full visibility of our devices, even when disconnected from the company network. This enhanced security posture is particularly beneficial for our remote workforce.

We can securely manage both company-owned devices and personal devices enrolled in our BYOD program. Intune allows us to create different profiles with varying security settings. This enables us to enforce strong security policies while maintaining flexibility. In case of a compromised device, Intune allows us to remotely wipe it, ensuring our data remains secure.

Intune does not provide real-time visibility. Since it's an online tool, it can take a few hours for the records to update.

I have been using Microsoft Intune for two years.

Microsoft Intune is stable.

Intune reduces the number of people needed for routine tasks, freeing them up for higher-value projects. This reallocation of resources delivers a clear return on investment.

Our enterprise agreement includes Microsoft Intune at no additional cost. To add advanced endpoint protection, we need a separate, but relatively inexpensive plan. This makes it a much more cost-effective solution compared to buying these capabilities as separate products.

We considered other mobile device management solutions, such as Davenport and a VMware product, but ultimately chose to stay with Intune due to its rapid development pace.

I would rate Microsoft Intune 8 out of 10. Microsoft Intune excels in environments with standardized devices, but organizations with a mix of models and devices may require significant manual configuration to ensure functionality.

In the past, I wouldn't have recommended Intune. However, with its integration into the Microsoft product line, it has become a valuable tool for any organization's IT portfolio.

We use Microsoft Intune to secure and control our notebooks and mobile devices.

Intune is deployed as SaaS.

Microsoft Intune has been instrumental in helping facilitate remote work.

Microsoft Intune brings our endpoint and security management tools into one place.

Microsoft Intune provides full visibility and IT control across our device platforms.

The Microsoft Intune user experience is seamless. The users are not affected by the control we have over the devices.

Enforcing privilege access using the privilege management feature allows us to quickly address the user's service requests.

Microsoft Intune has helped reduce the risk of security breaches. This control over our devices reduces the attack surface and makes them more secure.

Microsoft Intune has helped consolidate our vendors making it easier to administer control.

Intune suite's ability to integrate with Microsoft 365 and Microsoft Security for all managed devices is important and makes managing them easier.  

The policies restricting non-corporate devices on our network and the installation of unauthorized apps are the most effective for managing and securing devices.

The ability to block and erase remote devices is valuable to us, especially when those devices are lost.

I would like the ability to install the agent on devices from suppliers, which would enable us to implement a zero-trust strategy for guest devices.

I have been using Microsoft Intune for almost two years.

Microsoft Intune is stable. I have not encountered any issues.

Microsoft Intune is scalable. We are planning to increase the size of our company within the next 12 months.

I have contacted Microsoft support once because we primarily use one of their local partners for support.

Positive

One infrastructure analyst completed the deployment.

We used a Microsoft partner to help with the initial deployment.

On a scale of one to ten with one being the cheapest, the cost of Microsoft Intune is a five.

We evaluated a solution from Blackberry but did not like it because it was not as intuitive and the configuration was antiquated. Microsoft Intune was also less expensive.

I would rate Microsoft Intune nine out of ten.

We have only 100 users. It is easy for us to administrate this number of devices.

A junior-level infrastructure analyst manages the solution.

Before implementing Microsoft Intune make sure to have a good plan and become familiar with all the solution's features.

One plan that we are currently testing for the near future is related to our BYOD fleet. Instead of opting for MDM, we have decided to use Microsoft Intune to manage access to our company through BYOD. Moreover, we plan to use Microsoft Intune to perform autopilot PC deployments in the near future.

We had two distinct issues we needed to resolve with Microsoft Intune for two different use cases. Firstly, for the BYOD scenario, we needed Intune to ensure a sufficient level of security while enabling users to bring their personal mobile devices. Secondly, we aimed to automate PC deployment, even when users are not connected to the network, due to the COVID pandemic and the increase in remote work. Currently, to reimage a machine, users must be on the network. Our goal is to enable them to reimage their machines from home, using autopilot.

We found that Microsoft Intune met our expectations for the BYOD section, and we are optimistic about its potential for PC deployment through autopilot. The main advantage is that Intune performs its intended functions effectively.

As a Microsoft 365 user, we found Microsoft Intune to be a practical choice since it was already included in the bundle. The solution was effective, so we didn't need to look for other options or invest in additional tools. Intune performed the necessary tasks efficiently, making our decision straightforward.

The UI is not user-friendly and has room for improvement.

I have been using the solution for four years.

We have not had a single outage in the last four years. Microsoft Intune is extremely stable.

Microsoft Intune is auto-scalable in the cloud.

The initial setup was straightforward. The deployment required two people from the third party and two of our architects, one for security and one for the network.

We used a third party and our architect for implementation.

We have seen a return on investment because we were able to quickly deploy and start using Intune.

Intune is included in the Microsoft 365 licensing package that we have.

We assessed VMware and found its MDM to be promising. However, since we were already utilizing other Microsoft solutions, and Intune was capable of meeting our requirements, we did not require further evaluation of additional solutions.

I give the solution an eight out of ten.

We have around 10,000 people in over 20 different countries whose devices are managed by Microsoft Intune.

There is no maintenance required for the solution.

I highly recommend Microsoft Intune to others.

The primary use case of Microsoft Intune is for patch management and app deployment.

Microsoft Intune is deployed in a hybrid environment and we use Atel cloud.

I can see that the patch management process is much improved with the bundled patch management option available in Microsoft Intune compared to the KPI deployment required by the other deployment solutions.

Deploying an app can be a complex process due to dependencies. For example, I have a package with three files that need to run, but one of them has a dependency on another one. This can be challenging to manage with the Intune app deployment and has room for improvement.

I have been using the solution for one month.

We have premium technical support from Microsoft.

We currently also use BigFix.

We have not yet implemented the solution but the app deployment is a bit complex.

When we add a device to the Azure domain, the activation process for Intune is simple and straightforward with no added complexity.

We partnered with Microsoft to help us implement the solution in our environment.

Intune is cost-effective as it is included in some of the Office 365 packages. GMF can be more expensive.

We evaluated Jamf Pro and will be rolling it out for Apple devices.

I give the solution a seven out of ten.

As of now, we deployed the solution onto 10,000 devices and when completed it will be 30,000 devices. The solution is used in multiple departments in multiple geographical locations.

Microsoft Intune is a Windows solution, and organizations can take advantage of its features. However, I would not recommend using iOS devices with Microsoft Intune as it is suited for Windows only.

We use the solution for information and protection. The solution identifies anything that can be exploited.

Microsoft Intune allows us to ensure that all devices are authenticated and that they use policies to prevent people from logging in and accessing unauthorized resources.

Autopilot is the most valuable feature.

Unlike VMware Workspace ONE, which provides system configuration and endpoint management, Microsoft Intune is not a standalone application. This is a limitation of Microsoft Intune because it does not provide all the information we need or the application details of the devices connected.

Microsoft Intune's support for Mac devices is lacking and could be improved.

I have been using Microsoft Intune for seven years.

With our number of users, Microsoft Intune is stable.

Microsoft Intune is currently able to meet our requirements, but as we expand in the future, we may need to consider other options. 20 percent of our employees are using Microsoft Intune.

The technical support is slow at responding.

Neutral

The initial setup was somewhat complex. We encountered some issues with the security group, which prevented us from enrolling some of the devices. Our strategy was to onboard all the new users first. The deployment involved around eight people.

The implementation was completed in-house.

Microsoft Intune is included in the E5 license at no additional cost.

We evaluated VMware Workspace ONE but ultimately decided to use Microsoft Intune because we already had a Microsoft E5 license.

I give Microsoft Intune a seven out of ten.

We have not required any maintenance as of now.

I recommend Microsoft Intune.

I'm using all the services that Intune provides, including managing Windows 10 devices and mobile devices, with both the mobile application management and without enrolling the devices. I use it for deploying configuration profiles, compliance and app protection policies, as well as onboarding Windows 10 devices to the Defender portal.

I haven't used other mobile device management solutions, but compared to SCCM, we eliminate a lot of on-premises infrastructure and maintenance by using Intune.

For mobile device management, especially for the Windows operating system, it's quite impressive. But it would really be helpful to have the option to manage server operating systems as well, like Windows Server, at least. That way, we could scrap the use of SCCM, which requires a lot of on-premises infrastructure.

Another area for improvement is the reporting structure. For example, currently, when deploying Windows 10 or Windows 11 updates, I don't get any detail or structured reports showing which updates are installed on the devices. It only gives me information on whether the update policy has been successfully deployed on the device or not. That type of installed-updates detail would be helpful.

I've been working with Intune for more than four years. I'm part of a support operations team managing clients' infrastructures on Intune.

The product is very stable. If you have to think about managing devices securely, go with Intune. Although I have not used any other mobile device management solutions, Intune is very reliable and it's hardly out of service at all.

From the start of my career, I have been managing clients in Europe but Microsoft has no boundaries when it comes to using Intune. There are certain services that are restricted to specific regions, but that is not the case with Intune. It can be used in any region and with any number of users. I have managed environments with 5,000 to 10,000 devices enrolled in Intune.

If there is a service outage, that is made very clear on Microsoft's service portal in the admin center. But if an issue comes up where, for example, a policy deployed from Intune has not been received on a device, it is very difficult to evaluate whether the issue is with Intune or the device. In that scenario, Microsoft itself is confused about whether the situation has to be escalated to the desktop support team or the Intune team.

Other than that, everything is good.

Neutral

The initial deployment process is very straightforward. It's software as a service. You just buy the subscription and start using it. It's not the case that there are very complex configurations or prerequisites to start off.

It does not require any maintenance on the customer's side. Microsoft takes care of all the maintenance.

Having devices managed at scale and maintaining security posture are, of course, value-adds, in comparison with the cost our clients pay to purchase the service. It is worth it.

Microsoft offers different licensing structures. It offers standalone licensing for Intune, but Intune is also included in other licenses, such as for Microsoft 365, E3, and E5, Business Premium, and Business Standard.

There are other MDM solutions, like Workspace One from VMware, which has support for server operating systems as well. I've never used it but I did a quick comparison of the supported operating systems.