Microsoft Intune Reviews

We are using Microsoft Intune for the management of desktops and laptops because we have a business where we don't have all users in the office. Many of them work from home from different countries. Management of the devices was almost impossible with the tools that we were using before, such as ServiceDesk. We are using Office 365, and we are Microsoft users in a Microsoft environment. After that, we decided to grow with Microsoft Intune. Initially, it was planned to better manage the devices and serve as a deployment tool.

Microsoft Intune has definitely affected IT productivity in our company. We shortened the time for issuing new PCs and changing PCs. It enforced our security and deployment of the Gold Build. We were waiting for that; it shortened that time significantly, and we got our security certifications regarding that very fast after we bought it. Junior technicians and help desk staff had much less time to spend on the deployment of the PCs.

We are using the endpoint privilege management feature and find it very useful and good.

The thing I appreciate most about Microsoft Intune is that the management of the devices was very simplified. We have all machines connected to it at all times, whether they are in the office or working from home. The greatest thing is that we create unique deployments for security, which we call the Gold Build Windows 11, and the deployment of that operating system with all the security settings that we set up for our business is very easy; it is much simplified compared to before. We created everything that we needed on Microsoft Intune, and all you need to do is just set up a new PC or an existing one, put it on the network, and let Microsoft Intune do everything else in order to have a completely full machine with everything you need from one place. Everything that you need to change, when we decide to change something, is in one place and will be deployed immediately.

Reporting can be better. Only global administrators can see detailed reports at the moment, and I don't want to use the global admin. We have only two global administrators in the USA and Europe, and it should be available for the global reader role because currently, when I need to do some reporting, I have to send a request for the global admin report.

We didn't have any complaints in terms of user experience, from administrators or from users. The only problem for us was that we had different access levels for the administrators, and that was very hard to accomplish. That was the one part that we were keen on and contacted support. It's not so granular. That was the problem.

One thing that I don't appreciate in deployment is that it needs to be put in the group of the machines over the security group; you cannot put it into only one PC.

I started using Microsoft Intune in my last company, and I have been using it for almost two years.

We didn't have any issues regarding stability.

Microsoft Intune is very scalable.

It's a great suite for big companies that have over 3,000 users and many devices to manage. It's great from the management point of the devices, and also users; it's collaborative with Office 365, and the pricing is for companies that have more than 3,000 users.

We contacted them when we had the issue with the serial numbers of the machines. Microsoft support was not very responsive, and it took approximately one and a half months to get on a call to clear what the problem was. Every time they changed technicians, we had to explain the problem again. We were explaining for one and a half months without getting help. We ultimately resolved the problem ourselves. They are not responsive and not intuitive in giving solutions.

We used Service Desk Plus previously. At the moment, we are using other management tools, but very soon, we will go for Microsoft One. Between Service Desk Plus and Microsoft Intune, I prefer Microsoft Intune because of its pricing and features.

In terms of app discovery, deployment, and automatic updating, it's great; although sometimes, it's very hard to find the deployment version of the applications for Microsoft Intune because some software companies do not create them. For example, we find it much simpler in other software, such as Datto. We use Datto for remote access and deployment of some specific applications, but for most applications, we use Microsoft Intune. 

The initial deployment was not difficult for me. The project took one month to deploy.

We saw the benefits of Microsoft Intune after some time. We had some issues, and we contacted support at Microsoft. We used a lot of non-brand machines, and that was the issue. We couldn't enroll them in Microsoft Intune because they didn't have serial numbers, and unfortunately, Microsoft couldn't help us on that. We solved the issue by ourselves by writing down in the BIOS our internal number with a script, and that was the solution. After we crossed that bridge, it was much better.

We had a very small team; three engineers were doing the implementation.

The overall pricing of Microsoft Intune is good for companies that have big IT budgets, 3,000 or more users and devices.

We started using Copilot, but we stopped the usage of AI at the moment in our domain. We want to make it more granular in terms of who can use it. Our end users cannot use it. It was a request from our clients to set that up at this point, and we have an IT department in the company that will make improvements. We took Copilot professional licenses, and it's very good.

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 are still in hybrid mode, but within Intune, Office 365, and Azure, we will soon be in the cloud, totally independent of anything on the ground.

