Microsoft Intune Reviews

We are partners with Microsoft Intune as well as customers. 

The valuable feature of this solution is its ease of use. 

I find the solution quite old school with not many features. Managing devices is a little complex when they are not Microsoft projects. Additional features I'd like to see would include Wi-Fi and network security.

We use Microsoft Intune for application deployment and for some of their security policies and end-devices policies. We also use it for patching. Patches for Windows 10 devices and MacOs, we're still figuring out what to do because we don't have many options on Intune for Mac operating systems. Patching and looking for OS deployment as well. Operating system deployment.

Within our organization, there are roughly 150 users, using this solution.

We use Microsoft Intune on a daily basis. What Microsoft does, is it releases patches every month. The device hash reports to Microsoft Azure Intune. If you want it to receive patches or policies, which you have created on Intune and you have deployed, then the device will receive the policies and patches only if it's online and connected to the internet. Whenever the device is online and connected to the internet, it's connected to Intune. You don't have to worry about having an additional agent or anything on your devices.

Patching for Windows in operating systems is great. Most organizations are going remote now due to this pandemic, so patching is one of the most feasible solutions we can think of — patching end-user devices. Application deployment and keeping the devices secure no matter where they are, by having this cloud solution — that has been great. Deploying the security policies to the devices. 

There needs to be more support for Mac operating systems. Support for patching, because we have very few, or minimal options from Intune for patching Mac operating system.

In the next release, I would like to see better compatibility for Mac operating systems — that would be really helpful. Also, if the support for Mac was as flexible as it is for Windows, that would be really appreciated.

Personally, I have been using this solution for the past 13 months.

I haven't experienced any issues relating to stability.

We have spoken to the technical support on a few occasions. They have only ever provided us with minimal information. 

We used to use a SCCM or System Center Configuration Manager tool; it was also provided by Microsoft, but it's an off-prem tool. You need an on-prem setup and a server operating system and everything. On that server operating system, you can install this tool and start using it. We also used another tool called Automox, which was a patching tool. It's only meant for patching devices, different operating systems, Linux operating system, Windows, Mac operating system; however, it didn't have support for mobile devices.

The initial setup is a very simple process. You don't have to do anything on on-prem. Since it's a solution from Azure, it's a software service. You just have to buy the subscription. You just need to have the license in place and then you can just start using it. There is not much setup involved. If you want to integrate your Azure solution with your on-prem solutions, then you have to do a bit of integration.

If you're going with standalone Intune, you don't have to think of setting up anything. You can just use it, pay for whatever your problems are, find a solution for that, and start using it — that's all. You don't have to worry about the setup for standalone Intune.

All maintenance is handled by the vendor.

Licensing depends on how you are providing support to your enterprise, whether it's device-based or user-based. If you're providing device-based support, you need to buy a device pertaining license. If you're providing support for users, then you have to go with user licenses. If are integrating Intune with FSCM, which is an on-prem tool, then the same scenario comes in either devices or users.

If you are providing support only for devices, like device-based policies, with Intune, there's a type of policy that allows you to deploy to either the devices or users. If you're looking for a solution where only devices can receive it, rather than users, in that case, you need to purchase only one license for Intune — I'm talking about integrating Intune with FSCM. You only need to purchase one license. Since you have already purchased FSCM on-prem, Microsoft has that flexibility; you can extend those licenses with the devices as well when you're integrating the devices with Intune. I don't know about the pricing, but I know about the licenses.

I would absolutely recommend Microsoft Intune. Currently, I would definitely recommend any cloud solution. Most organizations were actually using on-prem solutions for managing their enterprise devices. Now, since everything is remote, people are confused. How can they manage their devices the same as they were before this pandemic? If they find Intune very pricey, they can go with another cloud solution. Intune it's very user-friendly. You just have a screen and console and you can just go in and start deploying anything. All you need are the user guides, which are fully-available with Intune.

Intune is a very good cloud solution for managing devices. They could actually make it better by putting everything together, in one place, like other MDM solutions are doing. If you compare Intune with VMware, VMware also has an MDM solution called AirWatch. Intune should compare itself with other MDM solutions and try to bring up those features as well. For right now, I would just say it's a very good solution for managing remote devices.

On a scale from one to ten, I would give this solution a rating of six.

The use case for this solution varies depending on the user's requirement. Some are only interested in MDM, while others are interested in managing Windows plus Mac. It really depends. We are partners and provide on-prem, cloud and hybrid services to our customers. I'm tech lead infrastructure operations. 

