Microsoft Intune Reviews

The solution is primarily used to manage iOS, Android, and also Windows 10 or Windows 11. It's to manage end-user devices.

The best thing about Intune for the customers is simply that it's included in the different plans of Microsoft 365. If a customer needs Office or collaboration tools, Intune is included. It's for free. If the company has another MDM, normally they are paying for it. This product is included in the license of Microsoft 365. We find that the customers, in general, want to change the solution, to move from another classical MDM to Intune due to the fact that they save money.

If you need only to load a specific profile and you don't have deep security functionalities, etc, Intune is very nice and good.

The initial setup is very simple.

If you need some restrictions or some integrations or you need integrations with security options, or if your mobile terminals are industry-special or ruggerized, bar code readers, printers attached, this might not be the best option. If your MDM has to be really specific, perhaps Intune is not the better option. You have to consider MobileIron or Workspace ONE or MaaS360 or similar.

They need to integrate more with security options. When the customers want some specific security functionality they begin to think about other platforms. 

The stability is very good. There are no bugs or glitches. It doesn't crash or freeze. It's pretty reliable. 

Scaling is simple. It depends on the licensing. If you have licenses for that, the only thing you have to do is to continue with the enrollment of the terminals. It's very easy. You have to assign the terminals to a group of users with different restrictions or policies and that's it.

With the CSP licenses, we as a cloud service provider, are obliged to provide services. With our service, we provide support to the licenses. When we sell licenses differently, in the LSP scheme, then we have to sell the premium service for the customers.

I don't use it directly. That said, I know the ratings of the services that we provide for our services. The only thing that I should say is that normally when we have an SLA with a customer for Microsoft, there is a specific response time that we can provide as a service provider. They do not consider that. They say, "Our service is this. This is our SLA." Then, our service level agreement is eight hours. 

Sometimes, when you offer a service level agreement with a customer, the support of the manufacturer or of the vendor is included. It's the only thing that, if you are providing services on an end-to-end basis, you have to consider. Sometimes, when you call Premier Support and you say, "Please, I need a solution before six hours," it doesn't matter for them. They say, "I have not six. I have eight, so don't call me if I'm in the eight hours."

It's very simple to set up. To set up the terminals, it's very easy. You have a manual, and it's very easy to follow. You can configure functionalities for specific users or a specific group of users or things like that. It's great.

The time it takes to deploy depends on the number of terminals and it also depends on the number of different groups. Perhaps you have to configure the different policies for different groups. That might take longer than a straightforward setup. In an installation with, for example, 1,000 terminals, it typically takes less than a month -three weeks or so.

I don't personally handle the deployment myself, however. I offer it to clients. I'm not the one to actually do the manual work of implementing it. 

The amount of people we need to deploy a solution depends on the number of terminals that we have to manage.

Some customers configure everything at the beginning and nothing changes over time. That said, we have other customers that they are continuously asking for changes. This group of customers will likely need three people more to handle maintenance. For every 1,000 devices, you typically need one and a half full-time employees.

In terms of ROI, it depends. If you have licenses included in your plan for M365, Microsoft 365, from the very beginning, if you have to sell that, it depends on the business case that you can do. It's different if you buy a CSP or LSP license.

One kind is considered as a cost and another is considered as an investment. The LSP is an investment. 

In the products and services space, from a pay-per-use perspective, I don't see a relationship between this product and ROI. 

There are different kinds of licenses. We sell two licenses from Microsoft, the LSP or the CSP. The service that we have with Microsoft is based on the CSP kind, so the payment is monthly, considered as an expense, not an investment o asset. It depends on if you buy a set of licenses only for Intune - which can be sold separately, or can be included in M365.

We are gold partners with Microsoft.

I would rate the solution at a nine out of ten.

For simple installations, for simple management, perhaps Intune is fine. However, for more complex installations, it might not be enough.

We are primarily using the solution for managing the devices. Some employees are using their own devices and some employees are using company-owned devices. Basically, we use it to control company data and personal data, we are keeping them separate and we are managing those devices such as Windows computers, Mac and mobile phones, iOS, Android, et cetera, via Intune.

