Microsoft Intune Reviews

Currently, we use Intune for endpoint security and deployments. We're migrating from SCCM to Intune cloud-first technology. We use it to deploy applications, CSPs, and conditional access.

Previously, we used on-prem SCCM to deploy applications we built manually. After migrating to Intune, we automated and streamlined the process of deploying applications with Autopilot. I can do more with my day. I can manage more applications and ensure that they're updated without monitoring and manually starting that process all over again.

My director used to say that we need to have cattle, not pets. You need to care for and manage pets, but you only need to feed cattle and put them out to pasture. Once you deploy it, you just let them out to pasture, and they update themselves. It's streamlined and so easy.

I've been exploring the Intune Suite, which includes Security Copilot and enterprise application management. EAM is a godsend. I can manage my third-party applications without having to worry about it. I

I set up a proof of concept for the advanced analytics. It was very streamlined. I like the information I got from it. For example, when we were troubleshooting an application, it told me possible scenarios and commonalities between group one and group two and what could be the issue. It is great in that aspect, but we decided ultimately we didn't want to go with it.

We're still learning how Copilot fits into our environment and setting up a POC for Security Copilot. We're trialing Copilot for a subset of users to get a baseline of how we're gonna be using it. I use it to manage my day, meetings, teams, and chats. It keeps me organized.

There are challenges with Intune, specifically in reporting. Many third-party companies offer single-pane-of-glass reporting that shows you what your update environment looks like, how your patch is doing, application status, etc., but Intune's reporting is not intuitive. You can connect to Azure, monitoring, and the workbooks, but it's not streamlined. 

The user experience is still a little difficult. In the first version of Intune, everything is all over the place. It wasn't organized, and things weren't categorized. They changed the name in six months, and we had to relearn everything. 

I have used Microsoft solutions for about 15 years.

I am very impressed with the stability of Microsoft Intune. There hasn't been an instance where things just weren't working. While there may be service alerts or outages, it doesn't significantly impact our operations.

I rate Microsoft support five out of 10. Customer service is inconsistent. Sometimes, the support provided is excellent, and the representative is knowledgeable, while other times, the service needs improvement.

Neutral

We looked at Tanium and Recast for servers and management but ultimately chose to stay with Intune.

The initial setup was made easier with online resources. After setting up some basic components and connections, everything was interconnected seamlessly.

We used a consultant for further development after it was configured. CDW was used to help refine the setup.

There is a return on investment, particularly with the Enterprise Application Management and the efficient deployment features of Intune. It has given me more time in my workday.

Experience with pricing and licensing was challenging. Understanding Microsoft's licensing costs can require certification, making it difficult to know exactly what is needed versus what is available.

I would rate Intune seven out of 10. As much as I sing Intune's praises, I would like more improvements, especially in the reporting. We need to standardize how we use the solution. For example, just in October, we had the update rings completely fleshed out. Then, I went on vacation, and when I came back in October, it had completely changed with new names and new scenes. There are lots of strategic hoops to jump through, but it's a solid solution.

Hybrid Cloud

From my previous experience and my current experience, I deploy Microsoft Intune for all the devices in the company. In my current company, Copilot is being used by all the users to do their work. I can also use automation tasks for Microsoft Intune. I combine the use of Microsoft Intune with Microsoft Purview, Sentinel, and Defender to maximize cybersecurity protection.

For the PKI, most of the products are now using the cloud. My daily task is managing and monitoring things on the Microsoft web page. We have not fully stopped using Sophos because some other office licenses will expire at the end of this year.

The most valuable features for Microsoft Intune are direct control over devices. I can set the policy for USB and data transferring for all company devices. This makes device management easier. It is user-friendly because most companies use Microsoft products, making the interface and features quite good, although the price is higher than other products.

It is much easier to deploy software updates and Windows updates globally because of the cloud base. Thus, I can manage from anywhere, making it quite convenient for me.

The areas that Microsoft Intune can upgrade include BYOD devices. I am currently facing issues with BYOD devices, receiving many alerts about software updates and corrupt files, although I have already whitelisted them. Microsoft Intune should update or upgrade their interface or system to reduce false positive alarms.

I have been working with Microsoft Intune for three to four years.

Initially, almost every day I would chat with technical support for the initial deployment to find solutions for problems, such as false positive alarms.

I give Microsoft Intune a seventy percent rating for scalability because it is much easier for me to manage the 500 or more devices in the company, deploying updates for software and Windows.

Almost every day during the initial deployment, I would chat with technical support for solutions.

They did not give me a suitable solution to solve the false positive alarms.

Negative

I used Sophos previously. We are still using both Sophos and Microsoft Intune since some other office licenses will expire at the end of this year. There are pros and cons between Sophos and Microsoft Intune, but my company chose Microsoft Intune because many users are familiar with Microsoft products.

