Microsoft Intune Reviews

Intune provides a platform for managing all our devices, including mobile iOS devices and PC workstations. It can also control some aspects of servers.

We can automatically enroll our devices with Intune. It helps us implement company-wide policies and ensure regulatory compliance because we can restrict how company devices are used. Intune improves security by enabling us to set conditional access policies for each device. 

Intune can wipe devices. For example, if a disgruntled employee wants to leak the data on their company phone, Intune can terminate their access and wipe the entire device with a click. Conditional access is another essential feature. 

You can set up two profiles on every device to keep personal data separate from company data, and the employee cannot copy data between them. This is a critical requirement for most companies to avoid the loss of sensitive data.  

Intune doesn't provide much control over Windows servers. It's something we struggle with.

I have worked with Intune for six years.

Intune is mostly stable. Microsoft guarantees 97 percent availability throughout the year, so it's pretty stable. 

Intune is scalable. 

I have used multiple endpoint management solutions in the past nine years. I also work with Jamf, a solution that focuses on iOS devices. Compared to Jamf, Intune also has some limitations when working with iOS. For example, Jamf can create specific policies for each iOS device, whereas Intune can't go that far. It also has role-based and device-based features. You can do more customization on iOS devices with Jamf. 

The initial installation isn't too difficult, but it can be complex if you have a large number of devices and need to do lots of customization. It is more complicated to onboard Windows PCs versus mobile devices, which are pretty easy.

The number of staff members required also varies according to the job and the timeline for deployment. For example, I would probably need additional resources if I'm enrolling 20,000 devices in under a month. However, we don't need too many resources if we have enough time

Intune is a cloud-based solution, so Microsoft is responsible for maintaining the infrastructure. We only need to handle the administrative and configuration adjustments on our side. 

Most clients get the ROI they expect, with the exception of those organizations that primarily use Mac and iOS. Jamf is more appropriate for iOS users. You may need to buy two solutions if you have a mixture.

Intune is reasonably priced. When we design a solution, we always compare costs for the client, but I don't know the price of Intune off the top of my head right now. It varies depending on the size of your organization, the market, and the reseller. You can buy a stand-alone license for Intune, or it may be included in a 365 license. 

I rate Microsoft Intune nine out of 10. 

Before implementing Intune or any endpoint management solution, I recommend looking at your internal requirements. Are most of your devices iOS or Android? Do you need automated enrollment? Go for Intune if you're using mostly Android mobile devices and Windows PCs.

I use Intune to manage all the organization's PCs.

We use a local Active Directory, but we weren't able to manage all our on-site systems without a solution like Intune, and we needed to deploy software like VPNs and other things. It's seamless now to do this through Intune.

The reporting is subpar. That's the only issue we have with Intune. We use another solution for that purpose. 

I have used Intune for about two years.

Intune is stable. 

Intune is scalable.

We purchased our licenses locally. We contact the reseller when we have support issues, and they contact Microsoft support. We've only needed to contact them once or twice. 

Deploying Intune isn't easy, but it isn't too complicated. Someone with two or three years of experience can do it. I completed the initial installation quickly, but migration took a long time because it's a manual process. We deployed Intune in-house with only two people. 

After deployment, Intune doesn't require any maintenance. It's a cloud solution, so Microsoft is responsible for maintaining it. However, we need to handle any tenant-level configuration.

Intune has somewhat of a monopoly. There aren't many alternatives for this kind of solution, so we have to pay what they're asking. Still, I think it's reasonable. 

We are primarily using Microsoft products, so our options were Google Cloud or Intune. We decided that it was better to go with Intune because the learning curve would be steeper with Google. 

I rate Microsoft Intune eight out of 10. We have never faced any serious issues with Intune. My advice to future users is to plan before you deploy or migrate. 

We use Microsoft Intune for controlling and managing all of our in-house and remote devices. It allows us to deploy applications to all devices.

The most valuable feature of Microsoft Intune is having all our devices compliant with our policies.

The solution can have some compliance problems in general and the end-point user can bypass easily the company policies in Intune.

