Microsoft Intune Reviews

I am a mobile developer who has been involved in integrating Microsoft Intune SDK into applications. I can provide a general overview from both a developer perspective and a user perspective, as I have been using it corporately with Teams, Outlook, and other applications.

From the developer perspective, I have worked on integrating Microsoft Intune SDK into enterprise mobile applications. This work mainly involves implementing app protection policies, handling policy callbacks, and ensuring the app behaves correctly under compliance requirements.

Microsoft Intune helps enforce enterprise security policies at the application level. For example, when entering a mobile app, users might be required to enter an app PIN, and the system automatically encrypts the data. There are various other features like restricting copy-paste and enabling selective wipe of corporate data.

Microsoft Intune provides strong security controls, including strong application-level security, encryption, and data leakage prevention. A very important feature is the selective wipe capability. Whenever Microsoft Intune detects any rooted device or any tampering with the device, it involves both MAM (mobile application management) and MDM (mobile device management).

From the developer perspective, Microsoft Intune offers centralized policy management, which is another significant advantage because you can update everything remotely without changing the app.

From the user perspective, the experience is quite different because most controls are enforced seamlessly in the background. The primary advantage from the user perspective is the security aspect. Encryption and data protection happen in the background without requiring any manual effort, making the experience more seamless.

A lot of behavior depends on policies configured externally. It is not just that you code and then integrate the SDK. The Microsoft documentation about Microsoft Intune SDK is fairly structured, which is fine. The primary hurdle is the visibility gap between the Intune SDK and the Admin Portal. Improved logging or a 'Developer Mode' for policy simulation would help bridge the gap between the mobile implementation and the tenant-side configurations

There are many policy scenarios that are time-consuming and depend on external configurations. Additionally, the debugging process requires a test environment and dev environment, and getting access to those environments for debugging is challenging. It becomes difficult to determine where issues are occurring and why policies are not being enforced.

One major concern I have is user friction. When you enforce many policies and people log into apps like Microsoft Teams or Outlook, they encounter numerous MFA and other policies. Users feel friction due to additional authentication steps such as PIN or repeated login requirements.

From the user perspective, these restrictions can feel limiting. Blocking copy-paste or screenshots can sometimes feel limiting from a usability perspective. Another concern is limited visibility into why things happen. Users do not get full transparency because they see messages stating "Your device is blocked" or "You cannot access this right now," but the exact reason behind these messages lacks transparency. Additionally, many policies depend on device configurations and compliance. If the device is not compliant, users might lose access, which can be frustrating without clear guidance.

My suggestion for improvements would be better tooling for testing policy scenarios both locally and improved debugging support, which would make developers' work easier with Microsoft Intune.

I have been working as a mobile developer for one and a half years. I have been using Microsoft Intune for two to three years, dating back to university level where we had Teams, Outlook, and other applications. For corporate use, I have been using it for two years, and as a mobile developer, I have been using it for around one and a half years.

Microsoft Intune has been stable. Whenever we log into Teams, Outlook, or apps where we have integrated Microsoft Intune, the policies are getting enforced. However, sometimes when Azure AD  (Microsoft Entra ID) identifiers are not recognizable, the policies do not get enforced in very rare cases. This does not cause any application crash or a hard stop. It simply means that the identifiers are not identified and then policies are not enforced for that account at that point in time.

Microsoft Intune is scalable because you can include it in a variety of apps. As the application users increase and everything else related grows in size, Microsoft Intune is capable of handling all those scales.

We integrate the SDK and then configure the policies. We have a separate team responsible for looking into the configurations in the Azure portal, checking the effects, and managing the endpoint. As developers, we do not have access to that portal. A separate team handles those responsibilities.

As a developer, I focused on the implementation of the Microsoft Intune SDK. While our architecture team decided on the solution, I have researched other SDKs like those from VMware or MobileIron to understand industry standards for app protection policies. We found that Intune’s tight coupling with Microsoft Entra ID conditional access made it the most logical fit for our enterprise environment.

From the user perspective, Microsoft Intune enables access to corporate data and apps even on personal devices, which is convenient. The selective wipe feature builds user trust because only corporate data is removed while personal data remains untouched.

Users get a consistent experience across devices because the policies are centrally managed.

We have IT solutions in this organization, but it's different. It's AWS, majorly.

I am dealing with AWS S3 storage services myself, and apart from this, we have multiple services which we are using, the different instances of VM, virtual machines. Majorly the VMs and the storage part we are utilizing. We are planning to use Route 53 as well for the network.

I don't think we have been dealing with something Amazon Virtual Private Cloud. We are just launching the VMs, the instances, and utilizing it for the services. The storage services we have been using in it to store our data.

The user experience of Microsoft Intune is very friendly and the interface is very good. It's very easy. Although Microsoft keeps on changing the console, you log in today and you will find something, and then after two months you log in and you will see the options change. That's how it is, but then again, it's quite interesting. It's always nice to explore things in it, always nice to connect and do things. It's not very difficult for me; I don't find it very difficult. Somebody who has worked on SCCM or these products can easily use Microsoft Intune. If they understand the technology, they will be able to use it. It's very good. Microsoft Intune is very good in terms of support as well. We get very good support from Microsoft. Overall, my experience is awesome.

We have utilized Copilot in Microsoft Intune very well.

My experience with Copilot was good. There are always some chances to do some enhancement and improvement, and of course, there is a lot of competition in the market as well against the AI tools we have, the open AI tools we have, and the chatbots we have. Definitely, but it is very good. It is very nice.

