Microsoft Intune Reviews

Microsoft Intune's absolute core use case can be boiled down to one phrase: securing corporate data on any device, anywhere. Modern enterprises operate with the traditional network perimeter essentially dead, and people work from home, airports, and coffee shops. Unified Endpoint Management and enabling secure hybrid and mobile work is the distinctive answer to this challenge.

I want to specify one scenario where the company was onboarding fifty new remote employees across three different continents. The legacy way was that IT would have spent the previous week unboxing fifty laptops, manually logging and imaging them with a corporate OS file, repackaging them, and shipping them out. However, how Unified Endpoint Management actually helped is that the hardware vendor ships the laptop sealed straight from the factory to employees' homes. The employees unbox their machines, turn them on, and connect their home Wi-Fi. Then they type their corporate email and password. Instantly, the Unified Endpoint Management platform takes over. It pushes down the corporate security baseline, installs the core software suite including Office, Teams, browser extensions, and so on, and configures the company VPN. Within twenty minutes, the employee is fully productive and IT never had to touch a single piece of plastic.

Another situation involved a critical zero-day security vulnerability that was announced for a major web browser at ten o'clock in the morning and had to be addressed for both Windows and macOS users. Instead of actually jumping into two separate systems, I logged into the single Unified Endpoint Management console, packaged the updated browser version and targeted it to global device groups. The action taken was to set an explicit deadline for the installation first. For active machines, the browser updates silently in the background without interrupting the user. For offline machines, the policy waits patiently and executes the millisecond they check back in. By the end of the day, the dashboard showed ninety-five percent remediation across both operating systems, giving the security team complete peace of mind.

The best features I can name are the following. First is Mobile Application Management with App Protection Policies. The second one is Windows Autopilot integration. The third one I can recall is Conditional Access integration with Microsoft Entra ID. The fourth one is Endpoint Privilege Management and Cloud PKI.

If I have to pull back the curtain and look at the single mechanism that holds the entire modern enterprise framework together, I find myself relying most on Conditional Access integration with Microsoft Entra ID. While features such as Autopilot are incredible for onboarding, Mobile Application Management is brilliant for mobile devices, Conditional Access acts as the brain of the entire security infrastructure. It is the feature that actively stops data breaches in real-time.

In the past, security was operated as a castle with a moat. Once a user was inside the office network, they were trusted implicitly. Today, that model is a massive liability. Conditional Access flips the script. It assumes every connection request is weak until proven otherwise. It takes telemetry from Microsoft Intune regarding the device health. Is it encrypted? Do you have any antivirus? Is it fully patched? It is combined with the identity signals. Is the user logging in from an unusual country? Are they using multi-factor authentication? Only when every single condition is satisfied does it grant access to the data. This is very useful information and a useful feature which implements a true zero trust and verify explicitly approach. Because this was the most valuable asset for any modern organization, and it helped us provide security to any connection the system had for our organization.

From a strategic and intellectual perspective, the product fundamentally shifts how a company operates by changing IT from a traditional cost center into an engine of operational efficiency. When you evaluate the impact the product had on the enterprise, there are three distinct areas. One is radical optimization for IT overhead upon a team. Before a unified cloud platform such as Microsoft Intune, managing a global workforce required an expensive, fragmented stack of specialized tools. One was for Windows imaging, another for macOS management, and entirely separate third-party licenses for mobile security. The second one is the elimination of the onboarding bottleneck. The third one is bulletproof data isolation on mobile assets. The most complex challenge for any enterprise is managing the risk of intellectual property theft and any accidental data leakage on mobile devices. Historically, my company tried to solve this by completely locking down or seizing control of an employee's personal phone, but which caused really bad reviews from the employees and very user friction, legal liabilities, and massive pushback from personal privacy concerns. Microsoft Intune Mobile Application Management elegantly orchestrated a solution. It enforced a strict cryptographic boundary on corporate applications such as Outlook and OneDrive while leaving the rest of the device completely alone.

Microsoft Intune operates at a massive cloud scale, and I am not able to pinpoint any improvements right now because it already solves so many problems our organization had. It implemented a true zero trust and verify explicitly policy. It avoided security headaches for our IT team. Endpoint Privilege Management was a best feature with Cloud PKI. Windows Autopilot integration was one of them, which was really helpful and I think it literally solved most of our problems. I think it perfectly balanced our corporate security with individual privacy.

I think we can expand tools such as Endpoint Privilege Management and automate driver and firmware patching so they operate identically and flawlessly on macOS and Linux as they do on Windows. This would make Microsoft Intune an untouchable and truly platform-agnostic operating standard.

I have been working in my current field for around three and a half years.

Microsoft Intune is very stable for our organization.

From an architectural perspective, Microsoft Intune's scalability is virtually limitless because the product is decoupled from physical hardware constraints. Whether the organization is managing thirty devices or three hundred thousand devices, the underlying infrastructure scales effortlessly because it runs on a microservice-based architecture on top of a global Microsoft Azure public cloud, which is the in-home cloud. There is no more server sharding.

The customer support experience with Microsoft Intune is highly efficient and built directly into the administrative workflow, specifically designed to meet our standards and demands for the environment. We also appreciate its native and in-console support architecture because when we push the in-console support request, it does automated tenant diagnostics. It has a self-remediation insight link, and if it was unresolved, it was quickly shifted to engineers based on severity of multiple types. Every time we had a problem, the support team really helped us get through it.

