Microsoft Intune Reviews

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:

• where it ranks in industry reviews
• for the features that I'm looking for
• pricing.

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.

The primary use case is to manage devices that are dedicated to processing as well as managing work stations and sales devices. I'm an Intune engineer and administrator and I implement this solution.  

This is a great solution for anyone wanting a modern endpoint device management solution.

I'd like to see an ability to deploy more ways of management, managing devices and processing the policies. 

I've been using this solution for three years. 

This solution is stable. 

The scalability is good. 

The initial setup is very simple. 

Licensing costs are based on the number of devices being used. 

Indeed, it's a correct solution for any client who wants to use this modern endpoint device management solution.

I rate this product nine out of 10. 

The solution is deployed on cloud.

Autopilot is a great feature. Most users are looking for zero-touch deployment. 

There are many things that could be improved in Microsoft. Reporting and troubleshooting for the application deployment could be better. It's very difficult to understand. 

It's also very difficult to monitor where exactly the error is and the kind of scripting we're trying to deploy. PowerShell scripting is even getting a delay compared to other applications or policies. Usually if we deploy the configuration profile, there is an immediate sync and it will be applied to the devices, but it's not happening on PowerShell. This is an apparent option for PowerShell that is not working properly, so that again needs to be rectified. The reporting is a major drawback in Microsoft in Intune. They're not properly reported on the console.

I have about seven years of experience with Microsoft. I have been working with Intune for the past four years.

The solution is stable, but the reporting steps could be improved. The product has been released for more than six years, but some complete information is required.

The solution is scalable.

Technical support is very active. We used to interact mostly with Microsoft, so we had a lot of issues from the Intune side, so we were often troubleshooting steps. The technical side is pretty good. Whenever it's required, they will immediately schedule a call. I would give them a 9 out of 10.

Initial setup is of average difficulty. It requires a lot of people. We need to have an Azure AD license, so some AD integration is required. A kind of firewall is included.

In Jamf, it's not like that, so we have a single console and we can implement it. But here, we have multiple because it can be integrated and co-managed. I can't say it is very easy to deploy. For very small-scale industries, then it's definitely easy if you have minimal user devices or user IDs. If you're looking to deploy the solution on a corporate-level, and if they have multiple tenants, in that case, it is definitely complex.

If you are looking for it to be co-managed, there'll be an SCCM and an AD team. Otherwise, one or two engineers is fine for Itune.

I would rate this solution 7 out of 10. 

If you are working as a SME, anybody can do the major part of troubleshooting and configuration. Even someone who isn't certified will be able to do the configuration and implementation part. Logs are required to troubleshoot.

Intune is the best tool going forward because everyone is moving to the cloud. If you have a cloud environment, it will be easy for a service provider to provide support. The solution can also be easily integrated to other tools.

There are so many additional features included in Intune that it's very easy for the users, corporate, and for companies to manage the devices. Even if the device is out of office, even if it is not domain-joined, it will be easy for us to manage for the client, or for the companies to manage it.

Compliance and the policies that can be set are the most valuable features.

It should be simplified. I've worked with many different mobile device management solutions, and Intune is one of the more complex ones. It could be more simplified, and some of it is related to the wording that is being used, such as a configuration profile versus a policy. They really should have had different names to make it less confusing.

I haven't really seen any negative on that yet.

Tech support is pretty decent for Microsoft. A colleague of mine had previously talked to them about Intune. As a partner, we also get counseling time with them. We get advisory services with them where we can speak back and forth with them on projects. We can ask them how would we implement it and what are the pros and cons. Sometimes, they came up with things that we weren't even thinking about or they confirmed what we were finding. I was on a call earlier this week, but it wasn't specific to Intune in this case. We found out something was not possible, and they confirmed it for us, which actually saved us hours of additional research. As far as I know, the advisory is only for partners.

One of the pieces of advice is to become very familiar with the cloud environment. In general, always think in the big picture, not just in the isolated issue or item that you want to accomplish. That's because Intune or Azure, in general, is just so over-encompassing. You really have to think about the big picture and not just about the simple project that you're trying to focus on. Otherwise, it will come back to bite you if you didn't plan it right.