The product is very useful in terms of Windows Information Protection. Our employees, if they try to leak data will not be able to as the data is encrypted. Intune keeps our data encrypted. If you send me an email, that email is stored on my personal OneDrive. I cannot store that email in my WhatsApp, for example. I cannot store my data anywhere else. The data protection on offer, therefore, is great. 

The initial setup is very easy.

We can use the solution with the Active Directory, which has many policies. We can restrict and protect devices accordingly. 

The solution can scale.

The stability is great.

The cost of the solution is great and was recently lowered to make it even more affordable. 

Intune has a lot of great features and we have yet to utilize 100% of their offering. 

Day-by-day Intune is improving. It has a roadmap for how it will continue to improve over time. 

They need to improve their technical support and make sure Intune is covered under their SLAs.

Our company is very new. We've only been around for about seven months. In that time, we've used Microsoft Intune. It's been less than a year. 

The solution has been stable so far. There are no bugs or glitches. It doesn't crash or freeze. It's reliable. 

The solution can scale as needed. We are satisfied with its scalability capabilities. 

Technical support is not that great. The basic support comes with a Microsoft subscription, however. Intune support from my experiences, the basic support they have, does not have any SLA.

They're working on it only during their business hours and our country is in a different time zone and has different business hours. Our country office's start time is 9:00, however, the business is coming from China. China begins at 7:00. We're getting six hours, maybe, of time where we can get support if we need it - and the basic support on offer is not good.

The initial setup is not overly complex or difficult.

The initial setup was very easy as Microsoft has a setup guide similar to what you would expect if you set up 365. If I'm following the set-up guide, it's very simple. You just click along. 

Previously the price was $4 per month per user. Now it's $2.25 per user per month. The cost is really affordable.

I'd rate the solution at a nine out of ten.

Typically, for customers that tend to come from a transportation logistics background, it's essentially free or the TCO is literally non-existent. It's a good fit for our resume offerings. Anywhere between 50 to 200 users is a typical use case that we see, where they're leveraging the product for low subscription costs.

Its overall integration into Microsoft 365 is great. 

I would say the biggest benefit is the single-pane view. There's no jumping around multiple UI's to do your overall management. Linkage to a single pane is probably the best benefit.

I'm looking at it in comparison to other EMMs and there are better EMMs out there. It's still for me at an MBM stage, as it's addressing other areas that make up EMM, however, if you put it in comparison to others, for instance, the overall experience is better. We get OL and DM and we get in the mobile threat detection. We get in a lot of other things into that EMM. 

Intune, in their port description, for me is still pretty infantile. I will say in the next 18 months to two years, they'll start becoming a bit more major, I hope.

It's pretty straightforward to implement as long as you've got a Microsoft subscription. However, it's kind-of convoluted how they explain it and what you are paying for. Obviously, we know that the more money you pay, the more features you get. I think that they can lay it out a little bit better, sometimes it's pretty hard to follow what their offering actually is.

There's quite a lot of development that they can do within their Intune dashboard. I think there are too many lines hyperlinked to move you around. Others, in contrast, give you a simple dashboard and an intuitive administrative walkthrough.

The solution looks too technical. Even though it is a technical feature, it comes across as too technical to navigate through. They can certainly work on the overall dashboad and the layout, to simplify everything.

They can do a lot more with Enterprise Firmware over here to give it full support.

Coming from a Samsung perspective, they need to comprehensively support the Android provisioning methods.

I’ve been using the solution for three years now.

From a stability perspective yes, it's very stable. The SLA that Microsoft gives around their network, the cloud service offering, makes it very stable.

It's highly scalable. Anything that's in the cloud should come with scale, and in this case definitely a highly scalable option.

I'm not sure, in total, how many people are actually on the solution. With Samsung, there's no preferred EMM solution in place. Most of it tends to come down to local/regional preference. Each region's location has its own mobile provider or EMM provider. We don't manage Intune for ourselves or for customers. Therefore, within the business, I would say it's less than 5%. As I say, we have our own solution. Nobody's going to use Intune within Samsung and we have our own EMM. Therefore, I don't forsee us increasing usage.

As we're consultants, we never rely upon a specific Microsoft consultancy to resolve anything and we clear our own testbed issues. We've very rarely been in contact with Microsoft's technical support. We're more engaged with Microsoft from a strategic partner level or in partnership as regards to our EMM offering. We have all the expertise we need in-house.