Prior to consolidating on Microsoft Intune, our endpoint infrastructure was managed through a combination of traditional on-premises tools and third-party solutions. We previously used on-premises Windows management. We relied on Microsoft Group Policy Objects paired with basic scripting tools to manage internal Windows desktops. This setup worked flawlessly as long as employees were physically sitting inside the office building, connected directly to a local area network. For mobile device management, to manage the corporate smartphones and tablets, we used a specialized third-party platform such as MobileIron. This created a fragmented operational workflow. IT had to jump between one console for laptops and another separate console for mobile assets. The strategic switch was made because our legacy tools served their purpose during the era of the traditional corporate office. The shift towards remote and hybrid work exposed a deep installation and architectural limitation. The off-network visibility was the blind spot with Group Policy Objects, because if a remote employee did not connect to the corporate VPN for three weeks, their laptop would not receive critical security updates or configuration changes. Siloed operations and those were too clouded. Juggling MobileIron for phones and Group Policy Objects for PCs meant duplicated effort. Other options we assessed were VMware Workspace ONE and Jamf Pro for Apple fleet only.

We definitely saw a one hundred eighty-one percent return on investment because when factoring in the cost of implementation and licensing against the total savings, the platform delivered an overall one hundred eighty-one percent over three years. Turning the endpoint infrastructure into a highly efficient operation was the best thing that happened to our organization. The key metric I would like to share is that the composite enterprise saved thirty-eight percent on endpoint licensing cost alone, contributing to many more thousands of dollars in reclaiming budget over a three-year cycle. We had a fifteen percent reduction in risk of material security breach because a single pane of glass that forces devices to meet a security baseline reduced the data breach risk by fifteen percent.

Our licensing experience was really great because from a procurement to deployment standpoint, analyzing the financial and setup architecture for this product reveals a highly strategic model. When properly aligned with an organization's existing licensing estate, it minimizes waste and accelerates time to value. We purchased a standalone Microsoft Intune Plan One, which cost eight dollars per month per user. However, the most mature user wanted to shift to Plan Two. The real financial efficiency comes from bundling. Plan One is already included at no incremental cost in suites such as Microsoft 365 Business Premium, which was the very sweet spot because our organization was under three hundred users.

Some of our projects we used Microsoft Azure. For some projects, we use Amazon Web Services, but mostly our company uses Microsoft Azure.

Ensure your identity foundation, Microsoft Entra ID, is clean and organized before enrolling devices, as Microsoft Intune relies entirely on solid group structures for targeting. Leverage bundled licensing such as Microsoft 365 Business Premium or E3 or E5 to eliminate redundant third-party tools and maximize your return on investment. I would rate this product a ten out of ten.

I mostly manage devices with Microsoft Intune, applying policies such as MAM (application management) and MDM. We have companies who have managed devices, mobile devices, laptops, and mobile telephones. 

I work in a company where we serve medium-small companies up to a few enterprise clients, and we have many customers. I work in cloud support, not doing migration to the cloud, just managing it. I make changes if they want to have a group of people who shouldn't have access to company resources anymore with their non-compliant devices, setting the compliance, and conditional access policies. On a daily basis, it's more about application management - making packages, uploading them to Microsoft Intune, and distributing them to groups of people.

My favorite feature about Microsoft Intune is that I have good logging capabilities. I can effectively troubleshoot, though I'm also missing some aspects. 

It gives me a good base to troubleshoot device conflicts of policies, but when an application fails, it doesn't provide enough information about where to look for the issue.

I use advanced endpoint analytics in Microsoft Intune extensively and think it's good but has room for improvements. You see error messages directly, but sometimes you have to search for them and find more information in random blogs from MVPs rather than from Microsoft itself. Everything which is policy related is very good in logging, but everything app related needs improvement.

There can definitely be more transparency in synchronization. Sometimes you push a policy and then you're waiting without knowing if it will take 10 minutes or 25 minutes. Then you go to the device, and it's already there, but the information isn't in Microsoft Intune that it's already there. As an administrator, you are somewhat lost in the synchronization part. There's no information about which process it is and how long it would take. If there was any information that it takes 25 minutes, that would be fine. Sometimes it's fast, sometimes it's not, which can be annoying.

I have been using Microsoft Intune for five years.

We've experienced issues, especially for enterprise customers where we enrolled 150 to 250 devices per week for more than one year in Microsoft Intune. This customer has more than 25,000 devices running. You can have a bad day where 80% of the enrollments failed. The next day it's running with the same devices without any changes, and you don't know why. The downtime isn't officially tracked in your health report. It appears Microsoft Intune undergoes changes without informing customers. It happens for short periods only, but it seems they are doing some changes without informing the customers.

Microsoft Intune is good in scalability in general because we have enterprise customers with many policies and devices.

The quality and speed of support depends on the agent. You can get very basic support or very professional support. My company has premium support, which runs much better. We get routed to the correct persons who give us good answers. What is annoying is when they close a ticket because they are very fast with closing it, you have to provide all the logs again. Once the support said they couldn't see or reopen an old ticket where all the logs were already included, so we needed to do all the fiddler logs again with the customer, which is pretty annoying for them as well.

Neutral

I haven't tried using any alternatives to Microsoft Intune.

Related to what you can do and manage with Microsoft Intune, I would say it's easy. The Windows Autopilot profile is pretty straightforward. Troubleshooting when it fails is challenging. This involves going through forums, and with Dell, some drivers get swiped, making remote management impossible. The initial deployment and setting for Windows Autopilot is straightforward and good.

