Microsoft Intune Reviews

It is mainly used as an endpoint management tool for MDM. We are using it for Windows devices, iPads, and Macintosh devices. 

We have its latest version. It is mostly cloud-based or SAS only, and we have a couple of clients that use hybrid.

The Autopilot feature is fantastic. It is a Microsoft product, so it deals best with Microsoft operating systems, but it can integrate with iOS, Mac OS, Linux, and Android.

It just doesn't handle software updates well at all by itself. You need to be a scripting wizard to make those happen properly, or you use third-party tools. The Windows feature updates are very difficult to implement.

I would like to see a proprietary built-in remote control tool. I know that they have Team Viewer integrated, but it is not seamless. It would be nice if they had a seamless remote desktop capability directly from the Intune console.

I have been using this solution for four years.

Outside of a couple of little hiccups, it is very stable.

It is scalable. 

Overall, they're pretty decent. Their response time is sometimes a little slow, but they do get back to you and offer assistance.

I have used Workspace ONE. Workspace ONE works really well for iPads and Androids. I haven't used it recently for Windows. They had just started to sort of delve into that arena, but I can't really say how well it works because I haven't really tried it on Windows 10. Workspace ONE is far superior when it comes to iOS and Android OS. If I remember correctly, they're comparable in price.

It is straightforward for somebody who has got experience. It is certainly not something that somebody who came off the street can do easily. There is a lot of documentation, but the documentation varies widely, and it can be difficult to set up. Microsoft does offer some good support and assistance with it. If you have a user base of 300 devices or more, they'll actually walk you through the entire setup and assist you.

Currently, I am solely providing support for eight different clients who probably have over a thousand devices in total. So, the maintenance isn't difficult.

Most of our clients come to us with licensing already in place. On average, it costs $6 per device per month to add Intune to an Office 365 subscription, but I am not sure.

If your clients have Office 365, and they're not using Intune, they should be.

I would rate Microsoft Intune a six out of ten.

The solution can be primarily used for mobile management. We're using the solution to enroll Windows 10 devices.

The policies on the solution are very good.

The process of enrolling devices is a useful aspect for us.

The features that allow us to control the devices are helpful.

The initial setup is not hard at all.

Technical support, in general, has been quite helpful.

We've found the configuration capabilities to be quite good.

So far, the solution is fast and has an intuitive interface.

The feature that allows us to import the business application from the configuration manager to Intune is not very good at this time. They should be getting better in the application input on that platforms. It's an aspect that could use some improvement.

Other than that, I can't recall the solution lacking any features. Overall, we've been happy with the offering.

I've used the solution in the last 12 months. We've been using it for one year, more or less. It hasn't been a very long time just yet.

The stability of the product is quite good. there are no bugs or glitches. It doesn't crash or freeze. The performance is reliable. 

We do plan to increase the use of the solution over the coming year. Our intention is to scale a bit. We don't plan on switching products anytime soon.

I've dealt with technical support in the past, and I'm quite satisfied with them. They are knowledgeable and responsive. I have no complaints.

We did not previously use a different solution. We've only ever used Microsoft Intune for these current use cases.

We found the initial setup to be quite easy and straightforward. It's not complex. If a company wants to set it up themselves, they shouldn't have an issue doing so.

The deployment didn't take very long. It was a pretty quick process overall. 

I can't speak to any aspect of the pricing. It's not something I handle. I don't deal with licensing and therefore don't know if it is expensive or reasonably priced.

I've been testing the solution. I'm a customer and an end-user. My company does not have a business relationship with Microsoft.

In general, I would rate the solution at an eight out of ten. We've been happy with the capabilities overall.

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 use Microsoft Intune to manage iPhone devices that we currently deploy to the end-users, and I manage all that. Right now, we're running close to about 60 devices. 

But eventually, what we want to do is go ahead and enroll the Windows platform on that as well because there's only one license per user that can deploy up to five devices. That is going to be my next migration roadmap. We're going to be managing laptops through it as well. So it would be Windows 10 platform along with the iPhones.

I like how Microsoft Intune lets me lock down the email profile and make it accessible only on certain devices. I also like how one user license allows up to five devices.

I'm still playing around with it and haven't had any issues with the product yet, but support can definitely be improved.

I have been using Microsoft Intune for about eight months.

I would say that it's a stable solution.

It's definitely scalable because one single-user license can allow up to five devices to be added. We're going to be rolling some laptops out, and we can definitely work with either an Android or an iPhone. It doesn't matter which device. 

It's scalable to that point, and the fact that only one user license will allow up to five devices, I think that's something that we would be looking to do, and we're definitely happy with it.

I've dealt with Microsoft way too many times, and needless to say, I'm not too fond of Microsoft support most of the time. I've always had a better experience with Workspace ONE and VMware, and they're very good with their support. Microsoft support can definitely use a lot of improvement.

