Microsoft Intune Reviews

My current organization uses device management, deployment of packages, and releasing updates to Windows, Linux, and Mac machines.

Microsoft Intune is being used in my organization.

Microsoft Intune helps when we are preparing devices, as it automatically registers them with Microsoft Intune and self-installs the Intune packages, allowing us to manage that device entirely through Microsoft Intune later.

For Windows, it is easy to deploy Microsoft Intune, but for Mac, it is somewhat difficult, and it is impossible for Linux.

I appreciate how Microsoft Intune deploys Windows-related policies, application deployment, and the application rules that we can create for Windows, which I have automated extensively. I am very satisfied that when any user comes into our organization and we provide the user ID and password, the setup will auto-complete with basic applications and security installed automatically, making the device ready within approximately ten to fifteen minutes. This reduces my manual workload to configure that device significantly.

Microsoft Intune saves me around eighty percent of the manual configuration time for devices.

There is room for improvement in Microsoft Intune regarding Linux and Mac compatibility because some limitations exist. For instance, if I want to install any third-party application on Mac, the process is very complex, requiring multiple deployments and creating an application deployment policy before the Mac rules deployment. It would be easier if, like Windows, it automatically rolled over to the devices without much intervention. Linux presents a major concern as our organization grows and our technical team considers moving to Linux systems for better stability for developers. We are thinking about how we can manage or mitigate the risk for our organization.

The main area of improvement in Microsoft Intune is compatibility. If everything works well, then pricing can be a negotiable point later on, especially if there are multiple users in a large organization. Features that help reduce manual tasks would be particularly helpful.

I have been using Microsoft Intune in my current organization for one and a half years.

I would rate Microsoft Intune's stability around eight out of ten because there are some glitches we face, and we have escalated them to the internal team, who are working on them.

I rate Microsoft Intune's scalability around ten. I have not faced any scalability issues thus far.

I have not connected to the support portal for Microsoft Intune-related issues until now, so I cannot provide a rating for that. I have done everything my own way, so I cannot comment on the support process. The support for Microsoft Office products has been very good, and I hope it remains the same for Microsoft Intune.

I have tried Jamf and forty-two Gears among other platforms. Due to limitations in Microsoft Intune, I cannot do a direct comparison because other platforms provide better services for Mac, Windows, and Linux while pricing is very high compared to Microsoft Intune. If Microsoft Intune provides basic features that can manage endpoints across all operating systems, that would be very helpful.

I need to regularly maintain the patching system in Microsoft Intune because there is no automated system to approve packages and deploy them to the machines. However, it is easy because I only need to create a Microsoft Intune Win package file and then upload it to the respective application that I want to deploy or update on all the devices. I upload that application, and it will do so automatically. I have to regularly maintain and monitor every device to ensure all applications are up to date with updated packages deployed to Microsoft Intune.

Microsoft Intune is moderate in pricing. It is not cheaper or expensive but meets the requirements we need.

I do not use the Enterprise Application Management feature in Microsoft Intune yet, but we are planning to implement it.

I am not using the Advanced Endpoint Analytics feature currently, but I am planning to add more features in a couple of months, as we are in discussions with vendors.

I recommend implementing Microsoft Intune, especially if your organization relies on a Windows environment, as it is easy to manage. However, if multiple operating systems are involved, I suggest using another platform offering better support for those environments based on their technicalities and features. I would rate this review an eight out of ten overall.

Public Cloud

Microsoft Azure

I have used Microsoft Intune for six months. I used it for MDM solution and MAM, but for the packaging, Autopilot configuration, compliance profiles, compliance policy creation and configuration profile creation, I worked for six months because we were moving assets from SCCM to Microsoft Intune. It was a migration project where I was part of the team. In that project, I worked on the packaging side where I was responsible for creating new packages that were already present on SCCM for laptops. The main use cases for Microsoft Intune are for compliance policy deployment and application deployment for laptops.

I assess the user experience of Microsoft Intune as good. It's cloud-based with no need for on-premise infrastructure. You can access it anywhere and start working on it. You will have the record of data in your hand anytime if you need it quickly. The benefits that Microsoft Intune brings depend on what you are using. It's directly integrated with Azure AD. If you are using on-premise Active Directory, there is a process to integrate easily and use those resources. This tool works beyond the boundary, which is why organizations use it.

What I appreciate about Microsoft Intune are the detection method and the supersedence option, dependencies we can add on, and multiple software we can install with a single package. That's a plus point inside the solution. It's directly integrated with Azure AD, and if you are using on-premise Active Directory, there is a process to integrate easily and use those resources.