Once the Autopilot profile is set in Microsoft Intune, it doesn't need any maintenance. This works pretty fine. Later on, you have some apps included and build a bigger profile which has to be set up. If something goes wrong, we check what we did later on, but we don't touch the Autopilot profile much.

We have a team of three people for Microsoft Intune deployment, and we check in teams during integration.

Microsoft is generally super complicated in pricing because they split every package into an extra subscription. I know about the licenses such as Business Premium, E3, E5, F3, and so on. This is straightforward and clear what you get. But with Copilot additional license and endpoint security advanced packages, it's not clear for customers whose main business isn't Microsoft Intune or M365 administration. As a middleman, I have to explain the complicated stuff from Microsoft to the customer.

Regarding enterprise application management, I use it more through Azure portal to give consent to apps and give permissions there. 

I would rate Microsoft Intune an eight out of ten.

My main use case for Microsoft Intune is device management, policy enforcement, application deployment, and ensuring endpoint compliance.

For example, I use Microsoft Intune to enforce BitLocker encryption by creating a compliance policy that automatically checks if devices are encrypted and blocks access to company resources if they are non-compliant. This ensures all endpoints meet security standards without manual investigation.

In addition to that, we are using Microsoft Intune for zero-touch device provisioning with Windows Autopilot, remote troubleshooting, and automated app deployment.

The best features Microsoft Intune offers include centralized device management, strong security compliance, application management, and the ability to easily deploy updates and control apps across all managed devices. Centralized device management, easy app deployment, conditional access, and seamless integration with the Microsoft ecosystem are particularly valuable.

Another great feature of Microsoft Intune is Windows Autopilot, which enables zero-touch device provisioning along with remote actions such as wipe, reset, and lock for lost devices, and detailed compliance policies with conditional access.

Microsoft Intune has positively impacted our organization by simplifying device management, improving security compliance, and reducing manual efforts through automation, enabling faster processes. We have seen a 30 to 40 percent reduction in manual effort. Device onboarding time has reduced from hours to under 30 minutes using Autopilot, and the compliance rate has improved to around 90 to 95 percent due to automated policy enforcement and real-time monitoring.

Microsoft Intune could be improved by making the UI more intuitive, enhancing reporting and analytics for better visibility, simplifying troubleshooting and error messaging, and improving performance and policy sync speed in larger environments.

Besides reporting and the UI, troubleshooting could be clearer with more detailed error logs. Policy sync delays should be reduced, and advanced reporting analytics could be more customizable.

I have been working in my current field for around two to three years.

Microsoft Intune is stable.

Microsoft Intune scales very well, allowing organizations to manage thousands of devices across multiple platforms seamlessly through its cloud-based architecture.

The customer support has been generally good. The support team is knowledgeable and responsive. While sometimes response times can vary for complex issues, they provide helpful guidance and proper resolutions when needed.

We previously used manual device management and basic tools such as on-premises Active Directory and some third-party solution. We switched to Microsoft Intune for its cloud-based management, better security, easier policy enforcement, and seamless integration with the Microsoft ecosystem.

We have seen around 30 to 50 percent time savings, much faster onboarding from hours to minutes, and improved team efficiency without needing additional resources. This clearly shows a strong ROI.

The pricing for Microsoft Intune is per user per month and quite reasonable. In many cases, it is already included in Microsoft 365 licenses. It is cost-effective and easy to manage, especially if you are already on Microsoft 365 licensing. The setup does not require a heavy investment.

We looked at tools such as VMware Workspace ONE and ManageEngine Endpoint Central and UEM as they are common alternatives in this space. These tools offer strong device management and automation. We chose Microsoft Intune mainly because it integrates very well with the Microsoft ecosystem, it is easy to manage, and it fits better with our existing infrastructure.

My advice to others looking into using Microsoft Intune is to make sure to plan your device management and compliance policies clearly from the start, especially if you are in a Microsoft environment. Take time to understand Autopilot and conditional access. Once properly configured, it will significantly simplify device management and improve security.

Cloud control made simple, device secured with ease, and workflow runs smoothly. Microsoft Intune is a reliable and effective solution for modern endpoint management. It simplifies device control, strengthens security, and works especially well with the Microsoft ecosystem, making day-to-day operations smoother and more efficient. I would rate this product an 8 out of 10.

My use case for Microsoft Intune is for remote access and configuration management, and it primarily serves security purposes.

The lot of time we saved at deployment. 

Overall, the best features of Microsoft Intune are its ease of management and robust security protocols, which are what I value most about it and how it stands out. Copilot helps in keeping my environment protected by offering real-time assistance with security protocols and compliance checks.

Advanced endpoint analytics in Microsoft Intune help me to detect and remediate anomalies effectively.

Areas that have room for improvement in Microsoft Intune include network dependency, among other factors.

I have been using Microsoft Intune for some time, and my experience with it is extensive.

I would rate the stability of Microsoft Intune highly; I rarely experience downtime, bugs, or glitches. The stability is very high, with minimal issues.

I would rate the scalability of Microsoft Intune as an 8 from 1 to 10.

I would rate the technical support for Microsoft Intune as a 10 from 1 to 10.

The deployment of Microsoft Intune is generally easy, although I do encounter some complexities at times, and I have had challenges deploying it. Deploying Microsoft Intune is often a mixed experience; while it is easy, I have faced challenges at times.

The return on investment I have seen is about 20%. It has saved me time and resources, but quantifying a specific amount has been challenging.

I would compare Microsoft Intune favorably with other products and vendors on the market, emphasizing its integration capabilities and user experience.

