Microsoft Intune Reviews

We use the solution for endpoint management, which includes security and compliance. 

We are a remote company, and the product helps us manage the global endpoints. It helps us natively manage the endpoints in the cloud from anywhere. 

Microsoft Intune's most valuable feature is Autopilot. 

We faced issues with macOS support. The product should have better inventory and asset management. 

I have been using the product for four to five years. 

Microsoft Intune is stable. 

My company has 200 users. 

Microsoft Intune's deployment is straightforward. 

We did the deployment in-house. 

I liked the tool's pricing until P2 came into effect. I am unsure about the current value versus the cost of the new licensing model. 

Microsoft Intune has improved access to devices for remote wipes. We can act quickly whenever someone leaves a company or a device gets stolen. It offers more visibility into our IT group. 

The tool's cloud-focused availability has improved the organizational security posture. It has helped to save time. We can do a lot more with a smaller team.

I rate the product a nine out of ten.  

We use Intune for device management to ensure mobile devices such as laptops and tablets comply with our organization's regulations and requirements. We have some on-prem resources and operate a hybrid, primarily cloud-based environment.

We have seen many benefits from using Intune, especially in security. We have fewer company data leaked to the public as our security is tighter, and our company network is safer.

The ability to wipe data from and reset devices is one of the most important and valuable features. If a device is reported stolen, we can freeze it or wipe the data from it, preventing data leakage.

The solution offers excellent visibility into all devices connected to the network and whether they are safe or compromised.

There are some issues using the solution with macOS and iOS, and it offers limited granular control with them. Intune works better on Windows and Android. 

I've used the solution for two to three years as an end user and an IT admin.

Intune is very stable. 

The solution's scalability is excellent, though it could be improved regarding macOS and iOS.

We've reached out to Microsoft technical support many times, and they have always helped resolve our issues promptly and efficiently; I rate them ten out of ten.

Positive

We previously used Microsoft System Center Configuration Manager (SCCM) for group and on-prem policies, which we also pushed out to devices. We switched because Intune is more modern and cloud-based, so it fits our organization better.

As an IT admin, I was involved in the deployment of Intune as a consultant. The implementation was very straightforward as we're an experienced team of security professionals consisting of two IT admins and an IT manager. There was also a test environment for our benefit, and moving that over to a production environment was seamless.

We carried out the implementation internally. 

We definitely have an ROI with Intune, and the benefits are compounding. Security is a non-negotiable area; our business has to be secure, and our sensitive company data has to be protected from malicious actors. The security of company resources is always an ROI for the business, so it's essential.

The product is relatively pricey, but considering its benefits, I'd say it's fair. The benefits outweigh the expensive licensing fees, especially for large organizations, but medium-sized and smaller businesses may be unable to afford it.

We didn't consider other options; we wanted a Microsoft product, as it's great to add to our existing suite of business applications, and the integration is more seamless than it would be with third-party products.

I rate the solution ten out of ten. 

We implemented the solution to solve security concerns; users access our company resources from outside the network, and we must ensure the devices they connect from are safe. As an admin, I have complete visibility into devices connecting from outside and can ensure they are safe and secure.

My advice to those considering the solution is to be aware of its capabilities, limitations, and their business needs. These factors will allow you to determine if Intune is the best device management tool for you. Depending on the environment, you may have to combine Intune with an older technology to manage all company devices.

We're an MSP, and our primary use case is for fleet management; our entire fleet is handled through Intune, so all our mobile devices are logged in through the Azure portal, and we can manage our apps that way. We've been able to lock down our devices and control our field of frontline workers.

The solution allows us to keep track of an extensive device fleet so we know where they are and whether they're secure and compliant. Those that aren't compliant enter a pool, and our tech staff work to rectify that. Intune improved our organization by helping keep our data secure.

The security-related tools are excellent; these features allow us to secure devices, lock them down, and ensure compliance.

Due to the abundance of features, there's a lot to organize, which makes managing and setting up the solution challenging. The setup is immense, and it would be good to see improvement in this area.

The stability could be improved. 

We've been using Intune for around six years. 

Intune is a stable platform for the most part, though Microsoft can still make some improvements in this area. 

The solution is very scalable. 

Microsoft has slow technical support; getting through to anyone typically takes a day or two. Once we get through, then the support is good.

Neutral

The deployment is relatively straightforward; we send out an email, and our users click the link; it downloads the tool to their phones, and they can log in using their credentials. If it's set up correctly, then the deployment is easy.

The solution requires a small amount of maintenance; I have one full-time member of staff to maintain 420 total devices split between two of our clients. 

The cost is handled through our Office 365 license, so I have yet to be able to compare it directly with other tools in its class.

I rate the solution seven out of ten. 

My advice to those evaluating Intune is that you need to know Azure. This isn't a product you can jump into without prior Azure knowledge.

We use it for proposing solutions to customers and for co-management of the end-user devices, as well as for unified endpoint management. We also use it for mobile device management.