I haven't worked extensively with Microsoft Intune to identify many areas for improvement. However, one thing I would suggest is that servers are not getting managed through Microsoft Intune. If that feature would be added, everything would be improved.

I have used Microsoft Intune for six months.

When it comes to the stability and reliability of Microsoft Intune, I don't hear about any downtimes, crashes, or performance issues because it's server-based and those are managed by Microsoft only.

We can discuss Microsoft solutions, Intune or SCCM.

When implementing Microsoft Intune in my environment, it was straightforward. It's not as complex as other tools. It's easy to learn things, and I could easily work on it.

I was part of a team working on a migration project where we were moving assets from SCCM to Microsoft Intune. I worked on the packaging side where I was responsible for creating new packages that were already present on SCCM for laptops.

Everything about ROI and measurable benefits in terms of time saving, cost saving, and resource saving depends on the organization and their requirements. Products get acquired based on requirements. If you have maximum servers, you will go with a solution that patches the software most frequently and is good with compliance. If you are going to manage only laptops and workstations, you should go with a solution that is easy and very low cost to manage.

I don't have any information about the pricing of Microsoft Intune.

Regarding the key differences between Microsoft Intune and JAMF or Ivanti products, there are many things increasing inside Ivanti now. They are working on the cloud part and coming up with new features. I haven't worked on the new features and updates, so I cannot share much experience on that part.

My advice to others considering Microsoft Intune for their organization depends on the infrastructure they have in place. Based on that, they can determine if Microsoft Intune will be best for them. If they are going to manage laptops and desktops only, it will be beneficial for them. They can apply MDM and MAM on those devices if there are few and remote devices. Laptop, iPad, mobiles, Android, iOS, everything can be managed through it. MacOS and Linux can also be managed. On a scale of 1-10, I rate Microsoft Intune a 7 out of 10.

Public Cloud

The main use cases for Microsoft Intune are to manage all types of devices, especially Windows.

The selling points for Microsoft Intune are very good. You don't have to enroll the devices, however, you can still push an app through some policy and with a few restrictions. If you want to push one single app to end-user devices, once you push it, you can also push it along with the security that they cannot copy your data or misuse it. This is one of the key benefits.

Microsoft Intune can be used with co-management. There are clients who don't fully want to go with Microsoft Intune as they are already spending with SCCM or other platforms. They want to partially transition into Microsoft Intune, then later fully transition into it. That's when the co-management works, and that feature is available in Microsoft Intune.

The user experience of Microsoft Intune is good. It's a very old tool, and many engineers are available in the market. There are multiple knowledge articles and videos about this tool. The user experience is good since users understand their path and how to proceed. If users understand that, it's easy for them. In that way, it deserves ten out of ten as users know how to work on this tool.

Everything has remained the same in terms of Enterprise Application Management in Microsoft Intune. App discovery still requires user initiation for installation, whereas auto-installations occur silently and remain on the device screen.

The PKI tool is cloud-based, and they are doing excellent work. In terms of complexity, they reduce the task. You cannot keep giving certificates to all the devices one by one, and the PKI tool handles that. They provide the certificate and stamp on it for the device seamlessly, so you never know the device is secured with this type of certificate.

The granular support for other device types in Microsoft Intune could be improved. Microsoft Intune works well with Windows, however, we are not as well-suited for Mac devices. If you're looking to support Mac, consider other products such as AirWatch or Jamf. MobileIron is not that effective. That said, Jamf is good for Mac. Microsoft Intune offers numerous features for Windows, allowing for substantial customization; however, for Mac, it lacks this capability.

In the next releases of Microsoft Intune, a feature to renew the certificate automatically would be beneficial. Currently, for Wi-Fi certificates, we need to do it manually, which can cause most devices to disconnect and reconnect, resulting in big issues for clients facing connectivity problems. The renewal should happen automatically, and that is something they need to work on.

I have been working with Microsoft Intune for approximately five to six years.

Microsoft Tech Support is good, providing solid support. That said, it often depends on the representative. There are levels of support; level two and level three offer great assistance, while level one primarily collects data and doesn't provide as great of support.

The deployment is okay. It depends, from client to client. It's not like every console needs some time for deployment. So for example, if you're already on the on-prem margin of Intune, then we have a certified vendor who would deploy in the initial phase. I'm talking about initial deployment, where you configure Intune, you log in to a new Intune, and then you add users, and then you add the devices and things like that. So the initial deployment for that, we have certified vendors. Even our company is a certified company that does this deployment. We have certain tools for direct migration. However, if you're trying to deploy from a different console, like AirWatch or a mobile app or things like that, it may take maybe three months, for example. We need to be ready with all the profiles. We need to be ready with all the products. We need to be ready with all the app deployments. We need to be ready with multiple things. That way, once the device is enrolled, it gets what it needs. It gets the certificate. It gets the apps, and the user experience is seamless. 