I would rate Microsoft Intune an eight out of ten.

I am using Microsoft Intune for device management, device enrollment, policy compliances, application management, patch updates, and security protection.

The user experience in Microsoft Intune is very useful for maintaining work-life balance. Employees are managing their work through the Microsoft Intune application on mobile devices and through Android. This is very flexible for employees who work in the corporate sector.

I am using Copilot in Microsoft Intune for the creation of policies. While writing policies, I use Copilot for Microsoft Intune to generate automatic tasks for these scenarios and conditions. This has been very helpful to the employees. In some organizations, it has been blocked for security reasons.

It is very easy to deploy Microsoft Intune because of the zero-touch possibilities. Without touching the device, we can manage our devices and configure the device policies and required configurations.

Using the Microsoft Intune portal and the company portal, we are configuring the devices for both Android and Windows devices. For Windows devices, we are using Active Directory to Azure AD join. For Android devices, we are using the company portal for the configurations.

I am using the advanced endpoint analytics in Microsoft Intune for analyzing. Because of security threat allocations, through Microsoft Defender, we are getting the threat intelligence allocations. This is a good built-in feature of Microsoft Intune and is very beneficial from a security perspective.

Microsoft Intune has almost all of the best features. For current situations and scenarios where almost all employees are working from home in a hybrid model, this tool is very useful for device management. This is a very good tool for device management without any restrictions, and we can manage our security data. The best thing about it is that it is a cloud-based device management tool.

As of now, no maintenance is required for Microsoft Intune. It is a very easy and understandable tool. For migrations, sometimes we experience some issues with OS deployment and the user experience side. It would be better to implement something on the GUI side.

The GUI in Microsoft Intune is perfectly good, but they are updating the terminologies. The application terminologies are changing. It would be good to use an updated version so employees can easily understand the terminology.

I have been using Microsoft Intune for four years.

I would rate the stability of Microsoft Intune very highly, as I see no downtime anywhere. Sometimes we need downtime because we need to update our portals and our software. The downtime is managed well, and that is good. No changes are needed.

Microsoft Intune is scalable, and I am giving it a nine rating.

I would rate the technical support of Microsoft Intune a nine.

Positive

It is very easy to deploy Microsoft Intune because of the zero-touch possibilities. Without touching the device, we can manage our devices and configure the device policies and required configurations.

As of now, Microsoft Intune's pricing is in the middle range. I think many people worldwide are using Microsoft Intune, and education institutions are also using it. It would be better to reduce some costs. Like Azure, in Microsoft Intune, we are taking the subscription on a monthly basis. If we are using it or not, it will automatically expire. My suggestion is to charge based on what we are using and for how long we are using the service.

Deployment of any OS or application in Microsoft Intune will take one or two hours only, based on the size and capacity of the application.

In my current organization, most of the members are using the client application of Microsoft Intune. In the client application, almost five thousand members are using it from my client in my project. Almost one hundred thousand devices are using Microsoft Intune.

The enterprise application management in Microsoft Intune has been very useful. When the automatic update option is selected, applications are automatically updated when the application company releases updates. We have the option to update, and if they release update features, they automatically update. Otherwise, they stay on the same feature which we deployed. This is better.

I do not have any objections to Microsoft Intune. It is a very recommended product and very useful. Microsoft Intune is a must and should be needed for this time, for this hybrid model period. The product is very useful, and I highly recommend this product for employees, education institutions, or device management. I would rate this product a nine overall.

My use case for Microsoft Intune includes managing a fleet of about close to 800 laptops and another 500 mobile phone devices like iPhones. We migrated to Microsoft Intune to control and reduce the MSP cost, as our provider was very old-fashioned. As the solution architect, I create plans to ensure cost reduction and process efficiency, particularly regarding Windows patching. 

