Microsoft Intune Reviews

We use the solution for information and protection. The solution identifies anything that can be exploited.

Microsoft Intune allows us to ensure that all devices are authenticated and that they use policies to prevent people from logging in and accessing unauthorized resources.

Autopilot is the most valuable feature.

Unlike VMware Workspace ONE, which provides system configuration and endpoint management, Microsoft Intune is not a standalone application. This is a limitation of Microsoft Intune because it does not provide all the information we need or the application details of the devices connected.

Microsoft Intune's support for Mac devices is lacking and could be improved.

I have been using Microsoft Intune for seven years.

With our number of users, Microsoft Intune is stable.

Microsoft Intune is currently able to meet our requirements, but as we expand in the future, we may need to consider other options. 20 percent of our employees are using Microsoft Intune.

The technical support is slow at responding.

The initial setup was somewhat complex. We encountered some issues with the security group, which prevented us from enrolling some of the devices. Our strategy was to onboard all the new users first. The deployment involved around eight people.

The implementation was completed in-house.

Microsoft Intune is included in the E5 license at no additional cost.

We evaluated VMware Workspace ONE but ultimately decided to use Microsoft Intune because we already had a Microsoft E5 license.

I give Microsoft Intune a seven out of ten.

We have not required any maintenance as of now.

I recommend Microsoft Intune.

One plan that we are currently testing for the near future is related to our BYOD fleet. Instead of opting for MDM, we have decided to use Microsoft Intune to manage access to our company through BYOD. Moreover, we plan to use Microsoft Intune to perform autopilot PC deployments in the near future.

We had two distinct issues we needed to resolve with Microsoft Intune for two different use cases. Firstly, for the BYOD scenario, we needed Intune to ensure a sufficient level of security while enabling users to bring their personal mobile devices. Secondly, we aimed to automate PC deployment, even when users are not connected to the network, due to the COVID pandemic and the increase in remote work. Currently, to reimage a machine, users must be on the network. Our goal is to enable them to reimage their machines from home, using autopilot.

We found that Microsoft Intune met our expectations for the BYOD section, and we are optimistic about its potential for PC deployment through autopilot. The main advantage is that Intune performs its intended functions effectively.

As a Microsoft 365 user, we found Microsoft Intune to be a practical choice since it was already included in the bundle. The solution was effective, so we didn't need to look for other options or invest in additional tools. Intune performed the necessary tasks efficiently, making our decision straightforward.

The UI is not user-friendly and has room for improvement.

I have been using the solution for four years.

We have not had a single outage in the last four years. Microsoft Intune is extremely stable.

Microsoft Intune is auto-scalable in the cloud.

The initial setup was straightforward. The deployment required two people from the third party and two of our architects, one for security and one for the network.

We used a third party and our architect for implementation.

We have seen a return on investment because we were able to quickly deploy and start using Intune.

Intune is included in the Microsoft 365 licensing package that we have.

We assessed VMware and found its MDM to be promising. However, since we were already utilizing other Microsoft solutions, and Intune was capable of meeting our requirements, we did not require further evaluation of additional solutions.

I give the solution an eight out of ten.

We have around 10,000 people in over 20 different countries whose devices are managed by Microsoft Intune.

There is no maintenance required for the solution.

I highly recommend Microsoft Intune to others.

Essentially, we use it to manage devices. We are looking at potentially moving away from VMware and bringing mobile devices and tablets into Intune along with desktops and laptops, which we currently manage, so that it serves as an all-in-one active asset list where we can look at the health of the entire technical estate. We can manage against threats. We can roll out apps, policies, et cetera. We can also manage logins, reset logins, et cetera, and it's an all-in-one, 24/7 solution.

Microsoft Intune has absolutely improved the way our organization functions. We're currently going through the AAD migration, so we are transitioning away from the old on-premise domain to Azure. The ability to take devices that were locally managed via AD but weren't managed via Intune is brilliant. We can see who last logged in, who it's managed by, which OS is there when it was last updated, etc. It gives us a micro overview of what's happening there.

Generally, we find it quite useful. We don't use it to the full extent. We've only got a P1 license, but generally, the application health and the ability to create and manage policies are valuable. We can split them very quickly into groups, multiple policies, etc. So, it's those core basics that we use, but they work very well.

It's very informative when there is an error. It allows us to backtrace where the error is and resolve that ourselves. It's a bit of a Swiss Army penknife. We find that it fixes most issues.

