Microsoft Intune Reviews

We primarily use Microsoft Intune for device management and application management. It allows us to control and restrict user access, preventing data sharing and leakage. 

Additionally, we utilize it for endpoint management of Windows and Mac devices, ensuring their security and compliance.

The benefits include that it's very easy to deploy and integrate. Users actually feel satisfied and have a great experience with it.

The most valuable includes managing everything from a single console.

Integration with Mac devices requires some improvement.

I have been working with Microsoft Intune for eight years. I currently use the latest version.

It is a stable solution. I would rate the stability a nine out of ten. Sometimes we get some alerts from Microsoft Intune, but our team is responsible for managing that internally.

It is a scalable solution. Around 3,000 endpoints are being utilized in our organization. 

 Customer service and support are good.

Positive

We used VMware AirWatch. We switched because of the ease of use that we get from Intune. It's much simpler to work with.

The initial setup was very easy, not at all complex.

We have our own team that handles the deployment. Three to four people were included in the process. 

The deployment process was simple. We just enrolled devices and created the necessary policies, and that's it. It took approximately twenty to forty minutes, depending upon the use case.

Moreover, it is easy to create policies with Intune. It's not difficult at all to maintain. We have the same team taking care of the maintenance.

Just go with it. It's very simple to use. Overall, I would rate the solution a nine out of ten. 

Our use case is relatively typical; we primarily use the product for managing Windows laptops, pushing policies, and some configurations. 

The ability to send configurations to our systems is valuable, particularly as we don't have a regular Windows AD server. Our current environment doesn't have a Windows AD, which limits our ability to push GPOs. However, this is where the solution can step in and help us push policies.

The reporting could be improved, as it's pretty poor compared to other products of this type. 

Patching needs improvement, as it hasn't been working well recently. 

We've been using the solution for over two years. 

The solution is very stable. 

The scalability is there, and it's automatically based on the number of users in the back end, so we don't even need to think about it.

The tech support is excellent, and I give them a nine out of ten.

Positive

At my old organization, we used Microsoft System Center Configuration Manager (SCCM), which is more of an on-prem system. Microsoft seems to have recognized that everyone is moving to the cloud, and I expect they will bring SCCM's capabilities onto Intune as a kind of product upgrade.

SCCM is a more versatile tool than Intune; we can't patch third-party applications in the latter, which is a significant headache.

The deployment was pretty straightforward; the solution came in a prebuilt configuration, and we just needed to enable it in our Azure domain.

As the product is cloud-based, we don't have to do any maintenance as a customer. 

Intune is available as an individual product, but it also comes with Office 365 Premium or an Enterprise license, and the price varies for each version. 

I rate the solution eight out of ten. 

Those considering the solution should look into it because it may already be part of your license or available with a small upgrade. Once upgraded, you have a tool and don't need to bring in another one. The deployment is simple, there is no other third party and no agents to be deployed. You also have a dedicated console that provides visibility and management, which is very easy to handle.

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.

It's usually used for managing mobile devices, such as Android and iOS, for application deployment, for securing the device landscape, and for making sure all devices are compliant.

Help Desk engineers don't need to spend a lot of time enrolling new devices. In the past, you had to do that by using a complete infrastructure on-premise, or if you wanted to do it by hand, you had to go through every device. You had to install Windows, configure it to set security, etc. Intune does that automatically for you. It saves a lot of time.

There are so many features, but Windows Autopilot is one of the features that are very valuable for most customers. Personally, I like most of the aspects of Intune. I've been working with it for about 10 years. I'm a Microsoft MPP for the Modern Workplace. I like a lot of features. There's no one particular part of Intune that is the best for me. It has developed into a very mature product. About 10 years ago, it wasn't a very good product, but now, Intune is a very good mobile device management platform.

There should be more support for macOS. Even though macOS is supported by Intune and Microsoft is working very hard to get more features into Intune to manage macOS, that's one thing they can give a lot more attention to.

I've been using Microsoft Intune for about 10 years.

It's stable. There are issues once in a while, but they are not worth mentioning.

It's very scalable. It's deployed across multiple endpoints. My customers vary, but there are between 50 and 15,000 endpoints.

I do have experience with Microsoft technical support, and I'm happy with it. I'd rate their support an eight out of ten.

Positive

I've migrated from other platforms to Microsoft Intune, but I've not used any other similar solution.

It's a cloud solution. The cloud depends on the customer, but Microsoft Intune is a cloud solution serviced by Microsoft. My customers have various cloud environments. It could be a hybrid, public cloud, or private cloud. It depends on the customer.