There wasn't any visibility regarding our devices. Most of the time, we couldn't tell which devices were turned on and which weren't. This lack of clarity resulted in delays with patches, as some devices were not powered on. Overall, it was a mess. To address this issue, we centralized everything into Intune, and we've been handling the patching process since last year. Additionally, we removed Bitdefender and whatever version we were using, and we implemented BitLocker.

From Microsoft Intune, everything is automated. If you need to get the keys, it's super easy for users to obtain them, and someone from IT should also be able to access them. We use Intune because it supports a hybrid environment, allowing us to manage both on-premises devices and our cloud-based services. This means we can still utilize our Active Directory organizational units (OUs) through Microsoft Intune's policies.

Eventually, we plan to migrate everything to Microsoft Intune. However, if we acquire another company that is behind in technology, we might still leverage the traditional Active Directory approach. This would involve integrating their domain into ours, while at the same time continuing to use Microsoft Intune.

We work in the agricultural supply chain, but we prioritize technology. We have the world's fastest terminal for grain loading and unloading, located in Vancouver, Canada. We operate our own trains and are responsible for nearly 20% of Canadian grain exports.

I find Microsoft Intune most valuable for its user-friendly automation and ease of use compared to other tools. We also started using Azure Windows Update Manager for our servers. Microsoft Intune is automated, where you don't need to be an Active Directory guru to manage OUs. This ease has significantly improved our patching process, allowing users to have options on whether they want to receive updates immediately or delay them, which enhances user experience compared to when we used other tools that forced reboots during meetings. With these improvements, I estimate we've reduced our patching costs by over $100,000 a month, as the MSP previously had to troubleshoot various issues manually.

To improve Microsoft Intune, I suggest enhancing reporting capabilities, including better visualization and more export options for deeper analysis. Integrating Power BI reports would be beneficial, as it currently requires manual API interaction rather than having straightforward pre-built reports.

I have been using Microsoft Intune for about two years now.

I have an issue with my MSP who is providing Azure service and other things. I used to work at ExxonMobil, where when you called or sent an email, you would receive a response within an hour. However, with Microsoft, it takes a lot longer, and I’m not getting quick resolutions. Sometimes, I find myself bouncing around between different support groups. I believe that for smaller clients, there should be a special support system in place.

Neutral

We were previously using McAfee for security. At that time, we didn’t have Microsoft Intune. After we transitioned to Microsoft Intune, we used it to encrypt our devices. As a result, we removed Bitdefender, which was the McAfee equivalent, and started using the Microsoft version instead.

I was involved in the initial setup and deployment of Microsoft Intune. It depends significantly on how the initial Active Directory was configured, and we faced considerable challenges during the registration of a hybrid setup, as hybrid configurations are complex. While cloud setups are easier, hybrid is more cumbersome. It requires knowledgeable consultants or an adept IT team familiar with all features and registrations. Through three months of trial and error, we reached a setup that works for us.

We have a cloud engineer. We also have some analysts, so about four or five people were involved.

With these improvements, I estimate we've reduced our patching costs by over $100,000 a month, as the MSP previously had to troubleshoot various issues manually.

I've heard that they might take it away from the E3 license and charge us separately. I'm not sure if it's true or not. My E3 license covers Microsoft Intune, so I think we're good.

Microsoft Intune does not yet bring all endpoint and security management tools into one place as we are still integrating everything. We haven't yet started using Microsoft Endpoint Protection and are still relying on other tools such as Tenable.

The user experience with Microsoft Intune has improved significantly over time. When I started, there was a learning curve, but I find Microsoft to be consistently better than other vendors. I might be biased as I'm essentially a Microsoft shop being a Microsoft certified solution architect with six different certifications from Microsoft.

Using Microsoft Intune alongside Microsoft Office and integrating tools via Graph API allows for seamless extension within the Microsoft ecosystem, while integrating third-party tools can complicate management. My experience with Enterprise Application Management in Microsoft Intune includes managing some applications, although we haven't yet started with dashboards to show downloadable applications.

