We are using this product for enterprise development within our organization.
The primary use is for building Unified Endpoint Management (UEM) capabilities.
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.
My primary use case for this solution is for MDM. We use it to manage our devices and phones. We want to make sure that data is not stolen from the devices of our staff. Staff members often bring their own devices to work, and we need to manage that.
The aspects I find most valuable are the managing the data and applications. I can also restrict the users to install any applications. I can also wipe the data if the phone was misplaced or stolen. These are the basics for me.
I would like to be able to track the phone. I am not sure this is a feature that is readily available.
I find that this is a stable product and it is convenient for our business.
I have no issues with scalability because I have already used it for our organization and we have it for around 40 phones, and it seems to be suitable for our needs.
Until now, I have not really used the technical support.
I have previous experience with VMware Airwatch. But, I find that the integration is better with Microsoft Intune because we are already using Azure as a domain. It is a much easier integration with the Microsoft products.
I have no comment on pricing of the solution.
We have previous experience with VMware Airwatch.
I would advise other colleagues to use Microsoft Intune.
We have several different use cases. We have a BYOD (Bring Your Own Device) policy for corporate owned devices, and managing those devices is our responsibility.
It is a very helpful and easy solution. When deploying different configuration policies and compliance policies it is helpful. In addition, deployment of applications on devices is a valuable feature.
I think that there is room for improvement with the reporting. If this is done, it will be a better product.
I have not encountered any issues with stability of this product.
It is quite scalable. It is quite easily able to extend the capabilities of whatever you want to do. And, it is not always visible to the end customer.
I have used technical support in the past. When considering the seniority level of the tech support, I think they are quite good in comparison to other products. They are quick to respond to our needs.
We previously used VMware Airwatch.
The purchase of the product was handled by someone else in our company. I do not have experience with pricing of the product.
We received Intune with a bundle of Microsoft products.
We use this primarily for security on our devices. We use this product because it came with the bundle from Microsoft.
By using Microsoft Intune, I can control my Outlook on my phone. Whenever I try to open any file attatchment, it will be more secure. There are additional security precautions it provides with photos, as well.
The security features are valuable to us. We have a BYOD (Bring Your Own Device) policy at our organization. Many employees need help managing these devices. Microsoft Intune helps us manage MDM (Mobile Device Management). We find it provides MAM (Mobile Application Management) to a lesser degree.
The MAM feature could be improved. In addition, the security of photo sharing could be improved.
It is very scalable. Our organization has over 26,000 employees.
Microsoft Intune is a cost effective choice. It is less expensive than other products on the market.
We also looked at VMware AirWatch.
Our primary use case is using Microsoft Intune MAM, which is the mobile application management. We are using basically it for application management type needs.
We are using a model for productivity through Microsoft Intune. For example, we are using Microsoft Themes to share all our contents and we connect that with Skype. We also use the Microsoft PowerApps, to help developer apps on a mobile. All of these functions are managed by the Microsoft Intune.
One of the most valuable features is the overall UI. It's really easy to access, so user interface is very good. Secondly, the enrollment is a nice feature. It is easy to move into the Intune company portal with minimal steps to do so. In addition, the storage solutions are a nice feature that can be used together with other Microsoft products such as OneDrive and SharePoint. A nice sidebar feature of this is that you can actually restrict the people to mark or store data inside a device and you can bound them to store it in only a white drive and then you can an create an overall encryption around that. For other companies you need to use a container, but not with Microsoft.
I think that in the future Microsoft Intune should have an EMS (Enterprise Mobile Security) feature added.
Yes, there are a couple of issues with stability. The issues have to do with adoption. Also, organization has to change.
Our company has not quite reached a level where this is an issue.
Technical support is good. They have a free kind of support ecosystem, one is the premium support and one is the channel support. In both the ecosystems, the response is, good. Obviously, if you have the premium support, you get a response within a shorter amount of time. But I have found that even if you're doing the standard support also, you will get an immediate response. So, overall, the support is very good. For now there's no challenges coming from the technical support.
It is really easy to integrate and manage all Microsoft products with Microsoft Intune.
There is a cost benefit of using Microsoft Intune because of the packaging with other Microsoft products.
The primary use case is managing mobile devices and applications. It really answers the question of managing BYOD end-point devices.
The benefit is the way it integrates with the entire Microsoft ecosystem. If you're a company that has a bit of this, a bit of that, and a bit of everything else, then Intune probably doesn't hold up so well. But if you say, "We're going down the path of Microsoft's strategy, we believe in what Microsoft is doing as a cloud provider," then Intune, as far as security and managing end-point devices and managing everything, brings in the story quite nicely.
When a customer asks me about the most valuable features, one is that Intune itself integrates with that entire Microsoft ecosystem. As an individual product, it's okay. It holds up. But when you start saying "I've bought this as part of a wider solution, as a company we are going Microsoft throughout," then it makes more sense to have Microsoft Intune, because it plugs into Azure AD Premium, it plugs into Information Rights Management, it plugs into Windows Defender, so you have that single dashboard. It also has an integration with System Center which means again, from a single pane of glass, I can manage everything.
I believe they've just released a Mac OS support so that's great. And it has its own sandboxing.
I would like to see micro VPN. I like the way that some of the other providers have done something similar where, as you open that app on an end-point device, it creates a micro VPN straight into your device, which is quite a nice little feature.
Also, Microsoft Intune relies heavily on its fellow products in the suite. It would be nice if Microsoft Intune could stand on its own two feet.
The stability is better than it was. It's brilliant. It's a lot better than it was about three or four years ago. Four years ago, you wouldn't even have considered it as an MDM solution. Now, it's in the top-right quadrant.
The scalability is there. Microsoft has always said it's for SMB, public sector, and enterprise users. It needs to be there because, if you look at some of the bigger organizations using Office 365 and Microsoft 365, it's got the scalability.
My advice would hinge on what your strategy is. It comes down to: If you're using Citrix then Citrix ZenMobile makes more sense. But if you've got a Microsoft strategy and you're looking at Microsoft security and you're looking at buying into the Microsoft cloud strategy, then Windows Intune is a very viable solution.
For me, the most important criteria when selecting a vendor depend on what is it I'm trying to achieve. I always want to check:
For example, I may have a product that's brilliant and is amazing and does 120 things, but costs $10 per month; if I only need two of those features and I've got another product that has only those two features and it only costs $2 per month, I'd rather go for that.
I would rate Intune at about a nine out of 10 because it has come a long way, it is continuing to be developed, and I can see it as part of Microsoft's wider vision. It's not 100 percent there but it's getting there. The fact that you can now plug Intune into third-party products is fantastic.