I have been using Microsoft Intune for approximately three years.

I have not had any problems with the stability of Microsoft Intune.

The solution is deployed for end users and all of our devices.

Microsoft Intune scales well.

I have not used the support from Microsoft Intune.

I have not used a similar solution to Microsoft Intune.

The solution is worth the money for us.

We have the business premium licenses for the solution.

I rate Microsoft Intune a nine out of ten.

It's usually used for managing mobile devices, such as Android and iOS, for application deployment, for securing the device landscape, and for making sure all devices are compliant.

Help Desk engineers don't need to spend a lot of time enrolling new devices. In the past, you had to do that by using a complete infrastructure on-premise, or if you wanted to do it by hand, you had to go through every device. You had to install Windows, configure it to set security, etc. Intune does that automatically for you. It saves a lot of time.

There are so many features, but Windows Autopilot is one of the features that are very valuable for most customers. Personally, I like most of the aspects of Intune. I've been working with it for about 10 years. I'm a Microsoft MPP for the Modern Workplace. I like a lot of features. There's no one particular part of Intune that is the best for me. It has developed into a very mature product. About 10 years ago, it wasn't a very good product, but now, Intune is a very good mobile device management platform.

There should be more support for macOS. Even though macOS is supported by Intune and Microsoft is working very hard to get more features into Intune to manage macOS, that's one thing they can give a lot more attention to.

I've been using Microsoft Intune for about 10 years.

It's stable. There are issues once in a while, but they are not worth mentioning.

It's very scalable. It's deployed across multiple endpoints. My customers vary, but there are between 50 and 15,000 endpoints.

I do have experience with Microsoft technical support, and I'm happy with it. I'd rate their support an eight out of ten.

Positive

I've migrated from other platforms to Microsoft Intune, but I've not used any other similar solution.

It's a cloud solution. The cloud depends on the customer, but Microsoft Intune is a cloud solution serviced by Microsoft. My customers have various cloud environments. It could be a hybrid, public cloud, or private cloud. It depends on the customer.

It's quite straightforward to deploy it, but configuring it and doing it right is something else. The deployment duration varies. Some customers have 100 devices and others have 10,000. It depends on the landscape of a customer. Even though nothing changes technically, it's more difficult to move large enterprise organizations to a mobile device management platform.

The number of people required depends on the qualifications of the person who is deploying Intune. Intune can be deployed by one person. 

Its maintenance depends on the company. If you have a very big landscape with tens of thousands of devices, you want to have more engineers monitoring Intune and configuring. If it's a smaller environment, you can manage it with one or two people.

The ROI has been in terms of time savings.

It's affordable. In comparison to the competitors, the price depends on what features you need from Intune, but it's affordable. There are no hidden costs, but there are some features that go for a premium price. Those are the add-ons for which you have to pay extra.

I did have a look at other options, but I'm a Microsoft specialist, so it's a Microsoft-first sort of policy. If Microsoft can do it, I'll do it with a Microsoft product.

Get yourself well-informed. Talk to a specialist who can help you out with deploying Microsoft Intune.

I'd rate Microsoft Intune an eight out of ten.

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.

When using Microsoft Intune our main focus was on Office 365. Our Azure Active Directory was only held up for users. When we had implemented the endpoint user management in our workstations in a cloud environment, then we started to use Microsoft Intune on an everyday basis, such as remote connection, deploying workstations, Autopilot, and deploying applications. It is a great tool.

Microsoft Intune is a cloud solution. For an on-premise solution, you have SCCM from Microsoft. However, it is old and it will be an obsolete tool soon. There are other solutions such as ManageEngine. Microsoft Intune tool is in the cloud and we can manage everything. You can manage Azure AD, Intune, and not only mobile hand devices, such as iOS or Android, the main focus is on workstations. This is what makes the solution powerful.

I expect Microsoft Intune to have more features in the cloud because there are two major functionalities that we need to be added. This is software metering and license management. These functionalities, for now, must be on-premise. For this purpose, we have set up a SQL Server and I hope that in near future this option will be in the cloud in Microsoft Intune.