We use Microsoft Intune to manage Windows 11 upgrades, which proceed smoothly. With Microsoft Intune, I am managing devices, including mobile devices such as iPhones, but I plan to incorporate security endpoints soon, possibly next year. We conducted Windows 11 upgrades recently since the deadline for Windows 10 licensing is approaching. This project initiated last year with the focus on drive encryption, followed by transitioning rules from OU to Intune, and we are now proceeding with Windows upgrades.

We use the cloud interface of Microsoft Intune only, without utilizing any SDKs yet. 

I would advise adopting Microsoft Intune as soon as possible. It's crucial to manage a multitude of devices since efficient patching is essential for security. Outdated devices pose vulnerabilities for hackers. Microsoft Intune is a leading tool in this regard, as it passively pushes updates with minimal user intervention.

We currently have only our managers utilizing Co-pilot in Microsoft Intune by activating it specifically for them. I am familiar with Co-pilot, and I am also a manager. I have heard that the licensing for Microsoft Intune may be separated from the E3 license. Currently, I believe that my E3 license covers Microsoft Intune, enabling us to operate without concerns.

I would rate Microsoft Intune a nine out of ten.

Microsoft Intune is mainly used by me for device management and security in the Microsoft 365 environment. I have worked on enrolling devices, managing Windows endpoints, applying compliance policies, and deploying security configurations. It has helped centralize device management and enforce security policies remotely. For example, we use Microsoft Intune to manage company laptops remotely. We configure compliance policies, enforce encryption, and deploy security updates. It allows us to control devices even when users are working remotely.

One of the main advantages of Microsoft Intune is its centralized device management. It integrates very well with Microsoft 365 and Azure Active Directory (Azure AD). It also improves security by allowing administrators to enforce compliance policies and manage devices remotely.

Microsoft Intune brings endpoint security into one place. The benefit of Microsoft Intune is that it centralizes all device management and strong security policies in the same interface.

I use the endpoint management feature in Microsoft Intune to manage and secure company devices. This includes device enrollment, applying security policies, and monitoring.

Microsoft Intune helps secure hybrid work by allowing organizations to manage and secure devices remotely. Administrators can apply security policies, enforce compliance rules, and ensure that only trusted devices can access company resources.

The downsides of Microsoft Intune include the fact that the interface can sometimes be complex for new administrators. Some configurations require a good understanding of the Microsoft environment. Additionally, troubleshooting device enrollment issues may sometimes take time.

I have been working with Microsoft Intune for three years overall.

Microsoft Intune is a generally stable solution. Its performance is good for device management and security in production. In my experience, Microsoft Intune is a stable platform as it is a cloud-based service, and updates are regularly delivered by Microsoft.

Microsoft Intune is highly scalable. It can manage a few devices or tens of thousands of devices across multiple locations without issues. Microsoft Intune is designed for scalability and supports large enterprises with thousands of users and devices, allowing IT teams to deploy policies, manage devices, and monitor compliance across the organization efficiently.

I have contacted the technical support or customer support of Microsoft regarding Microsoft Intune.

The quality of the support for Microsoft Intune is good. Microsoft provides good technical support for Microsoft Intune, including documentation, community resources, and official support channels, and you can open a ticket. In general, the support is reliable, especially the Microsoft documentation and enterprise support channels.

I would rate the quality of support for Microsoft Intune as a ten because it is powerful.

Positive

I have mostly worked with Microsoft solutions. Compared to traditional on-premise device management tools, Microsoft Intune offers more flexibility because it is cloud-based.

The initial deployment of Microsoft Intune is easy to difficult, depending on the experience of the administrator. The deployment process falls between easy and difficult.

You need two people to deploy Microsoft Intune.

For organizations already using Microsoft 365, the cost of Microsoft Intune provides good value, as it includes the device management and security features in one platform.

It is not me who manages the pricing for Microsoft Intune. A finance service manages this, but I do not have many insights about the price for Microsoft Intune.

I did not use Copilot in Microsoft Intune, but I used Copilot separately.

I remember Microsoft Intune. I would rate this review a nine overall.

