Microsoft Intune Reviews

We use it to a small extent for approximately 1,100 devices. The biggest portion of it is used in the Aviation department, which is one of our departments. They have invested heavily in some customized software that they've developed in-house. It is put on the devices, and the devices are primarily used by field staff. It's basically a mixture of work order assignment and work order management, as well as record keeping. For example, I could have a technician who is assigned to go and do a preventive maintenance inspection on an HVAC component in one of the terminals. That request or work order is submitted to his device. When he gets there, he scans barcodes for the room he is in and for the piece of equipment that he is working on. So, they track their actual work order, work order status, workloads, and equipment life cycle, and that's all done through Intune.

It helps us in securing devices. It has eliminated a lot of paperwork. It has simplified record-keeping and maintenance of equipment, life cycle management, staff workload, work hours, et cetera. That's the biggest impact on us, and that's also where most of the devices are used.

Its security is most valuable. It gives us a way to secure devices, not only those that are steady. We do have a few tablets and other devices, and it is a way for us to secure these devices and manage them. We know they're out there and what's their status. We can manage their life cycle and verify that they're updated properly.

It doesn't economize when you scale up. We have over 14,000 employees, and we have between 7,500 and 8,000 city-owned or personal devices being used to conduct city business. Its price can be improved. It is not a cheap solution.

It has been years since it was implemented.

Its stability has been fine. We've had no issues at all.

I don't see any issues with it. We currently have only about 1,100 users and licenses for the Intune product. The largest portion or over 50% of usage is by our Aviation department for tracking and managing their work order, workload,  equipment life cycle, etc. Other users are scattered in small numbers throughout a number of departments. 

Our Parts department also uses it. One thing that's a little bit unique is that they also have these assigned to temporary workers. So, we provide the licenses for a number of temporary workers for the summer or for the winter, and then we take them back and reassign them to somebody else. 

The other departments mostly use it for educational or small use cases where they think this will be a good fit, and it is the product that is available to them. I've heard nothing bad about it, and I have no problem at all with Intune.

In terms of future growth, we're currently looking at another product, but that doesn't mean we're going to go with that other product. We're working with a vendor on another solution, and that vendor also has a mobile device management product, but we're not yet ready to go there.

I've no direct input on it. Right now, we're on unified support, but we've always had their premier support. If we ever have a problem with any of our Microsoft products, including Intune, we do have a way to reach out and get additional assistance.

I'm not aware of any other solution being used. I know there were one or possibly two failed mobile device management project implementations. I was not a member of the department then, so I don't know the details. I only know that both of the deployments failed. In other words, either the vendor promises were not met, or we found a function that was supposed to exist but did not exist. 

It was pretty straightforward. It was not a very long, complex, and involved process. It was fairly easy to set up.

It was done in-house. For its maintenance, we have no one dedicated to it. Our client computing side takes care of that.

I've never tried to quantify an ROI for the program. We have just a small number of devices. At some point, we will look at implementing large-scale mobile device management, and that'll be a different case where we may look at Intune, Workspace ONE, or another product.

It is not a cheap solution. The price for a device when you start using it at a large scale can be improved.

It is covered under our enterprise agreement. We pay once a year. I am not aware of any additional costs.

It meets the basic security needs and management needs for most organizations. It allows you to monitor the security of devices and manage those devices if they're organization-owned. It is fairly easy and straightforward to manage. It is not difficult. Some of the other solutions are a little bit more difficult.

I would rate it an eight out of 10. It meets all the basic needs that most organizations will have for device management and device security. I am not sure if it can provide the required level of security for different business scenarios that require additional security, which means you'd have to run two systems in tandem.

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.

The primary use case is to safeguard the company's data. My management wanted to categorize the applications and ensure privacy and security in terms of corporate applications versus personal applications on corporate devices. We began to prioritize B objectives in 2013 and 2014, which is why it is essential for the organization to prioritize its categorization. To accomplish all of these objectives, we embarked on a successful journey.

Since Microsoft Intune has provisioned data, application, and device security, it helped us significantly increase our security posture.

We restricted certain geographical locations with which we are not doing business, which minimized risk, and Microsoft Intune's conditional access feature helped secure our environment from a recent hacking attack originating from a specific country.