It's quite straightforward to deploy it, but configuring it and doing it right is something else. The deployment duration varies. Some customers have 100 devices and others have 10,000. It depends on the landscape of a customer. Even though nothing changes technically, it's more difficult to move large enterprise organizations to a mobile device management platform.

The number of people required depends on the qualifications of the person who is deploying Intune. Intune can be deployed by one person. 

Its maintenance depends on the company. If you have a very big landscape with tens of thousands of devices, you want to have more engineers monitoring Intune and configuring. If it's a smaller environment, you can manage it with one or two people.

The ROI has been in terms of time savings.

It's affordable. In comparison to the competitors, the price depends on what features you need from Intune, but it's affordable. There are no hidden costs, but there are some features that go for a premium price. Those are the add-ons for which you have to pay extra.

I did have a look at other options, but I'm a Microsoft specialist, so it's a Microsoft-first sort of policy. If Microsoft can do it, I'll do it with a Microsoft product.

Get yourself well-informed. Talk to a specialist who can help you out with deploying Microsoft Intune.

I'd rate Microsoft Intune an eight 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.

Our main use cases with Microsoft Intune are about how we automate the deployment. Auto-pilot is a feature that we normally recommend. Another piece is about the package deployment, where we recommend, or have helped, customers in deploying and converting their Win32 application. These are the two main areas in terms of automating the enrollment and Win32. Another use case in terms of the Apple, which is being used more by the customers, is where we recommend them to go for the zero touch process by using the AD.

Intune's feature that I have found most valuable is its auto-pilot feature. The main thing is that it keeps building it. Also Intune's capability in terms of Mac, which is slowly increasing, although the customers are moving towards vMOX and leaving the Intune just because of its limited capability with Mac, though it has already been enhanced. More features include the conditional access and the app production policies with respect to BYOR devices. These have been increased a lot in terms of security.

In terms of what can be improved, I am looking for better enhancements regarding Apple management, not only on the mobile device, but also on the laptop.

Other than that, it already has good capability with Windows, and it is already very good for the mobile device. The only area that is missing is for the Mac products.

I am using Microsoft Intune for the last two, three years.

In terms of maintenance, since it is a cloud product, it automatically gets updated by Microsoft. So there is no maintenance required for the upgrade part. But definitely the maintenance part that we track is the software asset management - that the devices are there and that the patches are deployed on a timely basis. We also do maintenance on the dashboard reporting feature in terms of whether the devices are compliant or not compliant.

In terms of performance, devices will be automatically enrolled and all the applications will be deployed. So it will be ready to use once they log in with their Azure-ready credentials. That is zero touch for them. In terms of having integrations in place with other tools, any issues they face will have proactive or automated actions to resolve their issues, instead of raising them and going through the long process of raising a ticket and the resolution.

Scalability is good.

In my experience, the customers who are mostly going for the Intune are small, medium and large companies. We have seen a mix. These days we have seen a large base of customers having more than one device. So it could be suitable for any size company.

Not too much to say on support. It is pretty fast. But in some of the instances we did not get much or a proper resolution where we had to troubleshoot a lot. But in most of the cases, support was good.

Initial setup is a simple process. It is a cloud solution. It is easy to deploy and easy to integrate with other tools as well. If we have to integrate with on-prem or Azure-ready through an AD connector, it is easy. Also, it is capable of integrating with other tools.

In terms of deployment, having things in the VM or physical VM or physical system in place and the ports enabled, as the main infrastructure is all in the cloud, is only part of connecting with the Azure already and the AD connectors, and does not take much time. With full testing, it takes one day if all things are in place.

Their price is really good. That is the reason customers move here, because as part of the Office 365 package, they always get the E365 as well, which makes it easy for them to manage their devices without having additional licenses for Intune.

That is the best part.

The main differences between Intune and other products are, like I mentioned, in terms of the Mac. If the customers are majorly moving and adopting Mac laptops while they are using the Intune, they are leaving for other platforms, like Workspace ONE and vMOX. That is the reason for moving and the major difference I have seen these last couple of months. But at the same time, if there is not much dependency on Mac devices, they are moving from other platforms to Intune, also.

My advice to anyone considering Intune would be to definitely test it and have devices enrolled at least in a pilot phase. They will get feature compatibility, the policies, and the auto-pilot feature. So, I would recommend to do at least a POC, and then decide.

On a scale of one to ten, I can rate Intune an eight.

We use it for the rollout of Windows and Apple devices to our users.

Its direct integration with all the other products that we have from Microsoft is valuable. We're using the E5 license, and we have a whole wealth of different products available. It just makes it easier to have everything from one provider. 