I see room for improvement with Microsoft Intune because the only thing is that under the policies, there are certain policies which are very deep dive. Somebody has to understand it very particularly, then only they should implement it. That's the only thing. Some demo videos would be available on the portal, that would be helpful. If somebody has to do some implementation of any new policies, how would they do it? The person has to search somewhere how this policy works, and that will help. A small demo would be available in the portal itself. That would be helpful if Microsoft itself can launch some demos.

So far, I think the things are going smooth with Microsoft Intune. I do not see any conflicts with that, any additional features. In terms of comparing with the other cloud providers, the things are smooth. But when it comes to AWS, they have a bundled package of security and everything in one portal, including the billings part as well. Whereas in Microsoft, it is separate. A bundle package would be helpful. Although with AWS, we can get it through Marketplace, in Microsoft it is subscription-based. That is also good, but if I compare with both of them, then console-wise, of course, Microsoft Intune has very good features and everything in terms of endpoint devices. But in terms of the virtual machines connect and onboarding the virtual machines and syncing them, it is a bit tricky. One improvement that is needed if I compare with AWS where it's pretty easy.

I have been working with AWS for three months already, but this organization has been working on AWS for the past one and a half years or more.

During the onboarding of Microsoft Intune, we faced the problem that the policies were not getting synced. Sometimes, even after removing the devices from the domain and then re-onboarding the devices, joining the domain again, the sync was not happening. For example, there was one case where the devices were already synced, everything was synced, the user was logged in, and then suddenly when we handed it over, when somebody left the organization, we handed over the asset to another, assigned it to somebody else. In that case, that syncing was not working. It was taking a lot of time. It was very difficult. We removed it from the domain, we formatted the machine completely, then again installed the fresh image. Everything we did, it took time. Then ultimately, we had to take the help from Microsoft. It got resolved, but that was a difficult situation.

Microsoft Intune support is very good. We get very good support from Microsoft.

Ultimately, we had to take the help from Microsoft. It got resolved, but that was a difficult situation.

Positive

Before this, I was working with Microsoft in my previous company, where I was using Microsoft Intune and other services of Azure and Microsoft.

My experience with the deployment of Microsoft Intune was a bit tricky. It was tricky. But the overall experience was good because there was a lot of learning and enough support from Microsoft in terms of deployment as well.

I haven't used Microsoft Intune Suite Cloud PKI. We haven't used it. But we were having the Citrix environment, so we were launching the Microsoft Intune services in it, connecting our services, and connecting our virtual machines on Microsoft Intune, onboarding the VMs on Microsoft Intune. That's how we were using it, through Citrix.

I need to check that with the engineer regarding something Amazon DCV.

I would rate technical support at least a nine.

I would rate Microsoft Intune at least eight to nine overall.

I would rate it at least eight out of ten. My overall review rating for Microsoft Intune is eight.

I have been using Microsoft Intune for the last twelve years. Primarily, I use Microsoft Intune for device management. I am involved in managing security policies related to Active Directory, endpoint compliance, access control, patch management, conditional access, and identity governance across the environment using Microsoft Intune.

I manage security policies in Microsoft Intune including device compliance, conditional access, endpoint security, application protection, encryption, and patch management policies to ensure devices remain secure and compliant.

The best features of Microsoft Intune are centralized endpoint management, compliance policy enforcement, conditional access integration, application deployment, remote device management, and seamless integration with Microsoft 365 and Microsoft Entra ID, which together improve security, simplify administration, and support remote workforce management efficiently.

I find compliance policy enforcement and conditional access in Microsoft Intune to be the most valuable in my daily work because they ensure only secure and compliant devices can access corporate resources, which significantly strengthens security and reduces operational risk.

Additionally, the remote management and automation capabilities in Microsoft Intune are very valuable as they allow me to deploy applications, enforce policies, troubleshoot devices, and perform remote actions efficiently without requiring physical access to endpoints.

Microsoft Intune solutions, especially Microsoft Intune and Microsoft 365, have positively impacted my organization by improving endpoint security, enabling centralized device management, supporting remote work efficiently, reducing manual administrative effort through automation, and enhancing compliance and collaboration across the enterprise environment.

Microsoft Intune can be improved with faster policy synchronization, more intuitive troubleshooting tools, enhanced reporting and analytics, and simplified management for complex and hybrid environments, along with better third-party integration support and more granular administrative controls for enterprise-scale deployments.

Additionally, improving real-time visibility, reducing delays in policy application, and providing more detailed error reporting and automated remediation features in Microsoft Intune would make daily administration and troubleshooting much more efficient in an enterprise environment.

Overall, Microsoft Intune has covered most areas, but the solution could still improve in terms of faster support response for complex enterprise issues, more intuitive administrator interfaces, enhanced cross-platform management consistency, and deeper real-time reporting and analytics capability for large-scale environments.

I have been working in my current field for around twelve years.

Microsoft Intune is generally very stable in an enterprise environment with reliable cloud-based performance, strong scalability, and consistent device management capability, although occasional delays in policy synchronization or service-related issues can occur, which are usually resolved quickly by Microsoft.

Microsoft Intune scales very well for an enterprise as it is cloud-native in architecture, supports managing a large number of users, devices, applications, and policies across a distributed and remote workforce without significant infrastructure overhead.

Customer support for Microsoft Intune has been generally good with strong technical expertise, detailed documentation, and effective guidance for most deployment and troubleshooting scenarios, although the response time for complex enterprise issues can sometimes vary depending on the support tier.

I previously used Microsoft System Center Configuration Manager and traditional on-premises management tools, but I switched to Microsoft Intune to support cloud-based management, remote workforce requirements, simplified administration, and better integration with Microsoft 365 and other services.

