Microsoft Intune Reviews

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.

We use Microsoft Intune for application deployment and for some of their security policies and end-devices policies. We also use it for patching. Patches for Windows 10 devices and MacOs, we're still figuring out what to do because we don't have many options on Intune for Mac operating systems. Patching and looking for OS deployment as well. Operating system deployment.

Within our organization, there are roughly 150 users, using this solution.

We use Microsoft Intune on a daily basis. What Microsoft does, is it releases patches every month. The device hash reports to Microsoft Azure Intune. If you want it to receive patches or policies, which you have created on Intune and you have deployed, then the device will receive the policies and patches only if it's online and connected to the internet. Whenever the device is online and connected to the internet, it's connected to Intune. You don't have to worry about having an additional agent or anything on your devices.

Patching for Windows in operating systems is great. Most organizations are going remote now due to this pandemic, so patching is one of the most feasible solutions we can think of — patching end-user devices. Application deployment and keeping the devices secure no matter where they are, by having this cloud solution — that has been great. Deploying the security policies to the devices. 

There needs to be more support for Mac operating systems. Support for patching, because we have very few, or minimal options from Intune for patching Mac operating system.

In the next release, I would like to see better compatibility for Mac operating systems — that would be really helpful. Also, if the support for Mac was as flexible as it is for Windows, that would be really appreciated.

Personally, I have been using this solution for the past 13 months.

I haven't experienced any issues relating to stability.

We have spoken to the technical support on a few occasions. They have only ever provided us with minimal information. 

We used to use a SCCM or System Center Configuration Manager tool; it was also provided by Microsoft, but it's an off-prem tool. You need an on-prem setup and a server operating system and everything. On that server operating system, you can install this tool and start using it. We also used another tool called Automox, which was a patching tool. It's only meant for patching devices, different operating systems, Linux operating system, Windows, Mac operating system; however, it didn't have support for mobile devices.

The initial setup is a very simple process. You don't have to do anything on on-prem. Since it's a solution from Azure, it's a software service. You just have to buy the subscription. You just need to have the license in place and then you can just start using it. There is not much setup involved. If you want to integrate your Azure solution with your on-prem solutions, then you have to do a bit of integration.

If you're going with standalone Intune, you don't have to think of setting up anything. You can just use it, pay for whatever your problems are, find a solution for that, and start using it — that's all. You don't have to worry about the setup for standalone Intune.

All maintenance is handled by the vendor.

Licensing depends on how you are providing support to your enterprise, whether it's device-based or user-based. If you're providing device-based support, you need to buy a device pertaining license. If you're providing support for users, then you have to go with user licenses. If are integrating Intune with FSCM, which is an on-prem tool, then the same scenario comes in either devices or users.

If you are providing support only for devices, like device-based policies, with Intune, there's a type of policy that allows you to deploy to either the devices or users. If you're looking for a solution where only devices can receive it, rather than users, in that case, you need to purchase only one license for Intune — I'm talking about integrating Intune with FSCM. You only need to purchase one license. Since you have already purchased FSCM on-prem, Microsoft has that flexibility; you can extend those licenses with the devices as well when you're integrating the devices with Intune. I don't know about the pricing, but I know about the licenses.

I would absolutely recommend Microsoft Intune. Currently, I would definitely recommend any cloud solution. Most organizations were actually using on-prem solutions for managing their enterprise devices. Now, since everything is remote, people are confused. How can they manage their devices the same as they were before this pandemic? If they find Intune very pricey, they can go with another cloud solution. Intune it's very user-friendly. You just have a screen and console and you can just go in and start deploying anything. All you need are the user guides, which are fully-available with Intune.

Intune is a very good cloud solution for managing devices. They could actually make it better by putting everything together, in one place, like other MDM solutions are doing. If you compare Intune with VMware, VMware also has an MDM solution called AirWatch. Intune should compare itself with other MDM solutions and try to bring up those features as well. For right now, I would just say it's a very good solution for managing remote devices.

On a scale from one to ten, I would give this solution a rating of six.

The use case for this solution varies depending on the user's requirement. Some are only interested in MDM, while others are interested in managing Windows plus Mac. It really depends. We are partners and provide on-prem, cloud and hybrid services to our customers. I'm tech lead infrastructure operations. 

Lately I've been working on the Remote Wipe and Autopilot. Autopilot is one of the best features because we can use it during remote migration. It especially helps in this pandemic situation where we don't need any end-user computing engineer support. If someone wants to remix a machine, we can initiate it remotely.

