Microsoft Intune Reviews

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.

We primarily use Microsoft Intune for device management and application management. It allows us to control and restrict user access, preventing data sharing and leakage. 

Additionally, we utilize it for endpoint management of Windows and Mac devices, ensuring their security and compliance.

The benefits include that it's very easy to deploy and integrate. Users actually feel satisfied and have a great experience with it.

The most valuable includes managing everything from a single console.

Integration with Mac devices requires some improvement.

I have been working with Microsoft Intune for eight years. I currently use the latest version.

It is a stable solution. I would rate the stability a nine out of ten. Sometimes we get some alerts from Microsoft Intune, but our team is responsible for managing that internally.

It is a scalable solution. Around 3,000 endpoints are being utilized in our organization. 

 Customer service and support are good.

Positive

We used VMware AirWatch. We switched because of the ease of use that we get from Intune. It's much simpler to work with.

The initial setup was very easy, not at all complex.

We have our own team that handles the deployment. Three to four people were included in the process. 

The deployment process was simple. We just enrolled devices and created the necessary policies, and that's it. It took approximately twenty to forty minutes, depending upon the use case.

Moreover, it is easy to create policies with Intune. It's not difficult at all to maintain. We have the same team taking care of the maintenance.

Just go with it. It's very simple to use. Overall, I would rate the solution a nine out of ten. 

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.

Microsoft Endpoint Manager is simply a desktop, a laptop, a smartphone, or a tablet. An endpoint is exactly what it sounds like. Microsoft, on the other hand, makes use of that tool.

Endpoint allows you to deploy the operating system level. It enables the packaging and deployment of applications. It enables you to secure systems with BitLocker and incorporate things with Active Directory.

We are a consulting firm.

Our clients use it to simplify desktop builds and to maintain the patch management on their servers and desktops, as well as to have an easy mechanism for both rolling out BitLocker, which is a Microsoft tool and publishing new updates for their various software packages.

Microsoft is investing significantly more in the cloud. For our use and our clients' use, and again, our clients who use Endpoint number over 500, with an increase of 1,000 users. It is effective. It significantly reduces the overhead associated with providing support. It actually works quite well.

The installation could be improved to be simplified.

I have been working with Microsoft Endpoint Manager for the last 12 months.

We are Microsoft partners. 

We have been working for well over a decade with SCCM, and now with Microsoft Endpoint Manager.

They are deployed both on the cloud, and on-premises.

Microsoft Endpoint Manager is quite stable.

Microsoft's cloud has a capacity of 100,000 users. Depending on what you are dealing with, it's highly scalable, depending on how and where you deploy it.

It's from Microsoft. However, we are a Microsoft Premier partner. As a result, we are quite familiar with the product. Again, there isn't much of a need for it. However, our clients call us if they run into problems, which happens very rarely.

You do not have to maintain the Microsoft Endpoint that is built into their cloud, it's a cloud-based service. Locally, there is now maintenance every 16 months if you are deploying the local endpoint or creating a hybrid to Microsoft's cloud. You have to upgrade if you are deploying the local deployment. The current build changes every 16 months, but the upgrade is a very low skill set, you don't need anyone to upgrade it.

SCCM is no longer known as SCCM. It's known as Endpoint. Microsoft no longer recognizes that product. Endpoint refers to both the local and cloud-based installations. And, prior to their acquisition by Dell, we were a long-term partner with Quest. We've had clients use Quest products, but we haven't.

According to Microsoft, SCCM is no longer in use. Microsoft Endpoint is the new name for the current build. You can now deploy an Endpoint structure locally or pull Endpoint from Azure.

SCCM is no longer active.

I have worked with both Microsoft Endpoint Manager as well as Quest in the last 12 months. We have clients running the Quest Software.

The most recent Quest software we've seen is the Exchange PTS, or mail migration tool. That is probably the tool that we've had clients deal with twice. However, that is apples to oranges in comparison to SCCM.

It is the mail migration utility. According to my understanding, Quest recently sold that to a different company. So it's an old Quest product.

The initial setup is complex.

You have to appreciate two points with Microsoft Endpoint Manager. Microsoft Endpoint is based in Microsoft's cloud, 365 Azure. And Microsoft has simplified it quite a bit. They also work well with Intune. Many of their services are complementary to the solution. Autopilot is being sent out. You can have a machine auto-built from a remote location, or you can order an Autopilot deployment from your HP, Dell, or Lenovo. They've simplified it considerably since the old days, but there is still a technical element. For those with a technical nature, it is quite simple. Anything is simple if you understand the product.

You should probably consider cloud deployment before local deployment because Microsoft has made significant investments in the cloud. The local deployment is still in place. Microsoft's cloud comes with a lot of extra features that are free of charge. Furthermore, if you deploy it locally, you must own SQL, whereas, in the cloud, SQL is not required.

I would rate Microsoft Endpoint Manager a nine out of ten.

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.

It works pretty well for us.

The configuration and pricing can be improved. It would also be better to meet with people in the country and teach us how to manage personal information because we will not look at or touch any personal information. They should teach us about managing personal information and make it really easy for us.

Pricing can be improved.

On a scale from one to ten, I would give Microsoft Intune a ten.

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.