My experience with the pricing, setup cost, and licensing for Microsoft Intune has been positive overall as it is commonly bundled with a Microsoft 365 Enterprise plan, which simplifies licensing and reduces additional setup cost, while the cloud-based deployment minimizes infrastructure expenses and provides good value through centralized management.

I would advise starting with a pilot deployment of Microsoft Intune, designing compliance and conditional access policies carefully integrated with Microsoft Entra ID and Microsoft security tools, and focusing on automation and user training to achieve smooth adoption, stronger security, and efficient endpoint management.

I saw a strong ROI with Microsoft Intune through approximately forty to fifty percent faster device onboarding, significant reductions in manual endpoint management efforts, improved compliance automation, and reduced security incidents, which save operational time and improve overall IT efficiency without needing additional support resources.

Since implementing Microsoft Intune, I have reduced device onboarding time by approximately forty to fifty percent, improved compliance visibility significantly, reduced manual endpoint management effort, and lowered security incidents related to unmanaged or non-compliant devices through the centralized policy enforcement and automation.

Before standardizing on Microsoft 365, I was evaluating options such as Google Workspace and some standalone endpoint management and collaboration tools, but I selected Microsoft 365 because of its strong integration across security, identity, endpoint management, email, and collaboration services within a single ecosystem.

I would rate this review an eight out of ten.

Microsoft Intune is primarily used for endpoint management, device compliance, and deploying security policies across company laptops and mobile devices.

Microsoft Intune is used to enforce BitLocker encryption, require MFA, and block non-compliant devices from accessing corporate apps such as Outlook and Teams.

It has also been useful for remote app deployment and keeping Windows devices consistently patched without much manual effort.

Microsoft Intune has improved our endpoint security, reduced manual device management work, and made onboarding remote users much faster and more consistent.

We have cut device setup time by around fifty percent and significantly reduced compliance related support tickets since most policies and updates are now automated.

The best parts of Microsoft Intune are its centralized device management, smooth integration with Microsoft 365, automated policy deployment, and the ability to manage remote devices without needing users on the corporate network.

Policy and compliance management is relied upon the most because it automates security enforcement and saves a lot of manual admin work day-to-day.

The reporting and integration with Azure AD and Defender also make troubleshooting and security monitoring much easier.

Microsoft Intune could improve its reporting depth and make some policy configurations less complex, especially for hybrid environments.

The admin interface can also feel fragmented at times, so simplifying navigation would help with day-to-day management.

Faster policy sync times and more detailed built-in troubleshooting tools would be beneficial, especially for complex device enrollment issues.

I have been working in this field for one year.

Microsoft Intune has been relatively stable in production, especially for device compliance and policy management, although policy syncs and app deployments can occasionally be slower than expected.

Microsoft Intune scales really well in our experience. We have been able to manage thousands of devices across remote and hybrid environments without major infrastructure concerns, although larger deployments can sometimes expose slower policy sync and reporting delays.

The customer support for Microsoft Intune has been decent overall. Basic issues usually get resolved fairly quickly, but more complex cases can take time and often require escalation or multiple follow-ups.

We previously used basic on-premises SCCM management but switched to Microsoft Intune to better support remote users and modern cloud-based device management.

Microsoft Intune is used in a hybrid setup, mainly cloud-managed with some integration into our on-premises Active Directory environment.

We have seen solid ROI through reduced manual IT workload, roughly forty to fifty percent faster device provisioning, and fewer support tickets related to compliance and patch management.

Our experience with Microsoft Intune pricing has been fairly positive since it is bundled well with Microsoft 365 licensing, but understanding all the licensing tiers and add-ons can get a bit confusing during setup.

Before choosing Microsoft Intune, we also evaluated VMware Workspace ONE and JMF Pro for endpoint management.

My advice would be to plan your device policies and identity integration carefully before rollout because Microsoft Intune works best when it is properly aligned with Azure AD, compliance tools, and your overall Microsoft 365 management.

Overall, Microsoft Intune has been a strong fit for modern endpoint management, especially for remote and hybrid environments, and it keeps improving as Microsoft expands the platform. I would rate this product an eight out of ten.

My use case for Microsoft Intune involves remote access and mobile management. The purpose is to improve our operational efficiency.

The best features of Microsoft Intune that I appreciate most include its comprehensive management capabilities and user-friendly interface.

I do use the cloud PKI feature in Microsoft Intune, which enhances my management of the certificate infrastructure effectively. In cloud PKI, it helps me manage my certificate infrastructure by ensuring secure operations and streamlined processes.

I also use Microsoft Copilot as it offers significant value in enhancing my experience with Microsoft Intune. My experience using Copilot has been very positive as it integrates smoothly into my workflow. Copilot helps protect my environment by automating security processes and facilitating timely updates.

I am also using the enterprise application management feature in Microsoft Intune for better app discovery and deployment. I use the application management feature extensively within Microsoft Intune for automatic updating and deployment.

There are areas that have room for improvement in Microsoft Intune, particularly regarding integrations.

I have been using Microsoft Intune for about three years.

The stability of Microsoft Intune is relatively high, and I would rate it a 9 regarding downtime or bugs.

For scalability, I would also rate it a 9 as it adapts well to our growing needs.

From one to ten, I rate Microsoft Intune's technical support as 8, indicating it meets my needs satisfactorily.

Positive

I utilize a different solution for some aspects of endpoint management, which offers additional functionalities.

The deployment of Microsoft Intune was fairly easy, though it had its complexities as well.