The conditional access feature in conjunction with Microsoft Endpoint Manager is a fantastic combination.

The device profiling which uses the official Outlook email enabled us to control the screenshot feature and prevent copying outside of the organization's application. This is really helpful in controlling data breaches.

Microsoft needs to enhance device-level security, as sometimes when using Microsoft Intune, the device's operating system becomes stuck and requires a full uninstall to remove the Intune bug.

The price of the solution has room for improvement.

I have been using the solution for almost ten years.

The solution is extremely stable.

The solution is scalable. We have 300 end users in our organization.

Prior to the COVID pandemic, the technical support was excellent, but since then there has been a marked decline in the quality of support.

Neutral

We previously used VMware Workspace ONE which is a very good solution and in some areas better than Intune, and Cisco Meraki Systems Manager. We switched to Microsoft Intune because of the better integration with Microsoft products.

The initial setup is a bit complex. Initially, we deployed for the executives of the organization. We deployed Microsoft Intune for one hundred users in the first year. After receiving positive feedback, we expanded our model and provided security for all the major executive users of our organization, protecting their data, devices, and applications. We had two administrators and six service desk screen engineers deploy the solution. In addition, our two administrators were verifying the policies and implemented the solutions on end users' devices.

The implementation was completed in-house.

Microsoft Intune is a very good solution and in time I am sure we will see a good return on investment.

Microsoft Intune is expensive.

I give the solution a seven out of ten.

There is no external maintenance, but at the device level, we must adhere to Microsoft's patches and policies and keep our devices up-to-date with the latest patches. The company portal may not allow for older versions, so we must ensure that the solution is kept up-to-date.

Microsoft Intune is a very good solution and when compared to VMware Workspace ONE, it is a strong competitor. I would not call it the topmost or leading product in this domain, however, with Microsoft's progress, I'm sure it will be a leader in a few years. On the Microsoft side, they may need to improve their support system and build releases of the solution.

We are going to use Intune for registration and then we're going to use some kind of condition policies for resource access for unmanaged devices. With on-prem AD-based access, when the users are working from home or somewhere else, they need to connect to the VPN or something to access the corporate network, whereas, with Azure and Intune, we are going to provide the resources for application access. We can directly provide them access by using conditional policies.

It has been only three months since we took the Azure subscription and migrated all the users to it. We are running it in the production environment. We are not running it in the testing environment. We are not implementing everything in one go because if any issues happen, it's not easy to roll everything back in minutes. For this reason, we're implementing them one by one.

With on-premises Active Directory, the main challenge was that we had no control when a user was working from home. We didn't know what exactly a user was doing and whether the AV was up to date or not. Intune provides better control of their machines.

A few of the options are a bit hard to understand. As compared to on-prem services such as AD, it's a bit different. For example, group policy objects have different names. It takes some time to find out where various options are available.

I wanted to check if there is any provision at the Intune level to restrict certain things, such as a website, but unfortunately, that feature is available only in Microsoft Defender. Intune has web filtering capabilities, but they are only useful for protection from malicious websites, whereas we would like to be able to restrict a website. For example, YouTube is a clean website. No one would identify it as a malicious website, but if we want to stop the end-users from going to that website, we have to go for another product, such as Microsoft Defender or another third-party proxy solution. It would be great if this capability is included in Intune.

We started using it three months ago. 

Over the past three months, I haven't seen any instability from the Intune point of view.

We have approximately 220 users. We don't have any immediate plans to increase its usage, but by the middle of next year, we might increase the usage of the product to another 70 or 80 people. We would be able to scale it based on our needs.

I haven't raised any case with Microsoft support, but I believe Microsoft has different types of service agreements based upon which they provide support for different applications. 

I have gone through multiple Microsoft articles, and they have sufficient to-the-point information there. 

We were using on-premises Active Directory, and we were restricting certain things through GPO, but there were a lot of challenges when the users started to work from home. 

Its initial setup is fine. I haven't seen any issues. I have worked as a technical lead at the architect level on different products. For that reason, I haven't had many challenges.