One big problem with Microsoft is that they're changing the names of the products quite often, or they're quite consistently doing so. Intune is now Endpoint administration. Constantly switching the user interface or the administrative interface makes it quite hard to keep pace. If you are on a two-week holiday and you come back and look at the same screen you have looked at for the last couple of months, it looks different, which is annoying. Changing things around all the time doesn't make it easy.

There are some elements where the integration isn't finalized. So, for some of the things, you use the user interface, meaning the administrative website, and for some of the things, you have to use PowerShell to make changes, and it's not quite clear why you have to do things at one point this way and at the other point that way. If they could improve that a little bit more, it would be a good thing.

Other than that, functionality-wise, it, more or less, serves our purpose. I'm not really sure what I would wish more at the moment.

I have been using this solution for over a year.

It is stable 99% of the time. There are some problems with Microsoft in terms of outages, but overall, the solution is very stable.

It is very easy to scale. It is basically adding additional licenses. It requires adding additional domain names and things like that and maybe adjusting a couple of security groups, but other than that, it's really easy to scale up or down.

We have only 120 users in 44 companies. A few of them have financial, accounting, or legal backgrounds. We are not an engineering company; we are a service company. We are a shared service center catering to the needs of more than 44 other companies. That's our business. We are a managed service provider to all these companies.

Its documentation is quite okay, and if not, if you Google things, you would find almost everything. 

We had four, five issues over the last year, and we had to contact them. They were actually quite swift at solving problems. So, overall, we are happy.

It was easier than expected. We did the full deployment for 44 companies and about 120 users in about three months.

ROI is very high at the end. We were using a full data center before with three racks built up with about 30 host systems and 220 virtual servers that we operate in, and by just switching to Microsoft 365, we could get rid of all of them. It made our life easier in terms of support and maintenance. We have saved the costs for all the hardware that we had and all the hassle that we had when parts were broken.

If you ask the accountant or the finance department, they'll tell you that it is way too expensive, but when I look at the cost and compare it with the value you actually get, it's more than fair.

We looked at the Sophos solution as well. We are a Sophos partner, but it was easier to deal directly with the Microsoft solution primarily because of the rules management and the Microsoft groups and the security groups that we use. We use rule-based access, and we have access packages so that users can elevate their rights with an approval process in the back.

I would rate it an eight out of 10.

We are using it to protect our devices. We are using it for protecting our corporate data on the phone and for GDPR compliance. 

We are using its latest version.

It is helpful for protecting our corporate data on the phone. In the event a phone is stolen, we can remotely wipe the phone or destroy the data on it.

It also helps us with our GDPR compliance. We also have the GDPR module on the cloud that links to all the endpoints, laptops, mobile phones, and tablets. So, we can also remotely protect the data on the phones, wherever they are.

Intune makes it possible for us to reach all the endpoints and have them protected at all times. We have what is called Defender now, but it used to be called Advanced Threat Protection.

The ability to manage devices with different sets of policies is most valuable.

We haven't really gone through all the features of Intune. We are just discovering them. Every day, we see a new feature that we want to apply, but what will be great for Intune is to be able to deploy apps in a simple fashion. We should be able to easily install various apps on the Windows platform, iOS, and Android. Currently, we have to write some scripts. It's not as straightforward as we would like it to be. It should be simplified so that we can do it just with three clicks—next, next, finish—without needing to write a script.

I have been using this solution for about six years.

So far, it has been good because what we tend to do is get high-end phones with lots of processing power, RAM, and storage. That way, its capacity is never an issue.

It is scalable. It is a multi-user license, and because there are templates for policies, it's easy to just assign what you have set up for executives, for ordinary users, for marketers, etc.

We have about 150 users who use this solution. I work with this on a daily basis.

I would rate them a 10 out of 10 because they knew what the problem was, and they walked us through resolving it. I am satisfied with their support.

Positive

The first one we used was VMware AirWatch. The reseller overestimated our requirements, and we got a very expensive package. It was about $57,000 every year, and eventually, we found out they had a package for $6,000 every year that did exactly what we wanted, so we had to drop it. We had spent two years on VMware AirWatch with the expensive module.

We switched to Intune because we were already on a Microsoft subscription for Office 365, and the add-on wasn't that expensive.

It was simple. I would rate it a four out of five in terms of the setup. It took about a week.

It is a cloud product. It doesn't require any maintenance from our side. We get an update every time they upgrade a feature.

We did it internally. We just went through the documentation.

It's affordable for the protection it gives. There are no additional costs.

I would advise getting a Microsoft partner to deploy it for you. It's a lot quicker. 

I would definitely recommend this product. I would rate it a 10 out of 10.