It took me weeks to deploy Microsoft Intune fully, balancing the setup with existing systems.

I estimate I have seen a return on investment of about 20%, highlighting the value provided by Microsoft Intune.

Microsoft Intune has saved me about 30% of my time through streamlined processes and efficient resource management.

The pricing of Microsoft Intune, considering its features, is cost-efficient.

In terms of overall pricing, I find it to be fairly priced, reflecting its capabilities.

Considering the features, I recognize its pricing is competitive within the market.

I compare Microsoft Intune to other solutions based on its features and performance, indicating its advantages.

When comparing with other solutions I have used, I find Microsoft Intune to be quite effective.

To others looking to implement Microsoft Intune, I recommend them to evaluate through a proof of concept before finalizing their decision.

I would rate my overall experience with Microsoft Intune a 9.

I'm responsible for the end-user computing. I'm responsible for packaging the applications, deploying it to all the end-user devices in my organization via Intune, and also creating the monthly patching through update rings and deploying all the patches to the workstations across the entire organization. 

We have also created an Autopilot profile, deployment profile, and enrollment status page to ensure all the new devices are compliant with company policies and compliance policies as per our organization rules.

It significantly reduces the need for manual human efforts and is very cost-effective. This makes it particularly advantageous for large enterprises, especially in the financial sector, as it is secure and reliable. Microsoft Intune helps protect against vulnerabilities and third-party attacks by providing timely patches and update rings, ensuring compliance with security standards.

The best features of Microsoft Intune are creating the package in very simple terms using the Content Preparation Master tool, which I find easy. I'm able to pull reports and get device status very easily, which has been very helpful. 

Regarding the compliance policy settings and configuration profile, I can check on each device to see where it failed. However, I struggle to troubleshoot the exact root cause of these failures, which I want to highlight. 

I have observed that while I can generate reports, I am unable to address the log files from end-user devices effectively. For instance, when an application is deployed on a user device and it shows an error indicating failure, I can't pinpoint the exact reason for the failure. In Microsoft SCCM, we can access log files in the "C:\Windows\SCCM\Logs" directory. From there, we can check the "AppEnforce.log" and "AppIntentEval.log" files. Unfortunately, Intune’s management extension does not provide the same level of logging. When I try to review the "Windows IMEI" logs, I cannot determine where the application is failing.

Moreover, I lack the visibility in Intune that I had with SCCM. Looking ahead, with Windows 11 on the horizon and Windows 10 support ending on October 14th, I am currently involved in a Windows land migration project. I plan to image the new devices using Autopilot. Once the hardware hash is added to Intune, we are able to assign the group tag, which allows for the deployment profile to be assigned, enabling both device enrollment and user enrollment. This approach helps minimize the overall experience issues.

Maintaining Microsoft Intune is not very complex; we generally export the entire list of applications we've created once every three months, and we make sure to update or remove any old policies that are no longer required in our organization. However, this is a time-consuming and tedious process. I suggest that Microsoft include an option, similar to SCCM, for every three months or 90 days to automatically remove devices from the console. This suggestion could apply not just to device management but also to application management and compliance policies or configurations.

Because Microsoft Intune is cloud-based, we would like to gain a better technical understanding of how Microsoft develops the tool from the backend. For instance, with SCCM, we learned how it operates—creating distribution points, performing system discovery, and identifying machines present in Active Directory. We understood how to create boundaries and assign boundary groups for distribution points to access content. However, in Intune, we struggle to determine where content is stored. For example, when I create a .IntuneWin file or a package application, I want to know where it is stored and how to retrieve the raw files or the source media if needed. These are some of the challenges we face with Microsoft Intune. We lack a lot of visibility in Microsoft Intune.

I have been using Microsoft Intune for the past eight years.

I find that Microsoft Intune is stable, but it would be beneficial for support infrastructure engineers to receive presentations about new features and how earlier issues were overcome, as this information is not readily available to them, which affects the perceived stability. On a scale of one to ten, I would rate it a seven out of ten for stability.

For scalability, I would rate it a six out of ten.

Currently, I'm managing around 6,000 devices at Alter Domus, and once I deploy an application, profile, or policy, it takes around two weeks to achieve 92% to 94% compliance. We have around 13,000 users.

For technical support, I previously received direct calls from escalation engineers at Microsoft, and I found that very supportive. However, now Microsoft has changed their process, and L1 and L2 tickets are often assigned to third-party companies where the personnel may lack the necessary knowledge, resulting in lengthy resolution processes. In my organization, management suggests we handle issues ourselves until a solution is provided.

When an escalation support engineer at the L3 or L4 level assists me, I would give them a rating of 10 out of 10. However, for L1 or L2 engineers from third parties, I would rate them a four out of ten due to the lengthy resolution times. 

Overall, I would rate vendor support very poorly, at three or four out of ten. However, when I talk to engineers directly working for Microsoft, especially those familiar with SCCM and Intune, I would give them a 10 out of 10 due to their proper understanding of the tools.

Neutral

I have seen a return on investment with Microsoft Intune, as it has saved me resources. Previously, I managed my infrastructure with a team of around six to seven members, but after transitioning to the Microsoft Intune hybrid model, I am able to manage it with just one resource, allowing me to cut costs significantly, around 50-60 lakhs.

It's expensive.

When comparing Microsoft Intune with other solutions or vendors, I find that it is a very fast and safe procedure technology. While I believe it is good technology, there are minor issues that could be resolved by Microsoft. We want transparency for engineers to understand where issues arise so we can troubleshoot effectively.