I have been using Microsoft Intune for approximately two years.

The stability of Microsoft Intune is great.

Microsoft Intune is highly scalable. When you configure your network connection, there are a lot of firewalls and you can optimize your internet speed. Everything works great. You can tune up some repository sizes with Microsoft because if you have large applications, such as AutoCAD, when you upload the images to the cloud it takes some time and it needs more space.

We had four people in my company that used Microsoft Intune on approximately 100 systems.

The technical support of Microsoft Intune is good.

I previously used BEAM for client management from an American company and SCCM from Microsoft. Additionally, I used ManageEngine and Lansweeper. Lansweeper was a light tool with similar functionality. We use it in combination with TeamViewer.

We have projects all over the world. It took us four months to implement Intune Microsoft Intune for approximately 100 clients in three countries. We implemented it in many locations, such as Germany in three cities, Croatia, and Bosnia, there is a total of 50 locations. Microsoft Intune is easy to work with.

The initial setup is not simple, you need a specialist to be involved that has the appropriate experience. This is not a solution where out of the box you run the executable file on your system and hit next, next, to finish the installation.

Microsoft Intune requires specialists to implement the solution. We used an external team of two engineer specialists that was dedicated to the project. I helped too because I have experience in plant management.

There is a license required to use the solution. If you're core users in Office 365, for example, you have Outlook email and E3 license, this is only email. You have to buy an EMS license to have Microsoft Intune. It is expensive.

I would recommend the solution to others.

I rate Microsoft Intune a nine out of ten.

We use it for the rollout of Windows and Apple devices to our users.

Its direct integration with all the other products that we have from Microsoft is valuable. We're using the E5 license, and we have a whole wealth of different products available. It just makes it easier to have everything from one provider. 

One big problem with Microsoft is that they're changing the names of the products quite often, or they're quite consistently doing so. Intune is now Endpoint administration. Constantly switching the user interface or the administrative interface makes it quite hard to keep pace. If you are on a two-week holiday and you come back and look at the same screen you have looked at for the last couple of months, it looks different, which is annoying. Changing things around all the time doesn't make it easy.

There are some elements where the integration isn't finalized. So, for some of the things, you use the user interface, meaning the administrative website, and for some of the things, you have to use PowerShell to make changes, and it's not quite clear why you have to do things at one point this way and at the other point that way. If they could improve that a little bit more, it would be a good thing.

Other than that, functionality-wise, it, more or less, serves our purpose. I'm not really sure what I would wish more at the moment.

I have been using this solution for over a year.

It is stable 99% of the time. There are some problems with Microsoft in terms of outages, but overall, the solution is very stable.

It is very easy to scale. It is basically adding additional licenses. It requires adding additional domain names and things like that and maybe adjusting a couple of security groups, but other than that, it's really easy to scale up or down.

We have only 120 users in 44 companies. A few of them have financial, accounting, or legal backgrounds. We are not an engineering company; we are a service company. We are a shared service center catering to the needs of more than 44 other companies. That's our business. We are a managed service provider to all these companies.

Its documentation is quite okay, and if not, if you Google things, you would find almost everything. 

We had four, five issues over the last year, and we had to contact them. They were actually quite swift at solving problems. So, overall, we are happy.

It was easier than expected. We did the full deployment for 44 companies and about 120 users in about three months.

ROI is very high at the end. We were using a full data center before with three racks built up with about 30 host systems and 220 virtual servers that we operate in, and by just switching to Microsoft 365, we could get rid of all of them. It made our life easier in terms of support and maintenance. We have saved the costs for all the hardware that we had and all the hassle that we had when parts were broken.

If you ask the accountant or the finance department, they'll tell you that it is way too expensive, but when I look at the cost and compare it with the value you actually get, it's more than fair.

We looked at the Sophos solution as well. We are a Sophos partner, but it was easier to deal directly with the Microsoft solution primarily because of the rules management and the Microsoft groups and the security groups that we use. We use rule-based access, and we have access packages so that users can elevate their rights with an approval process in the back.

I would rate it an eight out of 10.

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.