Internet-based access with security is what I have found to be most valuable.

It is also a stable and scalable solution. We have not had any issues with technical support as well.

The initial setup is straightforward too.

Currently, for a new customer or when a device refresh occurs, I can introduce Microsoft Intune as a unified endpoint management solution. However, for an existing customer who has an SCCM it would need to be upgraded to an MECM first before I can introduce Microsoft Intune.

Microsoft even recommends it as a co-management solution because even if I need to go for UVM as a unified endpoint, I need to rebuild all the missions, which is not practical. So, they need to look into it and provide an easy and flexible moment to UEM.

I've been dealing with Microsoft Intune for at least fours years.

Stability-wise, it is good and stable.

It has very good scalability.

We have had no issues with technical support.

The initial setup is easy. Deployment usually takes around eight weeks of time, including pilot testing. We do requirement gathering, designing, and building, so it takes us a minimum of eight weeks.

From a solution perspective, I always recommend that you go for it. From a scalability aspect and on managing the devices over the internet and ensuring that the security of the devices for customers is always taken into account, we always recommend to Microsoft Intune.

On a scale from one to ten, I would rate this solution at nine.

Primarily we are rolling the product out because we want to be able to have remote access and control over our desktops and laptops from external locations.  

The most valuable aspect of the product when it is in production is the basic thing it was made to do. We want to be able to allow access to various applications remotely which we can not otherwise do with remote workers.  

This type of question may be premature because we have just started rolling it out now. We have not had a chance to work with it to capacity at this stage. I think, so far the implementation is all a bit shaky and should be better planned and better supported. The deployment seems to not be as simple as what I would have hoped that it would be considering it is a Microsoft product.  

When it is fully rolled out, we will see where the other shortcomings actually are. However, this difficulty in rolling the product out is a significant stumbling block.  

We just started testing the product several months ago. The technical team is working toward trying to roll it out to production in about the month. As that is the case, we are not really using it yet in production. We have got only about half-a-dozen of the 4,000 projected users working with it currently.  

Again we have not really tested and deployed the product broadly across the company at this stage. But it is exactly because we have not seen the kind of stability and performance we were expecting that we have not completed the roll out.  

If we can not seem to get even half a dozen users working with the product in a way we consider stable, the scalability is in question. It should not be.  

As far as the set up, we only have the first half-a-dozen technical people on the product just to do a pilot. We have had issues with it. This is the reason we have not even deployed it for the users' space yet to deploy to a larger test group. I would expect the deployment would be a bit easier. That could eventually be a changing factor in what we do moving forward.  

I have rolled our company onto a 365 E5 licensing scheme. We are not on E3 anymore so we do not need to. With an E3 license, you would have to consider licensing the product.  

We did not really look at any other competition. We are a Microsoft 365 E5 customer and the product promises the capabilities that we need and is available without additional cost. It just made sense to try to use this part of the suite.  

On a scale from one to ten where one is the worst and ten is the best. I would rate Microsoft Intune as about a six. I am not totally impressed with the complexity of the rollout. 

We use Microsoft Intune for controlling and managing all of our in-house and remote devices. It allows us to deploy applications to all devices.

The most valuable feature of Microsoft Intune is having all our devices compliant with our policies.

The solution can have some compliance problems in general and the end-point user can bypass easily the company policies in Intune.

I have been using Microsoft Intune for approximately three years.

I have not had any problems with the stability of Microsoft Intune.

The solution is deployed for end users and all of our devices.

Microsoft Intune scales well.

I have not used the support from Microsoft Intune.

I have not used a similar solution to Microsoft Intune.

The solution is worth the money for us.

We have the business premium licenses for the solution.

I rate Microsoft Intune a nine out of ten.

Generally, the top three uses are operating system deployments, software updates and patching, and software deployments to endpoints.

If you're a small shop, a two-person organization, yet you have many endpoints, five to 10,000, you can easily manage them. You can manage the masses with one person part-time and it's a good automation tool that takes away the need for multiple folks to do a lot of things in the environment like software deployments or patch management. It's very good at automating those functions.

The reporting aspect is very nice. It's got about 450 canned reports in it. They're easily customizable. You can get really good granular reports for inventory, patch management, status, and everything. It's very good at reporting.

It's not hard to set up. It's easy to manage.

Third-party patching and other solutions integrate with Endpoint Manager. From that perspective, there's no deficiency. 

The UI is good. You can filter things out so that you'll only see things that are pertinent to your function. 

It's really matured and improved over the years by assimilating competing products. There are a lot of things that used to be better than Endpoint Manager or not available in Endpoint Manager that were absorbed or purchased and placed into this product. From a deficiency perspective, I can't recall coming across anything substantial. I'm trying to think of a weakness. I compared it to Ivanti. From a new user's perspective, it may be a little overwhelming because there are quite a few things to look at in the console, however, once you are sort of acclimated and are familiar with your core functions, it's fairly simple and straightforward.

You can modernize the UI a little bit, however, change for a sake of change isn't always a good thing.