I'd like some more reporting so that I don't have to delve into PowerShell and I can pull more of the local device information such as memory, apps installed, etc. It would be nice to be able to see the apps that are present there but might not be managed. For example, if they installed 7Zip, it could report that back via an installed program or feature to see what was currently installed. Generally, it works, and nobody complains about it.

I've been using this solution for a couple of years.

Sometimes, they can take a little while to come back in showing that they are compliant. Typically, they may show us as not compliant even when we are. Typically, we find that it takes a couple of hours or a couple of days at worst for the machines to show as being compliant for them to settle down, but generally, it does what it says on the tin. We can set the policy, and we can put a machine or put a device into a group. That policy gets defined or pushed out, and it works. We can then move on to the next job. From my perspective, it works well, and that's why I'm just looking forward to using more Azure technologies moving forward.

It's deployed across multiple locations, departments, teams, and endpoints.

I haven't had any experience with them.

At the moment, we're using VMware AirWatch, which isn't my first choice purely because it's a super segmented platform. We are predominantly, about 95%, Microsoft. It feels a bit of an oversight not having a solution on a Microsoft platform where we've got full transparency and can make live changes. Currently, we have to go through our outsourced IT to make the changes and then we have to wait to see those changes rather than me or a colleague being able to make those changes in a live environment, so it would be my personal preference to get that moved over, which we're looking at. 

I wasn't a party to why they used AirWatch. I presume it was bundled in with the Microsoft service partner's offering originally. The IT team here is quite new. I've only been in the post for about a month, and my IT manager has only been in the post for about two months. We're just making sure that everything is easy to use and easy to manage, and it's cost-efficient for the charity moving forward.

Essentially, the way it was set up, it wasn't set up as a hybrid model. At the moment, we have got on-premises, and we have a cloud, but they're not joined. There is no passthrough, which is interesting. A lot of the on-premise has been copied over to the cloud. We are now taking the cloud to default, and the overall plan is to mothball the servers and reuse those as very high-powered desktops wherever possible. I just predominantly use the cloud.

I was not involved in its deployment, but in terms of maintenance, typically, our MSP makes the changes, but I've got GA rights to make anything that is critical. Generally, there are about 20 people at the Microsoft solution partner, and there are four of us on the IT team. There are less than 30 people in total.

I'm not sure. Certainly, it has been at least three years since the software has been rolled out, but it's not particularly well maintained by the solution partner. So, it's hard to measure the ROI. It does have merit, but in our particular sector, it's just overkill. We just need to make small and light changes whilst having effective security. We don't need corporate class, biometric/conditional access level security. Whilst we have multiple offices, they're very small. They're all under 20 users, and there's a lot of work from home. So, as long as we've got encryption, a form of AV, an anti-spam, and good account security, it certainly staves off a lot of the threats.

Personally, I feel that we haven't had the ROI purely because we're paying about £13,000 for under 300 users a year, which is a little bit top-sized. My personal feeling is to make a business case to switch to Microsoft Defender. Obviously, we've got P1 in our business premium licensing, so we've got a very basic protection at the moment that we don't use. We've got a large number of credits, and we could use those credits to switch over for a year to a higher project and see where we go from there.

Generally, it's not too bad. Obviously, a cheaper price would be great. Typically, we are in touch with the partner to provide non-profit discounts wherever possible. Generally, we get favorable discounts, so it's not too bad. Obviously, we're looking at decreasing those wherever we can to bring value back to the public purse because it's all charity based. It's all publicly funded.

Create a test group and create test policies, and then just test, test, and test before anything is rolled. It's the usual IT gambit. Test everything, and then just test it again before you roll it out.

I worked for a couple of MSPs before. I've seen it in very remote areas. I'm very impressed with it. Whilst it seems almost fashionable to criticize Microsoft, Intune is pretty much a well-laid-out product. It does what it says it's going to do. There is a lot of dependence on Microsoft products being pushed to it, and that's probably my only criticism. It would be good if Intune was a bit more open-source, but that would lead to more complications. It's a bit of a complicated beast, but generally, I like it.

I'd rate Microsoft Intune a nine out of ten. I'm happy with it.

We use Intune to manage mobile devices and applications. I'm not solely using Intune for the agents installed on each machine. I use the Microsoft Endpoint Manager solution primarily for device configuration, device compliance, and mobile application management.

I have 80 different clients, and their environments vary. We have people that work in offices across multiple foreign countries and domestically. Most have a strictly cloud-based deployment, but a few have a private cloud that we host ourselves. Some have their own data centers. I've got a couple of clients with hybrid environments. None of them are entirely on-prem. Everybody is using a hybrid cloud or completely on the cloud.