An improvement would be if we were able to leverage more iOS device management internally. My goal is to manage all the tools in one centralized tool. Intune does 30 percent of Mac management, but if it could have complete management including patching and automating for Mac devices, that would be good.

I've been using this solution for three years. 

This is a stable solution. 

This is a scalable solution. 

I have been trying to contact technical support but haven't been able to reach anyone. I have a couple of questions to which I haven't been able to get any answers. 

The initial setup is pretty straightforward.

The cost is fair but it would be helpful if they would segregate the licenses. There are a lot of features that many of our customers don't need but have to pay for because it comes as a bundle package and we're unable to exclude anything that is not necessary.  

I also work with Jamf Pro but you can't compare the two because Jamf Pro doesn't have real-time features and it doesn't do most of the things that Intune does. 

If a customer is looking for a macOS solution, I would for sure recommend Jamf Pro. If it is for Windows and macOS in a combined environment, then I would recommend Intune for managing it. The consideration is based on the customer's macOS family, based on how many users they have. If they have 100 users, then we can still manage it through Intune. If it's a complex environment, for sure we'd need Jamf Pro.

I would rate this solution an eight out of 10. 

We are a consulting agency and we help people make technology and business decisions. 

Our environment is fully online and we're a Microsoft 365 shop. We are using Intune for security. It is their MDM for mobile devices, but it is also their application ADM and it works on desktops as well.

We primarily use it to maintain compliance for our customers. They require that we use it to enforce compliance with the same level that they do internally, so we're following the compliance guidelines of several Fortune 100 companies. Intune is what we use to meet those requirements.

Using this product has completely stopped DLP, so people cannot take material off of corporate machines or corporate imagines, and that's a huge benefit.

The biggest thing for us is enforcing logins only from devices that are managed by Intune.

We also use it for enforcing DLP and all of the other security policies that you need for compliance in order to do work for major corporations.

It integrates well with the Microsoft environment. Once it's deployed, it's set and forget.

Once it's configured it is unobtrusive, but it does take some hands-on to configure and deploy it properly.

I have been using Intune for a year.

Intune has been very stable.

We're a small company of fewer than 100 people and it scales well enough for us.

We are financial analysts and IT consultants.

I have not used the technical support personally, but it seems to be okay.

We used a third-party package before, and we moved to Intune because it was easier to integrate with Microsoft Windows or Microsoft 365. It also provides coverage for desktops.

The initial setup requires user participation. You can't push it without the client being engaged. That is part of the configuration.

Overall, this product works pretty well. Security products are the disgusting medicine that we don't like to take, but we have to take it to stay healthy.

This is a good product because it's transparent and works well, although it's unfortunate that we have to have it.

I would rate this solution a seven out of ten.

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

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

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

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

I have been using Microsoft Intune for five years.

This is a stable product.

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

We have approximately 30,000 users.

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

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

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

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

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

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

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

I would rate this solution a seven out of ten.

We are using this product for enterprise development within our organization.

The primary use is for building Unified Endpoint Management (UEM) capabilities.

The most valuable feature is the UEM capabilities.

The user interface should be improved because it is a little bit slow.

It does not have support for containerization.

There is no catalog for mobile access management (MAM) security.

I have been working with Microsoft Intune for more than six or seven years.

Because we are doing a PoC, there have been no issues with scalability as of now.

We started with a user base of 5,000 and are aiming to have 30,000.

Because we are still in the PoC, we are only testing it with a few users.

We have not been in touch with Microsoft technical support.

The configuration is straightforward and there is nothing complex about it.

Intune is a good product for UEM, which is helpful for Windows 10 management. However, for MAM, there is lots of improvement needed. For example, the application catalog should be there.

I would rate this solution a six out of ten.

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

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

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

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

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

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

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

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

Those are some of the different use cases.  

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

We are using Microsoft Intune to control, manage, and to protect the data on mobile devices.

The most valuable feature is the scalability.

There are differences in protecting the data on a mobile device and on iOS. When you protect the data on iOS, you protect the entire device.

From an Android, you can select certain applications to protect. What this means is that the employee who uses Android devices are protected only from emails, and the personal data on the device is not protected. When the employee uses the iOS they control all of the devices, which is not convenient.

There are items that require improvements. One is the controls from iOS.

I have been working with Microsoft Intune for approximately four years.

We have not experienced any bugs or glitches with this solution.

We have not had any issues with the scalability. We have more than 1,000 users.

We have contacted technical support several times.

Technical support is sometimes okay.

The initial setup is a bit difficult.

It took almost a month to deploy. There were several requirements to set up the conditions.

I would recommend Microsoft Intune.

I would rate this solution an eight out of ten.