Microsoft Intune is deployed in a hybrid model. I use it on Azure cloud, and the deployment time can vary, typically ranging from days to weeks. Approximately 100 users in Capgemini work with Microsoft Intune. My clients are primarily in the medium to enterprise business sector. The solution does require maintenance, and it is complex to maintain, especially regarding updates, patching, and releases. My thoughts on the pricing of Microsoft Intune are that it is fairly priced considering the features offered. From one to 10, I think Microsoft Intune is around a 5 in terms of being cost-efficient. I would rate the pricing of Microsoft Intune as a 5, where 1 is cheap and 10 is expensive. I am using the Enterprise Application Management feature, and it has been beneficial. I would definitely recommend Microsoft Intune to other users due to its features and support. My overall rating for this review is 9.

We have an auto-enrollment process. There are many features in Microsoft Intune. Particularly, my expertise is with Autopilot enrollment and app deployment to workstations and mobile device management. Microsoft Intune is quite comprehensive in its capabilities.

My main use cases revolve around supporting customers who have enrollment processes for laptops that come out of the warehouses. We support that and push packages, set up conditional access, and manage their devices from Microsoft Intune. We handle reset, reboot, deploying app software and deploying apps such as Microsoft 365, any kind of third-party software, Microsoft products, and removing them from an operations point of view. We are a managed service provider for many technologies, and Microsoft Intune is one of them.

Microsoft Intune has affected IT productivity in my customers' organizations overall greatly. It has been a significant help. Microsoft Intune Autopilot enrollment plays a big part in supporting all of these machines, such as users being onboarded, provisioning computers, and mobile devices. All of that is managed from Microsoft Intune, which has simplified the process. Conditional access, determining which users get which apps, what access they have, and what privileges they need, is all handled and managed by Microsoft Intune. This is a great feature that is extensively used by many organizations and administrators.

Policies can be easily managed with Intune. As everything shifts to the cloud, many organizations will likely transition to a remote-only or cloud-only model in the future. They will be using Azure Active Directory, from which these policies will be derived, rather than traditional Active Directory group policies, similar to how organizational units function.

Microsoft Intune brings together all of the endpoint and security management tools in one place. Any endpoint security solution, such as Cortex XDR, Qualys, CyberArk, or CrowdStrike, can be deployed out of the box through Microsoft Intune during the Autopilot process. 

From a security perspective, if a device is lost, you can wipe that machine, laptop, workstation, or mobile device. That is the kind of control you have when using Microsoft Intune. You can effectively manage the device.

I wish there was a way to exclude certain applications based on groups. It is currently making it difficult as we need to keep creating new groups and add those users to that group to segregate. This creates a situation where we must specify which user gets which application and which user should not get certain applications installed. I wish there was an easier way to exclude based on user and not just devices. That is one of the downsides we are facing; we have to keep creating new groups to avoid conflict. The way the apps are getting deployed, the checkboxes for deleting previous versions are actually creating more conflicts than fixing problems. I am certain many people are struggling with that.

The best example I can provide is related to an application I use—Microsoft 365. Microsoft 365 includes a lot of products, such as PowerPoint, Excel, Microsoft Access, and Copilot, among others. However, you don't want everyone to have Microsoft Access installed on all the computers since it's quite outdated and not necessarily needed for everyone. For instance, if I have ten people and I want just one person to have access to Microsoft Access, there's no straightforward way to do that directly. The system doesn't allow me to simply select a user and give them access while ignoring the others. As a result, we often end up creating a new application within Microsoft Intune. This requires putting the user into a separate group to make them eligible for access, while other users stay outside of that group. This process creates unnecessary complexity because it adds more elements to manage. It would be ideal if Microsoft could simplify this process by allowing us to include specific individuals in a group or exclude others more easily.

I have been working with Microsoft Intune for the last six months. 

Microsoft Intune is very stable. It is hosted and managed by Microsoft. When it comes to shared responsibility, there is nothing except for administrators to manage from the operations point of view. Everything else is readily available and quite stable.

There are no real scalability limitations with Microsoft Intune. It all depends on how many E5 licenses or E2 licenses the customer is ready to purchase. The cost typically increases by $4 per computer based on how many laptops or workstations are being managed. It depends on the contracts between the vendor and the customer.

If we encounter problems we cannot solve, we reach out to Microsoft support. There are some MVPs (Most Valuable Persons) who are experts in Microsoft Intune, and we work with Microsoft support when issues become too complicated to resolve independently.

Positive

The deployment model can be either Entra devices only or hybrid. Organizations with on-premises infrastructure might opt for hybrid deployment because some group policies based on organizational units remain legacy. Not everyone can move entirely to the cloud. Customers who are consolidating everything in their data center may choose to go completely cloud-based with Entra devices. The future trajectory suggests everything will be in Microsoft Intune within the next five to ten years.

I have been involved in configuring Microsoft Intune rather than deploying it. We activate Microsoft Intune, set up the applications, dynamic groups, deployment profile, MDM profile, configuration, and encryption. When everything is set up and ready, we begin the enrollment of new devices, and out-of-the-box machines get all the apps installed, completely provisioned from Microsoft Intune. We perform this service for many of our clients.

The process is not straightforward. The process begins with assessment and requirement gathering, along with several preliminary tasks, such as pre-migration activities. For instance, we need to analyze all the group policies to determine which ones are compatible with the new system. I would consider this a project in itself. There are numerous features available in Microsoft Intune, but the client won't use every single one. Ultimately, it depends on the customer's goals and the recommendations provided by the solution architect. What the customer chooses to implement will also play a crucial role in this process.

