Microsoft Intune Reviews

The primary use case of Microsoft Intune is for patch management and app deployment.

Microsoft Intune is deployed in a hybrid environment and we use Atel cloud.

I can see that the patch management process is much improved with the bundled patch management option available in Microsoft Intune compared to the KPI deployment required by the other deployment solutions.

Deploying an app can be a complex process due to dependencies. For example, I have a package with three files that need to run, but one of them has a dependency on another one. This can be challenging to manage with the Intune app deployment and has room for improvement.

I have been using the solution for one month.

We have premium technical support from Microsoft.

We currently also use BigFix.

We have not yet implemented the solution but the app deployment is a bit complex.

When we add a device to the Azure domain, the activation process for Intune is simple and straightforward with no added complexity.

We partnered with Microsoft to help us implement the solution in our environment.

Intune is cost-effective as it is included in some of the Office 365 packages. GMF can be more expensive.

We evaluated Jamf Pro and will be rolling it out for Apple devices.

I give the solution a seven out of ten.

As of now, we deployed the solution onto 10,000 devices and when completed it will be 30,000 devices. The solution is used in multiple departments in multiple geographical locations.

Microsoft Intune is a Windows solution, and organizations can take advantage of its features. However, I would not recommend using iOS devices with Microsoft Intune as it is suited for Windows only.

We use the solution for auto-enrollment with app EPP and application deployment with EPP.

We're currently testing the possibility of using the solution as a new MDM tool for mobile applications.

All regions and departments operate on the same model; we turn on the device, select if it's personal or corporate, and all the products and profiles are loaded onto it.

The solution hasn't improved our organization yet, as we're still in the testing phase and have yet to go into full production.

The ability to switch between Affinity and non-Affinity enrollment is great. 

The wiping features are very good. 

The capacity to create more profiles and switch between corporate and personal devices are beneficial features.

One of the main advantages of Intune is that it's a Microsoft product, so it integrates with the other MS products we use.

The solution needs to be better for managing laptops; many functions are still unavailable in this regard.

The scalability could be improved, and like most other MDM products, Intune is good but not 100% there yet.

We've been using the solution for a couple of years. 

The stability is good, and there has been a lot of progress since I last used the solution.

The solution is working well for the most part, but some improvements could be made to the scalability. 

I never had to contact technical support. 

I previously used MobileIron UEM and VMware Workspace ONE.

I wasn't involved in the initial deployment. Now that it's set up, deployment to devices requires turning the phone on, and the device will automatically pull up the profile if the client is linked to our Apple Business Manager tool. We currently have one staff member involved with the maintenance, but we're looking into distributing it to others on the same team.  

The pricing for Intune and the competitor products are all within the same range, there is no true advantage when it comes to cost. 

I evaluated MobileIron and VMware. 

I rate the solution seven out of ten. 

We have yet to reach a level where we can notice flaws or identify areas for improvement since we're still checking and have yet to run the solution through a capability list.

My advice to others evaluating Intune is that it's the best solution for mobile devices like Androids and iPhones. However, if you're rolling out physical laptops, I recommend using a second tool, as there are still many unavailable options on the Intune app for laptops.  

We use Intune for device management, including policy management, application deployment, and patching.

Intune helps us evaluate and manage devices remotely. The solution enabled us to increase the security posture on all devices using compliance policies and configuration profiles. It took us a while to roll these things out because users were uncomfortable with the changes, so many pushed back on any limits to their freedom of access. 

After a couple of months, everyone realized that we were trying to ensure all their devices were working as effectively and efficiently as possible. It took us about three to four months before we began realizing the full benefits of Intune. 

Intune's most valuable features are the device, compliance, and configuration policies.

One area for improvement is app deployment. Another is the Windows update rollout. If you're rolling out an object to a device that's offline, Intune stops trying to reach this device after it sits idle for a bit. We are forced to find a workaround that could help manage that.

We have used Intune for about two years now.

Intune is stable. 

Intune is scalable. 

I rate Intune support a 10 out of 10. They're responsive.

Positive

Setting up Intune wasn't straightforward. It took us about three or four months. We did a test phase and rollout then collected feedback. Based on that feedback, we did another test phase and rollout. Initially, we did it in-house, but we got stuck, so we reached out to Intune support. 

It would be easier with one person, but the person doing the deployment needs to work with various teams, like cybersecurity, infrastructure, and IT.

We have seen a return. Using Intune, we've effectively ensured all our devices are compliant based on our own redefined compliance policies. It is also highly efficient.

Intune is inexpensive. It also comes bundled in some Office 365 licenses, so you can choose to purchase it separately or as a package. 

I have used Manage Engine, SolarWinds, and Desktop Central. We switched to Intune when we realized it was a full-fledged MDM that covers mobile devices, desktops, and other pieces. The other solutions had more RMM features for device management but fewer MDM features. Intune was a better fit for our requirements,

