Microsoft Intune Reviews

I started using this solution in the summer of 2021. It was three years ago, and I remember it was to deploy new computers. I aimed to get a brand new laptop with the processing system entirely configured and ready to work with applications deployed.

I would say Autopilot is a feature I really like. It allows us to send a brand new computer directly to the user without needing to go through IT. This capability is powerful as it allows us to remove any compromised device remotely, whether it gets stolen or not. 

It's a great product to secure data, although it might be a bit more complicated with iOS devices when you're using your own device. It's nice for mobile devices, though smartphones might be less suitable compared to personal computers. This solution saves us a lot of time once it's implemented.

I would like to see better integration with Microsoft. There are a few things I can still do with Jamf that I am unable to do with Intune yet.

I have been using the solution for three years.

Stability issues almost never happen. The worst case I experienced was when Autopilot failed a couple of times, but that's the only issue I had.

I did not use any previous solutions except Jamf for Apple devices.

The initial setup was somewhat between easy and difficult. It took about a month to learn how to use it, initially in a small environment. During the first implementation in March, I did not like all the new features as they took time.

I used it twice. The first implementation took a long time, and there were two of us the second time.

I am sharing my experience between Intune and Jamf. Regarding the user experience, I'm not sure that users realize what Intune does for them. It automates tasks so that from their perspective, things happen automatically without understanding what is being done. 

I'm not sure about the name, but I had a personal plan because I started using it without training. It took a few weeks to learn how to use it properly. For application deployment, maintaining packages for updates is necessary. I advise using a testing environment and taking the time to understand how this will impact the infrastructure before putting Intune into production. 

Overall, I would rate this product seven out of ten.

We use Intune to connect university staff and faculty to secure resources on their computers quickly.  

Intune is a force multiplier coming directly from Active Directory. We had to engineer over some limitations of Active Directory, and Intune resolves that by addressing known trouble areas. It allows us to do things quicker and more efficiently. 

We like Intune's Autopilot functionality, which enables one-touch deployment. Dynamic grouping is another feature we find valuable working in academia. We have people in buckets based on their roles in the university, such as faculty, staff, alum, or grad. Sometimes, they will fit into multiple places, and dynamic grouping helps with that. So far, using Intune has been easy and intuitive. Once everything is set up, our user base finds it much easier and more modern.

We've recently purchased Copilot licenses for Intune, but we've only had it for a week or two. It's a new deal for Syracuse, but it has been good so far. It moves quickly. You can see that it's constantly learning, and I love that. Today is the dumbest it will ever be. It's going to continue getting better and better. Even when we're wowed, we understand that more "wow" will come. 

It has some growing pains, but they are no different from anything new. We're implementing Intune on an individualized data set. So there's no way Copilot can know everything about every data set it's going to get, but it does grow pretty quickly, which is phenomenal. 

It would be awesome if Microsoft opened their API so we could filter more properties. If we have to do anything outside of Intune that requires a third-party solution to talk back to it, we're very limited in what we can do. Trust your people. We promise not to break your stuff. Open it up just a tiny bit wider.

We started using Microsoft Intune about a year and a half ago. We transitioned our fleet from Active Directory to Azure Active Directory. Then, we took that hybrid and shifted it into Intune for our MDM solution.

Intune is solidly reliable. Microsoft has some peaks and valleys that you need to get used to. Stability is essential when transitioning from on-prem to the cloud, where Microsoft manages your infrastructure. There have been a few drops in performance, but that's more growing pains from our rapid expression than an indicator of major problems.

Scalability is fantastic. 

I am a technician, so when I'm reaching out about problems I cannot solve myself, they tend not to be tier-one or tier-two problems. When I contacted Microsoft, they had the same expertise, if not more, which is phenomenal because I felt heard and my problem was solved. That is delightful because I have contacted support for other solutions. After trying several troubleshooting steps, I contacted them, and they asked me to restart something. I have gone beyond that point and tried to tell you where I am. 

Positive

We previously used Active Directory and spec ops for software deployment, with Active Directory handling computer and user management. Intune was a natural progression for MDM. For Mac users, we still use Jamf but plan to transition them to Intune as support for Apple products grows.

It is absolutely a positive investment. Everything we've gained from it makes my job easier day after day, and I see value in it as an engineer.