I can provide a specific example of how I use Microsoft Intune in my daily work. Application deployment and device configuration represent key areas where I utilize Microsoft Intune. For example, in my daily work, I use Microsoft Intune to deploy applications, assign configuration profiles, and enforce compliance policies on corporate devices. When a new device is enrolled, I can ensure it automatically receives the required security settings and business applications. This helps standardize the environment and reduce the operational effort.

Microsoft Intune is especially valuable when you need to standardize and automate endpoint management at scale. In my work, I have also used it to solve more complex challenges, such as migrating devices from traditional management to modern management, for example, from on-premises to cloud-first. A unique aspect is the ability to combine Microsoft Intune with tools like Windows Autopilot instead of SCCM OSD deployment. You can use compliance policies and conditional access to build a more secure and consistent user experience.

From an operational efficiency perspective, Microsoft Intune has helped reduce the amount of manual work involved in device provisioning, application deployment, and policy enforcement. We don't always measure it with exact numbers, but the improvement is clear in day-to-day operations. For example, preparing a new device now takes much less effort than in more traditional management models because many activities are automated and standardized.

Conditional Access is valuable for us and for everyone because it allows connecting device compliance with access control. In practice, you can use it to ensure that only compliant and trusted devices can access corporate resources such as Microsoft 365 apps and other company services. For example, if a device is not compliant with the security requirements, such as encryption, password policy, or device health, access can be blocked or limited. This is extremely important in an environment because it helps enforce security without relying only on the user's identity.

One of the biggest advantages of Microsoft Intune is not only the management itself, but also how well it integrates with other Microsoft technologies. For example, when you combine Microsoft Intune with Microsoft Entra ID, Conditional Access, Windows Autopilot, and Microsoft Defender, you can build a much more automated and secure endpoint management model. From my perspective, this integration is one of the main reasons why Microsoft Intune is valuable in modern environments.

Microsoft Intune is a very strong platform, but there are still some areas where it could improve. In my personal opinion, reporting and troubleshooting could be more detailed, especially when dealing with complex scenarios. I also think some features could be more consistent across different platforms, and some administrative workflows could be simpler. Overall, the product is very good, but there is still room for improvement in visibility and usability.

For example, the user interface could be improved in some areas. Sometimes the admin experience is not as intuitive as it could be, especially when features are spread across different sections or when it takes too many steps to find a specific setting or troubleshooting detail. I also think support and feature consistency across operating systems could be stronger. Windows is clearly the most mature platform in Microsoft Intune, and while some capabilities on macOS, iOS, and Android can feel more limited or less consistent, depending on the specific scenario. Overall, there is room to improve usability, visibility, and cross-platform consistency.

I have been working with Microsoft Intune for more than 10 years, mainly in endpoint management, device compliance, security, and modern workplace projects.

Yes, overall I would say Microsoft Intune is stable. It is a mature cloud service and in my experience it performs reliably for everyday endpoint management tasks such as policy deployment, application delivery, compliance management, and device administration. Microsoft also provides service health and tenant status visibility, which helps administrators monitor incidents and planned changes. Of course, like any cloud platform, it can occasionally have service issues or rollout delays, so it is not perfect. But overall, I consider it a stable and dependable solution for modern endpoint management.

Microsoft Intune is highly scalable because it is well suited for organizations of different sizes, from smaller environments to very large enterprises. One of its main strengths is that as a cloud-native service, it can scale without the same infrastructure constraints you typically have, for example, in an on-premises solution. In my experience, it supports growth well, especially when combined with the broader Microsoft ecosystem for identity, security, and automation.

I would say the customer support is generally good. It is reliable overall, although the experience can vary depending on the complexity of the issue. Standard cases are usually handled well, while more complex scenarios may take longer to resolve, but overall the support experience is positive.

Positive

Before Microsoft Intune, we used SCCM or Microsoft Endpoint Configuration Manager. The main reason for the switch was the need to move toward a more modern, cloud-based management model. Microsoft Intune offered better support for remote management, modern provisioning, and mobile device management, and also the integration with services such as Entra ID, Conditional Access, and Autopilot. It also helped reduce the dependency on on-premises infrastructure and made endpoint management more flexible and scalable.