Intune helps us from a compliance standpoint by making it easier for system admins to configure devices and ensure they conform to business policies. It gives us more visibility into where the devices are and their postures.

I try to use conditional access policies for every client I can. It's essential for a zero-trust security posture. Conditional access policies make it possible. This dramatically reduces the risk of unpatched devices connecting to our corporate network.

The conditional access policies, compliance, and updates affect employees positively. Once the value is explained to them, they don't complain much about MFA.

You can use Endpoint Manager to see whether or not a device is compliant and apply conditional access policies in Entra to only allow connections to your environment from compliant devices. That significantly reduces your risk from unpatched software because that device cannot connect to your machine or environment. Using those two features together definitely helps protect us.

It saves some time. Either way, you will have to manage an Active Directory environment, but Intune allows you to manage devices over the internet. You don't need to worry if the machines are connected to a VPN or on-site.

The most valuable feature is probably mobile device management. Small businesses are coming under greater scrutiny and requirements for compliance as time goes on. We don't have to worry about a VPN because we can manage these devices, control company data, and lock users out. If needed, we can remotely wipe devices and switch them. 

It's a big deal to be able to assure an insurance company or auditor that our endpoint devices are effectively managed. Intune is a solid solution if you use Microsoft and Microsoft 365 products.

Intune's third-party patch management could be better. It should be easier for an average system admin to keep non-Microsoft applications updated. 

I have used Intune for about six years now.

Intune is highly stable. 

Intune is highly scalable. Thus far, I haven't had to expand it to a thousand users, but the scalability appears to be readily available.

I rate Microsoft support a nine out of ten. I enjoy working with them, and I'm often surprised at how good they are. 

Positive

I've used Rocky MDM and Google MDM. Microsoft is the primary platform on which we do business. Intune works better with the Windows operating system, desktop applications, and SharePoint. It also reduces vendor complexity. I don't require multiple vendors, which reduces my costs because many features are baked into it. 

I log into fewer systems daily. Microsoft's virtual monopoly on productivity applications in your average small business makes them the right choice in most situations.

Deploying Intune is pretty straightforward. It doesn't matter whether you use autopilot or manual deployment. Each machine is enrolled in Intune automatically if it's connected to Azure AD with the correct user licensing. It's a relatively painless enrollment process.

Intune involves some maintenance, like any solution. You must ensure it's still working correctly and helping you achieve your business goals for compliance and configuration of your endpoints.

Meraki and Google are relatively common in small businesses. Many small businesses use Meraki for wireless and networking solutions, so that is one MDM option. Also, small businesses often start with Google and transfer to Microsoft 365 once they mature. Google is already in the environment. I don't sell anything as an IT guy, so I don't care what solution my clients use. I choose what's best for them in that particular instance.

I have tried Okta, but I haven't used it seriously as an MDM solution. I've only used Okta as an SSO provider. I didn't realize they did MDM solutions. I don't understand the point of Okta. If you have Azure AD and Entra, I can't fathom why you would bother with Okta. It seems redundant to me.

I rate Microsoft Intune a nine out of ten. Don't underestimate the solution, and spend time learning about it. Intune has some powerful capabilities. Often, small businesses acquire systems but never fully utilize them because nobody has the time to dive deeply into them. It's a big solution with a lot of features. 

We are currently using Intune, and we are also deploying it for customers. We use Intune to manage our mobile devices. We manage our Android and iOS devices with it, and at the same time, we also use Intune to manage our macOS and Windows devices.

During the pandemic, there were devices that we couldn't control. For example, we wanted to manage BYOD and make sure that they are secured so that when they access our corporate resources, our data, computers, users, and mobile devices are protected. We use Intune to publish some of our company applications and at the same time push down our restriction policy and configuration profiles, such as VPN.

We are a vendor, and we deploy the Intune solution. We see that our clients have benefited from this solution. They're able to manage devices that were previously not managed. They are able to secure those devices. It also improves the productivity of the users. They can work from wherever they are and leverage their own devices to access company resources. So, productivity-wise, users are more productive when it comes to Intune.

Based on my experience, I find Intune very flexible for managing Windows devices. We can use scripting, and we can make use of the self-service portal or the company portal to publish some of the applications for Windows.

I'd suggest adding more features for macOS in Intune. There should be more functionality for managing macOS. There should be a better capability for pushing things down on macOS. Currently, Intune is not capable of managing macOS at the same level as Windows.

It has been four years since I've been using Intune.

I'd rate it an eight out of ten in terms of stability because it sometimes breaks. That's mainly because Windows OS keeps on changing because of upgrades and things like that, and there are some instances where it's not supported, or it has not been tested fully on a specific version of OS.