Obviously, it needs some time. We have worked on two clients and it takes three months minimum.

The cost-effectiveness of Microsoft Intune is about 90%. Most clients, specifically with Windows devices, adopt it, so it's effective. The licensing model has advantages, as they bundle services such as Azure AD with Office 365, which many clients find valuable, leading to Microsoft Intune's dominance in the industry.

The pricing for Microsoft Intune has different types of packages. Currently, if you go with all the packages, the mid-variant of the top-level package such as E3 or E5 offers benefits such as AD and Azure AD. If you require all these tools, it could be cheaper, however, if you do not need certain tools and still want Microsoft Intune, it is not that cheap. It can be quite expensive. 

Additionally, if you are already on one cloud-based platform and moving to Microsoft Intune, the transaction will also involve some costs since deployment is necessary. 

Cost-wise, it varies from project to project. If the client wants to move, they may need to go for the E5 license; the difference between E3 and E5 is not significant. If your organization has a large number of Windows devices, Microsoft Intune is a valuable tool. But for Mac users, Jamf would be recommended.

If you're looking to support Mac, you need to look at other products such as AirWatch or Jamf. MobileIron is not that effective; however, Jamf is good for Mac.

Copilot in Microsoft Intune is a new tool used for answering questions, similar to ChatGPT or Gemini. There are two types of Copilot; even in Workspace ONE, there are similar tools. The licensed version is not used as it comes with a price, and our client doesn't want to go with that. The basic level of Copilot is given, which can answer a few questions, however, it is still under the learning phase. If I ask a question, it sometimes gives an exact answer, yet at other times, it suggests going somewhere else to find it, and there is no button available there. In the paid version, it can perform simple tasks such as pushing or adding devices to a group, however, it wouldn't truly help with the current level of AI. We may need more complex AI for this type of console.

On a scale of one to ten, I rate Microsoft Intune a nine.

Microsoft Intune is a comprehensive solution for mobile application management and mobile device management, securing various endpoints like Windows, Android, and Apple devices. It excels in managing BYOD scenarios, employing work profiles to segregate personal and company data, and ensuring device configuration and compliance with company policies.

Intune provides a centralized management solution, although its suitability depends on specific needs and comparisons with alternatives like Jamf, Kandji, or ManageEngine. Overall, Intune is a sufficient solution for general use cases requiring essential device management and data security.

The Intune Analytics section is quite useful, especially for Windows upgrades on remote devices. We frequently utilize it to assess compliance and gather analytics on upgradable devices, including TPM and Secure Boot support, and memory capacity. This allows us to identify devices that meet the requirements for Windows 11 and proceed with deployment accordingly. It's particularly valuable for managing Windows 10 to Windows 11 upgrade scenarios.

Copilot for Microsoft 365 is a valuable tool that I use daily for creating proposals, summarizing Teams meetings, and generating content in Word and PowerPoint. It's even helpful in Outlook on occasion. Additionally, both Bing Enterprise and the standard Copilot in Edge are particularly useful when integrated with Customer Data Protection. This integration allows Copilot to securely access company data, including emails, presentations, and documents, to provide relevant recommendations and answers to queries.

Intune secures Bring Your Own Devices through network access management and work profiles, separating personal and company data. Additionally, it utilizes Defender for Endpoint for device security and facilitates deployment. Features like cloud app security, Microsoft Purview, and data loss prevention further enhance security and compliance, depending on the Microsoft 365 package, protecting both devices and data.

Privilege Access Management sits mostly on Entra ID and is deployed through Intune.

The primary challenge lies in managing employee devices, particularly differentiating between personal and corporate devices. Personal devices often face pushback against deploying security measures, while corporate-owned devices can be managed more securely and effectively. For instance, if a corporate device is lost or stolen, Intune enables remote wiping to protect company data.

Intune has helped in integrating Windows Update for Business to ensure machines are compliant. It provides functionality for workflow management on devices and separating company data from personal data. It is also used for deploying security and compliance capabilities depending on the Office 365 package used.

I find Microsoft Intune valuable primarily for its Windows management capabilities, along with its Android Enterprise and Apple device management for mobile devices. The mobile application management features enable BYOD support and work profiles on personal phones, enhancing security and control. Additionally, Intune excels in configuration and compliance management for Windows 10, ensuring devices receive timely updates and adhere to organizational standards.