I don’t want to constantly disturb the service support engineers by raising cases. As technical engineers, we want to solve problems on our own. We aim to become subject matter experts for Microsoft Intune within our organization.

In my organization, we use Copilot whenever we don't understand a particular feature, and it provides the answers we need. For example, when I need to create a BitLocker encryption policy, Copilot assists me and guides me through the steps and necessary settings required before creating that policy.

We have a certificate infrastructure, and we generally embed machine certificates and handle the PKI certificates via SCCM. 

The cloud distribution point that we have already configured in SCCM is particularly useful when an end-user device is not connected to the VPN (Virtual Private Network). During this time, the cloud distribution point allows content, such as application patches, to be distributed and successfully installed on end-user devices. This is why we have been able to achieve good compliance.

I would recommend Microsoft Intune to other users because it offers many benefits. Overall, I would rate Microsoft Intune an eight out of ten.

My main use case for Microsoft Intune is centralized endpoint and mobile device management, where I use it daily for device enrollment, enforcing compliance and security policies, deploying applications, managing Windows Update, and remotely troubleshooting corporate devices. For example, I automatically provision laptops with security policies and required applications during onboarding, which reduces manual efforts and improves security compliance.

Additionally, I use Microsoft Intune for conditional access integration, remote wipe-out of lost devices, patch management, and monitoring device compliance, which help improve security, simplify endpoint administration, and support remote workforce management efficiently.

The best features in Microsoft Intune are centralized device management, compliance policy enforcement, application deployment, conditional access integration, and remote device actions like wipe-out and reset because these features simplify endpoint administration, strengthen security, support remote workforce management, and ensure devices remain compliant with organizational policies.

I rely the most on compliance policy enforcement in Microsoft Intune because it ensures all corporate devices meet security standards like encryption, antivirus, and update compliance before accessing company resources, which is critical for maintaining security and regulatory compliance.

Microsoft Intune has positively impacted our organization by improving endpoint security, automating device management, and reducing manual administration effort. Tasks like device provisioning, policy enforcement, software deployment, and remote troubleshooting become centralized and faster, helping save operational time, improve compliance, and support remote workforce management more efficiently.

Using Microsoft Intune, we reduced device onboarding time by around forty to fifty percent, improved compliance visibility significantly, and reduced manual endpoint management effort through automated policy deployment and centralized administration while also helping lower security incidents related to unmanaged or non-compliant devices.

Microsoft Intune can be improved with a more intuitive admin interface, faster policy synchronization, better troubleshooting and reporting capabilities, especially for complex and hybrid environments, along with more granular control and simplified management for advanced configurations.

I have been using Microsoft Intune for around three to four years as a part of endpoint management, device compliance, application deployment, and mobile device management in the enterprise environment.

Microsoft Intune is stable.

Microsoft Intune scales very well for enterprise environments as it supports centralized management for a large number of devices, users, and policies across distributed and remote workforces. Its cloud-native architecture allows easy expansion without significant infrastructure overhead.

My experience with customer support for Microsoft Intune has been generally positive, as Microsoft support provides strong technical expertise, good documentation, and effective guidance for most deployment and troubleshooting scenarios. Although response times for complex issues can sometimes vary depending on the support tier and severity.

We earlier used traditional on-premises tools like Microsoft System Center Configuration Manager for device management, but we switched to Microsoft Intune to support cloud-based management, remote workforce requirements, simplified administration, and better integration with Microsoft 365 and Azure services.

We handle user training and adoption for Microsoft Intune through onboarding sessions, user guides, and step-by-step documentation for device enrollment and security policies, along with awareness sessions for compliance and remote access practices. The IT team provides support during rollout to ensure smooth adoption and minimal disruption.

We saw a strong ROI with Microsoft Intune, including around forty to fifty percent faster device onboarding, significant reduction in manual endpoint management efforts, improved compliance visibility, and reduced security incidents related to unmanaged devices, which overall saves operational time and improves efficiency.

My experience with pricing, setup cost, and licensing for Microsoft Intune has been positive overall, as it is commonly included with Microsoft 365 Enterprise licenses, which simplifies procurement and reduces additional setup costs. While standalone licensing is also flexible for different business needs, and although advanced features in the Intune suite or higher-tier plans can increase costs, the overall ROI is strong due to centralized endpoint management, security, and automation capabilities that reduce operational overhead and improve efficiency.

My advice would be to start with a clear device management and security strategy before implementing Microsoft Intune. Begin with a pilot rollout, properly design your compliance and conditional access policies, leverage automation and integration with Microsoft 365 and Azure services, and invest in user training and monitoring to ensure smooth adoption and effective endpoint management.

Microsoft Intune integrates seamlessly with tools such as Microsoft Entra ID, Microsoft Defender for Endpoint, and Microsoft 365 services, enabling centralized identity, security, compliance, and device management.

We use Microsoft Intune to centrally manage updates and patches by creating update rings and deployment policies for Windows devices, scheduling phased rollouts, enforcing compliance for missing patches, and monitoring update status.

We monitor and report device compliance in Microsoft Intune using compliance policy dashboards and built-in reports that track device health, including encryption, antivirus, OS version, and patch status, while integrating with Microsoft Entra ID.

We handle security incidents detected through Microsoft Intune by integrating with Microsoft Defender for Endpoint and conditional access policies, where compromised or non-compliant devices are automatically isolated or blocked from accessing corporate resources.

We use Microsoft Intune to centrally deploy and manage applications by creating deployment policies for required and optional applications, assigning them to user or device groups, scheduling phased rollouts, and monitoring installation status through reports.