There are some MDMs out there that are simpler and easier, perhaps even better to use. It also depends on the application. It depends on if you've got all Windows devices, all Apple devices, or all Android devices. It also depends on if you have a combination. If you've got all Apple devices, there are a couple of products out there that are probably the best MDM, but they won't help you at all with Windows or Android because they're not designed for that. Intune is trying to be all-inclusive to everything. In some ways, that's an Achilles heel too.

I would rate Intune a seven out of 10. 

We are VMware and Microsoft partners, so we offer services around their products.  

We are using Intune internally but we are leveraging it for our customers as well. That is a different story. One part of Intune is within our company, but we are also providing services around Intune and Workspace One for our customers.  

For us, Intune is on the public cloud. For our clients, it depends on the requirements and it varies from customer to customer. Some clients' requirements are deployed in private cloud mode or the hybrid setup. It depends. Requirements differ from industry to industry. If a company is BFSI (Banking, Financial Services, and Insurance), then they will be looking for a private cloud solution. If it is something which is not BFSI or maybe some industrial interest, they might go with the public cloud.  

In the end, most of our instances are in the public cloud unless there is some compliance requirement. Otherwise, the accounts are mostly in the public cloud to conform to regulations.  

Intune is used essentially to facilitate the ability of enterprise organizations to manage their endpoints. It is for end-user computing or UEM (Unified Endpoint Management) solutions.  

One of the major advantages of using Intune is for our ISO (International Organization for Standardization) certification. We have to meet requirements for ISO 27001 and 27002 and part of that is that we need to have a proper control mechanism for endpoints and the users who are using those endpoints. The other requirement is that we need to manage the workforce. We have to manage their time to understand how long they have been working, how long their device was on, when they were working, et cetera. So we use some other products that compliment Intune to gather the data on that.  

For example, we have something called Time Doctor. We use it to monitor how long people have been working. We get reports that detail how long their devices have been on. Then there are different ways we can leverage these results and statistics. For example, we can compare the uptime of the device and uptime of Time Doctor. With that, we can understand how long an employee was working on something, but how much more time the machine was up in addition to the work period. That shows the period of time that he or she was not using Time Doctor.  

The other thing is we can remotely access a device. For example, say we have to do some troubleshooting because a user is having an issue. We can remotely log in via Intune to troubleshoot the issue, as long as the device is accessible. Obviously, that can only happen if there is no issue with the internet and connectivity and services. But we can remotely access the device and troubleshoot the issue securely.  

Those are some of the different use cases.  

I guess in our company we are using most of the features in Intune. What we use it for is to control the endpoints. We publish some selected applications and the end-users are only able to download and install those applications. They are not allowed to install or use any other applications other than what we provide. We do compliance checking. We run assessments periodically on the endpoints using Intune, and Intune generates reports. Sometimes we need those reports to qualify for our ISO certifications.  

It is a similar thing for customers as well. There is a different requirement but it is a similar idea. For example, if we are engaged with an oil and gas company, they have back-office stations and point-of-sale solutions. In this case, those are Windows systems. What they used to do is they had to manage those solutions manually. They had a contract with some third party. The third-party would go on the sites if there was an issue or something, and maintenance and delivery were all manual. They did not have any EMS (Endpoint Management Solution) at all. The only thing they had was something called a radiant configuration management server. That was only used for configuration purposes, not for maintenance or other troubleshooting.  

The concern and the requirement over delivery was raised because of COVID. No one was able to go to the sites to do the troubleshooting, maintenance, and delivery. The only solution that they had was to engage with us to deploy these solutions on their endpoints. They did not all go with Intune, some went with Workspace One, which is also a UEM solution. So they wanted us to deploy UEM on AWS public cloud, then connect it, wire their MPLS (Multi-Protocol Label Switching) network to the end-point spots and box devices in order to manage them.  

The generic answer to what can be improved is that I hope that the reporting needs to be a bit more interactive.  

In our company, we have been using Intune for the past three years.  

I think Intune has been in the market for a long time now. That maturity makes it pretty much stable because it has been through so many iterations.  

Until now, we did not have any concern with respect to scalability within whatever we have done either for our organization or for our clients. We have done installations for bigger companies, for smaller workforces within bigger companies, but not for the larger endpoints. We do not know how well it scales in every direction and if scaling will cause any problems. We have not come across those things.  