The solution is cloud-oriented. As long as you have a valid Microsoft Enterprise Subscription, it's all subscription-driven. From an installation or deployment perspective, it's pretty quick and pretty straightforward. It's not complex. As long as you paid for at least a standard enterprise subscription.

Where I am with Samsung, we're pre-sales. This is the customer's OMS. We're engaging with customers that have these environments in place, to then obviously bolt in our Samsung cloud solutions port. Obviously, we become consultancy on our cloud solutions. However, more so you have the engineering aspects of that.

For my area of business, we have a yearly subscription, which provides us with Intune capabilities within our test labs. It is negligible. It's pennies compared to our growth target. It's very affordable.

I'm typically an Azure consultant. Therefore, anything on the Azure platform now obviously includes Intune from an EMM perspective.

We use a multitude of versions. I can't tell the specific numbers. We use many as we have to constantly compare against different customer environments. We have test labs that have multi-versions as well.

Predominantly, our deployment models are on the cloud. There's literally no call for on-premise at all, apart from network connectors.

I would advise users to consider the solution on a use case by use case. I personally work in a Samsung Android environment and there's a lot more feature support in other EMMs. Therefore, I wouldn't necessarily recommend it. In the next 18 to 24 months, I hope that severe changes are made as Microsoft establishes itself more.

Overall, I would rate it at a seven out of ten. There's still a lot of room for improvement in how they deliver. Their products and features are pretty good, and they serve the need. They probably just need to work on their explanation and probably the layout and UI quite a bit more. 

We primarily use the solution for remote workforce systems that are not connected to the VPN, to flexibility deploy software, and operate system upgrades and policies, as well as pushing scripts to the devices. Pretty much just about anything that we can do in Intune, we're going to be doing. If we're not doing it already, we will be doing it.

Right now, pushing out software and policies is the solution's most valuable aspect.

The pricing and support are great. 

The dashboards, the security, and the customization capabilities work very well for us.

Everything is so tightly integrated with the on-premise solution. 

In terms of what is missing on the solution, I can't really think of anything right off the top of my head. It's doing everything we need it to do.

It would be helpful if there was proactive remediation.

In terms of some of the reporting, I find that it takes too long for some of the reports to display actual data.

We started in February using Intune on an actual production project. We had used it on a very limited basis as a testing bed several years ago, however, it wasn't a mature product back then.

The stability is great. We haven't had any issues in that regard. We don't have bugs or glitches. It doesn't freeze. It's reliable.

The scalability is very good. If you need to expand the solution, you can.

It's a management system, so every single endpoint across the enterprise has Intune connectivity. I would say 100% of our users are basically on it. We're managing all of our internal resources through Intune and the on-premise solution configuration manager. We've got upwards of 8,000 employees currently.

The support has been excellent. We're quite satisfied with the level of service provided.

The initial setup is not complex. It's relatively straightforward.

Deployment was basically a three-day engagement.

We had some assistance from Microsoft. A Microsoft engineer came on-site to assist us over the course of the deployment.

We're not paying for Intune due to the integration with Configuration Manager. If you own Configuration Manager, you own Intune and vice versa. If you own Intune, you own Configuration Manager or the on-premise solution. As far as how much Configuration Manager costs, I'm not exactly sure. We set that up a long time ago and I just do not recall the cost on that.

Our company does not have a business relationship with the vendor. We're simply customers.

We're using the very latest version of the solution. We're using it with Microsoft Endpoint Configuration Manager, and we're running a 2006 build. With Intune, since it's the SaaS model, it's whatever version is available in the cloud.

My advice to other organizations considering the solution would be to be patient. Some of the reporting, for example, takes up to 24 hours before it is actually displayed in the console, depending on a number of endpoints you're trying to manage. 

The other recommendation would be is be prepared to switch your way of thinking around deploying policies through Intune. The policies in Intune are similar to GPOs, but there is a difference. There is a very, very distinct difference between those policies and the equivalent of the policy and the configuration as a baseline. They're similar in nature, but they're very different. You have to kind-of switch your method of thinking.

I would say I'm very, very pleased with the solution. Even with the delayed reporting, I would give it probably a solid nine out of ten.

When we develop, it's used for multiple different solutions. It could be anything, such as a portal, field services, web development, web apps, and lots of other different things.