We ensure data privacy and compliance in Microsoft Intune by enforcing device compliance policies, encryption, conditional access, and application protection policies while integrating with Microsoft Entra ID to restrict access from non-compliant devices and using remote wipe, auditing, and reporting features to protect corporate data and support regulatory compliance requirements.

I would rate this product eight out of ten.

I am still currently working with Microsoft Intune extensively, in and out, day in, day out.

We are currently a remote company. Since we don't work in a single enclosure—someone is working in the US, someone in India, and someone in the UK—managing all the devices is very important. Since there are many scenarios where we want to deliver some policies, we need to have a VPN on top of it; other than that, it's not possible. For a user distributed in different geographies, it is very difficult to do that in one shot. Microsoft Intune actually helps a lot for us in this regard. If we want to install some application, a recent example is Drata installation that I have done. Drata checks the disk and other settings to see whether they are encrypted or not. Drata is an agent that runs in the background on every system, be it Mac, Windows, or anything. We have forced the installation via Microsoft Intune to all the devices in one shot without any policy change or being on a VPN; it was straightforward. Every user was able to do it without any problem.

The deployment aspect is not within my management; I am just the user of Microsoft Intune. The company has purchased it, and they have asked us to use it extensively. I handle single sign-on scenarios and application onboarding. If we want to install software on different systems, I can manage those aspects. However, the actual procurement is handled by other teams.

The best part of Microsoft Intune is the onboarding aspect; whenever we onboard someone in our organization, we don't have to manually do anything. The moment we provide an Intune ID to them, or Entra ID basically, they get all their accesses based on the policy we have configured. Following that, their device gets enrolled, everything gets done via the company portal software, and whatever software we need we can install in one go with the software distribution. We have certain machines which are running on Windows, where we have some Mac OS machines also. From the company portal, they can even download the software which is given permission based on our company's requirement and other aspects or compliance requirements. That way we don't get the free versions of things which are not to be used. Rather, what we get is more emphasis on multiple compliance issues. For example, installing Slack and using GitHub, we can actually manage those. Onboarding is one aspect, but the offboarding aspect is also very critical. If someone leaves the organization or we need to wipe out some laptop data or exchange laptops, in those scenarios, wiping out data from the laptop becomes very easy.

The security compliance that Microsoft Intune provides is good. Whatever policies we configure, security depends on how strong our policies are and how secure our endpoints are. In this aspect, it helps a lot. However, the policy is something we need to write. I am satisfied with the base policies because they cover most of the necessary aspects such as application protection policies, remote wipe, and BitLocker management, which are good. I have no complaints, and Windows Defender helps a lot in managing many threats when users are working.

Microsoft Intune is on par with anything we have used. In terms of onboarding, offboarding clients, or any scenarios, everything is done via the company portal only. We extensively use Microsoft Intune, and we have a good ecosystem along with it, with integration with Microsoft 365 and Windows 365. We have good integrations with user credentials and other aspects; it has a great ecosystem overall with many integration options.

I extensively use Microsoft Copilot in Intune. There are a lot of improvements I can mention. It's not that great to be honest; it's okay. Copilot works fine, but compared to the integration we had with our VS Code and other tools, I find a better alternative such as Claude Code CLI for assisted coding that is faster. Copilot doesn't give us exactly the results we need, which points to a need for more AI-driven improvements. Better LLMs with better benchmarks will definitely perform better. Claude is there; it's a leader, and even OpenAI platforms are a leader, but Copilot lacks a little bit. It runs on OpenAI technology, but Claude is definitely better.

When I started learning Microsoft Intune, I struggled because it was not straightforward; everything is in forms and it takes time to understand. The UI is extremely bad; it has a lot of overlapping elements and is confusing in many senses. There are straightforward forms which we need to fill out, and there are no direct ways to create those policies via some JSON object or similar. However, after AI integration, it becomes easier to understand, though I had to spend a significant amount of time in the pre-AI era when I started working on it. I still remember it; it was quite challenging and honestly, boring. Troubleshooting is also problematic, and there are generic error messages for everything, with negligible logs. The experience I share is based on the pre-AI era, when things were less smooth. Now, application development is much more manageable compared to before. However, I still find issues with Windows management being excellent, while Mac is okay, and for pure Linux systems, Microsoft Intune offers very limited support. Intune's endpoint tools are almost nonexistent for Linux, an area where there is significant room for improvement.

In my previous organization, I have been working with Microsoft Intune for three to four years and in this current organization, almost two years; so overall, I have about six years of experience.

There are no complaints regarding the stability and reliability of Microsoft Intune. Microsoft has done an excellent job. I have only one complaint during the CrowdStrike incident, where Microsoft isn't at fault.

Our organization has around three hundred to four hundred employees, and in that context, Microsoft Intune works well. There are no complaints about its scaling, and we don't use it extensively. There are specific use cases where we implement it, and it has scaled well without any issues.

Customer service and technical support from Microsoft are good. I think they've done a great job. The AI bots and documentation they provide have made my experience smooth. I have never needed to contact technical support for issues.

As I have never contacted technical support, I rely heavily on the documentation and the knowledge of colleagues surrounding me. The documentation, along with internal resources and online videos, has facilitated our onboarding. Probably in terms of rating, I would say eight or nine for Microsoft support; it seems fine.

I have not used any different product prior to Microsoft Intune. I know that VMware Workspace might be a similar product I have heard of, but I have never used it. From what I gather, it's a bit more expensive compared to what Microsoft Intune offers. Cost-wise, Microsoft Intune is very cheap in the market based on the things it provides.