I am not involved in those discussions. We worked hard to acquire E5 licensing, and Microsoft collaborated well with the university to ensure everyone got what they needed.

We are managing different platforms including iOS, Android, and Windows using Microsoft Intune. We are not supporting Mac. For Mac, our organization uses JAMF Pro. 

We use Microsoft Intune for application deployment, creating compliance policies for organizational devices and BYOD devices, creating configuration profiles, managing users, and troubleshooting for end users' enrolled devices. I provide level two technical support for end users.

My favorite feature of Microsoft Intune is the dashboard. The dashboard is very simple and user-friendly. Any person, even without prior knowledge, can understand it easily by seeing the interface dashboard. Everything is available in one place. 

For example, if you go to devices, all platforms will be shown. When you select one platform, such as Windows, everything will be on the same page, including application deployment, configuration profiles, compliance policies, future updates, and enrollment types. Anyone can easily understand it when compared to the SCCM tool.

For platforms such as iOS, Android, and Windows, Microsoft Intune is very good. When it comes to Mac, everyone uses JAMF Pro for patching and upgrading. I suggest they can improve Mac-related features and platform-related features. We cannot manage servers in Microsoft Intune because it is completely cloud-based.

The main issue with Microsoft Intune is that for Windows, we can support only Windows 10 and 11 operating systems. We cannot deploy large application files. For that, our organization uses SCCM only. We also cannot manage older versions of devices from Microsoft Intune, such as Windows 7, Windows 8, and Windows 9, as it does not support them.

I have been using Microsoft Intune for the last three years.

Everything is good with Microsoft Intune. They are releasing many updates recently. Previously, we were using Company Portal for deployment. Now, they have introduced web-based enrollment. 

Without the Company Portal, a user can directly register the device by using the Outlook application. In the last two years, they have introduced many changes. The performance and everything is good with Microsoft Intune. For us, Microsoft Intune responds very well. They handle it and provide us with complete data without any issues. Follow-ups are also very good.

We mostly connect with Microsoft whenever we are unable to resolve issues. 

We can check with Microsoft subject matter experts. We log an incident and check with the Microsoft subject matter expert. Based on the priority of the incident, if we create a priority one incident, they try to get in touch within one to two hours. 

They assign one agent who connects with our architect. They try to help us with the root cause analysis of the issue. Mostly, it takes some time because they need to examine all the logs. Root cause analysis takes considerable time to find the exact solution. 

For Microsoft Intune support, I give an eight out of ten. While they are SMEs who can fix issues quickly, the cases we have raised with Microsoft take too much time, which affects end users and the organization.

Positive

One person is required for the deployment of Microsoft Intune, though it depends on the requirement.

When it comes to pricing, Microsoft Intune is very good compared to other tools such as Tanium, Ivanti, and JAMF. Those are very high-cost tools. 

Microsoft Intune is less costly when compared to them and provides many features and benefits. On a single E3 or E5 subscription, a user can enroll ten to 15 devices. A single user can enroll 15 devices. They can access company resources such as Outlook, Teams, and everything without any issues.

Copilot in Microsoft Intune was recently introduced. I am working as L2 L3 support. We are using Microsoft Copilot. We are testing Microsoft Copilot for troubleshooting issues in a non-real-time environment. We are testing it for normal cases, such as Microsoft blogs or when new issues arise for users. 

If a client asks to deploy multiple applications, then a team will be required. Our client is a US-based health sector company, and we are users of Microsoft Intune without any partners. 

I rate Microsoft Intune nine out of ten.

I have been using the enterprise application management features of Microsoft Intune Suite for couple of years now. 

We're deploying security baselines and configuration profiles (GPO) with ease. Tasks that could take much more time if done from the DC.

The features of Microsoft Intune that I appreciate the most are its user-friendly interface and robust security options.

I assess the user experience of Microsoft Intune as positive overall.

I think their advanced endpoint analytics help me proactively.

I would assess Cloud PKI for helping me manage the complexity of the certificate infrastructure as beneficial.

Microsoft Intune could be improved by enhancing its reporting functionalities (for entry level license).

I would request additional features in the next release of Microsoft Intune.

Two years

I would rate their support from 1 to 10 as a solid 8.

Positive

Ivanti Landesk, we switched mostly because prior platform was facing EOL.

