Microsoft Intune Reviews

We switched to Office 365 applications and we already had an Office 365 license that covers Microsoft Intune. We decided to use Intune for our Mobile Application Management solution.

I only use Microsoft Intune for Mobile Application Management for the management of Office 365 apps. Additionally, we have Microsoft Intune integrated with Workspace ONE.

We have used conditional access policies to prevent users from copying internal resources or internal data to external devices. This has helped protect our organizations from being compromised.

The conditional access policies that we set up are very useful.

Microsoft Intune could improve by being more user-friendly and having it geared toward device management. The graphic interface is not very good.

The VPN option within Intune is not as intuitive as the one available in Workspace ONE. We're trying to implement a VPN tunnel for SharePoint sites. This will allow users trying to access internal resources, such as SharePoint, and other Office 365 data, but it doesn't work as well as Workspace ONE. 

We are in the POC stage of the VPN tunnel. We only have a development tenant for the tunnel. We plan is to implement that in production and get rid of Workspace ONE, if it meets our needs.

I have used Microsoft Intune within the past 12 months.

The solution is stable.

I have found Microsoft Intune to be scalable.

We have over 5,500 users using this solution.

The technical support from Microsoft could improve, it is not as good as the Workspace ONE support. It is difficult to contact Microsoft support.

I have used Workspace ONE, and I would highly recommend it over Microsoft Intune.

The initial setup was complex, and the full deployment took us one year.

We did the deployment ourselves. There is little maintenance required, we have to only update policies. We have a mobility architect that set up most of the backend and we did work with a Microsoft resource for this process.

I have received a return on investment, the solution is inexpensive.

There is a license required to use this solution. However, it was part of a bundle package. 

Microsoft Intune is far less expensive than other solutions, such as Workspace ONE.

We are only using Microsoft Intune because it came with our Office 365 license.

I rate Microsoft Intune a five out of ten.

We propose Intune for information protection. We integrate Intune for application management and protection of company information on mobile devices.

It's normally able to meet 100% expectations of our customers. 

Sometimes, customers compare it with AirWatch, but the concept of Intune is different from other solutions. It's an application management app. It gets a bit difficult to explain it to customers, but it's not a product limitation. It takes a presale document or presentation to explain it to customers.

I've been working with Microsoft Intune for more than five years.

It's stable.

It's scalable. Our client has 1,000 people.

I'd rate them a ten out of ten. All of the ticket questions are answered. 

Normally, customers need a pilot. It takes around two or three weeks for the pilot. After that, we do the deployment. We start with a limited number of policies. Overall, it's done in three to four weeks.

We have five people in the company for implementation.

Its price is fair. It's a normal price. It isn't too expensive or too cheap.

Overall, I'd rate it an eight 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.

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.

I am an IT support engineer. I take care of all IT projects in my organization. I have implemented Intune and onboarded thousands of devices over Intune. I'm not an end-user. I am supporting our employees with IT policies.

I can reach devices or computers over the internet. I don't need to worry about the network connectivity between the offices. I can manage any device. That is the most important part. 

The Mobile Application Management (MAM) policy is also valuable. I can control applications, and I can secure applications by using the MAM policy. It is very effective and very helpful in protecting our users' data on mobile devices such as iPhones, Android phones, etc. I can apply policies, and I can protect user data.

I can also deploy the software and applications and do configurations. Windows autopilot is there. It is like self-provisioning on employees' computers. That is also an important part.

The most important thing is reporting. They should improve their reporting. They should give a free hand to users. In SCCM, I can create my own reports. For example, in SCCM, I can create an inventory report for my PC or for all PCs, but in Intune, we don't have an option to create any report. Microsoft claims that Intune is a successor of SCCM, but SCCM is more powerful than Intune. So, they should develop Intune more and make it equivalent to SCCM. Then, their product will be great in the market.

If I want to deploy an application, I cannot add multiple schedules. I can add only one schedule, and I need to rely on that. Adding multiple schedules over a period of time is not possible at this time.

I cannot evaluate any setting before deploying anything. In SCCM, we have the Compliance Baseline feature. If I want to check any service or anything else, I can do that, but in Intune, that is not available. There are very few compliance policies. They say whether your device is compliant or not, but if they don't provide enough and better compliance policies, why should I be compliant with those policies? They should give more options for the compliance policies so that we can choose something better, and we can make our devices comply with those policies. 

It lacks in terms of analytics. Analytics and all such things are not good, which again comes down to the reporting part. It should be better in terms of analytics and reporting. 

It also lacks in terms of automation. If we want to automate some of the things, we need to spend more time on automation. Other tools in the market are giving better automation graphically. So, they can work on that part.

Their support should also be improved. They don't know about their own product.

I have been using this solution for the last six months.

It is very stable. So, whatever features they provide are working great. There are no problems with those features.

My experience with them was very bad. They don't know about their own product. I know better than them by going through their articles and other resources. When I ask them anything, they come up with silly answers. They are making me feel frustrated. I have had a very bad experience with their support.

Its initial setup is very easy. We don't need to deploy any servers anywhere. With just a few clicks, we can set up Intune. We just need to set the MDM authority, and we need to set the automatic enrollment. That's it.

Most of the mobile device management tools are giving the same facility. I don't have experience with VMware Workspace ONE, but I have been reading about it. VMware Workspace ONE also gives similar features in a slightly different way, but the objective of all such tools is the same. 

I would rate Microsoft Intune a five out of 10 because they are still developing it.

Primarily we are rolling the product out because we want to be able to have remote access and control over our desktops and laptops from external locations.  

The most valuable aspect of the product when it is in production is the basic thing it was made to do. We want to be able to allow access to various applications remotely which we can not otherwise do with remote workers.  

This type of question may be premature because we have just started rolling it out now. We have not had a chance to work with it to capacity at this stage. I think, so far the implementation is all a bit shaky and should be better planned and better supported. The deployment seems to not be as simple as what I would have hoped that it would be considering it is a Microsoft product.  

When it is fully rolled out, we will see where the other shortcomings actually are. However, this difficulty in rolling the product out is a significant stumbling block.  

We just started testing the product several months ago. The technical team is working toward trying to roll it out to production in about the month. As that is the case, we are not really using it yet in production. We have got only about half-a-dozen of the 4,000 projected users working with it currently.  

Again we have not really tested and deployed the product broadly across the company at this stage. But it is exactly because we have not seen the kind of stability and performance we were expecting that we have not completed the roll out.  

If we can not seem to get even half a dozen users working with the product in a way we consider stable, the scalability is in question. It should not be.  

As far as the set up, we only have the first half-a-dozen technical people on the product just to do a pilot. We have had issues with it. This is the reason we have not even deployed it for the users' space yet to deploy to a larger test group. I would expect the deployment would be a bit easier. That could eventually be a changing factor in what we do moving forward.  

I have rolled our company onto a 365 E5 licensing scheme. We are not on E3 anymore so we do not need to. With an E3 license, you would have to consider licensing the product.  

We did not really look at any other competition. We are a Microsoft 365 E5 customer and the product promises the capabilities that we need and is available without additional cost. It just made sense to try to use this part of the suite.  

On a scale from one to ten where one is the worst and ten is the best. I would rate Microsoft Intune as about a six. I am not totally impressed with the complexity of the rollout. 

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.