It's pretty straightforward to set up Microsoft Intune. For me, it involves just a few steps; we have to create our Entra ID for a device. For example, when an employee receives a laptop, whether they want to get enrolled via Autopilot or the company portal, it doesn't matter; it ultimately hits the same API. It connects via the Entra ID, and once it's done, we apply the policies across and distribute the software.

There is definitely a return on investment with Microsoft Intune. It has excellent integration with Microsoft products because it's a Microsoft product. The security capabilities mean we don't have to do much; users with Windows laptops can check for disk encryption to prevent data exposure. The company portal is also a big advantage as it keeps our software catalog organized. In our completely remote organization, Microsoft Intune is very helpful.

We have used the advanced endpoint analytics in Microsoft Intune. We utilize the advanced analytics primarily to check device history and other information. We use it for reporting and other aspects.

The advanced endpoint analytics in Microsoft Intune actually helps. While I cannot specifically recall it solving a discrete problem, it provides us with good insights regarding user patterns and interactions with their systems. It identifies areas where malicious actors might exploit issues. The endpoint analytics provides this information, which is beneficial though it is more generic compliance in our case.

My advice for those implementing Microsoft Intune is to proceed with it. There is no other software that can perform the job better. Microsoft offers extensive experience with a mature ecosystem, so I recommend going for it. I am providing this review with an overall rating of nine out of ten.

My main use case for Microsoft Intune is to manage all the endpoints and use the conditional access policies to manage all the applications for Microsoft.

In my organization, we are using M365 with Microsoft Intune, and we do not want users to access their email on any non-managed devices, so we manage devices with Microsoft Intune and the Exchange, meaning online exchange mail is only accessible on Microsoft Intune managed devices. This is the use case we are following.

For Microsoft Intune, we also use it for patching our devices because patching is very critical for us, and Microsoft Intune helps us to get all the patches centrally without going to any further third-party sites. It is helpful, and it also gives me options to see the vulnerabilities on all the Microsoft Intune-joined devices.

The best feature of Microsoft Intune is the zero-touch device provisioning, which is very helpful to reduce the manual imaging, as we do not want any dependencies on local engineers to install the OS manually, and it is easy to manage our devices from remote sites. It also increases the compliance which we follow and helps to reduce the time to deployment, allowing us to customize the OS with the software our company uses, making it ready to go.

Microsoft Intune impacts our organization positively by reducing the time for our engineers, allowing them to focus on other important tasks. It provides a complete overview of all the endpoints managed by Microsoft Intune, showing which systems are critical, not critical, healthy, and not healthy, and how many devices comply with our organization's policies. It also reduces the risk of data being shared outside of our devices.

Microsoft Intune reduces the time of our engineers, cuts down costs for the deployment of our endpoints managed by Microsoft Intune, and helps to improve compliance and the security policies we wanted to apply on endpoints, which was not happening earlier. Now it is working fine.

For improving Microsoft Intune, it sometimes feels laggy, taking some time to implement any policies on machines. I understand it's dependent on the network, but some other device management applications implement changes more quickly. This lag is the only gap I see.

There should be an easy guide to getting started with Microsoft Intune. As an admin, I feel we need clear steps to follow based on the licenses we have purchased. Best practices for Microsoft Intune would help us utilize all its features fully, giving us confidence and better value for our investment. Currently, we have to figure it out on our own.

I have been using Microsoft Intune for four years.

Previously, without Microsoft Intune, we were using a manual method by booting all laptops with USBs after procuring them to our office. We installed the OS and all the applications, provided antivirus, configured the Outlook Exchange, and other user profiles, then sent those laptops via delivery to any remote users located anywhere in India. This process reduced the time and cost of delivery, as we can now send laptops directly to users without going through our office, and it has significantly reduced the time for deployment of applications, images, and configurations which can now happen remotely.

Sometimes, the AI gives options that are not available, making it difficult, leading us to search repeatedly. While the AI understands we have purchased only basic licenses, it typically provides generic answers related to the complete feature set of Microsoft Intune, making it tricky. This occurs only sometimes, as most of the time, the AI's output is accurate.

Microsoft Intune AI is one of the most valuable AI-driven capabilities within Microsoft Intune, with its integration with Microsoft Security Copilot and AI-based analytics for endpoint management, detecting compliance issues, application failures, risky devices, and deployment problems proactively. It helps us analyze compliance issues, and if we ask the AI to improve compliance or reduce application failures and risky devices, it provides answers that make managing Microsoft Intune easy.

For remote management, we use Microsoft's default application, Quick Assist, which is helpful as we do not have to depend on any third-party applications, making it easy. We can also use the remote wipe if anything goes wrong.

The cloud provider we use for deploying Microsoft Intune is Microsoft.

In my experience, Microsoft Intune licensing and pricing mainly depend on the size of the organization, security requirements, and whether it is purchased standalone or as part of the Microsoft 365 subscription. We are using M365 and Microsoft Intune together, with my organization preferring Microsoft Intune through Microsoft 365 E3 or E5 because it includes endpoint manager capabilities along with security and identity services. The setup cost feels lower compared to other software in the market.

I would rate this product an eight out of ten.

I work with Microsoft Intune on 365 Modern Workplace technologies. I have dealt with different Microsoft Intune-related projects because they fall within the security and compliance scope. I migrate customers to Microsoft Intune for endpoint management. I either onboard customers directly to Microsoft Intune or, as in my current employer experience, I detached their endpoints from SCCM and then fully managed those endpoints using Microsoft Intune.