Its implementation was a bit longer because we took our time in testing on multiple machines and multiple users. We wanted to ensure that we are able to achieve what we wanted. We completed all the use case scenarios and what we were expecting from the security point of view.

We implemented it in-house. We had two people for the setup, which included a junior person and me. 

We also take care of its maintenance. We are managing approximately 220 people. I take care of all the cybersecurity and software-related work at the corporate level. Most of the people are now coming to the office. So, we have prepared a simple document for them to follow. 

We don't have just the Intune license. We have the Enterprise Mobility + Security E3 license, but I don't have the exact figures. Someone else was involved in the initial discussions and purchase, and the entire environment was handed over to me.

Any bundle package, such as Security E3, covers multiple things, such as AAP, BitLocker, etc. If you go for them individually, they would be more expensive. Bundling makes the price more attractive and competitive.

It is suitable for small, medium, and large companies, but it also depends on your requirements, budget, and the things you want to restrict. 

I would rate it a nine out of ten.

The solution is deployed on cloud. I'm part of the support team. There's another server team that works closely with Microsoft. They purchased an old 365 license, and Intune was one of the included features. We wanted to take advantage of the feature because it was part of the package. That's why our top management decided to save some costs by making use of Intune and not using AirWatch anymore.

We are enrolling through the Intune company portal, and then we are using the Outlook app to configure the email addresses of the company.

We are using the mobile feature, and we are also using MDM to lock the devices, to push restrictions, et cetera. Compared with AirWatch, I think it's easier to manage the devices and the profiles in AirWatch. Intune has a lot of options, but I've only been playing around with it for a few months.

In the past, I raised some tickets for the enhancement feature, which was missing in Intune. It can take a long time for these features to appear, or maybe they will just never happen.

There are certain things that I'm trying to replicate from AirWatch, and it's not possible.

In AirWatch, we have a launcher, which is like a container. You can choose single-app mode or multi-app mode. But in Intune, for example, you need to factory reset the device and then apply the MDM. If we choose multi-app mode, which is the kiosk multi-app mode in Intune, I cannot lock the application on the screen. For example, in the set mode, you have the option to set the leave Kiosk password. You can exit the kiosk. But if you choose Intune multi-app mode, you don't have this leave kiosk option. For us, it's very useful.

If you have this leave kiosk option in the multi-app, you should also have it in the single-app mode. We need this because we have an application that you run on a tablet in hotel rooms, and we want to lock the application in a single-app mode, but besides the application, we also need to have some background applications running, like we need to do some configurations in Knox from Samsung, and eFolder. 

We have three applications that we need to push, but the guests will only be able to see one. Because I don't have the option to leave the kiosk in the single-app mode, I cannot do any configuration in the background apps. We have one app we cannot migrate to Intune from AirWatch because of this issue. This applies to more than 2,000 devices.

I think we need the leave Kiosk option available for the Kiosk single-app mode, because we are stuck with at least 2,000 devices or more because we want to completely retire AirWatch, but we cannot until this feature is available. The applications that we are using in our hotel rooms are not compatible with Intune. My bosses are not really satisfied because we still have expenses with purchasing a license with AirWatch because Intune cannot really fulfill our requirements.

This option is already available in the multi-app mode. It should not be a new feature. This feature already exists. They just need to apply the single-app mode the same way they're applying the multi-app mode.

Compared with AirWatch, Intune is not very stable because I haven't had to deal with these issues. With AirWatch, I would try to fix something and I would need to fine tune the settings, et cetera. But once I fine-tune and push everything, it will run and be stable. With Intune, we are new with this product, but it took some time for me to create a profile and test the devices. It has been working for a few months, but then suddenly this weird issue happened. It affected all devices at once.

In the Outlook application, the scalability is good so far. But there are some differences between on-premises mailbox users and cloud users. For example, let's say I'm my boss's assistant and I'm able to view my boss's calendar on my Outlook desktop. Let's say I want to view a shared calendar on my Outlook app. For the cloud-use mailbox, I'm able to do this, but if I'm an on-premises mailbox user, this option is not available. Usually the cloud mailbox users have more options than on-premise users.

We have around 2,000 users enrolled in Intune so far, not counting the MDM device. That includes just email, the one that I have enrolled in the Outlook email app.