It has helped save costs. Many people were using third-party tools, such as KACE or Quest, for patching and other tasks. However, Microsoft Intune has streamlined and automated these processes. This has significantly simplified the management of users and devices. Generally, just one or two people can efficiently handle a lot of administrative tasks using Microsoft Intune. For instance, they can ensure that workstations are compliant and manage various aspects of IT administration.

Microsoft Intune not only saves costs by reducing the number of personnel needed but also offers a comprehensive solution for managing laptops, applications, security, individual access, and enrollment. My customers have greatly benefited from these capabilities.

I would rate Microsoft Intune an eight out of ten.

The purpose of using Microsoft Intune is to provide security for all company devices and company data. 

As an Intune Consultant, the role involves suggesting ideas for implementation.

I use Microsoft's Copilot in Microsoft Intune. It helps tremendously. I work as an architect and consultant in Microsoft Intune, and it assists majorly in developing new scripts and customizations which do not have built-in templates in Microsoft Intune. We can customize our requirements using Copilot, which helps significantly in that aspect.

The Enterprise Application Management feature in Microsoft Intune helps tremendously with deployment because one of the strongest points is pushing out customized applications as Win32. Even without a package, deployment can be done as a PowerShell script. Customization in deploying applications can be managed using application protection policies, which provide control of company data even on personal machines, such as iOS or Android, without interrupting privacy.

I particularly appreciate the features for Windows machines because it's a Microsoft product that specializes in developing Windows machines and can manage them effectively. Any data on machines or devices can be monitored professionally and completely while securing the data. The security implementation has been developed brilliantly over the past few years, and its cost is very efficient compared to other MDM tools.

Microsoft Intune is very easy to understand for anyone. 

Certificate management within Microsoft Intune's Suite is still under development. It's not very reliable compared to other certificate tools, though it has made good progress within a couple of years. Microsoft Intune could provide more features in certificate management, delivery optimization, patching, and technical support. These areas have scope for significant improvement.

It has been around four years.

Nothing is perfect. Microsoft Intune deserves a rating of nine out of ten. It performs very well with no downtime at all.

Microsoft Intune is scalable but still has scope for improvement.

Our clients are large enterprise businesses. In my organization, there are many users specializing in Microsoft Intune, but in my project, I'm the main one. Overall, the company supports nearly 1,000 clients, but I'm not exactly sure how many Intune administrators we have. However, I can say there are quite a few.

The technical support of Microsoft Intune rates at seven out of ten. Having worked for Microsoft support previously, providing answers to organizational tickets, the experience was good. Many employees had great knowledge from their experience working at Microsoft. However, due to workload, organizations sometimes find it difficult to get timely answers when they reach out to Microsoft support.

Neutral

We have a hybrid deployment method for Microsoft Intune. One client was using SCCM previously, and we migrated all policies and related configurations to Microsoft Intune. We have already had machines set up, so all the previous machines are in a co-managed or hybrid state, you could say. But right now, we are enrolling all our machines with Autopilot, meaning they are all cloud machines.

It doesn't require much maintenance. If you have a subscription, your license takes care of everything. You don’t need to worry about updates or anything else; it updates automatically without user intervention or admin approval

It saves time, money, and resources. When there was a local liaison, managing everything was a significant challenge. Without utilizing any MDM tools, handling all the organizational units (OUs) was quite difficult. It has become much easier. I would estimate it to be around 60% to 70% easier. It is very beneficial. In terms of reliability and ease of use, it excels.

Microsoft Intune is very cost-efficient, which is a major reason for its rapid growth compared to other tools in the industry. Additionally, its ability to integrate configurations and collaborate with services like Copilot and recent offerings from Microsoft makes it stand out, allowing it to grow at a faster pace compared to other MDM tools.

Microsoft Intune is recommended for Windows management specifically. However, it's not recommended for managing iOS devices or Mac devices, as Apple products don't have many configurations within Microsoft Intune. Other MDM tools such as Jamf are superior for Apple products, though not as good for Windows, which is why organizations often use both tools together.

I would rate Microsoft Intune an eight out of ten.

Microsoft Intune was used by the organization that hired me. Microsoft Intune allows organizations to manage all devices. It is a cloud-based service that helps organizations manage and secure their devices such as laptops, smartphones, and iOS devices. We primarily used it for managing applications through mobile application management (MAM) and mobile device management (MDM). Device enrollment is another purpose of Microsoft Intune which automatically configures devices within the organization with their work accounts.

In the Microsoft Intune company portal, there is an option to develop and deploy applications that are trusted by the company. 

Additional use cases include compliance, conditional access, and endpoint security. To summarize, the main purposes are MDM for laptops, mobiles, and iOS devices; MAM; device enrollment; app deployment; compliance and conditional access; and endpoint security. I had access to compliance and conditional access, endpoint security, device enrollment, MDM, and MAM. App deployment was not part of my responsibilities.

Microsoft Intune provides valuable functionality for locating lost devices. Through the Endpoint Management Admin Center within Microsoft Intune, we can find the last seen location of enrolled devices that may have been stolen or misplaced. This requires device numbers, serial numbers, usernames, or IMEI for mobile phones.

Another excellent feature is the ability to enroll devices and set compliance status. Notifications can be pushed from the Microsoft Intune Admin Center to users' portals, informing them when devices are not compliant and providing steps to follow company policies.

