Microsoft Intune Reviews

We use it for mobile device management. Android devices, iOS devices, Windows devices, computers, and so on are managed with the help of Microsoft Intune.

It's easy to manage and easy to configure.

We use it to completely manage the devices and access policies. We have app protection policies as well. So when it comes to any person who is outside my current organization, he won't be able to access anything if he's not authenticated. That's a really great feature because data security or data privacy will still be there.

I see room for improvement with respect to China and Android devices. If we get Intune for China for the Android devices, it would really be a win-win situation. The devices we are using to manage devices in China are partial MDM and not complete MDM.

China blocks Google and Google Play Store, which makes installation challenging. Microsoft Intune is a company software, which has to be installed to the app portal or Microsoft Software Center.

With barcoded scanners, it works really well in countries where Google is not blocked, but again, it's a challenge when we have to install Microsoft Intune where Google is blocked.

I've been working with Microsoft Intune for roughly three years.

It's deployed on the cloud itself, and we have 10,000 plus users.

Technical support is not great. If you open up a case, it may remain there for a long time. I believe that they may have a lot of customers and that's why we don't get the response immediately. Also, with these difficult times with COVID-19, they may be facing other challenges.

We used AirWatch and switched because we were facing a lot of issues with the product. Some things were really great, but some things were not.

Maintenance took a lot of time because it was on-premises. Every month, we had to do upgrades and patching of all the servers.

Too much information was provided regarding the initial setup, and it was too difficult to understand sometimes. You would have to read each and every article and try to understand exactly where and what you need to deploy. That's a bit challenging, but if you have seen the videos or attended Microsoft's training, then it's easier.

I attended the training and was able to configure and understand really well. However, if you give it to a layman, then it would really be a challenge.

Hardly any maintenance is required, so a few people will be able to handle the occasional issues and iOS upgrades.

Pricing depends on the features. Microsoft offers special packages if there are more than 10,000 users, and you may be able to get a reduced rate.

Microsoft Intune is a great product, and you should use it. You can do wonders with this particular product. So, on a scale from one to ten, I would rate it at eight.

We have some security policies pushed to our laptops, and we use Microsoft Intune to mainly monitor if they are up to date. The reason why we use it is to keep the patch levels on par for our end points. 

Now, we have an automated registered inventory of all our laptops, and we know exactly which software needs to be updated.

It is easy to use and easy to roll out with low impact on users.

It is stable and scalable as well.

Also, the central administration con dashboard is very easy to use and provides very good oversight on all that needs to be monitored.

The pricing could be improved.

As for additional features, full integration with Microsoft Office 365 would be great.

We have been using Microsoft Intune for half a year or so.

It is a stable solution.

Microsoft Intune is a scalable solution, and we have about 142 users.

We've still got a few more end points to roll it out on, but our increase will be in functionality. Now, we're only looking at updates, but in principle, we can actually push security policies as well.

The initial setup was straightforward and easy to roll out.

Our own technical staff implemented it, and it took about one month.

I would advise that you educate your staff first before rolling it out. Give them ample education and training on how to implement it and on how it's going to be used.

The biggest lesson I learned from using Microsoft Intune is that the central administration con dashboard is very easy to use and provides very good oversight on all we want to monitor.

I would rate Microsoft Intune at nine on a scale from one to ten because it's so easy to use and easy to rollout with low impact on users.

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.

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.

It is used for mobile device management. We use it for mobile phones and even PCs. We have its latest version.

Its protection policies are most valuable. It protects mobile devices as well as individual apps.

It is pretty scalable, and its documentation is also pretty good. It is also pretty straightforward to deploy.

They need to add more group policies. I know that they are already working on it, but this is something that I would like them to do quicker. Intune currently does not have many group policies that you can deploy. It is quite limited in terms of group policies. For example, if I want to disable the password manager on my browser, I can get support in Google Chrome, Internet Explorer, and Edge, but not with Firefox. It would be ideal if they can add some of these things.

