Microsoft Intune Reviews

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.

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.

Serverless Win10 with App deployment, Azure Active Directory and remote support. Can now co-manage devices with both Intune and Configuration Manager!

The ability to (somewhat) manage full Windows 10 computers including EXE-based or MSI-based application deployments using Azure Active Directory as Identity.

And NOW (last quarter 2017), the ability to co-manage computers with BOTH InTune and System Centre Configuration Manager allows complex application delivery and ConfigMgr reporting etc to add more value.

For our customer, it meant no on-premise systems configuration infrastructure or identity management services were required.

Logs and similar deployment/remediation detail for application delivery to Windows 10 computers should to be improved

Additional application deployment options e.g. MSI deployment with more complex parameters or additional side-by-side files, and non-MSI deployment options.

Unsure. Some application deployments to Windows 10 computers would not start for a long period, with no recourse but to wait and see.

Not relevant in our situation.

It wasn’t necessary to escalate an any point.

We didn’t have a previous tool. The solution was required to extract a company from another as part of a demerger. The new entity was our customer.

Application delivery to Windows 10 was straightforward for someone with prior System Centre Configuration Manager and application deployment skill sets.

We are the vendor. Intune expertise was low at the start of the engagement, but we now have a fully developed Modern Management (Intune) practice.

Not calculated

Consider the Microsoft Enterprise Mobility Suite rather than choosing specific sub-components, e.g. only Microsoft Intune.

We didn’t examine other tools.

Allow sufficient time to pilot and test.

With the ability to now co-manage computers with BOTH InTune and System Centre Configuration Manager, you can pilot-test Intune without compromising on your proven systems management using ConfigMgr.

We use it for mobile device management. 

Intune is on a public cloud because it works on Office 365.

It provides control over all mobile devices that are being connected to the corporate network.

Data leak prevention can be integrated into it. Currently, it does not have data leak prevention.

We have been dealing with Microsoft for the past three decades, and we have been using Intune from the time it came to the market.

It is stable.

It is absolutely scalable. It is for enterprises.

It is world-class. It is the best.

Its setup is easy. It is a Microsoft solution, and everything is easy with Microsoft.

Its price is in the medium range. It is acceptable because you're paying for the features. I am not aware of any additional costs.

It is a wonderful product. I would advise others to go for it. It is definitely helpful for an enterprise. It has been improving constantly. When they introduced it, it was only for Microsoft, and now, even Apple has been included. They're doing well.

I would rate it a nine out of 10.

Being able to use it to control phones is the most valuable feature. 

It's a developing product, so there's lots of room for improvement. There's a lot of stuff we couldn't do because Google and Apple prevent you from doing a lot of the stuff you'd like to do. 

Microsoft documentation is a bit hard to get around, so having more control over devices would be good.

I've been using Intune for about a year or so.

We had no problems with stability.

It's hard to find the information to work out what you need to configure, but it's easy once you get to know how to work it.

The pricing is pretty good.

I would rate it an eight out of ten.

We use it for the inventory of phones and deployment of Office 365. It is used for conditional access.

We can better avoid information leaks.

Conditional access: This feature helps me control uncontrolled access.

It needs incorporation of Knox, ZeroTouch, etc.

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.

We use it for the following:

• MDM
• EMM
• Cloud app protection. 
  

It has improve our organization through the remote management of non-domain joined devices.

It needs certificate provisioning for S/MIME purposes.