Microsoft Intune Reviews

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.

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.

The solution is primarily used to manage iOS, Android, and also Windows 10 or Windows 11. It's to manage end-user devices.

The best thing about Intune for the customers is simply that it's included in the different plans of Microsoft 365. If a customer needs Office or collaboration tools, Intune is included. It's for free. If the company has another MDM, normally they are paying for it. This product is included in the license of Microsoft 365. We find that the customers, in general, want to change the solution, to move from another classical MDM to Intune due to the fact that they save money.

If you need only to load a specific profile and you don't have deep security functionalities, etc, Intune is very nice and good.

The initial setup is very simple.

If you need some restrictions or some integrations or you need integrations with security options, or if your mobile terminals are industry-special or ruggerized, bar code readers, printers attached, this might not be the best option. If your MDM has to be really specific, perhaps Intune is not the better option. You have to consider MobileIron or Workspace ONE or MaaS360 or similar.

They need to integrate more with security options. When the customers want some specific security functionality they begin to think about other platforms. 

The stability is very good. There are no bugs or glitches. It doesn't crash or freeze. It's pretty reliable. 

Scaling is simple. It depends on the licensing. If you have licenses for that, the only thing you have to do is to continue with the enrollment of the terminals. It's very easy. You have to assign the terminals to a group of users with different restrictions or policies and that's it.

With the CSP licenses, we as a cloud service provider, are obliged to provide services. With our service, we provide support to the licenses. When we sell licenses differently, in the LSP scheme, then we have to sell the premium service for the customers.

I don't use it directly. That said, I know the ratings of the services that we provide for our services. The only thing that I should say is that normally when we have an SLA with a customer for Microsoft, there is a specific response time that we can provide as a service provider. They do not consider that. They say, "Our service is this. This is our SLA." Then, our service level agreement is eight hours. 

Sometimes, when you offer a service level agreement with a customer, the support of the manufacturer or of the vendor is included. It's the only thing that, if you are providing services on an end-to-end basis, you have to consider. Sometimes, when you call Premier Support and you say, "Please, I need a solution before six hours," it doesn't matter for them. They say, "I have not six. I have eight, so don't call me if I'm in the eight hours."

It's very simple to set up. To set up the terminals, it's very easy. You have a manual, and it's very easy to follow. You can configure functionalities for specific users or a specific group of users or things like that. It's great.

The time it takes to deploy depends on the number of terminals and it also depends on the number of different groups. Perhaps you have to configure the different policies for different groups. That might take longer than a straightforward setup. In an installation with, for example, 1,000 terminals, it typically takes less than a month -three weeks or so.

I don't personally handle the deployment myself, however. I offer it to clients. I'm not the one to actually do the manual work of implementing it. 

The amount of people we need to deploy a solution depends on the number of terminals that we have to manage.

Some customers configure everything at the beginning and nothing changes over time. That said, we have other customers that they are continuously asking for changes. This group of customers will likely need three people more to handle maintenance. For every 1,000 devices, you typically need one and a half full-time employees.

In terms of ROI, it depends. If you have licenses included in your plan for M365, Microsoft 365, from the very beginning, if you have to sell that, it depends on the business case that you can do. It's different if you buy a CSP or LSP license.

One kind is considered as a cost and another is considered as an investment. The LSP is an investment. 

In the products and services space, from a pay-per-use perspective, I don't see a relationship between this product and ROI. 

There are different kinds of licenses. We sell two licenses from Microsoft, the LSP or the CSP. The service that we have with Microsoft is based on the CSP kind, so the payment is monthly, considered as an expense, not an investment o asset. It depends on if you buy a set of licenses only for Intune - which can be sold separately, or can be included in M365.

We are gold partners with Microsoft.

I would rate the solution at a nine out of ten.

For simple installations, for simple management, perhaps Intune is fine. However, for more complex installations, it might not be enough.

We are primarily using the solution for managing the devices. Some employees are using their own devices and some employees are using company-owned devices. Basically, we use it to control company data and personal data, we are keeping them separate and we are managing those devices such as Windows computers, Mac and mobile phones, iOS, Android, et cetera, via Intune.

The product is very useful in terms of Windows Information Protection. Our employees, if they try to leak data will not be able to as the data is encrypted. Intune keeps our data encrypted. If you send me an email, that email is stored on my personal OneDrive. I cannot store that email in my WhatsApp, for example. I cannot store my data anywhere else. The data protection on offer, therefore, is great. 

The initial setup is very easy.

We can use the solution with the Active Directory, which has many policies. We can restrict and protect devices accordingly. 

The solution can scale.

The stability is great.

The cost of the solution is great and was recently lowered to make it even more affordable. 

Intune has a lot of great features and we have yet to utilize 100% of their offering. 