I have not yet had ROI with Microsoft Intune.

I expect to see a return on investment in Microsoft Intune approximately in the next few months.

The pricing licensing model of Microsoft Intune seems competitive.

Give our company MS agreement, it was just a no-brainer.

I work for Viscofan S.A. as an Information Technology Modern Workplace Management. My email address is JAURIETAC.

I am interested in being a reference for Microsoft, and they can contact me if they have any questions regarding my review.

Public Cloud

We usually use Microsoft Intune to manage our devices and add security layers to protect access to all company resources.

The main benefit for us with Microsoft Intune is centralized management of all devices, allowing us to apply one policy across the company from one location.

What I like the most about Microsoft Intune is its ability to manage mobile devices. Through integration with System Center, it can also manage desktops and laptops. We also appreciate how easy it is to manage everything from the console.

The enterprise application management feature lets you manage, deploy, or uninstall applications from Intune. It also enables us to automate updates. The Cloud PKI feature helps us manage security keys on all company devices. 

Intune should improve the management of non-Microsoft devices. It would be better to manage Mac, Android, and other non-Microsoft operating system devices within the same Intune interface.

I have been using Microsoft Intune for almost five years now.

I rate Microsoft Intune nine out of 10 for stability.

We are not a huge company to check the scalability part. However, when discussing with our customers across the region, it seems fine, especially with the integration with System Center.

I rate Microsoft support nine out of 10. We have not used customer support, but it seems okay. If something happens, we open a case and receive assistance.

Positive

While I didn't perform the initial deployment, I know it's easy to roll out Intune across all devices. 

From the device perspective, particularly for desktops, it automates application deployment and secures all the devices. Importantly, when someone leaves the company, it helps protect document access on their devices. Onboarding and offboarding users is a great asset in terms of ROI.

We are partners, so we receive some discount. However, from the customer's perspective, Microsoft Intune's pricing is competitive with non-Microsoft technology, and the price is good compared to other market competitors.

I rate Microsoft Intune nine out of 10.

Public Cloud

We use Microsoft Intune to manage mobile devices for our parent company and our independent subsidiaries. These devices are not directly corporate-owned but belong to individuals or subsidiaries with whom we work. We enroll both their and our corporate devices in Intune to manage policies, ensure optimal security settings through compliance reviews, and deploy a VPN client for secure access to our internal network resources.

Microsoft Intune has provided valuable insight into the status of our independent computers, which previously lacked a management agent and had no standardized security policies. We could not enforce password expiration policies, hardened passwords, or even minimum password requirements, with some users relying on six-character passwords. By enrolling these devices in Intune, we have enforced more robust security measures, such as a minimum eight-character password length, and gained visibility into device compliance to ensure adherence to best security practices for data protection.

The Intune user experience is good, especially with the many improvements made to the web interface over the years. It has always been designed as a simpler interface than Configuration Manager, and Microsoft has done a good job in achieving this goal.

Dynamic groups are more efficient than static groups, which require manually adding members. This was cumbersome, especially when onboarding new people, as it necessitated manually adding them to the appropriate groups. Dynamic groups allow us to set conditions for automatic membership, eliminating the need for user intervention or manual review and ensuring a seamless workflow.

Microsoft Intune's app deployment presents challenges for non-MSI and non-store apps, particularly EXEs, requiring the use of a Win32 wrapper tool and adding overhead to the process. Additionally, deploying device-specific installers, such as VPN clients, is complicated by the inability to target users directly, necessitating knowledge of device names that may not be readily available. Furthermore, the web interface lacks detailed information for MDM-enrolled devices, such as the user's UPN, requiring the use of Graph Explorer API and necessitating Global Admin consent to access device properties. Enhancing app deployment, enabling user-targeted device application deployment, and improving the web interface, particularly for MDM-enrolled devices, by providing comprehensive device information and customizable columns, would significantly streamline Intune's usability.

Microsoft Intune should enhance flexibility and features to better match the granularity available in systems like SCCM.

I have been using Microsoft Intune for over five years.

Microsoft Intune has been stable, and I have not noticed any specific stability issues. While we've encountered problems with other services like Exchange, Intune has remained unaffected.