This is a very big question because it's not just technical. My advice would be to start with planning and know it configuration. First, define your device scenarios, ownership model, enrollment method, security requirement, and application strategy. Then, and only then, use a phased rollout with a smaller pilot group before scaling broadly because Microsoft's own deployment guidance recommends a phased approach and highlights the need to plan enrollment prerequisites and support scenarios yearly.

Other

We have seen a return on investment, mainly in terms of time saving, operational efficiency, and improved standardization. We don't always measure it in very strict financial terms, but the value is clear in day-to-day operations. With Microsoft Intune, tasks such as device provisioning, policy deployment, application delivery, and compliance enforcement require less manual effort than in more traditional management models. This helps reduce administrative overhead and allows IT teams to focus more on higher value activities.

In my experience, the prices and licensing are reasonable, especially for organizations that are already invested in the Microsoft ecosystem. The value becomes clear when Microsoft Intune is used together with other Microsoft services because it is a part of a broader management and security platform. Setup costs can vary depending on the size of the environment and the complexity of the project, but in general, the cloud-based model helps reduce some of the infrastructure costs you would typically have with a more traditional solution. The main challenge I think is usually licensing complexity because understanding the different Microsoft bundles and plans can sometimes be less straightforward than the technical setup itself.

I didn't evaluate another option because the choice was mainly driven by the Microsoft ecosystem we were already using. Since we were already working with Microsoft technologies, Microsoft Intune was the most natural fit because of its integration with services such as Microsoft 365, Entra ID, Conditional Access, and other security and management tools.

Overall, my view is very positive. Microsoft Intune is a strong solution for modern device management. One of its biggest advantages is how well it integrates with the broader Microsoft ecosystem because it helps improve security and standardization. There are still some areas that could improve, such as reporting, but overall, I see it as a very valuable platform. I love Microsoft Intune. My overall review rating for Microsoft Intune is nine out of ten.

I have used almost all features that Microsoft Intune provides for my use case, whether it is configuration management, remote access, or endpoint management.

The most valuable aspect of Microsoft Intune to me is the simplicity of the UI. It is not difficult for me to explain to my juniors how things work, and the admin console is well organized. For example, if I need to go to applications, I can navigate to Apps, then Windows apps or other apps. The organization is excellent.

The API is the best feature of Microsoft Intune. The Graph API is exceptional. I use Microsoft Graph API extensively through Python, PowerShell, or C# .NET SDK, and it is very effective.

It definitely saves considerable time with the new device provisioning process. Since the API is flexible and powerful, I have automated many activities that have saved hours of work. I would not say resources were saved, but hours were saved.

Microsoft Intune could be faster with client to server communication. Whenever I push something, it takes time. Sometimes it takes more than one hour to deploy on the Windows side, for example. Since Windows is a Microsoft product and Microsoft Intune is also a Microsoft product, it should be much faster, but it is too slow compared to other MDM solutions.

Speed is the main concern for people. Apart from these issues, there are definitely many things that could be proposed at the feature level.

Advanced discovery is an area where there is room for improvement. It provides whatever schema is designed in the backend, but when they say advanced, I should be able to fetch whatever I want. That is not the case. The feature has been added and they continue to add more. Perhaps in the future, they will provide additional functionality that can be utilized. The issue is that I can get reporting, but I cannot utilize the same reporting to convert it into a query for Azure AD groups to handle remediations or fix problems based on that data. I am not sure whether this is in the pipeline, but they have many research and development people, so they might be considering it.

I have been using Microsoft Intune for nine years and twenty-four days.

For stability, I would rate it nine point nine out of ten.

I would not rate it ten out of ten because nothing is perfect, but it is nine point nine out of ten for scalability.

I would rate the technical support at seven out of ten.

Microsoft outsourced the support to a third-party vendor, and they are not very effective. They are not good at handling issues, and they take too much time. I have to explain the same issues to multiple engineers, and they have a very rigid template. They do not think outside the box; they think only from the template perspective. That kind of approach drags out the issue even if it is not significant. I have given direct feedback to Microsoft on this, and support needs to be improved.