I rate Microsoft Intune a 10 out of 10. Intune is an excellent solution if you're a technical person. Be careful with macOS enrollment, which still needs a lot of improvement.

Generally, the top three uses are operating system deployments, software updates and patching, and software deployments to endpoints.

If you're a small shop, a two-person organization, yet you have many endpoints, five to 10,000, you can easily manage them. You can manage the masses with one person part-time and it's a good automation tool that takes away the need for multiple folks to do a lot of things in the environment like software deployments or patch management. It's very good at automating those functions.

The reporting aspect is very nice. It's got about 450 canned reports in it. They're easily customizable. You can get really good granular reports for inventory, patch management, status, and everything. It's very good at reporting.

It's not hard to set up. It's easy to manage.

Third-party patching and other solutions integrate with Endpoint Manager. From that perspective, there's no deficiency. 

The UI is good. You can filter things out so that you'll only see things that are pertinent to your function. 

It's really matured and improved over the years by assimilating competing products. There are a lot of things that used to be better than Endpoint Manager or not available in Endpoint Manager that were absorbed or purchased and placed into this product. From a deficiency perspective, I can't recall coming across anything substantial. I'm trying to think of a weakness. I compared it to Ivanti. From a new user's perspective, it may be a little overwhelming because there are quite a few things to look at in the console, however, once you are sort of acclimated and are familiar with your core functions, it's fairly simple and straightforward.

You can modernize the UI a little bit, however, change for a sake of change isn't always a good thing.

I've been using the solution for 25 years. It used to be called SCCM.

The solution is very stable.

The scalability is great.

The largest user base I've ever supported, for example, was a headquarters and they had 220,000 endpoints. In contrast, small colleges and educations may only have 500 users, so they can get by with a single server hosting everything. SQL and everything can be one server.

For us, the solution is extensively used.

If you're looking forward to deficiency, I'd say that the Endpoint Manager support at the lower levels is poor. As you go higher and you get like a more engineering level, then you're fine, however, the early stages of support are not the best.

I've worked with Ivanti and LANdesk and other tools.

I've used Endpoint Manager every day. I'm currently using it. I've been using it for 25 years. However, there are other ones like BigFix, which I've rarely used. I've used LANdesk a few times. And people would try to use LANdesk to avoid the expensive Endpoint Manager, however, at the end of the day, it costs them more in time to use the LANdesk solution. Ivanti is a competitor, however, they're cobbled together with Shavlik, for patch management they've got Altiris. They bought Altiris and Altiris has been passed around like a cheap hoe from Symantec to Intel, to everybody.

Altiris was actually developed to support Endpoint Manager and provide asset management. At the time, Endpoint Manager didn't have good asset management, so they actually worked with Altiris, only to find out that Altiris was actively taking Microsoft customers. Microsoft booted them to the curb and they haven't done well since. That was back probably in the late nineties that they did that. Endpoint Manager has been around the longest, it's survived, it's matured and it's the top dog in general.

Complexity-wise, it's not hard to set up. It's just a lot of small steps, such as making sure the firewall ports are open and certain things are in place, and all the perquisites are taken care of, as the wizard, the installation wizard for Endpoint Manager, is pretty straightforward. As long as you have SQL and some other features turned on to support the different functions of Endpoint Manager, you're fine. You'll need WSS or you'll need WSS for patching and you'll need SQL reporting services for the reporting portion of it. All those small things. The more lights you turn on, the more configuration you have to do.

The deployment itself took me four hours end to end, to put all the prerequisites in, however, understanding, of course, may take a while for someone new. I've done this now for over 25 years. For me, it's pretty straightforward and I have, a lot of these things PowerShell scripted so it works very well. You can create a PowerShell script and set the whole thing up from Powershell, which is what I've done.

Maintenance requirements are low. Since it lives on SQL, if you put a SQL maintenance plan in place, it's pretty much, it's very healthy, it's very stable.

We've seen an ROI. It enables you to pair down the resources necessary for configuration management. You don't need a large shop to maintain your environment. If you want to develop it, if you want to create new images all the time and that sort of thing, then you're going to need to staff yourself accordingly, however, not necessarily to support Endpoint Manager, just to develop those and payloads that it delivers.

I'm a partner. I'm using the most up-to-date version of the solution.

While the solution was on-prem initially, now it's converted to more of a hybrid. They have co-management so you can manage on-prem and cloud together.

I'd rate the solution nine out of ten.

We have policies that need to be enforced regarding mobile devices accessing email and the corporate intranet. We have defined them in Intune so that the devices are not able to connect to the resources that they are not supposed to connect. This is the main use case for which we are using Intune.

It helps with security because everybody is not cautious. For security, it is quite useful. It has had a positive impact on the organization. We have zero tolerance for cybercrime. We do not want any threat to our systems. Intune has reduced the number of security issues. It helps to ensure that the devices are compliant and can connect. It also helps with some tracking.