Microsoft Intune saves approximately 20% of time and resources through automated features that enable quick resolution and guided SOPs. It reduces troubleshooting and support time by 30-40%. The security compliance capabilities make it widely adopted across organizations. The user experience is robust, and the pricing model is budget-friendly. Its integration with Azure AD and Microsoft 365 applications adds significant value.

Microsoft Intune could be improved in several key areas. Policy and app deployment should be faster, as it currently takes between minutes to hours to apply, with an average of one hour. This could be enhanced by adding real-time sync or faster push intervals for critical changes. When users transition between devices, the process takes 45 minutes to one hour, which could be optimized.

The error reporting system needs improvement, particularly for automatic retry of failed installations. In the Microsoft Intune company portal, when application downloads fail, users must manually reinitiate the installation process. An automatic retry mechanism for failed installations would enhance the user experience.

I have been using Microsoft Intune since 2019.

Microsoft Intune demonstrates excellent stability with a rating of nine out of ten, providing a very stable experience.

In my role as an IT administrator, I have overseen Microsoft Intune implementation for approximately 10,000 users across multiple organizations. My previous organization had 7,000 plus users, and my current organization has between 3,000 to 4,000 users.

When comparing Microsoft Intune to alternatives such as Unified Endpoint Management solutions, VMware Workspace One, and Google Endpoint Management, each has distinct strengths. For Microsoft environments, Microsoft Intune rates five out of five, while Ivanti (formerly MobileIron) rates three out of five, and Google Endpoint Management rates two out of five.

For iOS environments, Microsoft Intune rates three out of five due to compatibility issues, MobileIron Ivanti rates four out of five, and Google Endpoint Management rates 3.5 out of five. Regarding user interface and ease of use, Microsoft Intune scores five out of five, Ivanti three out of five, and Google Endpoint Management four out of five.

In security and compliance, Microsoft Intune achieves five out of five, Ivanti four out of five, and Google Endpoint Management three out of five. For budget-friendliness, both Microsoft Intune and Google Endpoint Management rate five out of five, while Ivanti rates four out of five.

Microsoft Intune provides an excellent experience for both employees and IT administrators. While the user interface requires some initial guidance for new users, it is straightforward for IT administrators to navigate. The platform ensures device compliance effectively, earning a five out of five rating for user-friendliness.

Maintenance requirements for Microsoft Intune are minimal compared to on-premises applications such as SCCM or Active Directory Certificate Services. Required maintenance includes policy and app management, monitoring and troubleshooting, OS and app updates, and license and user management.

I recommend Microsoft Intune to other users and companies due to its password policies, seamless Microsoft system integration, multi-platform support (Windows, iOS, Android, macOS), simplified device enrollment management, cost-effectiveness, and smooth user experience. It represents a future-proof investment for companies.

Regarding Mobile Application Management, I have worked with MAM policies including conditional launch, PIN encryption, data encryption within apps, and copy-paste restrictions.

Overall rating: nine out of ten.

My main use case for Microsoft Intune is device management, policy enforcement, and securing endpoints across users in the organization.

Recently, I used Microsoft Intune to enforce device compliance policies including disk encryption, screen lock, and antivirus checks so only compliant devices could access company resources, which helped reduce risk from unmanaged endpoints.

We also use Microsoft Intune to automate device onboarding with predefined security baselines and app deployments, so new users get a fully secured and ready-to-use setup from day one.

The best features Microsoft Intune offers that stand out the most to me are centralized device management and policy automation since everything can be controlled from a single place. Strong security features including compliance policies and conditional access help protect data and restrict access to only trusted devices.

Policy automation in Microsoft Intune has saved a lot of time for my team by removing the need to manually configure each device as policies are applied automatically during onboarding. It also ensures consistency across all the endpoints, so every device follows the same security standards without manual checks. Additionally, automatic app deployment and update resources reduce repetitive tasks and keep devices secure without much intervention.

Microsoft Intune has positively impacted my organization by improving overall security posture, ensuring only compliant devices can access company resources and reducing risks from unmanaged endpoints. It also streamlined device management and onboarding, saving effort from the IT team and improving user experience with fast setup.

We saw approximately forty to fifty percent reduction in manual device setup time with Microsoft Intune as onboarding became fully automated. Security incidents related to non-compliant devices drop noticeably since only compliant endpoints can access resources. Onboarding a new user's device now takes less than an hour compared to several hours earlier.

Microsoft Intune could be improved by providing more detailed and easier-to-navigate reporting and troubleshooting, especially when diagnosing policy failures. The interface can feel a bit cluttered at times, and some configurations are not intuitive to locate.

Better real-time feedback on policy deployment status with Microsoft Intune would make troubleshooting much faster, and improved integration visibility across different Microsoft security tools would help manage everything more efficiently in one place.

I have been working in my current field for approximately two and a half years.

Microsoft Intune is stable, and I have not experienced any downtime issues; however, I have not encountered any reliability issues either.

Microsoft Intune's scalability is one of its strong points as it handles growth quite easily without needing major changes to infrastructure. In real-world use, organizations can manage thousands of devices smoothly through automation and centralized control. It is cloud-based, so as users and devices increase, I just scale licensing rather than worry about hardware limits, and policies continue to apply consistently across all endpoints. Overall, it scales well and is suitable for both small teams and large enterprises without much extra effort.

Customer support for Microsoft Intune has been decent overall, with multiple support options including documentation, chat, and enterprise support, which help resolve most issues. In my experience, basic issues get resolved fairly quickly, but for more complex cases, the response time can be a bit slow and sometimes requires multiple follow-ups. While documentation is helpful, it is not always up to date, so troubleshooting can take extra effort in some situations.