Our plan is to keep the solution because our primary solution for email mobile is now Intune because we are retiring AirWatch. We have already retired the email for AirWatch, and we are just using AirWatch for MDM devices. Of course, the plan is to keep increasing usage. If more users request email on their mobile, we are going to offer Intune.

Technical support is very responsive and helpful. There's another issue that I raised related to Adobe Acrobat. I'm not sure if it's a region issue, but I'm in Macau, and we also have some users in Manila, Hong Kong, and Cyprus. All of us are using the same profile. I make the Adobe Reader application available on the manage app store, but somehow the users in Macau, when they go to the manage play store, are not able to see Adobe Reader on the list. It's only happening in Macau.

I raised this issue. Support dragged the issue on for two months. Support said, "Because all the applications go through the Play store, maybe you need to reach out to Google." The issue was not really resolved because the issue might not be related to Microsoft but Google, et cetera. I just gave up.

Compared to AirWatch, I can upload APKs or I can just redirect the Play store link to push the apps. But in Intune for example, I'm forced to upload all the applications through the managed app store. To make it available is a different process, basically. There are some things that don't really stretch forward. 

If I upload a custom APK in the manage Play store and then I want to remove it, I cannot remove it myself. I need to send an email to Google and ask them to remove it. Then they will ask me to unpublish the app for 24 hours first. These are very simple things that I should be able to control myself, and it wastes a lot of time.

I think if you have the money and want something more stable, you should go for AirWatch. I don't think Microsoft is offering the same stability as VMware at this point. On other hand, I think the support from Microsoft is better, particularly the support in Asia. In VMware, all the support is from India, and sometimes I have a hard time with them.

Now that I'm starting to be familiar with the profiles, it's starting to get easier. A few weeks ago, there was a very odd issue that happened also related to MDM devices where we were using the manage home screen application to lock down the apps that we wanted to allow only the users to use, like the kiosk application.

We have configured the profile and have deployed to 200 or 300 devices. Some of our users called and said suddenly all the mobile devices were flashing. I don't know what happened, but it happened at the same time. The workaround that I had to do was to remove the manage home screen from the profile. Then all of the devices were kicked out and went back to the home screen of the devices. That was the only way they could resume the mobile devices. I don't know what happened, but something was wrong with the manage home screen app on that day because a few days after, I pushed back and everything resumed.

We have ROI because we are retiring AirWatch, so we're spending less and making the most of the free stuff.

The licensing is on a yearly basis.

I would rate this solution 7 out of 10.

Intune is our primary tool for managing our devices, including security profiles, confirmation profiles, applications, deployment, updates, etc. It manages all of our workstations but not the servers. It helps us manage and monitor devices, but we use Microsoft Defender for threat discovery and things like that. It's all within the E5 license. We also manage Android and iOS devices. 

Previously, they were using SCCM. It's an on-prem server, so you must maintain, update, and secure it. With Intune, you don't have to manage anything. Everything is available through a console on the web, so I think it's way better.  Enrollment and deployment are easy. 

Intune helps us protect data on the end-user computers, but we need another solution for the servers that Intune does not cover. However, we group computers and the endpoints with the security panel and connect them to Microsoft Defender. Everything reported in Defender can be customized in the Intune security section, like the security rules, local rules, firewall rules, exclusions, etc. 

Intune reduces the risk of security breaches because we follow some well-known security baselines that we translate into configuration and security profiles and apply at large. It's helpful for pushing out security stuff.

Intune is effective because of the configuration management and endpoint security it provides. The graphical interface makes it easier to configure and deploy devices. 

Intune has some limitations when it comes to application updates for third-party applications. You can schedule an update, but when it's a package setup, you need to supercede and replace it each time.  

I have used Intune for three years.

I rate Intune nine out of ten for stability. 

I rate Intune eight out of ten for scalability.

I previously used Microsoft SCCM. 

Intune is all on the cloud. I wasn't there when they migrated. 

I would say Intune is totally worth what we pay for it because you can customize and do everything related to the configuration, security policies, monitoring, etc. 

 Intune is included in the Microsoft E5 license.

I rate Microsoft Intune eight out of ten.