With Apple Business Management, we can pre-deploy everything, and we can manage everything on the phones with the lockdown. With Workspace ONE, I couldn't lock down the email profile and make it accessible only on certain devices. 

Especially with Office 365, this became the biggest issue because we couldn't lock down the profiles per device space. When I worked with VMware, I worked with Microsoft Office for a couple of weeks continuously to figure out a solution and couldn't find one. 

That's when we decided to go with Microsoft Intune management because we could lock it down to just those devices. Otherwise, it was locked, and our tenant is a government tenant, and we don't allow any external access to our tenant.

That was the issue I was having with Workspace ONE. Workspace One couldn't integrate Office 365 applications the way I wanted it to.

The initial setup was straightforward. I actually prefer Microsoft Intune over VMware Workplace ONE because it's a bit more complicated. The setup was also easy because I've worked with Intune before.

It's not a server license. It's an end-user license. Because it's an end-user subscription and it's on a monthly basis, and because we're a government tenant and have a lot more scalability and users, we use it monthly. 

We work with the subscription rather than a server license. I think it's economical this way because we don't have to have a server license for that, and I think that works in our favor.

I would definitely say that you need to work with Apple Business Manager first. If you don't set up that account first, you will run into some issues, especially if you're doing a managed profiles on it. 

Just make sure you do your homework before you get started because there are a lot of prerequisites. If you miss them and you don't do it, then you run into issues, and then you're literally recreating the same work you've already done.

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

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. 

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.

Intune is a cloud-based solution for MDM and endpoint management.

The most important thing for me is the autopilot feature. Other products have this capability but they have to first integrate with Azure. Because Intune is a Microsoft product, you don't have to do anything explicitly to get this feature working properly.

Microsoft really needs to improve the reporting in Intune. It doesn't come anywhere close to VMware Workspace when it comes to their reports. I am sure that Microsoft will improve but at the moment, they are underperforming in terms of reporting.

There is a feature called dynamic groups, which populates users and computers based on a query that is written, and it runs at some interval. I would like to see this updated more frequently so that the users don't have to fair for too long before computers appear in the group.

I would like to see the ability to deploy custom packages as a Windows 64-bit package, as opposed to the Windows 32-bit, which is the only one available now. Although it can run in 64-bit mode, I would like to see this supported natively.

I have been working with Microsoft Intune for about two years. I have changed companies since that time and we are now evaluating Intune for use in my new organization.

Intune is a stable product and it has improved a lot over the past year. This is something that Microsoft is always working on, and I think that it will continue to improve.

We have not had the chance to test scalability. We will have the real results when it is put into the field.

I have not been directly in contact with the support for Intune. Rather, when I have needed assistance, I went through a partner channel.

I set up Intune without any assistance.

The price of Intune is included with the license for Office 365, so we don't have to pay anything extra for it.

We are currently evaluating both Microsoft Intune and VMware Workspace, and we will choose the one that best suits our use cases. Our plan is to implement one of these products in a couple of months.

One of the conditions is that we have to make sure that it supports all of the devices that we have in the enterprise. For example, we have Windows, Mac, Android, and iOS devices that need support.

Second, we need to have the autopilot experience for the users running under Windows. If somebody joins the company and they are provided with a laptop then we need to have it set up correctly. Normally, when it ships from a vendor such as Dell, Lenovo, or HP, it will come with their software pre-installed. Given the current situation with employees working at home, the laptop ships directly to where they live. At this point, with autopilot, they should be able to log in using their cloud credentials as soon as the device is switched on.

Once logged in, all of the details will be picked up from Azure, including the policies, updates, and other mandatory software such as Skype, Zoom, and Microsoft Office. Essentially, it eliminates all of the laptop setup and configuration that used to happen inside the organization.

Intune supports autopilot natively through Azure, and VMware Workspace is on par with this as well.

Next, it should have good reporting features. All products are able to generate reports, but we should be able to customize them in the way that we want.

We also have to have good security, where we can push all of the security configuration and policies that our organization has. This will differ based on the department. For example, security in banking or finance will be different from the security in manufacturing.

Finally, we should be able to deploy applications all over the cloud.

I think that in comparison, VMware Workspace is a more mature product than those offered by competing vendors. It has been developed very intelligently. The UI is good, with fancy graphics. They also have Smart Groups, and a different way of deploying applications, which are very good features.

VMware Workspace also has a slight advantage over Intune when it comes to managing multiple hierarchies. Intune does not support this type of structure, where you can have sublevels. For example, I can have a root-level like Europe with sublevels such as the UK, Germany, and France. 

The suitability of this product depends on your environment, requirements, and use cases. If you have a reporting-extensive company, for example, then you may need to look for other products. Similarly, if you are a multi-hierarchy organization with a presence around the globe, then Intune may disappoint you.

Given all of the factors and things to consider, including features and cost, I would say that Intune has a slight edge over competing products.

I would rate this solution a seven out of ten.