While Intune effectively handles basic functionalities such as device management, data separation, and updates, it may present challenges with update times and limited advanced features.

Intune is not the most user-friendly mobile device management platform available. Compared to Jamf, AirWatch, or VMware Workspace ONE, it is not as intuitive or easy to navigate. 

The primary challenge with Intune's enterprise application management feature is its focus on the Microsoft application stack. This limitation makes managing third-party applications difficult, as there is no centralized store or streamlined process for batch operations. Intune lacks the robust support for third-party applications.

Microsoft frequently changes its offerings, so features previously included in Intune might now require Intune Suite. For example, managing device certificates, once an Intune feature, now requires this separate package. Essentially, Microsoft releases new features but places them in Intune Suite, requiring an additional purchase for functionality we might expect in the standard Intune license. This ever-evolving strategy means staying current with Intune can become costly.

I have been using Microsoft Intune for almost five years.

Microsoft's product support can be inadequate, with slow response times and unsatisfactory resolutions impacting the overall user experience. This contrasts with Jamf's support, which is generally perceived as superior due to its responsiveness and effectiveness.

Neutral

Microsoft Intune's costliness stems from licensing fees and the overhead associated with its management, user experience, and device remediation. While its licensing costs are high, the platform's limitations in manageability and user experience customization further contribute to the overall expense. Unlike Jamf, which offers greater flexibility and remedial capabilities, Intune's intrusive, yes or no approach limits user customization and potentially increases support needs. Therefore, determining Intune's true cost of ownership is subjective and depends on how these factors are measured.

I have evaluated Jamf, Kandji, ManageEngine, and VMWare Workspace ONE.

I would rate Microsoft Intune a six out of ten. Its management is not user-friendly, and device additions can take up to 24 hours to synchronize, unlike Jamf, which updates within 15 minutes. This delay is problematic for immediate remediation actions, such as removing harmful content or addressing device exposure, where a 24-hour wait is unacceptable.

It is advisable to prepare for the complexities of Intune and consider Jamf for better support and manageability if working alone. If you plan to use Microsoft Intune, be prepared for manageability and potential delays in changes and support responses.

We use Intune to connect university staff and faculty to secure resources on their computers quickly.  

Intune is a force multiplier coming directly from Active Directory. We had to engineer over some limitations of Active Directory, and Intune resolves that by addressing known trouble areas. It allows us to do things quicker and more efficiently. 

We like Intune's Autopilot functionality, which enables one-touch deployment. Dynamic grouping is another feature we find valuable working in academia. We have people in buckets based on their roles in the university, such as faculty, staff, alum, or grad. Sometimes, they will fit into multiple places, and dynamic grouping helps with that. So far, using Intune has been easy and intuitive. Once everything is set up, our user base finds it much easier and more modern.

We've recently purchased Copilot licenses for Intune, but we've only had it for a week or two. It's a new deal for Syracuse, but it has been good so far. It moves quickly. You can see that it's constantly learning, and I love that. Today is the dumbest it will ever be. It's going to continue getting better and better. Even when we're wowed, we understand that more "wow" will come. 

It has some growing pains, but they are no different from anything new. We're implementing Intune on an individualized data set. So there's no way Copilot can know everything about every data set it's going to get, but it does grow pretty quickly, which is phenomenal. 

It would be awesome if Microsoft opened their API so we could filter more properties. If we have to do anything outside of Intune that requires a third-party solution to talk back to it, we're very limited in what we can do. Trust your people. We promise not to break your stuff. Open it up just a tiny bit wider.

We started using Microsoft Intune about a year and a half ago. We transitioned our fleet from Active Directory to Azure Active Directory. Then, we took that hybrid and shifted it into Intune for our MDM solution.

Intune is solidly reliable. Microsoft has some peaks and valleys that you need to get used to. Stability is essential when transitioning from on-prem to the cloud, where Microsoft manages your infrastructure. There have been a few drops in performance, but that's more growing pains from our rapid expression than an indicator of major problems.

Scalability is fantastic. 

I am a technician, so when I'm reaching out about problems I cannot solve myself, they tend not to be tier-one or tier-two problems. When I contacted Microsoft, they had the same expertise, if not more, which is phenomenal because I felt heard and my problem was solved. That is delightful because I have contacted support for other solutions. After trying several troubleshooting steps, I contacted them, and they asked me to restart something. I have gone beyond that point and tried to tell you where I am. 

Positive

We previously used Active Directory and spec ops for software deployment, with Active Directory handling computer and user management. Intune was a natural progression for MDM. For Mac users, we still use Jamf but plan to transition them to Intune as support for Apple products grows.