In our organization, we probably have 250 to 300 people who are using the product. We will probably increase that usage in the future, but it depends. We were planning to introduce Microsoft ATP with Intune for advanced threat protection, which compliments the security part. Because Intune does not have advanced threat protection capabilities on its own this resolves that issue. There may be other considerations in the future that influence the importance of Intune to what we need it for and how we proceed.  

We are Microsoft partners and we have a different support model with Microsoft than a typical client will. We have not had any issues with our support team and they have worked well with us up to this point. We have a different channel than the partners who need to communicate with Microsoft another way.  

It is a tricky thing to answer exactly what I have used that either was prior to or a substitution for Intune. That depends on different things and factors. First of all, Workspace One is definitely highly scalable, that I know. Workspace One also has a lot of integration options wherein we can have a lot of peripheral tools. Workspace One actually started with only UEM, but it is now not limited to UEM only.  

Intune, is only a UEM. So Workspace One has one integration as UEM, but it has many other things. Apart from that, it has Workspace One Intelligence, it has Workspace One Assist, et cetera. There are four different parts that can be integrated with Workspace One and they can work together for a highly scalable, highly secure, and highly analytical solution.  

Microsoft also has solutions. It is just that they are different solutions implemented in a different way. For example, ATP (Advanced Threat Protection) Microsoft is for advanced threat protection. WAD is for virtual desktops. They do not have the same type of tight integrations as Workspace One. All of these Microsoft products work separately. In Workspace One, all the products compliment each other and all the products can be combined more like modules under Workspace One. They can push their findings to Workspace One Intelligence where all data intelligence can be done. Auto remediation can be done. We can get findings from VMware because now Workspace One security is there to make sure that this is secure under the umbrella. VMware Carbon Black is also the same in that it can send its findings to Workspace One Intelligence. So the integration is the part that is handled differently. Workspace One has many features. Microsoft also has those features. It is just that it is a different way to orchestrate. In Microsoft, it is not under one umbrella. In VMware, that is under one umbrella, which is Workspace One.  

The pros and cons are different because both approaches have their own advantages and disadvantages. Both have solutions for each of the functions. For example, each has advanced threat protection and all those capabilities. If you stay working with that family of solutions, you do not have a problem.  

Now say, for example, a company went with Workspace One because they wanted to leverage UEM. They adopted some other modules as well with it to create solutions for problems or needs that they want to solve. They have to have Workspace One for this solution and they can not work with it separately. That might be a cost factor because they can not work with one tool only, they have to make the license for two products because they do not work separately.  

For Microsoft, since the products are completely separate, customers can choose which one to go with and only use that. They can go with only one product, or they can add any of the others. They do not need to have the central component to bring them together.  

So that might be an advantage or disadvantage in using one product or the other depending on the use case.  

We did not experience any complexity in the initial deployment and there was no problem with the installation, I do not think. The complexity definitely depends on what you are trying to accomplish. I do not remember exactly because I do not directly deal with deployment anymore. I am actually leading it. We have a team that deploys the product. I do not look over their shoulder to know how much time it takes exactly and what factors it requires for successful deployment.  

We did the deployment by ourselves without the help of consultants or vendors, that I know. We are system integrators. We have the capabilities to do things for customers. We did it ourselves. The only thing is, we have a separate team for the Microsoft product installations. Especially for something like Microsoft Intune, we need to have a special expertise. Something called Microsoft Windows, virtual desktops, all of that needs someone to install it who is intimate with the application. Microsoft Azure is something that can be used for different Microsoft technologies and solutions. We have a different team that we will put on the implementation of these products depending on the requirements.  

The pricing for Microsoft Intune is reasonable. Our clients are satisfied.  

If someone is looking to have a more integrated result, they are looking for many other things like EDR (Enhanced Data Detection and Response). It is probably better to go with Workspace One because they have that under one banner. Obviously, if there is something under one banner, the integrations are simple, they are seamless, and they complement each other.  

I do not think I will have a good answer for what advice to give because technically I have not used Intune myself for some time now. I have a team that works under me for this. I am at an architect-level position now. My perspective reflects that.   