The initial setup for Microsoft Intune is not so complicated, but the hardest part is creating and assigning policies and rules. We kept receiving false positive alarms during the deployment, requiring adjustments to create new rules for Microsoft Intune.

Both an internal team and vendor are involved because my company has offices in several other countries such as Cyprus, Jordan, and Dubai.

We considered using Microsoft Azure but chose AWS instead because of the price difference.

I already mentioned using Microsoft Purview, Entra ID, Sentinel, and Defender for maximizing cybersecurity with Microsoft Intune. My overall review rating for Microsoft Intune is seven out of ten.

Hybrid Cloud

Amazon Web Services (AWS)

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

We do use Microsoft Intune internally in our company. We handle the distribution software, collect metrics for app usage, and create policies to make the device compliant for Microsoft Intune.

The features that we use very frequently include collecting information about the software installed and determining which software is allowed from our company or not. This is our main feature for now.

We have different departments in our company, and the configuration and distribution of Copilot is another team's responsibility. We use it, but we do not have any part of that process.

We handle the distribution software, collect metrics for app usage, and create policies to make the device compliant for Microsoft Intune.

The features that we use very frequently include collecting information about the software installed and determining which software is allowed from our company or not. This is our main feature for now.

The interface is easy, but it is not user-friendly when evaluating the overall user experience of Microsoft Intune.

The settings are confusing, and it is not always clear where I apply the configuration because we have to open various pages to see where we are applying the settings that we have configured.

We are using Microsoft Intune for about two years.

Microsoft Intune is acceptable and adapts well. I give it an eight regarding scalability.

The technical support of Microsoft Intune rates as an eight when rated from one to ten, where ten would be the best support.

We have addressed other questions and other possible customization, and it is satisfactory because our company also has support from Microsoft directly in our company. This makes it easy for us to ask questions and request features that can be useful in our company.

Positive

Before choosing Microsoft Intune, we did not evaluate other options other than BigFix.

The initial setup and deployment of Microsoft Intune is easy to participate in.

We actually used service technicians from Microsoft to deploy Microsoft Intune. We hired Microsoft technicians to do that.

The technical team from Microsoft are good technicians, and we can see that they are comfortable with the process.

Before choosing Microsoft Intune, we did not evaluate other options other than BigFix.

I am involved in solutions, and we have Microsoft Intune and BigFix in our company.

We are administrators and end users of this solution. However, it is not the priority application because our priority is BigFix.

We are separated into different areas in Microsoft Intune. We have many solutions in Microsoft Intune, but for now, we are only creating policies, managing devices, and installing software because other teams handle other configurations.

We are using Microsoft Copilot in Microsoft Intune. I cannot make any comments about whether Copilot in Microsoft Intune helped protect our environment because Copilot is another department's responsibility.

We had the BigFix platform before Microsoft Intune. We chose Microsoft Intune in the first place because most of our components and services are moving to Microsoft. Microsoft Intune is adding to all the services that we now have from Microsoft.

My overall review rating for Microsoft Intune is eight.

Our use case for Microsoft Intune is managing end-user endpoints, specifically Windows desktops. It is not limited to Windows desktops as it can also manage Mac OS desktops, laptops, and mobile devices for both Android and Apple iOS. 

In terms of needing Microsoft Intune to manage devices, first, there is a requirement that devices must be joined to an Azure domain, either hybrid joined or purely joined. 

From my perspective, purely joined is really the only viable way of setting up an environment. Once devices are joined to Azure, access to Microsoft group policy is no longer available. Because group policy is not accessible in Azure, another way to manage and control devices is necessary. This alternative method uses Microsoft Intune Windows profiles. 

When setting up devices using Microsoft Intune, Windows profiles can be established which perform most of the same functions that Microsoft Group Policy did in a local Windows Active Directory environment. Microsoft Intune can manage and control machines and install software. It allows for Windows provisioning on machines and enables autopilot deployment with pre-packaged installations. When a user receives the machine, sets it up, and turns it on, it connects to the domain and begins installing software, becoming ready within approximately half an hour, which represents a significant time savings for IT departments.

Companies using Microsoft Intune are much better at managing their endpoints with far more visibility. The endpoint inventory is far more accurate and up to date. The Windows versioning for the endpoints is much better, and Windows stays current. Companies not using Microsoft Intune still rely on manual or prior methods of updating and inventorying, which are subject to gaps and inaccurate information.

The Microsoft Intune management console provides visibility into the current status of machines and deployed software. It can automatically update components within its capability, primarily Microsoft products. Third-party software updates, such as VLC media player, are not within Microsoft Intune's update capabilities. Some companies, such as Adobe, have packaged their software to be updatable in Microsoft Intune, though this is more the exception than the rule. Installing software in Microsoft Intune can be challenging if it is not already prepackaged.