Its reporting, which is very limited at the moment, also needs improvement. I can see basic information, such as how many devices are enrolled, but I can't get customized information. It will be great if they can add report customization.

Its stability needs to be improved. Sometimes, when you register a device in Intune, it doesn't show up instantly on the engine portal on the admin side. There are sync issues between the admin side and the user side.

They need to provide better support for complicated issues. They also have a long turnaround time for resolution in regards to overall escalation.

I have been using this solution for three years.

It needs improvement in terms of stability. Sometimes, when you register a device in Intune, it doesn't show up instantly on the engine portal on the admin side. There are sync issues between the admin side and the user side. It is not very stable. Sometimes, it works instantly, and sometimes, something goes wrong, and you get stuck there. It is not consistent.

It is pretty scalable because you can also integrate on-premises stuff. You can also integrate it with SCCM.

When I contact technical support, I normally find the junior engineers to be not that good. They're just good with the basic issues. If there is something complex, you have to escalate the case, but they take a lot of time to escalate it. After the escalation, they are able to fix the issue, but the overall time they take to solve an issue is too much. Sometimes, the solution is very simple, but the process of escalation takes too long.

I find it pretty straightforward, which could be because I have been working on this solution for three years. It mostly involves clicking the Next button. It will also depend on your requirements and policies, but it is generally straightforward.

Microsoft documentation is a very good place to start. They have done a great job for beginners who want to deploy Intune in their organization. They have done a good job in describing different scenarios in the documentation. I would advise starting with the documentation and doing some certification as well.

I would rate Microsoft Intune a seven out of ten.

I work for Mastersystem Infotama who is a Microsoft partner. I am an engineer, and I deploy Microsoft Intune in several companies. Our customers use Intune for their mobile device management. We also use Intune to protect devices accessing the application's corporate data. First, you must be compliant with the same criteria. If users connect with the corporate IP address, they only connect with username and password. But if they connect from a coffee shop IP address or IP addresses that aren't corporate, they will have to engage in multi-factor authentication.

I like that we can implement conditional access. Microsoft has conditional access for mobile device management, and we can categorize it as a corporate application or a personal application. We can protect it so users cannot copy from the corporate application to the personal application, but users can copy from the personal application to the corporate application. 

We can also make one file with different permission for different people. The name of the feature is Microsoft Azure Information Protection. We can configure it to help the user work from home. They can download the file, and they can operate this file in another place, but the corporate organization still protects it. 

We can also protect user access from a mobile phone. They cannot save the file to internal storage for the mobile phone. They only can save the file to OneDrive or SharePoint drive.

It would be better if Microsoft can reduce the cost of the license. as we know the Intune device subscription is licensed per device at a cost of $2 a month. but for the best to enhanced security and feature we must added add-on license or buy/upgrade to bundling license such as M365E5.

Microsoft Intune is a core product, and it's very stable

Scalability is good. It can adopt Android and iOS and manage macOS. We couldn't support macOS two years ago, but now we can.

Technical support is good. We get help from Microsoft support. For Microsoft Intune, if we buy the license, we can get support for free. We can create tickets for the problems. We can also report the problem in the Microsoft portal.

Microsoft Intune is essentially software as a service for mobile device management. To configure Microsoft Intune, we only have to register the domain name and register the DNS. We can log in to enroll the device with Microsoft Intune. After we register the DNS and the domain name, we configure the policies. All policies like user access and permissions. After that, the admin can send the license to every user.

The configuration takes one to five days. But it takes a long time to educate the users on how they can use it. This is because some things change after we implement Intune. Users may complain that they can't do what they did before, but it's better from a security perspective.

Microsoft will maintain it. The customer only maintains the policy and the license.

The price could be better. Microsoft Intune pricing is based on the number of users. Every user license is for 15 devices. consists of 5 devices for PC (Windows or Mac), 5 tablets, and 5 mobile phones (Android and iOS). 