Scaling Intune is challenging due to the various device types we manage. Our parent company's mobile devices were already enrolled, and we've added our independent Windows devices, with plans to include corporate devices soon. A key hurdle is the lack of visibility into user attributes in Intune, hindering our ability to create dynamic groups effectively. Ideally, we want to automatically segregate devices based on user properties like primary use, but currently, dynamic groups seem limited to device properties. This forces manual group assignment after user enrollment, which is inefficient and reliant on user notification. Improved dynamic group functionality, particularly the ability to leverage user attributes, would significantly streamline device management.

Customer support has been reasonable overall. However, there have been cases, such as issues with BitLocker recovery keys, where support was less effective, leading to multiple hand-offs and delays.

Neutral

Before Intune, the independent devices were unmanaged without any agent. For corporate devices, we previously used SCCM.

The initial deployment of Microsoft Intune was fairly straightforward, despite a few challenges due to our unusual configuration of two on-premise domains syncing to our Azure tenant. This dual user sync caused issues because some users remained on the older domain, leading to conflicts when automated systems modified on-premise account attributes. These modifications triggered Azure to switch the sync to the other account, resulting in login failures for users with cached credentials from the old account. While we've mostly identified the cause and the fix, we still encounter this issue occasionally.

The deployment was handled in-house. Our organization benefited from having skilled personnel and guidance from our parent company.

The return on investment includes successfully distributing applications like a VPN client and Office 365. As a result, independent devices now have better application access, encouraging even non-enrolled entities to request Intune enrollment.

We considered Tanium for managing independent devices, but it's a comprehensive endpoint management tool with more functionality than we needed. Management felt it would introduce unnecessary overhead. Since all our corporate devices are currently managed with Intune, adding independent devices would require segregation. Ultimately, we opted for Intune due to its ease of use, allowing us to create targeted policies from scratch.

I would rate Microsoft Intune a seven out of ten.

Public Cloud

Microsoft Azure

I use Microsoft Intune to check if laptops are compliant or not, and to check if applications are added to user profiles. Sometimes there are applications users cannot find in the Company Portal or on their laptops, so we try to add them to their profiles. We can check if there are issues with Windows updates and verify if they have the latest version. We can check by hostname or serial number of the laptop if a user's computer is compliant or has access to the enterprise company platform resources.

The best features of Microsoft Intune include helping to know if computers are configured correctly and if users have access to apps or the platform. It provides an excellent overview of all machines for the company and helps determine if those machines are facing issues. It is particularly helpful when laptops face issues with upgrading or migrating to Windows 10 or Windows 11.

Automation has room for improvement in Microsoft Intune for fixing some errors. The knowledge and database in support can also be improved. If errors aren't in the database, we need to check forums or Google to understand and troubleshoot them. The most important improvement needed for Microsoft Intune is to have a comprehensive database about what each error means exactly and what steps to take for troubleshooting.

I have been using Microsoft Intune for about four years.

The stability of Microsoft Intune rates at nine out of ten.

Microsoft Intune has saved approximately 30% of time.

Users are mostly satisfied with Microsoft Intune because it helps them understand what's happening on their laptops. For some issues, I can assist depending on Microsoft Intune access. When comparing Microsoft Intune with other tools, the pricing is acceptable and it's easy to use. I recommend Microsoft Intune; it should be used in companies using Windows. I rate Microsoft Intune eight out of ten.

On-premises

I use Microsoft Intune on corporate devices as well as bring your own devices. It is always within an enterprise environment. I deal with industries such as manufacturing and health.

Microsoft Intune provides a more secure way by offering MFA policy, conditional access policies, and R-back policies. I can set up all my GPO policies, and Microsoft is moving these features to Microsoft Intune.

I could not discuss all the areas that need improvement due to time constraints. However, there are definitely challenges that could be addressed.

I have been using Microsoft Intune for around five to six years.

I rate Microsoft support between six to eight. The support often involves third parties hired by Microsoft who are knowledgeable, but sometimes the help I receive is not adequate.

Neutral

I previously used Blackberry until it was discontinued, which led me to switch to Microsoft Intune.

The setup is not difficult. The deployment time depends on the project specifics.

I rate the return on investment for Microsoft Intune as seven out of ten.

The pricing and licensing depend on my company's budget. If the company can afford it, it is manageable.

Overall, I would rate Microsoft Intune as eight out of ten.

Other