The main purpose of Microsoft Intune is to fully manage corporate or enterprise devices, mainly Windows. From time to time, I make decisions and take action for macOS. I also commonly secure data for non-managed devices, very likely smartphones, using policies to secure data such as Outlook, emails, and Teams.

There is not much measurable improvement in fairness to Microsoft Intune because I typically try to set KPIs, but eventually I cannot. Customers are not focused on that part for KPIs because it would not be easy for them to define clear KPIs such as the number of incidents to be minimized across a semester, quarter, or yearly basis. Another example would be to define an SLA whereby endpoint disruption must be minimized in terms of recognition and response. I always try to establish KPIs, but customers often do not have that mindset.

The integration with different kinds of endpoints is the most valuable feature in Microsoft Intune: Windows, Mac, iPhone, Android, and anything else. The most reliable feature is the integration with Microsoft XDR, which grants administrators and solution architects like me the ability to bring value to a business. Microsoft Intune integrates deeply with Windows and with Microsoft Defender for Endpoint, which is the antivirus. This integration grants comprehensive security from an endpoint perspective.

I am part of the private preview with Microsoft, which is a program for very few customers working with Microsoft to improve features in the future. I am currently working with Microsoft to improve Microsoft Intune RBAC, which is role-based access control because I came across a limitation. I worked with Microsoft for approximately four months, and I and other few customers participated in that program to give our inputs to improve that feature. They have made improvements, and I think later this year Microsoft will release the new RBAC feature in general availability, either in two or three months.

The other area needing improvement is Autopilot because there are currently other limitations. Microsoft opened another private preview for Autopilot and we have been working on that as of middle of February. Those are the two features that did not impress me much, and currently with other customers I am improving them with Microsoft directly.

I have used the solution since 2020.

Regarding the overall stability of Microsoft Intune, I would rate it a seven. Generally speaking regarding scalability, it works quite well. The problems I came across were the ones I already mentioned and led me to join the Microsoft preview program. Generally speaking, I am quite happy with the product, and I would have said even eight, but generally speaking it works quite well.

The problems I came across were the ones I already mentioned and led me to join the Microsoft preview program. Generally speaking, it works quite well.

Regarding customer service and technical support, I would rate it a seven on a scale from one to ten. I would say it is fair enough.

Prior to adopting Microsoft Intune, I was focused on Microsoft solutions, so I try to be consistent with Microsoft Intune. I saw a demo from another vendor, but I have not really worked with other solutions or other vendors.

In relation to the deployment regarding Microsoft Intune, the first difficulty I had to cope with was the decision to make between continuing with co-management or stopping and going to a full Microsoft Intune management. The difficulty there was co-management because there are some decisions to make and also some technical constraints to address. When I decided to go with full Microsoft Intune management, it meant I had to unlink those devices from SCCM and then uninstall the SCCM agent on endpoints and also fix some gaps. There were some difficulties in fully onboarding and unlinking those devices from SCCM and then fully onboarding those devices to Microsoft Intune. Those are the most difficulties I came across in my current Microsoft Intune project experience.

Regarding where I bought Microsoft Intune, that is a difficult question to answer because it depends. When talking about Azure, you are talking about a tenant. When you open a tenant, you open it by yourself. When you need licenses, you may either have a direct relationship with Microsoft, as is the case where I am currently working, or if I used to work as a consultant, I provided help for customers to open a tenant or to buy licenses.

Regarding ROI with Microsoft Intune, Microsoft Intune provides value for customers and they are happy. There is definitely a return on investment for customers when they adopt Microsoft Intune. For larger companies that can manage a large fleet of endpoints, there is definitely a return of investment.

Regarding the quotation for customers, which is something I did in the past, generally speaking from a sysadmin perspective, the pricing for what they offer is in line.

I will answer this question broadly because I work with 365 modern workplace projects and also Azure. I will not answer this question just from a Microsoft Intune perspective. Generally speaking, I try to leverage and maximize the value of a customer's license baseline. For instance, a customer has purchased E5 licenses, which grants the customer very different parts of the 365 ecosystem. There is a lot for a customer to improve. Every time I try to ask questions in relation to what they have now regarding awareness and understand what might be the gap from what they currently have. I am not talking about just in relation to licenses but their awareness for data protection, endpoint management, endpoint protection, identity protection, VM protection, and some workloads protections in the cloud.

There are constraints due to the technology of Microsoft Intune, but this applies to almost any technology. I have not had the chance to integrate with any third-party software. I was able to comply fully with Microsoft Intune solely.

The integration with different kinds of endpoints is the most valuable feature in Microsoft Intune: Windows, Mac, iPhone, Android, and anything else. The most reliable feature is the integration with Microsoft XDR, which grants administrators and solution architects like me the ability to bring value to a business. Microsoft Intune integrates deeply with Windows and with Microsoft Defender for Endpoint, which is the antivirus. This integration grants comprehensive security from an endpoint perspective.

Regarding missing features in Microsoft Intune, I was part of the private preview with Microsoft, which is a program for very few customers working with Microsoft to improve features in the future. I am currently working with Microsoft to improve Microsoft Intune RBAC, which is role-based access control because I came across a limitation. I worked with Microsoft for approximately four months, and I and other few customers participated in that program to give our inputs to improve that feature. They have made improvements, and I think later this year Microsoft will release the new RBAC feature in general availability, either in two or three months. The other area needing improvement is Autopilot because there are currently other limitations. Microsoft opened another private preview for Autopilot and we have been working on that as of middle of February. Those are the two features that did not impress me much, and currently with other customers I am improving them with Microsoft directly.

I would rate this product an eight overall.