The stability and reliability of Microsoft Intune is good. Microsoft takes everything in, and if users stay with Microsoft, everything works together effectively.

Microsoft support for Microsoft Intune is good. In my own use of Microsoft Intune, I did not spend significant time with support because the Microsoft documentation was adequate for our needs.

In a prior environment, when setting up Microsoft Intune, we utilized a third party for assistance. They contacted Microsoft on several occasions, and their needs were answered sufficiently.

We have a couple of companies using other options besides Microsoft Intune. One company is using Avanti Neurons.

I rate the documentation for Microsoft Intune very highly, approximately nine or ten out of ten. One of our companies is beginning to provision and establish a Cloud PK to replace their legacy on-prem ADCS server. 

I used Microsoft Intune extensively in setting up, running, and managing it for several years. In my current role, I don't have hands-on management responsibility for Microsoft Intune as much as responsibility for ensuring it secures the environment from a cybersecurity perspective. 

From an IT infrastructure team perspective, the experience with Microsoft Intune is good, although somewhat complex to navigate initially. From an end-user perspective, the experience is good as long as the infrastructure team has done their due diligence in setting it up to remove any obstacles from the user's setup of their own machine. 

I rate Microsoft Intune a ten out of ten.

My use case for Microsoft Intune is to deploy applications and enroll devices, pushing the apps to the devices.

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

The integration of Microsoft Intune with Microsoft 365 and Microsoft security for cloud and co-managed devices is flawless.

Microsoft Intune works smoothly for discovery, deployment, and automatic updates.

Microsoft Intune helps simplify our IT and security operations as it takes less time, and it's easier to use than SCCM.

Microsoft Intune is flawless for securing hybrid work and protecting data on company and BYO devices.

We are using Microsoft Intune's endpoint privilege management feature. For enforcing least privilege access with Microsoft Intune, we use Entra ID. It restricts unauthorized access, requiring roles to be activated to proceed with necessary tasks, enhancing security.

Microsoft Intune has positively affected my IT productivity, as the decisions made at the enterprise level show it to be a more efficient way than SCCM.

In Microsoft Intune, everything is great. The interface is user-friendly, and the reporting tool works in real-time. Uploading the content is fine as well.

There is room for improvement in server patch management and allowing direct uploads of EXE applications instead of needing to convert them to Intune format, which would save time.

I have been using Microsoft Intune for more than one and a half years.

We have not experienced any issues. I would rate the stability of Microsoft Intune a nine out of ten. 

We have approximately 90,000 devices in our organization. We have multiple locations across various regions of the world. In our IT team, there are about ten people working with Intune, with plans to add more.

I would rate the technical support for Microsoft Intune an eight out of ten.

Positive

Previously, we were using MECM. The reason for the switch to Microsoft Intune is that the organization I work for has migrated to Intune. Microsoft Intune is far more efficient and faster than MECM. The deployment would take a lot of time in MECM; Intune is quite faster.

We are still using SCCM for cloud PKI as it hasn't been migrated.

Deploying Microsoft Intune in the cloud was complex as the previous work needed to be deleted and recreated, which wasted time.

Microsoft Intune saves about 10% to 15% of time. For example, deploying a 2 to 3 GB application at an enterprise level typically takes around one hour to one and a half hours, but with Microsoft Intune deployment, it gets completed in 30 to 40 minutes.

Microsoft Intune saves us around 10% to 15% in resources.

We are using Microsoft Copilot in Intune as an AI tool; it doesn't protect much, but it is handy for our users.

I would recommend Microsoft Intune to other users, especially those using MECM or SCCM, because Microsoft is ending support for older solutions.

Overall, I would rate Microsoft Intune an eight out of ten.

Public Cloud

I use Microsoft Intune for endpoint management. I administer Intune for many clients, and I also use Bring Your Own Device (BYOD) application protection policies.

The most valuable feature of Microsoft Intune is its scalability. It helps reduce hands-on IT support, especially with remediations. Since it is a cloud solution, there is no need for on-premises infrastructure to support endpoints. Endpoint Analytics is considered very useful, although it can be slow. Endpoint Privilege Management greatly increases productivity by allowing admin rights to be assigned to individual applications.

The platform is incredibly slow and could be more responsive. Specifically, when making changes to security policies, I would like to see those changes take effect more quickly.

I have used Microsoft Intune since more than 2019, so approximately three years.

For me, the deployment is not complicated, but it is a complicated process overall.

Microsoft Intune is generally stable but slow. I would rate its stability at eight out of ten.

I would rate Microsoft Intune's scalability ten out of ten. Being a cloud solution increases its scalability.