For me, there are many strong points in the solution. Firstly, the skills are readily available. That's one of the things. There's a lot of Microsoft expertise in the market. 

Also, they've invested a lot in their software and continuously updated it. So I think those are the things that are very important to us.

There is room for improvement in integration and security as well. Those are areas that clients are always concerned about.

So, in future releases of the product, I would like to see better integration as well as enhanced security.

I have been using Microsoft Intune for seven years now. We are dealing with the latest update of Microsoft Intune. We have started working on it, and our developers and other personnel are currently getting certified for it.

It is a stable solution. I would rate the stability an eight out of ten.

I would rate the scalability an eight out of ten.

We have over a thousand endpoints using Microsoft solution.

Customer service and support are helpful and responsive.

Positive

If you've got the right skills, the initial setup is not that difficult. It is very quick to set up. It doesn't take long. 

Some customers have benefited from it.

We work with all Microsoft products,  like .NET, and a lot of development around those areas. 

Another one, Arc Systems, is a current platform that we use.

I would recommend using this solution. Overall, I would rate Microsoft Intune an eight out of ten. If they could make the integration a lot easier, it would be better.

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.

We are going to use Intune for registration and then we're going to use some kind of condition policies for resource access for unmanaged devices. With on-prem AD-based access, when the users are working from home or somewhere else, they need to connect to the VPN or something to access the corporate network, whereas, with Azure and Intune, we are going to provide the resources for application access. We can directly provide them access by using conditional policies.

It has been only three months since we took the Azure subscription and migrated all the users to it. We are running it in the production environment. We are not running it in the testing environment. We are not implementing everything in one go because if any issues happen, it's not easy to roll everything back in minutes. For this reason, we're implementing them one by one.

With on-premises Active Directory, the main challenge was that we had no control when a user was working from home. We didn't know what exactly a user was doing and whether the AV was up to date or not. Intune provides better control of their machines.

A few of the options are a bit hard to understand. As compared to on-prem services such as AD, it's a bit different. For example, group policy objects have different names. It takes some time to find out where various options are available.

I wanted to check if there is any provision at the Intune level to restrict certain things, such as a website, but unfortunately, that feature is available only in Microsoft Defender. Intune has web filtering capabilities, but they are only useful for protection from malicious websites, whereas we would like to be able to restrict a website. For example, YouTube is a clean website. No one would identify it as a malicious website, but if we want to stop the end-users from going to that website, we have to go for another product, such as Microsoft Defender or another third-party proxy solution. It would be great if this capability is included in Intune.

We started using it three months ago. 

Over the past three months, I haven't seen any instability from the Intune point of view.

We have approximately 220 users. We don't have any immediate plans to increase its usage, but by the middle of next year, we might increase the usage of the product to another 70 or 80 people. We would be able to scale it based on our needs.

I haven't raised any case with Microsoft support, but I believe Microsoft has different types of service agreements based upon which they provide support for different applications. 

I have gone through multiple Microsoft articles, and they have sufficient to-the-point information there. 

We were using on-premises Active Directory, and we were restricting certain things through GPO, but there were a lot of challenges when the users started to work from home. 

Its initial setup is fine. I haven't seen any issues. I have worked as a technical lead at the architect level on different products. For that reason, I haven't had many challenges.

Its implementation was a bit longer because we took our time in testing on multiple machines and multiple users. We wanted to ensure that we are able to achieve what we wanted. We completed all the use case scenarios and what we were expecting from the security point of view.

We implemented it in-house. We had two people for the setup, which included a junior person and me. 

We also take care of its maintenance. We are managing approximately 220 people. I take care of all the cybersecurity and software-related work at the corporate level. Most of the people are now coming to the office. So, we have prepared a simple document for them to follow. 

We don't have just the Intune license. We have the Enterprise Mobility + Security E3 license, but I don't have the exact figures. Someone else was involved in the initial discussions and purchase, and the entire environment was handed over to me.

Any bundle package, such as Security E3, covers multiple things, such as AAP, BitLocker, etc. If you go for them individually, they would be more expensive. Bundling makes the price more attractive and competitive.

It is suitable for small, medium, and large companies, but it also depends on your requirements, budget, and the things you want to restrict. 

I would rate it a nine out of ten.