Day-by-day Intune is improving. It has a roadmap for how it will continue to improve over time. 

They need to improve their technical support and make sure Intune is covered under their SLAs.

Our company is very new. We've only been around for about seven months. In that time, we've used Microsoft Intune. It's been less than a year. 

The solution has been stable so far. There are no bugs or glitches. It doesn't crash or freeze. It's reliable. 

The solution can scale as needed. We are satisfied with its scalability capabilities. 

Technical support is not that great. The basic support comes with a Microsoft subscription, however. Intune support from my experiences, the basic support they have, does not have any SLA.

They're working on it only during their business hours and our country is in a different time zone and has different business hours. Our country office's start time is 9:00, however, the business is coming from China. China begins at 7:00. We're getting six hours, maybe, of time where we can get support if we need it - and the basic support on offer is not good.

The initial setup is not overly complex or difficult.

The initial setup was very easy as Microsoft has a setup guide similar to what you would expect if you set up 365. If I'm following the set-up guide, it's very simple. You just click along. 

Previously the price was $4 per month per user. Now it's $2.25 per user per month. The cost is really affordable.

I'd rate the solution at a nine out of ten.

We primarily use the solution for device management. 

There are a lot of use cases, however, the base is the mobile security for our corporate devices and deployment of applications. We are a worldwide organization and in many countries. There are also country-based use cases, or areas that incorporate these use cases for some specific business units such as healthcare and similar SAP solutions. We have a lot of small areas where we use this, however, the main driver is improving the security of the devices and providing some automation configuration for the users including VPN solutions and corporate WiFi connections, applications, et cetera.

If I compared this product to XenMobile, except the conditional access, which was also partially possible to integrate with Citrix XenMobile, then there is not much difference between the two. The functionality s very good. However, the main way this has improved our organization is that there is support for conditional access and native integration with Office 365 services which we migrated to. 

The integration with conditional access is great. That's maybe the most important aspect of the solution.

The pricing is very good.

We already use a lot of Microsoft products in our company, and therefore, it made sense to also use this product.

For the most part, the solution is stable.

As a cloud solution, the scalability on offer is great.

There are a lot of small use cases where we realized that some technical solution was missing in Microsoft in comparison to other products. For example, it lacks something similar to sensing or location-based rules and configurations.

We would like, for example, integrated remote control or a remote session tool or something like this. You must have TeamViewer and the integration with this is limited and it's extra money. Nothing is built-in. Some functionalities are really limited to fully managed devices and so on. It took a long time for them to integrate the big ECS infrastructure into the corporate devices. This is now done, however, it took a longer time than expected.

Technical support could be h=better.

We've used the solution for the last three years, starting with the integration. 

The solution is pretty stable. As it is in the cloud, there are not many issues in terms of a service outage or things like this. Maybe when there are new patches integrated every month, which sometimes happens, some functionality may be influenced or affected. It's more or less a small issue, however, issues are possible. I don't recall a situation where downtime happened or users were really affected, however. It's just an occasional issue we may have with a patch that we would need to address.

The solution is quite scalable. As a cloud product, there are no issues surrounding expanding if you need to. 

We have maybe 27,000 people using the solution at this time. There is a plan to have all mobile users in this solution, so we are talking about 70,000 users at some point. However, it's a question also of the licenses, as you have to have a license for that product.

Technical support is hit and miss. Sometimes it's really good and other times it's not so great.

We used Citrix Endpoint Management in the past. We used it about two years ago. It was a good product. They are comparable, really, Citrix and Microsoft. 

I was not involved from the beginning of the project. However, from what I remember, we did the implementation directly with the help of a support engineer from Microsoft. Their involvement ensured the setup was not such a big deal.

Deployment took maybe one year in our environment, however, this was because we had a lot of time to tune it up and to test it, to have a pilot for a few months and then add more people to the pilot before we started migrations for mobile, for example. We took our time to really prepare the product as best as possible and then deployed it to the users and migrated them over.

We have two levels of people at a global level that handle deployment and maintenance. They mostly focus on improving the environment, not troubleshooting WiFi issues. 

We had direct assistance from Microsoft. Their assistance made the process seamless and it was a positive experience.

The solution offers reasonable pricing.

It's my understanding that we have the licensing set up for monthly payments, however, it's not an aspect of the solution I'm directly involved with. I don't know enough about it.

That said, I am aware that, in order to have mobile involved, you need the EMS solution or EMS license, and that's an extra cost to the standard Office license.

We're just a customer and an end-user.

As we are on the cloud version of the solution, we are more or less on the latest version of the solution.

The product was chosen for political reasons, as the company is mostly using Microsoft products and also the prices were maybe better than other options. 

I'd recommend the solution to others. If they are already using Microsoft or 365, it's a good product for companies sot have. 

I'd rate the solution at an eight out of ten.