The technical support for Microsoft Intune is slow to respond and not great. I try to avoid using it because of its slowness. If you can get through to technical support, it is great, but the triage process is lackluster. I would rate their technical support five out of ten.

Neutral

I previously used Symantec Altiris. I switched to Microsoft Intune for native cloud support, as Altiris was not native at the time with cloud support.

Using Microsoft Intune saves costs by reducing the need for hands-on IT support. It has improved our ROI by lowering licensing costs due to the consolidation of vendors.

I rate Microsoft Intune eight out of ten because it is improving all the time. The biggest lesson is that all solutions must be integrated, especially in the journey to the cloud. It is important to keep up-to-date with changes in Intune to ensure all adaptations are utilized.

Public Cloud

Other

Our primary use case of Microsoft Intune was initially to provide a more cohesive update platform. Our organization was trying to move away from SCCM as far as updating our device platforms across Windows devices. We chose Intune because it had a simplified way to configure Windows Update, view reports, and manage devices for updates. We expanded its use for configurations, moving from a hybrid join scenario to CloudJoin, which offers advantages for hybrid work and on-premise settings.

Everything has worked better since we started using Intune. Our devices use Intune for their authentication SSO process, which is also something that Intune integrates with, so we get fewer SSO prompts for our devices. There's more consistency in the configuration. 

Our configuration profiles used to be all over the place. For example, there's a lot of legacy in Active Directory. Going through Intune has helped us enforce settings, which has improved device security and functionality. When you apply something through Intune, you know it works. You don't have to worry about a legacy setting from Active Directory that was uploaded by somebody seven years ago. With Intune, you can see that a device has a setting, and you can be confident that the device is configured how you want.

The most valuable feature of Microsoft Intune is the extensive reporting that is available. The platform's transparency allows us to see when a device has been configured correctly and what it is receiving. 

We haven't implemented it yet, but Intune provides a cohesive platform for passwordless authentication. The single pane of glass is also huge. We were using SCCM with a third-party management platform. We took down five servers and consolidated everything into Intune. The ability to migrate everything into one platform greatly reduced our server footprint. It was effortless. We onboarded all 12,000 of our devices to Intune in a week.

Our users don't notice it, which is probably a good thing. If you don't notice something interacting with your computer, that's good from a user perspective. When we deploy stuff through Intune, it's silent. We recently deployed a bunch of potentially impactful settings to our users and tried to align devices with Microsoft's best practices. Nobody noticed.

Sometimes the syncing is inconsistent. I'm confident that the devices are checking in every eight hours, but sometimes the devices aren't picking up the settings as quickly as I would expect. Some features haven't been updated in a while, and Microsoft doesn't seem interested in developing them. Unless you talk to an engineer, you don't know whether there will be an update.

There are communication issues, so you might start working with a feature without knowing if it will be deprecated six months from now. Some reporting areas still need development. For example, I noticed that the reporting for driver updates is still confusing. 

We have been using Microsoft Teams since the middle of 2022 when we started rolling it out to our Windows devices.

Microsoft Intune has been very stable. There has been only one incident with an outage on the Microsoft side, but it is rare to have significant outages.

Microsoft Intune is a scalable platform with room for growth. Over the past year, it has significantly developed, with onboarding Mac OS devices now an option. Microsoft has put effort into making Intune manage macOS effectively, surpassing some other providers.

I rate Microsoft support eight out of 10. Microsoft Intune's customer service is generally efficient. When a support ticket is submitted, it directly reaches someone with Intune support expertise, unlike other Microsoft products where assistance may be delayed. Elevation to the right person is swift, though I haven't needed to submit many tickets because Intune functions well.

Positive

We previously used SCCM and a device management platform called Remedy in tandem. We switched to unify our mobile device management under one platform and eliminate internal servers. Intune functioned as that single pane of glass for us. Additionally, Intune is more functional and user-friendly than SCCM or Remedy, making it an obvious choice.

The ease of setup depends on your scenario because there are many ways to deploy Intune. Our setup was straightforward because our devices were already in Active Directory, so we could add them using a GPO. After that, we had to do some fine-tuning. We first onboarded our mobile devices and moved our Windows devices to it once the Windows management side matured a little. It took about a week to deploy the solution.

We did not engage a reseller or consultant for our migration. The migration was handled internally without external help.

I can't speak to specific ROI numbers, but there is a noticeable reduction in man-hours spent on support and troubleshooting. Applications are deployed through Intune, and we see fewer tickets for common issues because we can resolve them through the solution.

We did not incur additional setup costs for Intune, as it was already included in our E5 license.

We didn't evaluate other solutions; choosing Intune was obvious as the next step.

I rate Microsoft Intune eight out of 10.

Public Cloud