Microsoft Intune Reviews

Our primary use case for this solution is to implement conditional access policies to restrict mobile users from accessing emails until their devices comply.

Intune should be much more granular in terms of supporting more devices. It is mainly only supported for Samsung knox devices. If you want to restrict the user, and not to turn on the camera and such, most of the policies that I found were more supported only towards Samsung knox devices. But, some policies are supported for Android 4.0 operating systems. Most of these policies are only for Samsung knox. I wish there was more diversity regarding other Android devices. In our country, there are multiple vendors, such as: Samsung, Huawei and more. I would prefer other solutions if I'm implementing restricting the devices in terms of applying the policies.

It has many features, but the most prominent is that other mobile device solutions support more polices. Much more diversion is needed in implementing the policies in different kinds of devices. As I have worked, it has not supported too many policies for android devices. Every 3rd or 4th policy that was supported is for Samsung knox devices. So, most people prefer to use Intune if they want to implement conditional access policies to restrict customer exchange online or exchange user formats emails until their devices comply.

You can publish Apps on the devices and take inventory of the devices, but it's all about the companies who were interested due to implementing conditional access policies to restrict  users. They want to restrict the users in order to access emails until their device is secure and then comply with the security policies of the organization.

Most of the customers expect that most of the policies will be there for Android, to implement the policies. Unfortunately, most of the policies that I found are for Samsung knox devices, that is specific to a device or specific to a vendor. That's why most of the customers have a hard time with Intunes, because most of the policies they see is for Samsung knox. They want Intunes to support Android devices. If it is supported by other Android devices, then it's very complicated because if you want it implemented, you have to use some custom equipment. There are a very limited number of policies that are applied, and all generate other devices like Samsung knox devices.

Most of the customers in the business do not use Intune because it doesn't support that much policy for Android. Here in Pakistan, most of the end users are using Android devices. Windows is out of the question. They don't use Microsoft mobile phones. Most of the popular devices are iOS, and the ultimate users are Androids. I think 80% of the users are using Android devices here and less than 20% are using iOS devices.

So, the customer is expecting to apply policy on Android devices and it's not generated specific to a vendor like Samsung knox, so they don't buy it, and they don't consider it.

Yes, it is a stable solution. There were a few stability issues, but most of us are happy with the stability of the solution.

I do not think scalability is an issue.

It was not easy, but not too complex. If an engineer knows what he or she is doing, then it is not difficult.

The product is offered as part of a Microsoft standard bundle. The pricing can be competitive to VMware Airwatch, and IBM MaaS360.

We considered VMware Airwatch and IBM MaaS360. 

From my experience if the requirement is to lock down the Android devices through Intune, then I should advise to look at the different policies that are available for Intune before doing the implementation. Because, if the policies do not meet the requirements of the organization to lock down the devices or to apply the policies on the devices, then it does not make any sense. So, for Android devices in particular, if you are implementing Intune then you should first look at the policies that are available in Intunes and then try to evaluate and do proof of concept.

We use this for management of all mobile devices.

We would like to see support for Chrome and/or devices for Chromebooks.

I have been using this solution for about three years.

The solution is stable.

The solution is scalable. We currently have tens of thousands of users within our organization using the solution.

I think customer support is quite good, we have enterprise support and premier support agreements.

Initial setup was straightforward.

Potential users should run a proof of concept. This can be done easily because Microsoft is offering a free trial period of one month.

I would rate this an eight out of ten.

The primary use of Microsoft Intune is for device management.

The solution is easy to use and it has good performance.

We can manage all our devices with the policies we want and it is secure. We can apply any policies we want, which gives us more flexibility.

There can be some added features, such as an improved dashboard. Any new feature that could be a benefit to our customers would be good.

I rate Microsoft Intune for approximately two years.

The solution is stable.

Microsoft Intune is scalable, we use it across many groups.

We have approximately 1,000 users using this solution in my organization.

I have not used the technical support.

We previously used AirWatch.

The installation is simple and it can be done quickly, within minutes.

We have a team that does the implementation of the solution.

There are licenses required for this solution. We enable licenses on the devices we need to manage.

We have an enterprise agreement with Microsoft. It is part of our E3 and E5 of our bundle company package. We are happy with the solution.

I rate Microsoft Intune a nine out of ten.

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.

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

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

We are a consulting firm.

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

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

The installation could be improved to be simplified.

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

We are Microsoft partners. 

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

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

Microsoft Endpoint Manager is quite stable.

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

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

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

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

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

SCCM is no longer active.

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

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

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

The initial setup is complex.

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

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

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

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 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 use Intune for endpoint management. We manage our workstations via Intune because we have remote users on and off the corporate network. It's deployed across over 500 Windows workstations. We're also trying to incorporate cell phones, but we haven't reached that point as yet.

Intune reduces the load on our on-prem Active Directory by having everything go to one Intune panel. That way, we can configure group policies, deploy applications, and manage devices. It has really improved our operations. In the past, the device had to be on our corporate network, but now we can provision a device remotely.

I like the group policy management feature, which performs application monitoring and device enrollment.

It would be nice to have a location tracker for the mobile device management tool. I'm not sure if it exists but hasn't been configured or if it's missing, but we've been unable to utilize the location features.

I have been using Intune for about two months.

Intune is pretty stable. It's also great for helping us maintain compliance in our environment. If it's a hybrid deployment, you should be fine as long as the sync is running. 

Intune is easy to scale because it's in the cloud. There are no limits on what you can manage.

Microsoft support isn't too bad, but it depends on the department you called. Intune support is better than support for Defender for Endpoint. I would rate it about a six out of 10.

Neutral

I was previously using on-premise Active Directory with group policy management. Intune puts your dashboard and panels in the cloud, but they sync with the on-prem Active Directory. Most of the management is done from in the cloud. All we need is internet access to manage the devices.

Setting up Intune was straightforward. Microsoft provided all the materials we needed, and we had support from their team. We had about five guys working on the solution. It can be from one to five guys, depending on the scale of the solution. 

We went through the reseller.

The price isn't too bad

Yes, we've tried ManageEngine and SolarWinds.

I rate Intune 8.5 out of 10. My advice to future users is to perform a proper inventory before enrollment. This is essential cost-wise. You need a good idea of how much it will cost per month so you don't overrun your budget.