Positive

I worked with Jamf and I currently work with Jamf. One advantage of Jamf is that it is very fast compared to Microsoft Intune when it comes to client and server communication. Whenever I deploy anything, it reaches the device within a minute, but Microsoft Intune deployment is too slow.

Compared to other solutions in the market, Microsoft Intune is almost free because it is part of the Microsoft 365 E3 or E5 suite, which is why people do not complain much about the speed. In parallel, Jamf charges more than seventy USD per device per year. Microsoft Intune is a very cost-effective solution.

Initial deployment is very easy.

If somebody has good or even moderate knowledge and experience, they can set up the tenant and make it ready to use at a basic level within two or three hours.

Approximately thirty-three percent of ticket automation has been achieved. If I receive one hundred tickets, I now receive around seventy, so thirty percent of the tickets are automated. I am planning to increase this further to reach fifty percent this year.

I would definitely recommend Microsoft Intune to other administrators because this MDM tool provides the capability to manage Android, iOS, Windows, Mac, and now they have added Linux support. All these platforms can be managed from a single console, and I do not have to buy additional device-based licenses. It works on user-based licenses, and one user can use multiple types of devices without paying much. Other features such as application management are available, and it integrates well with conditional access to identify real-time threats during sign-in. Microsoft Intune is a very effective solution from my understanding, and I definitely would recommend it. The overall review rating I would give is nine point five out of ten.

I started my career with Microsoft Intune, so I am very close to it, and all aspects are fine except for the speed issue. For this reason, I would rate it nine point five out of ten.

My final rating is nine out of ten.

I work exclusively with Microsoft products, and we use the E3 license for Office, for the Microsoft portal, which includes some security solutions, SharePoint, and Office applications. Microsoft Intune is mandatory in our business. I work with Microsoft Intune as an integrator, user, and administrator.

The major purpose for using Microsoft Intune is enforcing policies, controlling onboarding processes of computers, and enforcing privacy and data link prevention. I am using Microsoft Copilot in Microsoft Intune. I am using the Enterprise Application Management feature in Microsoft Intune Suite.

The biggest benefit for me in Microsoft Intune is control. I can control my users and what they can do, and enforce the policies that I want to enforce. It is a great tool to control and put structure, to take the organization to the place I want to take it.

Microsoft Intune changes my ability when it comes to app discovery, deployment, and automatic updating. If I were to give it a score, I would give it eighty percent.

I do see that Microsoft Intune is saving me a significant amount of time. I think it allows me to do one hundred percent more within my time.

I would assess the user experience of Microsoft Intune as not user-friendly in general. It may cause some problems or require more time for training because it seems that Microsoft is doing their best to confuse me with menus that move to a different location every other day. However, there is a lot of knowledge online, so it is doable.

The information Microsoft Copilot provides is of concerning quality. It could be so much better if it would take me to the correct menu that I am looking for instead of giving me instructions to places that do not exist anymore. It is not something that I would recommend somebody to use.

Microsoft Copilot in Microsoft Intune is absolutely useless for protecting my environment.

I do not have any other areas for improvements that I have not mentioned or anything more that could be enhanced.

I have been dealing with Microsoft Intune for six to seven years.

I have not experienced any downtime, crashes, or performance issues with Microsoft Intune. Overall, I could say that Microsoft Intune is very stable.

As for scalability, I find Microsoft Intune scales very well with the growing needs of my company. I do not see any limitations, and it is not expensive to scale, so it is very flexible.

I have interacted with technical support from Microsoft. My experience is neutral because it is easier to contact ChatGPT to find answers. Based on my interactions with support in the past, I would give them six points from zero to ten, where ten points is the best. I give them six because it is hard to find them, and then it is hard to understand what they say usually because of accent issues with people coming from India or Africa or elsewhere, which I respect, but it is hard to understand for me.

Positive

Before Microsoft Intune, I was using another product for the same purpose that I forgot its name, but it was awful.

