Microsoft Intune Reviews

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.

We use the solution for endpoint management, which includes security and compliance. 

We are a remote company, and the product helps us manage the global endpoints. It helps us natively manage the endpoints in the cloud from anywhere. 

Microsoft Intune's most valuable feature is Autopilot. 

We faced issues with macOS support. The product should have better inventory and asset management. 

I have been using the product for four to five years. 

Microsoft Intune is stable. 

My company has 200 users. 

Microsoft Intune's deployment is straightforward. 

We did the deployment in-house. 

I liked the tool's pricing until P2 came into effect. I am unsure about the current value versus the cost of the new licensing model. 

Microsoft Intune has improved access to devices for remote wipes. We can act quickly whenever someone leaves a company or a device gets stolen. It offers more visibility into our IT group. 

The tool's cloud-focused availability has improved the organizational security posture. It has helped to save time. We can do a lot more with a smaller team.

I rate the product a nine out of ten.  

We use Microsoft Intune to deploy the software to Windows and iOS for the campus and to isolate any intrusion.

We can centrally control the software and the settings of the devices on the multi-platform using Microsoft Intune.

The most valuable feature of the solution is compliance. We have one MDM that works with Windows, iOS, and Android.

Microsoft Intune has a latency response time issue. The latency has room for improvement.

iOS devices have certain features that are not supported, which is not beneficial for end customers in terms of open deployment and device control.

I have been using Microsoft Intune for around three years.

Microsoft Intune remains stable if it is deployed correctly.

Microsoft Intune is scalable.

The initial setup is not complex. We started by setting up the environment on the cloud, then configured the devices and profiles. However, certain aspects of the deployment required the assistance of engineers.

The implementation was completed in-house.

I give the solution a seven out of ten.

We used Microsoft Intune because it is the only solution that can also support iOS.

In cases where a device encounters compatibility issues or technical problems preventing it from receiving the MDM profile, maintenance may be required. The maintenance is acceptable.

I recommend the solution to others.

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.

We use it for proposing solutions to customers and for co-management of the end-user devices, as well as for unified endpoint management. We also use it for mobile device management.

Internet-based access with security is what I have found to be most valuable.

It is also a stable and scalable solution. We have not had any issues with technical support as well.

The initial setup is straightforward too.

Currently, for a new customer or when a device refresh occurs, I can introduce Microsoft Intune as a unified endpoint management solution. However, for an existing customer who has an SCCM it would need to be upgraded to an MECM first before I can introduce Microsoft Intune.

Microsoft even recommends it as a co-management solution because even if I need to go for UVM as a unified endpoint, I need to rebuild all the missions, which is not practical. So, they need to look into it and provide an easy and flexible moment to UEM.

I've been dealing with Microsoft Intune for at least fours years.

Stability-wise, it is good and stable.

It has very good scalability.

We have had no issues with technical support.

The initial setup is easy. Deployment usually takes around eight weeks of time, including pilot testing. We do requirement gathering, designing, and building, so it takes us a minimum of eight weeks.

From a solution perspective, I always recommend that you go for it. From a scalability aspect and on managing the devices over the internet and ensuring that the security of the devices for customers is always taken into account, we always recommend to Microsoft Intune.

On a scale from one to ten, I would rate this solution at nine.

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. 

We use Microsoft Intune for our internal security policy and team management. 

The synchronization of Intune with other Microsoft solutions is a valuable feature.

The reporting and cost have room for improvement.

I have been using the solution for two years.

Microsoft Intune is stable.

The technical support is good.

Positive

The initial setup is straightforward. We used our own certified people for the deployment.

The implementation was completed in-house and we implement it for our clients.

Microsoft Intune is a bit expensive compared to the competition.

I give the solution a seven out of ten.

Most of our clients prefer Microsoft Intune over other solutions because of the seamless integration with other Microsoft solutions which most organizations use.

The solution is easy to maintain. 

I suggest using the demo of Microsoft Intune before making a decision.

Mostly the pricing can be improved. If you are using the solution with EMS E3, then it's very expensive, but if you are using it in combination with a lot of products, then it can be cheap. Microsoft doesn't sell Intune separately. That's another consideration. The third thing would be how to view the use case because Microsoft doesn't release any documentation on how to view it when you adopt Microsoft EMS. 

Their technical support could also be improved.

It is very stable.

It's scalable because this is a cloud solution only. They don't have it on-premises.

With Microsoft technical support, they only fix Teams and when they are open, they're mostly trying to close again at the quickest time. Sometimes, the solutions given are not very good.

It depends on the use case. If you only focus on Mobile Device Management, then it is very easy to setup. You just have to define the use case in the context you want to protect. If you are talking about how to integrate with the lock analytics and how to classify data in context, then this is another thing.

The main difference between Intune and Workspace ONE is the quality integration between Microsoft products and Office 365, which means that Intune is part of a solution; you are not only using Intune, but you have to think about its ecosystem. For example, with EMS, it will have at least three products. The first is Azure ID Premium, which is the IAM solution (Identity and Access Management), so there are use cases where you might need to use IAM. The one difference between EMS and Workspace ONE, since Workspace ONE doesn't focus on identity management, is that it only has the access part. It can leverage all identity management, like with the directory or any of the identity solutions. 

The second difference is in the integration with Office 365 because in the Office 365 ecosystem, you have a lot of products, like Azure Information Protection, which is focused on the labeling and classifying of data. Microsoft also has Defender DLP and Defender for Endpoint. These make up a total solution. Based on that, if you have a long-term roadmap, you can actually integrate it with other Microsoft security solutions, like Sentinel, which is a SIEM solution. When choosing Intune, the main difference is the ecosystem and the roadmap.

I would rate this solution a nine out of ten.

For advice, it depends on the use case you are trying to solve here. If we have a look at the use case for security, how would you control the mobile? How would you deploy? How would you protect them based on that? The lesson depends on the answers to those questions.