Lately I've been working on the Remote Wipe and Autopilot. Autopilot is one of the best features because we can use it during remote migration. It especially helps in this pandemic situation where we don't need any end-user computing engineer support. If someone wants to remix a machine, we can initiate it remotely.

An improvement would be if we were able to leverage more iOS device management internally. My goal is to manage all the tools in one centralized tool. Intune does 30 percent of Mac management, but if it could have complete management including patching and automating for Mac devices, that would be good.

I've been using this solution for three years. 

This is a stable solution. 

This is a scalable solution. 

I have been trying to contact technical support but haven't been able to reach anyone. I have a couple of questions to which I haven't been able to get any answers. 

The initial setup is pretty straightforward.

The cost is fair but it would be helpful if they would segregate the licenses. There are a lot of features that many of our customers don't need but have to pay for because it comes as a bundle package and we're unable to exclude anything that is not necessary.  

I also work with Jamf Pro but you can't compare the two because Jamf Pro doesn't have real-time features and it doesn't do most of the things that Intune does. 

If a customer is looking for a macOS solution, I would for sure recommend Jamf Pro. If it is for Windows and macOS in a combined environment, then I would recommend Intune for managing it. The consideration is based on the customer's macOS family, based on how many users they have. If they have 100 users, then we can still manage it through Intune. If it's a complex environment, for sure we'd need Jamf Pro.

I would rate this solution an eight out of 10. 

We are a consulting agency and we help people make technology and business decisions. 

Our environment is fully online and we're a Microsoft 365 shop. We are using Intune for security. It is their MDM for mobile devices, but it is also their application ADM and it works on desktops as well.

We primarily use it to maintain compliance for our customers. They require that we use it to enforce compliance with the same level that they do internally, so we're following the compliance guidelines of several Fortune 100 companies. Intune is what we use to meet those requirements.

Using this product has completely stopped DLP, so people cannot take material off of corporate machines or corporate imagines, and that's a huge benefit.

The biggest thing for us is enforcing logins only from devices that are managed by Intune.

We also use it for enforcing DLP and all of the other security policies that you need for compliance in order to do work for major corporations.

It integrates well with the Microsoft environment. Once it's deployed, it's set and forget.

Once it's configured it is unobtrusive, but it does take some hands-on to configure and deploy it properly.

I have been using Intune for a year.

Intune has been very stable.

We're a small company of fewer than 100 people and it scales well enough for us.

We are financial analysts and IT consultants.

I have not used the technical support personally, but it seems to be okay.

We used a third-party package before, and we moved to Intune because it was easier to integrate with Microsoft Windows or Microsoft 365. It also provides coverage for desktops.

The initial setup requires user participation. You can't push it without the client being engaged. That is part of the configuration.

Overall, this product works pretty well. Security products are the disgusting medicine that we don't like to take, but we have to take it to stay healthy.

This is a good product because it's transparent and works well, although it's unfortunate that we have to have it.

I would rate this solution a seven out of ten.

I am using Intune to manage both mobile devices and PC devices. I deploy applications and manage the security landscape.

The most valuable feature for us is the security, including risk analysis and patch management. The management is very important for us.

The configuration could be better by consolidating options and making it simpler. I would like to have one option in one place that corresponds to one feature, which I can check off and move onto the next one. As it is now, there are a lot of options. For example, when configuring security, I find that it is too much because you have to configure one task in one place, then switch and it is against in another place, and so forth.

In the future, I would like to see support for security and compliance management. I would also like to see iOS management options.

I have been using Microsoft Intune for five years.

This is a stable product.

Being a cloud-based solution, it is very easy to scale.

We have approximately 30,000 users.

I have contacted the Microsoft technical support lots of times. It is okay and I am satisfied with it.

We did not use a different solution for the same purpose before implementing Intune.

The initial setup was simple and it took us about two days to deploy it.

Intune only supports mobile devices in the cloud version. Because a number of my clients have both PCs and mobile devices, I deployed it in a hybrid model.

I am responsible for configuration and deployment, and sometimes maintenance. Our help desk also handles the maintenance.

The price of Intune is often included as part of a bundle with other Microsoft licenses, which makes it somewhat cheaper.

Microsoft Intune is cost-effective and easy to use, so I can recommend it. That said, it is not perfect, so I think that they can improve a lot of things.

I would rate this solution a seven out of ten.

We are using this product for enterprise development within our organization.

The primary use is for building Unified Endpoint Management (UEM) capabilities.