Earlier we relied on manual configuration and basic on-premises tools, which were time-consuming and hard to scale, so we switched to Microsoft Intune for centralized management automation and better security control.

We saw a clear return on investment with Microsoft Intune as device onboarding time reduced by approximately forty to fifty percent, saving significant IT effort. Support tickets related to password resets and device setups also dropped noticeably, reducing workload on the support team. Overall, it helps us manage more devices without needing additional resources.

We saw a clear return on investment with Microsoft Intune as device onboarding time reduced by approximately forty to fifty percent, saving significant IT effort. Support tickets related to password resets and device setups also dropped noticeably, reducing workload on the support team. Overall, it helps us manage more devices without needing additional resources.

My experience with Microsoft Intune's pricing, setup cost, and licensing is that pricing is reasonable as part of the Microsoft bundles, so the setup cost was minimal and licensing is straightforward. It can feel a bit expensive if you only need limited features.

We evaluated a few options including VMware Workspace ONE and MobileIron before choosing Microsoft Intune because it integrates better with the Microsoft ecosystem and is easier to manage in our environment.

My advice for others looking into using Microsoft Intune is to start with clear device and security policies before rollout to avoid rework later. Take advantage of built-in templates and automate onboarding to reduce device setup time. Test policies on a small group first to avoid unexpected issues at scale. Also, ensure you understand the licensing and integrations with other Microsoft tools to get the most value.

Microsoft Intune is a strong and reliable solution for endpoint management, especially within the Microsoft ecosystem. If planned and configured properly, it can significantly improve security, streamline operations, and reduce manual effort. I would rate this solution an eight out of ten.

We are customers of Microsoft Intune, not a company that designs solutions for others. Our internal IT department uses Microsoft Intune within a local healthcare company managing around 5,000 users and 5,000 PCs to secure the computers and manage PC operations such as installing and uninstalling software.

Microsoft Intune is deployed on the cloud in our organization.

Microsoft Intune does not support virtual machines in Azure. It supports only users' PCs with Windows 11 and does not support any server operating system.

I have certainly seen return on investment with Microsoft Intune. For example, instead of bringing PCs to the service desk where they are set up and then sent to the user, we now send the PC directly to the user and Autopilot handles everything for us. This saves a significant amount of logistic issues and time for the service desk.

The features and capabilities that I have found the most valuable in Microsoft Intune are Autopilot and Script Remediation.

I value these capabilities because Script Remediation allows me to run a script multiple times on a schedule. Additionally, the preview feature enables me to run the script on a specific machine to test it instead of testing on a group of machines. Autopilot is valuable because we do not need to set up the machine and then send it to the user, especially since we have many users in remote areas. We simply send them the machine, they connect it to the internet, and Autopilot sets up everything for them.

Overall, the user experience of Microsoft Intune is excellent. The software is installed in the background and the user will not feel any disruption. It is also a comprehensive solution because it is integrated with Microsoft's other products.

Specifically, Autopilot is very good. Regarding compliance policies, they are good, and baseline configurations are good. There is not only Microsoft documentation available, but also many blogs with detailed step-by-step guides.

Other than the add-on features that have bothered me, one feature I believe Microsoft Intune should improve is the deployment speed. When we deploy something, it should be deployed immediately. Sometimes we have to restart the service and sometimes we have to restart the PC for it to take effect quickly. The deployment time should be reduced so we can test it quickly and deploy it to production.

Regarding the pricing of Microsoft Intune, there are many features being introduced, but most features should be available in a license such as EMS E3, which is a high-quality license but does not include them. For example, KQL queries are behind a paywall, and I do not prefer their pricing strategy. EMS E3 should have more features than it currently does.

I have been working with Microsoft Intune for almost six years.

I am using Microsoft Intune on 5,000 devices and it performs very well. I would rate the stability and reliability level at 8 to 9.

I would rate the scalability of Microsoft Intune at 8.5 to 9. It is excellent software. There are a few things that sometimes seem as though they could be better, but Microsoft has done a really good job of introducing new features. The only reason I would give lower points is because the new features they are adding are behind a paywall as add-on features. Other than that, Microsoft Intune is excellent, and I really value it.

We have never needed to communicate with the technical support of Microsoft Intune specifically. We have been able to find the information we need in the online documentation. We have never needed to contact support specifically for Microsoft Intune, though we do sometimes contact support for other products.

Regarding Microsoft Intune documentation specifically, I believe the documents, guides, and manuals I have been using are good. They contain good information.

Before Microsoft Intune, I did not use a different solution for the same use cases. However, we acquired a company that was using SCCM and then we migrated that to Microsoft Intune. So I have worked with Microsoft Intune for this company, but I have also worked with SCCM previously.

Before choosing Microsoft Intune, I believe Microsoft only offers two solutions: SCCM for on-premises and Microsoft Intune for the cloud. There is no other solution.

I have set up many things in the initial configuration and baselines specifically for Microsoft Intune.

The first things I needed to perform in order to set up Microsoft Intune properly was to create a baseline and compliance policy. As a healthcare company, we focused on compliance extensively. We then set up global applications, which are applications common for every user, such as Adobe Acrobat Reader. After that, we set up Autopilot for users, which was not configured in the early stage but was added later. We also configured Conditional Access policies on top of that and set up Windows update rings. All the initial setup has been completed.

I find the initial setup of Microsoft Intune quite straightforward. There were some issues in terms of Autopilot configuration, but after thorough testing, it worked properly and proved to be quite straightforward.