On a scale from one to ten (where one is the worst and ten is the best), I would rate Intune as an eight at least if you are only talking about a UEM solution. Personally, I am not very concerned about the reporting part, so I will consider it at eight. But if someone is looking for extensive reporting detail that is easy to understand. Interactive reporting that will give them better-tuned results, then obviously the rating might go down.  

The only thing which I see that can be done to raise this product from an eight is to package Intune as a product under one umbrella. If that were to happen, it covers the whole of end-user computing and security solutions.  

At the moment, these are two separate things when using Intune. There may be another way to accomplish this under the one umbrella if you go with Intune. For example, if there is an add-on within Intune to leverage containerized security, auto containment, and all those things. This would be a more flexible solution if that were the case. At the moment, Intune is not required to be installed as a client. As a client in the system, it can communicate with servers and do some auto containments, endpoint detection, and response. If there was a separate solution that could be added as a paid solution to create the umbrella, you have created both solutions simultaneously.  

The main reason this problem came into the picture was because of this COVID pandemic. IT teams and security teams do not go well together normally. There has to be one solution which can offer both. It can be for both IT architects, IT technical support, and security support. That is the solution that can be leveraged for both security and end-user computing. It is simple.  

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.

I am using Intune to manage both mobile devices and PC devices. I deploy applications and manage the security landscape.

The most valuable feature for us is the security, including risk analysis and patch management. The management is very important for us.

The configuration could be better by consolidating options and making it simpler. I would like to have one option in one place that corresponds to one feature, which I can check off and move onto the next one. As it is now, there are a lot of options. For example, when configuring security, I find that it is too much because you have to configure one task in one place, then switch and it is against in another place, and so forth.

In the future, I would like to see support for security and compliance management. I would also like to see iOS management options.

I have been using Microsoft Intune for five years.

This is a stable product.

Being a cloud-based solution, it is very easy to scale.

We have approximately 30,000 users.

I have contacted the Microsoft technical support lots of times. It is okay and I am satisfied with it.

We did not use a different solution for the same purpose before implementing Intune.

The initial setup was simple and it took us about two days to deploy it.

Intune only supports mobile devices in the cloud version. Because a number of my clients have both PCs and mobile devices, I deployed it in a hybrid model.

I am responsible for configuration and deployment, and sometimes maintenance. Our help desk also handles the maintenance.

The price of Intune is often included as part of a bundle with other Microsoft licenses, which makes it somewhat cheaper.

Microsoft Intune is cost-effective and easy to use, so I can recommend it. That said, it is not perfect, so I think that they can improve a lot of things.

I would rate this solution a seven out of ten.

We primarily use the solution for both deployment and operating system deployment, and also as security for patching.

Its most valuable aspect is it is very connected with the Microsoft ecosystem. 

The solution is stable.

It has the capability to scale.

The monitoring and reporting are okay.

It's only good for a Microsoft environment. While it works very well for Microsoft users but if you have other kinds of operating systems, it's very painful to use.

They need to take into consideration the Linux operating system and not only the Microsoft operating system.

The solution needs better patching across applications.

I've been dealing with the solution for seven or eight years at this point. It's been a while. 

The solution is stable. The performance is good. There are no bugs or glitches. It doesn't crash or freeze. it's quite reliable for the most part.

In terms of scaling, it can scale more or less. It is scalable, however, you need a bigger infrastructure to achieve this scalability, which is not the case with other products.

Technical support is pretty good. We are mostly satisfied with the support on offer. 

We've used Microsoft Endpoint Manager and Ivanti Endpoint. With Ivanti, it's a much more open system for different kinds of IT infrastructure. Whatever the operating system, whatever the application, it's good. It's easier also to deploy as well. You don't need a big infrastructure to deploy Ivanti Endpoint. The ability of Ivanti to have an extension for the ITSM solution is good.

If you consider a Microsoft bundle in the operating system, it's pretty interesting in terms of pricing. If you're considering it as a standalone, it's difficult to sell, due to the price. 

We use both cloud and on-premises deployments. 

We're quite satisfied with this product.

I would rate the solution at a seven out of ten. We've mostly been happy with the product.