It is absolutely a positive investment. Everything we've gained from it makes my job easier day after day, and I see value in it as an engineer.

I am not involved in those discussions. We worked hard to acquire E5 licensing, and Microsoft collaborated well with the university to ensure everyone got what they needed.

We are a Dutch MSP delivering modern workplace solutions for all of our clients. We create tailor-made workspace environments for them.

It helps us to transform IT environments of our customers from on-premises to the cloud, focusing on both Azure and the modern workplace.

Windows Autopatch is the most valuable because it removes the burden of patch management. Intune's user experience is pretty smooth. The endpoint analytics works well if you know how to use it as a guess. Microsoft includes a little more added value by default. It's a great source of information. 

Intune should improve its software inventory to provide better metering of which software is used throughout the company. This is especially needed for reporting third-party software solutions.

I have been using Intune since 2017 or 2018.

Intune's stability is good and has improved a lot over the last year.

Scalability works well. It supports organizations with 200 endpoints and those with more than 15,000 endpoints.

I rate Microsoft support eight out of 10. Customer service is pretty good, partly because we have a contract with Microsoft. Transparency is good.

Positive

We used Active Directory group policies and ConfigMgr in the traditional way. However, most of our clients are already on Microsoft 365 Business Premium or the enterprise E3 or E5 stack, so it doesn't make much sense to use solutions from different vendors.

We are a reseller.

One of our clients migrated the model workplace based on Intune, achieving a 78 percent cost reduction, which is quite a lot. Even with the projects around it, they still gain cost benefits in the first year.

It's cost-effective because Intune is included in the E3 and E5 licenses. It's smart because it helps Microsoft sell the license.

I rate Microsoft Intune eight out of 10. There's always room for development.

Public Cloud

Microsoft Azure

My use case for Microsoft Intune is device management.

The best features in Microsoft Intune that I appreciate the most are the strong security, encryption, and operating system version.

Microsoft Intune can save a lot of time and resources. My estimate is that it saves approximately 50% of the time.

In Microsoft Intune, error messages are an area that has room for improvement.

Regarding error messages, I would like to see more detailed logs added. Additionally, the policy management was somewhat complex.

I have been using Microsoft Intune for about two months.

I would rate its stability as 8 over 10.

I would rate the scalability of Microsoft Intune as 9 over 10.

I would rate the technical support for Microsoft Intune as 8 over 10.

The deployment took some days. I did not have very large challenges implementing Microsoft Intune; they were small, and we resolved them shortly.

My thoughts on the pricing are that it is cost-efficient.

My advice for others looking to implement this product is to consider that Microsoft Intune is a scalable and cost-efficient solution. I would recommend it.

Public Cloud

Microsoft Azure

I primarily use Microsoft Intune for work, managing devices and user account management, mobile device configuration, policies, and general Microsoft Intune functionalities.

I use Microsoft Intune Suite's cloud PKI for certificate management.

My level of managing the PKI and helping with the complexity of certificate infrastructure is still at a beginner stage. I do not do a lot of that; I use it for work and have used it for the past few years, but I have not reached the stage where I have to deploy certificates, so I have not been able to use that feature yet.

I work with Microsoft Intune through 365; it is the cloud service.

I do not have the Advanced Endpoint Analytics feature enabled for myself with Microsoft Intune; I am currently on Microsoft Intune and do not see that feature.

The best features from Microsoft Intune are the ability to manage multiple devices and the ability to deploy multiple policies to devices across the system, which is a very impressive feature. Being able to manage other groups and tenants within the system are also impressive features in Microsoft Intune that I have learned.

I find Microsoft Intune very user-friendly.

Generally for the organization, Microsoft Intune has been a good investment for managing a lot of the company resources, saving a lot of money compared to using the on-premises version of the software.

I would say the interface and dashboard summarizing the devices' status and compliance could be improved. I think they could organize some of the dashboard information to be more compact and more insightful than the way it is right now.

What I think would make Microsoft Intune a 10, apart from the interface and dashboard I mentioned, is the other features within it.

I have been working with Microsoft Intune for three years.

Microsoft Intune is reliable; there has not been any downtime during my usage, so I think it is very reliable compared to what I actually use it for on a day-to-day basis.

It is easy to scale up Microsoft Intune when I need to expand the usage.

I have not used any different solution prior to adopting Microsoft Intune; I came on board about three years ago, learned the software, and since then, I have only used Microsoft Intune.

Microsoft Intune has Copilot integrated into it, but I do not use Copilot for any particular tasks.

There is no complexity in the deployment from Microsoft Intune.

Public Cloud

Microsoft Azure