I have certainly seen return on investment with Microsoft Intune. For example, instead of bringing PCs to the service desk where they are set up and then sent to the user, we now send the PC directly to the user and Autopilot handles everything for us. This saves a significant amount of logistic issues and time for the service desk.

We are not using Cloud PKI with Microsoft Intune because we do not have a use case for it. We have some wildcard certificates from a third party, such as DigiCert, but not from Microsoft. We are considering this in the future, but this feature is not free and does not come with EMS E3, which is our license, so we have not purchased it separately.

We are not using Copilot in Microsoft Intune.

I am not using the Enterprise Application Management features of Intune Suite because that is also not available in EMS E3. Instead, we are using Microsoft Store apps.

I am not using advanced endpoint analytics in Intune Suite because that is a separate license as an add-on.

Based on my entire experience with Microsoft Intune, I would rate this product between seven and eight, and I prefer to give it an eight. There are few things regarding pricing and other factors that I do not prefer, but other than that, I believe it is a really reliable product that is excellent. If you are running a Microsoft infrastructure, Microsoft Intune is tightly integrated with the Microsoft ecosystem.

I have several use cases for Microsoft Intune. The first one involves a company with 300 Zebra devices that wants to secure these devices and provide a better experience for end users. Microsoft Intune has a significant advantage because it is free, and when you combine the advantage of security with a free package, it creates a powerful solution for a company.

I have several clients today using Copilot. Microsoft has changed the name of Microsoft Office to Microsoft Copilot for users. I have already used and implemented several use cases of Copilot. I believe that for a company to succeed with Copilot, they must have good change management in place. If you don't have clear objectives and defined use cases, Copilot is very difficult for users to adopt.

What I appreciate most about Microsoft Intune is the design and simplicity for an administrator. If you use it for the first time, you will not encounter many difficulties. The terms of Microsoft Intune are very simple with Android and iOS options, which is a significant advantage. The second advantage is that it operates in the cloud, allowing you to work anywhere and anytime with only an internet connection. You can work in Microsoft Intune from New York, Australia, or around the world. You don't need a VPN or other complications. I have worked extensively with VMware Workspace ONE, and while it is simple, if you require high security with Workspace ONE, you must have a VPN and a company computer. With Microsoft Intune, you don't need a professional computer; you can work as an administrator with your personal computer.

Using Cloud PKI is a significant advantage for securing devices. Today, with so many devices in the world, if you want to control your mobile phone, it is necessary to deploy a certificate on the device. In Microsoft Intune, you can enroll any device, and deploying certificates is a very strong security feature.

What I dislike about Microsoft Intune is the time it takes Microsoft to develop a feature. Microsoft takes a long time to develop features for clients. Microsoft Office does not have much reactivity for the client because clients want features quickly, but Microsoft takes considerable time. I have clients today who are migrating from Domino to Microsoft and from Google to Microsoft. When the client requests a feature, Microsoft agrees, but it takes a long time—one year, two years—while the client needs the feature immediately.

I have used Microsoft Intune for seven years. It is not only Microsoft Intune but also Microsoft 365 and extensive work with Microsoft Intune, though I don't use only Microsoft Intune exclusively.

Microsoft Intune has never crashed for me. It always works without fail.

Microsoft support is very straightforward. You have support available, and you can call or send an email. I have already had tickets and have not experienced any significant problems. I have had issues with VMware Workspace ONE support where they did not provide good answers, but that was a different product.

I have contacted Microsoft several times. I currently have multiple tickets. One ticket is for a new feature that Microsoft deployed in the console, but it is not active. The feature is displayed, but it doesn't work, so a ticket must be opened. I believe I have approximately one ticket per month, which is not difficult or hard. The quality of support is good. If I compare it with Workspace ONE, the quality is very good. If you want to rate it, I would give it a 9 out of 10.

Positive

I have used VMware Workspace ONE and MobileIron by Ivanti before Microsoft Intune. These are the three solutions I have used: Microsoft Intune, VMware Workspace ONE, and MobileIron.

For deployment of Microsoft Intune, I believe a project chief is necessary, along with an administrator and a consultant. Three persons are required to deploy Microsoft Intune. You don't necessarily need many persons because you don't have servers to manage; it's all in the cloud. You don't have to manage servers or file data servers. All functionality is in the cloud. Previously, a company might have needed 10 persons to manage Workspace ONE, but with Microsoft Intune, you need only two or three persons. For a company, this is a significant advantage. In my company, Le Groupe Novah, we are a reseller of licensed Microsoft products, and we are the first reseller of IBM products.

The pricing for Microsoft Intune requires consideration. If you use Microsoft Intune, I believe it is necessary to use all Microsoft applications. You want to use Microsoft Intune with Microsoft Office, but if you use only Microsoft Intune, it is not a good deal for a company. You should use all Microsoft applications to achieve good pricing. For small clients, the pricing today is very expensive. In my company, where I work as an administrator of digital workspace, for small companies it is a very significant budget for Microsoft. However, a company with 30,000 users can achieve good pricing. But for a small company with 10 or 20 users, it will be challenging financially.

I have used Cloud PKI for Microsoft Intune certificates. I have used it with Microsoft Certificate Access by connecting Cloud PKI to Microsoft Intune. When you enroll a device and want to access Microsoft applications such as Outlook, you must have a certificate. I have already used this Cloud PKI configuration and have connected several PKI systems. My company has a partnership with TD SYNNEX, which is T-D-S-Y-N-N-E-X. My overall rating for Microsoft Intune is 9 out of 10.