I've been using the solution for 25 years. It used to be called SCCM.

The solution is very stable.

The scalability is great.

The largest user base I've ever supported, for example, was a headquarters and they had 220,000 endpoints. In contrast, small colleges and educations may only have 500 users, so they can get by with a single server hosting everything. SQL and everything can be one server.

For us, the solution is extensively used.

If you're looking forward to deficiency, I'd say that the Endpoint Manager support at the lower levels is poor. As you go higher and you get like a more engineering level, then you're fine, however, the early stages of support are not the best.

I've worked with Ivanti and LANdesk and other tools.

I've used Endpoint Manager every day. I'm currently using it. I've been using it for 25 years. However, there are other ones like BigFix, which I've rarely used. I've used LANdesk a few times. And people would try to use LANdesk to avoid the expensive Endpoint Manager, however, at the end of the day, it costs them more in time to use the LANdesk solution. Ivanti is a competitor, however, they're cobbled together with Shavlik, for patch management they've got Altiris. They bought Altiris and Altiris has been passed around like a cheap hoe from Symantec to Intel, to everybody.

Altiris was actually developed to support Endpoint Manager and provide asset management. At the time, Endpoint Manager didn't have good asset management, so they actually worked with Altiris, only to find out that Altiris was actively taking Microsoft customers. Microsoft booted them to the curb and they haven't done well since. That was back probably in the late nineties that they did that. Endpoint Manager has been around the longest, it's survived, it's matured and it's the top dog in general.

Complexity-wise, it's not hard to set up. It's just a lot of small steps, such as making sure the firewall ports are open and certain things are in place, and all the perquisites are taken care of, as the wizard, the installation wizard for Endpoint Manager, is pretty straightforward. As long as you have SQL and some other features turned on to support the different functions of Endpoint Manager, you're fine. You'll need WSS or you'll need WSS for patching and you'll need SQL reporting services for the reporting portion of it. All those small things. The more lights you turn on, the more configuration you have to do.

The deployment itself took me four hours end to end, to put all the prerequisites in, however, understanding, of course, may take a while for someone new. I've done this now for over 25 years. For me, it's pretty straightforward and I have, a lot of these things PowerShell scripted so it works very well. You can create a PowerShell script and set the whole thing up from Powershell, which is what I've done.

Maintenance requirements are low. Since it lives on SQL, if you put a SQL maintenance plan in place, it's pretty much, it's very healthy, it's very stable.

We've seen an ROI. It enables you to pair down the resources necessary for configuration management. You don't need a large shop to maintain your environment. If you want to develop it, if you want to create new images all the time and that sort of thing, then you're going to need to staff yourself accordingly, however, not necessarily to support Endpoint Manager, just to develop those and payloads that it delivers.

I'm a partner. I'm using the most up-to-date version of the solution.

While the solution was on-prem initially, now it's converted to more of a hybrid. They have co-management so you can manage on-prem and cloud together.

I'd rate the solution nine out of ten.

Mostly the pricing can be improved. If you are using the solution with EMS E3, then it's very expensive, but if you are using it in combination with a lot of products, then it can be cheap. Microsoft doesn't sell Intune separately. That's another consideration. The third thing would be how to view the use case because Microsoft doesn't release any documentation on how to view it when you adopt Microsoft EMS. 

Their technical support could also be improved.

It is very stable.

It's scalable because this is a cloud solution only. They don't have it on-premises.

With Microsoft technical support, they only fix Teams and when they are open, they're mostly trying to close again at the quickest time. Sometimes, the solutions given are not very good.

It depends on the use case. If you only focus on Mobile Device Management, then it is very easy to setup. You just have to define the use case in the context you want to protect. If you are talking about how to integrate with the lock analytics and how to classify data in context, then this is another thing.

The main difference between Intune and Workspace ONE is the quality integration between Microsoft products and Office 365, which means that Intune is part of a solution; you are not only using Intune, but you have to think about its ecosystem. For example, with EMS, it will have at least three products. The first is Azure ID Premium, which is the IAM solution (Identity and Access Management), so there are use cases where you might need to use IAM. The one difference between EMS and Workspace ONE, since Workspace ONE doesn't focus on identity management, is that it only has the access part. It can leverage all identity management, like with the directory or any of the identity solutions. 

The second difference is in the integration with Office 365 because in the Office 365 ecosystem, you have a lot of products, like Azure Information Protection, which is focused on the labeling and classifying of data. Microsoft also has Defender DLP and Defender for Endpoint. These make up a total solution. Based on that, if you have a long-term roadmap, you can actually integrate it with other Microsoft security solutions, like Sentinel, which is a SIEM solution. When choosing Intune, the main difference is the ecosystem and the roadmap.

I would rate this solution a nine out of ten.

For advice, it depends on the use case you are trying to solve here. If we have a look at the use case for security, how would you control the mobile? How would you deploy? How would you protect them based on that? The lesson depends on the answers to those questions.