My customers already know and use Microsoft, so they adopted Intune. They use Office 365 for secure collaboration between organizations. Microsoft is the preferred choice and has user confidence to work together securely.

MobileIron has two types of licenses. One is a SaaS-based model, and they provide support, and the other is a license for the on-premise solution. Microsoft Intune offers only a cloud solution.

If a customer already uses a Microsoft solution like Microsoft Office, or an email solution like Microsoft Exchange, it's better to use Microsoft Intune. But if they want an on-premise solution, they can choose another solution like  Mobile Iron or Airwatch solution.

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

I'm a senior information security analyst and a customer of Intune. 

Before having Intune, we didn't have the capability to have computers wiped. I couldn't manage the operating system from a central location and wasn't able to deploy policies and verify software updates. It's helped with software update needs, operating system version update needs, and security policy enforcement.

The support is excellent for this solution and the configurations are a good feature. 

There are some enrollment features that could be improved, possibly some other tools that do almost the same job with alternative ways to enroll the device. Intune doesn't have those features. Additionally, I think they could try to invest more on macOS devices making it more manageable, and making the management more accurate. A solution like Jamf, for example, gives you the greatest capability - more capability on management, on policy enforcement, wiping devices, locking devices, and many other things. This is the main reason I'm not using Intune for all the contractors now and the reason we're planning to have Jamf implemented at the beginning of 2021.

If they could improve the support on the macOS devices, it would be great. Then we wouldn't need to buy Jamf. I'm not sure it's possible because of the relationship the enterprise has with Apple, but if they could improve the macOS management, that would be great. 

I've been using this solution for about two years. 

The solution is very stable, we don't have any problems with the platform itself. We had a problem a few weeks ago with the whole Azure provider system which affected not only Intune, but most Microsoft services. This was the biggest problem I've had with Intune, no problems with the platform or instabilities.

I'm not able to scale because of the issues with macOS management. We really have some needs here that Jamf Pro covers more efficiently than Intune does. We are trying to work it to have Intune on Mac systems, but we need to install something extra to make that work. We were looking for a more transparent tool in order to get this enrollment done by a central console, and not have to install other tools on the computers. Jamf does that, so we essentially don't need to install any kind of tool. You just need to enroll your device using a URL and it's done. Scalability in relation to the entire Windows or Android or iPhone environments can be done without a problem. We have around 2000 computers. In my previous job we had 55,000 PCs, and they were all Windows.

We had four analysts working on implementation and we now have two people dealing with day-to-day maintenance. For now, we won't continue installing Intune on macOS. We'll just keep them on Windows, Android, and iPhone and we'll go through the macOS with Jamf Pro.

With Microsoft, everything is on the community and easily accessible. Jamf Pro also provides a very, very, good support team. They have engineers, and depending on the support you buy or the support agreement you make with them, you can have a personal engineer working with you 24/7. Both tools have very good support teams.

It's really simple to implement Intune. Everything is already deployed on the cloud and you get everything you need. If you have a Windows 10, you can perform this connection from the Windows control panel and it's quite easy. We are now working to get the Android and iOS cell phones enrolled as well. We are on a pilot right now for macOS. Computers running macOS are already in a pilot period. We're just verifying that everything works well. We're also proceeding with the implementation for the macOS computers as well. Deployment took one or two weeks and I did it myself. 

In Brazil, we need a partner to get a license. The partner communicates with Microsoft and provides us with the license. We have a monthly contract which is paid annually and we have a three-year contract with Intune. 

If you have a complete Windows workstation environment, Intune is fine. But if you have a mixed environment like I do, running Windows and Mac, Jamf Pro is the best tool to manage an Apple environment. The reason we chose Jamf is because it integrates to Intune. In a single panel you can have all the inventory you need, either from Mac computers or Windows computers, because they send the information to the Intune platform. This was the main reason we chose Jamf.

I would rate this solution a nine out of 10. 

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.