We understand that as an organization, we are not supposed to interfere with users' personal data. We are able to use Intune to segregate the applications. It controls what they are allowed to see on the bank network.

We have three different categories of staff, and we are able to create and enforce policies based on each category.

We have an overview of the devices in terms of security compliance and from where they are connecting with our network. We can also do root cause analysis when there is any issue. It also helps prevent data loss. If a user is doing something against the policy, it can inform the user.

We have good visibility over mobile devices and workstations. If we have any problem, we know where it is coming from.

Intune has helped with productivity. Before Intune, we were not able to give access to some remote workers because we were not able to check exactly what kind of devices they were using. We had a limited number of people who could work from home. With Intune, we are able to check the devices to allow them. If they cannot finish their work in the office, they can continue from home.

It has helped with compliance. It has helped to ensure that devices comply with the organization's policy. If they are not compliant and secure, they cannot access the resources.

It would be good if, in addition to the minimal patching and compliance, we could also use Intune for application deployment. For instance, if a device is not patched, Intune should have the ability to push not only a Microsoft patch but also other patches, such as a browser patch.

I have been using Intune for six years.

It does not have any problem.

It is scalable.

We were not using any similar solution previously.

We have it on a public cloud. We have Microsoft 365. 

It is not difficult to maintain because it is in the cloud. It is important for us that the capabilities of the Intune Suite are integrated with Microsoft 365 and Microsoft Security for both cloud and co-managed devices.

We had a Microsoft partner for some configuration and training. We did not have any issues.

We have seen a positive return on investment, but it is hard to quantify the ROI and put a value on it. As a bank, we must protect our data, and the cost of losing the data is very high.

We did not evaluate other options.

I would recommend it to others. I would rate Intune a nine out of ten.

We propose Intune for information protection. We integrate Intune for application management and protection of company information on mobile devices.

It's normally able to meet 100% expectations of our customers. 

Sometimes, customers compare it with AirWatch, but the concept of Intune is different from other solutions. It's an application management app. It gets a bit difficult to explain it to customers, but it's not a product limitation. It takes a presale document or presentation to explain it to customers.

I've been working with Microsoft Intune for more than five years.

It's stable.

It's scalable. Our client has 1,000 people.

I'd rate them a ten out of ten. All of the ticket questions are answered. 

Normally, customers need a pilot. It takes around two or three weeks for the pilot. After that, we do the deployment. We start with a limited number of policies. Overall, it's done in three to four weeks.

We have five people in the company for implementation.

Its price is fair. It's a normal price. It isn't too expensive or too cheap.

Overall, I'd rate it an eight out of ten.

We use the solution to manage the Microsoft apps on company-owned devices. 

The product has eased the deployment of Microsoft apps to the devices. We can manage it properly. We can control it and push the updates. Another company helped us with the deployment. However, we can do it internally. 

Microsoft Intune's most valuable feature is easy management. It also keeps our devices secure. 

Microsoft Intune needs to improve the initial login process.

I have been working with the product for two years. 

Microsoft Intune's stability is good.

We have seen ROI with the tool's use. 

We don't have to worry about security after deploying Microsoft Intune. We can manage the security of our data and apps on the devices by using a single authentication mode. I will use it again if I have to make a choice. I rate the product an eight out of ten. You need to consider user experience when making the choice. 

Mobile device management is the main thing for which we are using it. My role is to review the implementation.

Mobile device management is most valuable.

We only have major classifications for iOS and Android, but there are different brands that have different cycles of updates. If they can fine-tune it to make it more brand-specific, that would be even better.

I've been using this solution for three and a half years.

It's stable. I'd rate it an eight out of ten in terms of stability.

It's very scalable. I'd rate it a ten out of ten in terms of scalability.

It was deployed for an environment with multiple locations. There are about 500 end users. Our clients are mostly small-sized organizations.

I'd rate the previous vendor with which we had the contract a ten out of ten. We now have a new vendor. They haven't yet started.

We used BlackBerry. We switched because that was getting outdated, and it didn't have all the features that Intune has. Intune is continuously being improved because of the cloud service.

I reviewed its implementation. It was straightforward. There were some technical difficulties in getting it started, but after we resolved them, it was easy. There were some architectural issues we had to resolve because we had legacy architecture.

It was a consultancy service that was provided by us. There were about five people involved. One was a specialist; one was an architect. There were two different engineers having different specialties, and there was a project manager.

We have an engineer who works on the maintenance. There is a team of two engineers to manage Intune as well as Office 365.

There were quite a few, but this was the main solution that we looked at because Microsoft solutions integrate well with other Microsoft solutions.

I'd advise getting rid of legacy stuff. You need to go to the new architecture and new OS. The infrastructure should be matching for the Intune implementation. Otherwise, you will have a problem. That's what we faced. We had to upgrade all our operating systems.

Overall, I'd rate Intune an eight out of ten.