The most valuable feature is the UEM capabilities.

The user interface should be improved because it is a little bit slow.

It does not have support for containerization.

There is no catalog for mobile access management (MAM) security.

I have been working with Microsoft Intune for more than six or seven years.

Because we are doing a PoC, there have been no issues with scalability as of now.

We started with a user base of 5,000 and are aiming to have 30,000.

Because we are still in the PoC, we are only testing it with a few users.

We have not been in touch with Microsoft technical support.

The configuration is straightforward and there is nothing complex about it.

Intune is a good product for UEM, which is helpful for Windows 10 management. However, for MAM, there is lots of improvement needed. For example, the application catalog should be there.

I would rate this solution a six out of ten.

We are using Microsoft Intune to control, manage, and to protect the data on mobile devices.

The most valuable feature is the scalability.

There are differences in protecting the data on a mobile device and on iOS. When you protect the data on iOS, you protect the entire device.

From an Android, you can select certain applications to protect. What this means is that the employee who uses Android devices are protected only from emails, and the personal data on the device is not protected. When the employee uses the iOS they control all of the devices, which is not convenient.

There are items that require improvements. One is the controls from iOS.

I have been working with Microsoft Intune for approximately four years.

We have not experienced any bugs or glitches with this solution.

We have not had any issues with the scalability. We have more than 1,000 users.

We have contacted technical support several times.

Technical support is sometimes okay.

The initial setup is a bit difficult.

It took almost a month to deploy. There were several requirements to set up the conditions.

I would recommend Microsoft Intune.

I would rate this solution an eight out of ten.

Our primary use case for this solution is to implement conditional access policies to restrict mobile users from accessing emails until their devices comply.

Intune should be much more granular in terms of supporting more devices. It is mainly only supported for Samsung knox devices. If you want to restrict the user, and not to turn on the camera and such, most of the policies that I found were more supported only towards Samsung knox devices. But, some policies are supported for Android 4.0 operating systems. Most of these policies are only for Samsung knox. I wish there was more diversity regarding other Android devices. In our country, there are multiple vendors, such as: Samsung, Huawei and more. I would prefer other solutions if I'm implementing restricting the devices in terms of applying the policies.

It has many features, but the most prominent is that other mobile device solutions support more polices. Much more diversion is needed in implementing the policies in different kinds of devices. As I have worked, it has not supported too many policies for android devices. Every 3rd or 4th policy that was supported is for Samsung knox devices. So, most people prefer to use Intune if they want to implement conditional access policies to restrict customer exchange online or exchange user formats emails until their devices comply.

You can publish Apps on the devices and take inventory of the devices, but it's all about the companies who were interested due to implementing conditional access policies to restrict  users. They want to restrict the users in order to access emails until their device is secure and then comply with the security policies of the organization.

Most of the customers expect that most of the policies will be there for Android, to implement the policies. Unfortunately, most of the policies that I found are for Samsung knox devices, that is specific to a device or specific to a vendor. That's why most of the customers have a hard time with Intunes, because most of the policies they see is for Samsung knox. They want Intunes to support Android devices. If it is supported by other Android devices, then it's very complicated because if you want it implemented, you have to use some custom equipment. There are a very limited number of policies that are applied, and all generate other devices like Samsung knox devices.

Most of the customers in the business do not use Intune because it doesn't support that much policy for Android. Here in Pakistan, most of the end users are using Android devices. Windows is out of the question. They don't use Microsoft mobile phones. Most of the popular devices are iOS, and the ultimate users are Androids. I think 80% of the users are using Android devices here and less than 20% are using iOS devices.

So, the customer is expecting to apply policy on Android devices and it's not generated specific to a vendor like Samsung knox, so they don't buy it, and they don't consider it.

Yes, it is a stable solution. There were a few stability issues, but most of us are happy with the stability of the solution.

I do not think scalability is an issue.

It was not easy, but not too complex. If an engineer knows what he or she is doing, then it is not difficult.

The product is offered as part of a Microsoft standard bundle. The pricing can be competitive to VMware Airwatch, and IBM MaaS360.

We considered VMware Airwatch and IBM MaaS360. 

From my experience if the requirement is to lock down the Android devices through Intune, then I should advise to look at the different policies that are available for Intune before doing the implementation. Because, if the policies do not meet the requirements of the organization to lock down the devices or to apply the policies on the devices, then it does not make any sense. So, for Android devices in particular, if you are implementing Intune then you should first look at the policies that are available in Intunes and then try to evaluate and do proof of concept.