This solution is on the cloud. What is required currently by our organization is an internet-facing device. The challenges with on-premise have a lot to do with this pandemic. This is why we've seen Intune with the MDM background grow so fast — because we don't have any on-prem limitations. On the cloud, you can manage everything. You can push policies, maintain patches, and maintain security because everything interacts on the cloud. A VPN is not required. In the legacy method, you need to use a VPN for anything and everything. This increases costs.

For Windows services, there are multiple options within Intune to modernize it to be more internet-facing and dynamic. Intune also provides us with a lot of flexibility to manage Windows-specific devices. 

Mobile-wise, I like the MAM feature. It provides us with more control over the application identity levels. When combined with Azure, it provides us with multiple opportunities to design and construct a solution that meets a BYOD or CYOD model.

Regarding mobile devices, Intune is good, but there are other services that I would say are ahead of Intune from an administration and reporting point of view. These are a few things that could be improved from a mobile infrastructure point of view.

From a reporting point of view, it could use some work. If I need to push a profile, it's a challenge with Intune because first I have to go ahead, remove a user, then add him back; only then does it allow me to push or sync. If it synchronizes, it exits on a cloud-based synchronization time. With AirWatch, there is a function where you can push a profile directly on a device. 

Overall, Intune has improved from MDM. They have become EMM and now they're moving towards Unified Endpoint Manager. They're just beginning to compete in the market from a mobile point of view, but regarding Windows, they're great. 

I have been using Microsoft Intune for more than five years. 

I'd say it's 99% stable. Azure being in the background has impacted it a bit, but overall, it's stable. 

Currently, Intune is on track to exceed SCCM. In the near future, most companies will be using Intune. Currently, roughly 25% to 30% of companies use Intune. The rest of them, 40% to 50%, are still using SCCM and trying to evolve old solutions — this will change. This whole management model will completely change into a hybrid Intune model or a complete Intune model.

The vendor ships the machine directly to you. All you need to do is connect it to the internet. It takes around 30 minutes or 40 minutes depending on the configuration. After that, you're ready to go. Post setup, if you need anything, you can simply go to the built-in Intune company portal and shop from there. This saved us a lot of time.

Still, the initial setup was not straightforward. When we initially started with Windows, there were a lot of open items. There were a lot of things which were not there. Obviously, we couldn't just move a company directly from on-prem to cloud. There is complexity, there are some legacy procedures that we had to follow. At that point in time, Intune was not ready, but currently, there are a lot of options that can fulfill your security requirements, your network requirements, your application requirements, user accessibility requirements, and the user experience. All of these things are pretty much in the place now. To start with, it was not this way. 

When I started using this solution, it took me roughly one year and three months to understand how to build it, to do due diligence, etc. Now, I can migrate an organization within 13 days.

Implementation is a complete team effort. You have to understand a company from a network point of view, a security point of view, a compliance point of view, and a GDPR and HR point of view. These things take time to analyze; it's still maturing but it's a little bit better than what we had before. Now, after I have interacted with an organization, I can get it up and running within 15 or 16 days.

I never got a complete picture regarding how much we've saved thanks to this solution. Still, I think it's very significant. We stopped using a lot of services because we didn't need them anymore. We don't need a lot of resources — we don't need to procure them. We don't need a VPN solution, plus, shipping is all taken care of. 

I started my journey with AirWatch. It was primarily an MDM solution. According to Gartner, AirWatch and Microsoft are currently neck-and-neck. From an organization requirement point of view, regarding MDM, I'd say AirWatch is a step ahead of Intune.

For the last four years, I've only used Intune. I don't know how AirWatch has improved over the last four years. Still, simple things, like pushing a profile are much easier with AirWatch compared to Intune. From a UI point of view, it's really easy for an admin to go ahead and work using AirWatch. From a deployment point of view, there are multiple options for retaining user data. 

As long as it will not primarily be used for banking or security purposes, I would recommend Intune. If you work in a banking environment and are looking for a high-security solution, then I would recommend VMware, AirWatch, or Jamf. As I said, Intune is still developing. Maybe this will change after another year, but currently, regarding banking and security, AirWatch is a step ahead when it comes to mobile infrastructure policy. 

Overall, on a scale from one to ten, I would give Intune a rating of seven.