We haven't yet gone down to the scalability part. It meets the needs of our customers. What they have right now in the cloud is sufficient and satisfies the requirements. So, scalability is not a problem.

Some of the deployments are done across sites, so there are multiple sites.

I have interacted with their support. I'd rate them a ten out of ten.

Positive

We have previously used MobileIron and Jamf Pro.

The deployment model for Intune is cloud basically, but for other MDM solutions, it's on-prem because the government and healthcare sectors prefer to use the on-prem solution.

The deployment duration depends on the project timeline and the complexity of the deployment. A fresh Intune deployment is straightforward. We just need to do the configuration and create configuration profiles. For example, for Windows OS, we can enroll 1,000 devices in a month or something like that depending on the availability of the machine. Everything is configured in the backend, so they just need to power on the device, and everything works as expected, and everything is pushed down.

The number of people required depends on how many machines need to be deployed and users' availability. The model that we're having right now is that for a new device, it's straightaway delivered to the user. So, there is no involvement of IT because it's an autopilot deployment. When a user powers on a device, the configuration kicks in. The users just log in using their user accounts, and that's all. So, one IT person is enough to configure the backend.

We implement it in-house. It does require some maintenance, but that's taken care of by another party.

It's affordable. It's cheaper if you have an Office 365, E5, or E3 subscription because everything is there.

I evaluated VMware Workspace ONE, which is similar to Intune. They both can manage multiple OSs. 

While evaluating, I'd advise evaluating each and every feature of Intune and using multiple operating systems, such as Android, iOS, Windows, and macOS. You should see the capabilities of Intune and also check how to integrate Intune with other solutions. For example, for security, there is endpoint protection, etc. You need to check that because one of the requirements is to make sure that the computers and the mobile devices are secure, but Intune cannot secure your device itself. It's just an MDM solution. It only restricts some of the functionality. It cannot do more in terms of security. You need another solution to secure your devices, and you must check that your security solution can be integrated with Intune.

I'd rate Intune an eight out of ten.

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.

We use Microsoft Intune to deploy devices with Autopilot, manage apps, autopatch, device and application management, and enroll security policies.

The solution is fully integrated with the Microsoft platform and the Autopilot feature, which is a unique feature.

The user experience with Microsoft Intune is not so good. Sometimes, you see an error saying policies or configurations are not applied, but you don't get enough insights to know why.

The solution's app deployment needs to be improved. It now has advanced app management as a feature, and you have an app marketplace.

I have been using Microsoft Intune for two years.

Microsoft Intune is a stable solution.

Microsoft Intune is a scalable solution.

My experience with the solution's technical support has been mostly bad. We have a high skill set, and we test most things. When we call support, we normally need second-level or third-level support, and the first level is not very useful.

I rate the solution’s technical support a five or six out of ten.

Neutral

I have also worked with other tools like MobileIron. Compared to its competitors, Microsoft Intune is fully integrated with Microsoft.

Although the onboarding for hybrid devices can sometimes be a bit complex, most setup tasks are very easy.

Microsoft Intune is not cost-effective as a standalone product. It provides good value in an integrated Microsoft solution.

We implemented the solution because we wanted to have a zero-touch deployment. Microsoft Intune brings all our endpoint and security management tools in one place. Microsoft Intune is the base for everything because we use Zero Trust. You don't have Zero Trust if you cannot manage the device.

The solution's app discovery and app automatic updating features are very important. The App Catalog is not currently implemented, but I hope it will be on the roadmap. The solution's advanced endpoint analytics help a lot to proactively detect and remediate anomalies in endpoints. When you have issues with boot time or login time, you can see what the processes are.

I would recommend the solution to other users. In my opinion, Microsoft Intune has a good feature set and good value, but the price for the stand-alone solution is very high. I recommend including it in other license bundles, not as a stand-alone product.

We had Copilot for a testing period, and we used it to better understand or gain insights into problems and to get recommendations. We use Copilot very intensively, and it has been of help to us. However, we don't use Copilot for security in Microsoft Intune because the costs are too high.

I am satisfied with Microsoft Intune's ability to secure hybrid work and protect data on the company (BYOD) bring-your-own devices. The endpoint privilege management feature in Microsoft Intune has some limitations, but in general, it provides better security. Microsoft Intune has impacted our organization's attack surface. There is no need to have local admins.

Microsoft Intune affects our organization's productivity. It is not difficult to maintain the solution. I work with the cloud version of Microsoft Intune.

Overall, I rate the solution a 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.