My experience with the deployment of Microsoft Intune is that it was straightforward. The deployment part is not complex.

I bought Microsoft Intune directly from Microsoft.

The pricing is reasonable.

I replaced the product with something else, but I forgot what it was. The reason for replacement was that I think Microsoft Intune is better and it is integrated inside our environment. It is much easier to connect it to the environment than to bring a third party and connect it.

I try to use Microsoft Copilot, but it is uncomfortable. It seems that ChatGPT usually knows better what to do, and the last time that I used it, I used it to find how to get rid of it. I give this review a rating of eight.

I manage around 3,000 Windows devices across different countries. Before that, I used Microsoft Intune as a consultant at Cluster Reply, working with customers including IVECO Group. Over time, I have also worked with related tools including Autopilot, Autopatch, and Entra ID.

I value Windows Autopilot in Microsoft Intune the most. Devices set themselves up when turned on for the first time, eliminating the need for manual imaging. Windows Autopatch is another feature I use extensively to automate Windows updates across different groups of devices in a safe and phased way. Remediation scripts are also a feature I use frequently because they allow me to execute small scripts that automatically detect and fix configuration problems on devices.

Using Microsoft Intune has helped my organization save time through automatically executing actions remotely on devices. This is a great advantage because we do not need to go physically to each device and execute actions manually. We can use Microsoft Intune to automatically execute them instead.

I use advanced endpoint analytics in Microsoft Intune to verify the health status of our devices. With advanced endpoint analytics, we can identify devices that are in a bad health status and determine the boot status of the devices, including how long they take to start and turn on. This feature provides several other capabilities that are very helpful for IT administrators.

Microsoft Intune is an easy solution for IT administrators, and I would recommend it, though this depends on the organization. There are a few areas where Microsoft Intune still needs improvement. For example, app packaging, policy conflicts, and reporting require attention.

Reporting in Microsoft Intune presents challenges because the built-in reports are often too basic. For detailed data, you usually need to set up Log Analytics and write custom queries. Policy conflicts are another concern, as when two policies target the same setting, it is not always clear which one takes precedence. This can cause unexpected behavior. App packaging is also an area for improvement, as packaging Win32 apps for Microsoft Intune is more manual and time-consuming compared to SCCM, Configuration Manager, which is an on-premise tool.

I have been using Microsoft Intune for over four years.

I would rate the stability as seven. In my opinion, it can be improved because sometimes we experience bugs in the portal, which is why we prefer to interact with PowerShell to automatically perform our tasks.

I would rate the technical support for Microsoft Intune as eight.

I have used Workspace ONE in a few projects. I prefer Microsoft Intune because it is more user-friendly than Workspace ONE, and it is easier to deploy devices and patch managed devices with Microsoft Intune.

Deploying Microsoft Intune is really easy. Compared to SCCM Configuration Manager, Microsoft Intune trades some low flexibility and control for cloud-native scale and simplicity. SCCM still wins for complex software deployment scenarios, but Microsoft Intune is a good upgrade that is easy to deploy without any need for a VPN.

I would say Microsoft Intune saves us about forty percent.

It is a little expensive for organizations using Microsoft Intune. I am aware that Microsoft increased the cost of the E3 and E5 licenses starting from July, and I think that this pricing is a bit expensive.

I use Security Copilot in Microsoft Intune to troubleshoot issues. For example, Copilot is really helpful for understanding policy conflicts because it allows me to understand the root cause of the issue. I also use it to identify non-compliant devices and determine how to remediate them, either by understanding how not to patch the devices or by using an existing catalog rather than a remediation script.

Microsoft Intune provides good integration with other products. For example, it integrates with the HP Portal Company to manage the BIOS settings of the devices and their updates, and it integrates with Configuration Manager and Entra ID. This integration provides a good experience with other products.

My feedback is positive, and I would recommend Microsoft Intune to others. I would say that Microsoft Intune is absolutely the right choice for any organization that is already invested in the Microsoft 365 ecosystem and wants a unified cloud-native endpoint management approach. I give this product an overall rating of nine out of ten.