Microsoft Intune Reviews

As an enterprise, I work with Microsoft Intune with clients. I am a project engineer in the IT field working with Microsoft Intune. The usual use cases for Microsoft Intune that I work with mostly involve setting it up from scratch, creating the profiles, and creating the out-of-box experience for clients. When they sign in to their device, all applications are loaded and all security policies are applied to it. I also handle deploying Microsoft Intune to the environment.

I participated in the initial setup and deployment of Microsoft Intune. For clients, I have done it from the ground up, setting up and creating the profiles, doing the device wipeout, adding the applications, adding the security, and adding the Entra ID identifiers so it can be assigned to every device.

I have been dealing with a lot of on-cloud and on-premises Microsoft Intune solutions, so more of a hybrid solution.

The features of Microsoft Intune that I have found the most valuable and useful include adding applications, doing single sign-on for applications to integrate into Microsoft Intune. I have worked with profiles, security, firewalls, BitLockers, creating conditional access, creating policies in Microsoft Intune, and deploying it to mobile devices such as Android and iOS devices.

What I have found most useful in Microsoft Intune is creating an environment where customers or clients need someone to work immediately with an out-of-box experience. When they sign in with their username, their device is already set up and completed, their profiles are all there, and the applications are all there. They are able to sign into all the required applications. Previously, that used to take time to set up a laptop. The security policies we can apply to every device and the automation of Microsoft Intune represent the most useful parts.

The user experience with Microsoft Intune has been quite successful because when onboarding and off-boarding customers, it is a seamless interaction between the user and the IT team.

In terms of Microsoft Intune, it would be nice to have everything on one single page instead of links for every option that I need to access, such as Defender, Microsoft Intune, Entra ID, and Exchange. It would be beneficial to have it on one dashboard so I can view everything from one dashboard.

The only issues I have had with Microsoft Intune were with applications where if they are not an MSI file, I cannot really upload it as an application. I will have to first convert it, and that has given us some problems where the application does not actually deploy to the device. In some cases, I will have to do a manual deployment to the device.

I have been working with Microsoft Intune in depth for four years.

I assess the stability and reliability of Microsoft Intune as very reliable and very user-friendly, and it is easy to deploy and work on.

Microsoft Intune works quite well with scalability because if the environment is small at one moment, it might grow. It is quite seamless in scaling up to more users, more licenses, more security, and different locations and regions without any complications.

I do communicate with the technical support of Microsoft Intune in general. I would rate it a seven out of ten. In some cases with Microsoft support, it takes long to reach back to me. If they do reach back to me, I get transferred from engineer to engineer until I escalate it, and then they respond with clear instructions of what the problem is.

I found the deployment process of Microsoft Intune quite straightforward. Initially, there is some pushback. However, with doing it from the ground up, I learned quite easily what the issues are and I was able to deploy it the next time without any other problems.

I do use Microsoft Intune's cloud PKI.

I have not dealt with cloud PKI in Microsoft Intune so much, but the complexity involves providing and making sure that the virtual AVD is set up, the databases are there, networks are all connected, hosting applications, managing the infrastructure, and scaling the IT solution.

I use Microsoft Copilot in Microsoft Intune on a daily basis because it is much safer because it is contained into the environment. If I put any customer information into it, it is secured and protected.

I usually use Microsoft Copilot in Microsoft Intune for emails and also with troubleshooting. If I have troubleshot anything, I do a process of elimination where I can see exactly where the issue is. If I cannot resolve it, I use Microsoft Copilot to assist with the issue and provide me with some fixes.

Because Microsoft Copilot in Microsoft Intune is a built-in system and with all the open-source AI models now available, it is much safer to add information or clients' information into Microsoft Copilot because it is much more protected than ChatGPT and other AI devices.

I would rate my overall experience with Microsoft Intune a nine out of ten.

I have been working with Microsoft Intune for around three to four years. My experience has mainly been endpoint management, device enrollment, application deployment, compliance policies, Windows updates, and supporting remote workforce management.

A recent example is onboarding a batch of new laptops for remote employees using Microsoft Intune. We use Windows Autopilot and Intune to enroll the device automatically. Once the user signs in with their corporate credentials, the required security policies, compliance settings, Microsoft 365 applications, VPN configuration, and endpoint protection policies are applied without requiring manual intervention from the IT team.

Overall, the process was fairly smooth. We had our enrollment profiles, compliance policies, and application deployment properly standardized. One challenge we faced initially was with a few devices that were not correctly registered in the Autopilot before being shipped to users. In these cases, the enrollment experience was not as seamless and required some manual intervention from the support team. We also spent time fine-tuning application deployment and compliance policies because being too restrictive can generate unnecessary support tickets.

One additional area where we use Microsoft Intune regularly is compliance and security policy management. For example, when security requirements change, we can update device compliance settings with BitLocker policies, antivirus configuration, or application restrictions centrally instead of relying on users or local IT teams to make changes manually. We also use Microsoft Intune quite a bit for troubleshooting and device lifecycle management if a device is lost.

For our team, the most valuable aspect was actually centralized control combined with remote management. Before Microsoft Intune, tasks such as deploying new security policies, updating device settings, or removing access from lost devices often required local IT involvement or manual coordination. With Microsoft Intune, we could perform those actions from a single console, regardless of where the device was located.

In my experience, the best features of Microsoft Intune are device management, compliance policies, application deployment, and integration with the Microsoft security ecosystem. If I had to pick one feature that stands out, it would be the ability to manage and secure devices remotely, whether it is deploying applications, enforcing security settings, or checking compliance status.

Microsoft Intune has positively impacted our organization by giving us a more centralized and consistent way to manage endpoints, especially as remote and hybrid work become more common. Before Microsoft Intune, device management often depended on local IT support and manual processes. With Microsoft Intune, we were able to enforce security policies, deploy applications, and monitor compliance from a single platform, regardless of where users were located.

Another feature that deserves a mention is compliance policy and conditional access integration. We found this particularly useful because device management is not just about deploying settings; it is also about ensuring that only compliant devices can access company resources. For example, if a device was missing required security controls, such as encryption, antivirus protection, or critical updates, it could be flagged as non-compliant and its access to certain resources could be restricted until the issue was resolved.

One area where Microsoft Intune could be improved is troubleshooting and reporting. While the platform provides lots of information, finding the root cause of a failed application deployment, policy conflict, or enrollment issue can sometimes require digging through multiple logs and views. Another area is third-party application management. Microsoft applications are generally straightforward to manage, but packaging, updating, and maintaining some third-party applications can still require additional effort.

One area I would especially mention is the overall administrator experience. Microsoft Intune has become much more capable over the years, but as Microsoft continues adding features, settings can sometimes be spread across different portals and policy types. For newer administrators, it can take time to understand where a particular configuration should be managed.

I have been working in this field for the last four years.

Rather than one dramatic metric, we saw improvements across several operational areas after implementing Microsoft Intune. One noticeable outcome was onboarding efficiency. New devices could be provisioned and delivered to users with much less hands-on involvement from IT, which was especially helpful for remote employees. We also saw a reduction in support tickets related to application installation and device configuration because many of those settings were deployed automatically through Microsoft Intune policies.

My advice to organizations considering Microsoft Intune is to spend time planning your enrollment and security strategy before deployment, rather than treating Microsoft Intune as just another endpoint management tool. Start with a small pilot group and validate enrollment, application deployment, compliance policies, and conditional access rules before rolling out broadly. We found that testing policies with a limited set of users helped avoid unexpected disruptions later.

From a governance and security perspective, I think this is one of the strongest parts of the platform. What I appreciate is that governance is not treated as a separate process. Device compliance, conditional access, encryption policies, application controls, and endpoint security settings all work together within the Microsoft ecosystem.

If we are talking about Microsoft's AI-driven capabilities within the broader Microsoft Intune and Microsoft security ecosystem, my experience has been generally positive in terms of accuracy and reliability. Features such as security recommendations, risk insights, compliance reporting, and automated remediation suggestions have usually been helpful as a starting point for investigation, rather than something we would apply without validation. In practice, the recommendations have been fairly accurate. I would rate this review a nine out of ten.

My main use case for Microsoft Intune is to secure, manage, and monitor all the endpoint devices from a central platform. I use Microsoft Intune to secure and manage endpoint devices by enrolling a new laptop automatically when a user signs in with corporate credentials, providing security settings and applications without any manual intervention for the IT team.

Microsoft Intune has positively impacted my organization in many ways, enabling us to perform remote actions and have device lifecycle control, such as remote wipe, reset device, and lock the device, along with role-based access control.

These positive impacts translate into real results for my team by saving a good amount of time. With Microsoft Intune, we set up the device within 20 to 30 minutes, reducing the provisioning time by 70 to 80%, and it has also reduced the IT workload by 40 to 60%.

The best features Microsoft Intune offers include centralized device management and automating provisioning, which is really helpful with this device.

Out of centralized device management and automated provisioning, I find centralized device management most valuable because it gives us good visibility from a single place, allowing me to see all the devices, whether their compliance is okay or not, and their security posture from a single console for real-time control and response.

I have not seen any kind of challenge with Microsoft Intune; it is working well and providing deep, built-in visibility that improves troubleshooting steps, though I believe detailed customized reporting can be improved.

I have been using Microsoft Intune for more than three years.

Microsoft Intune is stable.

Scalability with Microsoft Intune is good, handling the growth of the organization over time.

The customer support for Microsoft Intune is good in their technical aspects and provides great support to our IT teams.

From the start, we have been using Microsoft Intune and did not switch from a different solution.

Microsoft Intune is deployed in my organization through the public cloud.

We have seen a return on investment with Microsoft Intune, including time-saving and money-saving outcomes.

We have not gone for evaluation of other options before choosing Microsoft Intune.

My advice for others considering Microsoft Intune is to deploy it as it will really help build a foundation for their identity first, aligning Microsoft Intune with their identity setup by starting with a pilot phase and keeping policies simple during the initial design. Microsoft Intune is deployed in my organization through the public cloud, and we do use Azure as our cloud provider. I would rate this solution an 8 out of 10.

Microsoft Intune is used for technical support. We handle client cases and help in the resolution of cases from post-commercial support. We have not yet moved to premium cases, but we provide technical support for any issues with Microsoft Intune.

Microsoft Intune has broad capabilities, particularly with mobile device management. The management features are excellent, especially the ability to push configuration policies to all devices across the company and manage them effectively. The configuration capabilities are strong, and the compliance features are also really good.

The application management is a valuable feature because it makes the process easier by centralizing applications in one place, which contains most of the things needed when configuring or deploying applications. This is a really good feature to use in Microsoft Intune.

The admin portal for Microsoft Intune is not yet on the same level as other Microsoft 365 admin portals when comparing the interface and user-friendliness. The admin portal is something that still needs improvement, though I believe it will be updated in the future.

The admin portal has not yet been updated to the level of other admin portals such as Entra, Microsoft 365 admin portal, and compliance portals. It is usable and can be used, but it is not as user-friendly as those other admin portals when compared side by side.

I have been working with Microsoft Intune for about two months, starting in December, and I am now in my third month as the product ready trainer for Microsoft Intune here in Rwanda. It has not been that long, but because it is a new technology we are supporting, the experience has been valuable.

During the time I have been using Microsoft Intune, there have not been many issues. There have been no service incidents, no total shutdowns, and no lagging that I have observed. However, because we interact with customers and support them with Microsoft Intune cases, there have been some complaints from customers. Sometimes there is lagging, policies are not being pushed, or the eight hours of synchronization have passed without anything happening. For myself personally, I have not had any lags or downtime with Microsoft Intune as a product.

Microsoft Intune is really scalable because it is broad and has many things and dedicators for various functions. The scalability is really good.

There is a partnership since we support Microsoft cases. We deal with technical support for Microsoft coming from Microsoft Intune to other lines of business, so there is a partnership in place.

Positive

I have only used Microsoft Intune.

The initial setup is easy. It took me around thirty minutes, and the whole process was seamless because following the steps was straightforward. I would not classify it as difficult—it was easy.

It is better to implement with a team due to the different efforts involved, but a single person can also complete the deployment. However, it is preferable to have a team.

Microsoft Intune provides a good return on investment.

The prices are good. The licenses are good, and since Microsoft Intune is mostly embedded in other licenses such as E5s, the pricing is customer-friendly. I cannot compare it to other licenses, but I think the pricing is really good.

There are alternate solutions, but not many. When talking about certificate handling, we do set up or support customers with certifications, but mostly this is done by a different support team, the on-premises team. I have not interacted very well with Cloud PKI because it is dealt with by a different team, mostly the security and compliance team. I do not have much experience with it, but I have interacted with it here and there.

I have been a product ready trainer for Microsoft Intune for two months, but in the field of Microsoft technical support, I have been doing this for two years.

I have seen the CoPilot feature in Microsoft Intune, but I have not interacted with it much because the licensing we are using at the moment does not provide access to CoPilot. We do not have that access, and because it is also a feature in preview, we have not really interacted much with CoPilot in Microsoft Intune. However, I have interacted with CoPilot in other admin centers, and it is good.

We use the feature, and it has been beneficial.

With Microsoft Intune, you must always check the policies to ensure they are interacting with the devices. You must keep checking the compliance of the devices and the health of the devices. This is something you keep checking regularly, so you must always be looking after these things in Microsoft Intune. It really does require ongoing maintenance.

Organizations can implement Microsoft Intune successfully. My review rating for Microsoft Intune is seven point five.

In my career, I have used Microsoft Intune for about four or five months during my internship at my previous company, which is a global organization where I learned about Microsoft Intune and Entra Admin. I was using the cloud-based system all of the time. I am knowledgeable about many aspects and can manage requirements as needed, including device management and application management. I can handle whatever part of the premises needs to be taken care of.

What I appreciate most about Microsoft Intune is that we can manage multiple devices simultaneously in a single frame of time. I can manage everything remotely from anywhere. There are policies I can implement for compliance on several things, such as for sales teams, finance management teams, or tech teams. I can focus on the segment where I'm implementing policies or accessibility and manage it very quickly. Microsoft Intune brings all our endpoint and security management tools into one place, and we can minimize the endpoint and security management aspects. The security doesn't need further development as it already has multi-factor authentication options. If we want to add another option, we can mail a QR code; if the organization has that QR code, any employee can access it similar to multi-factor authentication. By using Microsoft Intune, we can protect our system through security checks, allowing us to define which party can access our system from remote locations. There are various applications being utilized for remote functions, and with our firewall in place, we don't need to worry about security.

The downside of Microsoft Intune is that in a fast-moving world, most people are using AWS or Azure. Specifically, cloud-based technologies nowadays manage this stuff automatically after deployments, particularly for application purposes. For application and device management, I suggest combining them in a mode where managing both things could have shortcuts throughout the system. For instance, when applying anything to a tech team, it should automatically apply to their applications on phones as well. There should be a system already designed, and as a developer, I believe I can design that type of framework.

I have used Microsoft Intune for about four or five months.

I have faced stability issues with Microsoft Intune plenty of times, but I think it's part of the process. It functions adequately sometimes; nothing is 100% perfect.

The scalability of Microsoft Intune is quite good; it won't affect the work environment or struggle with multiple PCs. For large-scale use, there might be timing issues during installations or setups, which requires more time.

I have contacted technical support many times, and they respond quite accessibly, making it easy to reach out to them.

It takes around 45 minutes to set it up for me.

Microsoft Intune doesn't require any maintenance; the only cost involved is paying for the package on a yearly or monthly basis.

I haven't tried using any alternatives to Microsoft Intune. There is a system with Google that has its endpoint system, but I haven't used it. Most people around me are using Microsoft.

On a scale of one to ten, I would give Microsoft Intune a rating of eight out of ten.

We use Microsoft Intune to manage mobile phone devices and laptops to ensure they are synchronized with the company. They are not used for tracking or third-party software, and they comply with company regulations. If devices get tampered with, lost, or stolen, we can track them. The devices are registered to our systems, so if anyone forgets their user IDs or passwords, we can resolve that using the authenticator. We use the Cloud PKI, which is straightforward and easy to learn. Everything is documented, and a self-starter can learn it. It is not highly technical. It requires being comfortable with Microsoft Windows knowledge and knowing how to use a desktop and commands. Someone with basic knowledge can pick it up easily.

We use the Copilot integration in Microsoft Intune which helps protect our environment. We are using the Enterprise Application Management features of Microsoft Intune. These features have improved our abilities in app discovery, deployment, and automatic updating. The Advanced Endpoint Analytics in Microsoft Intune has improved and helps us proactively detect and remediate anomalies in endpoints.

Everything about Microsoft Intune is something that I value the most. It is something that I use for employees, whether for new starters or anyone who makes a request. It is a requirement and a need, and it works great. So far, there have not been any issues. It performs very well.

The documentation and authentication could be improved. Sometimes, there can be issues where you have to restart multiple times. There have been instances where enrolling devices should take 10 minutes but ends up taking an hour due to various issues. Performance is something that needs to be worked on.

I have been using Microsoft Intune for around a year in my career, not necessarily in this job, but overall.

Sometimes there has been instability such as crashing and downtime. This happens as part of business operations.

The scalability of Microsoft Intune can be good at times and off at others, so it falls somewhere in between.

I have not had to contact their support.

Neutral

My initial introduction to Microsoft Intune was straightforward because everything was written and documented, so it was simply a matter of following their instructions.

We have used an application called Pyrus as an alternative. That is software our company purchased, and it actually helps.

I followed the documentation from my colleagues and have used some documentation from Microsoft. The Microsoft documentation is adequate. I do not know the pricing of Microsoft Intune, as that is not something I manage. When I joined my current company, Microsoft Intune was already in place, so my role was to enroll new devices and distribute them to new people.

On a scale of 1-10, I rate Microsoft Intune a 7.

I have been using Microsoft Intune for around a year now. I have worked on Microsoft Intune on a few cases mainly for device management and policy setup. Recently I used Microsoft Intune to push security policies and apps to company devices and make sure everything stays compliant.

I have also used it for remote troubleshooting and resetting devices and to enforce compliance policies such as password rules and device encryption.

I think the best features are its very easy device management, strong security policies, and the ability to manage everything remotely from one place.

Device management is easy because I can control and monitor all devices from one dashboard and the security policies stand out since they help enforce things such as passwords, encryption, and compliance automatically.

App management is really useful. I can easily deploy and update apps remotely, and it integrates well with other Microsoft services which makes everything smoother.

It has improved security and made device management much easier. Plus, it saves a lot of time since most things can be handled remotely.

I think it could be improved by making the interface a bit more user-friendly and simplifying some policy configurations as they can feel a bit complex at times.

Reporting could be more detailed and easier to understand and sometimes troubleshooting or support takes time. That part could be improved as well.

I am working in my current field for three years or more.

Microsoft Intune is generally stable and reliable for day-to-day use but sometimes you might see delays or minor issues since it is cloud-based.

Microsoft Intune is highly scalable. You can manage thousands of devices easily and since it is cloud-based, it can grow with the organization without major changes.

Customer support is decent overall, but not perfect. Most issues get resolved but sometimes response time can be a bit slow or require multiple follow-ups.

Earlier we were using basic manual setup and some on-premises tools, but we switched to Microsoft Intune for better cloud management, security, and easier remote access.

We have definitely seen a good return on investment. Roughly, it has saved a good amount of time in device setup and support, reducing manual effort by around forty to fifty percent and also fewer on-site interventions since most issues are handled remotely.

Overall pricing was pretty reasonable. It is usually bundled with Microsoft 365. We did not have much separate setup cost and licensing is per user which makes it easy to scale as needed.

We looked at a few options such as VMware Workspace ONE and MobileIron, but Microsoft Intune fit better since we were already using Microsoft services.

I would say plan your policies properly from the start and take time to understand them. Overall, Microsoft Intune is a solid and reliable solution for device management, especially if you are already in the Microsoft ecosystem. It really helps in simplifying security and remote management. I give this product a review rating of eight out of ten.

We deploy Microsoft Intune for clients and give them support for 

The main use cases for Microsoft Intune among our customers currently include migrating a client that was initially with Dell; they were using a Citrix solution along with other solutions. We migrated all the infrastructure on Azure, and they have almost 400 to 500 users. We have registered users' laptops and desktops with Microsoft Intune. I integrated them with Entra ID and Active Directory authentication. We are providing them support with managing all the devices, including their laptops, mobiles, and PCs with Microsoft Intune, along with all the policies and other configurations.

The most useful features of Microsoft Intune for our customers include centralized management; administrators can access all device reports, which devices are expiring MFA, which are not using MFA, device details, and other important information. All details about users and devices can be accessed through a centralized portal and dashboard. That is the main feature.

Regarding user experience, Microsoft Intune is very user-friendly. We need to register the device with Microsoft Intune through the Company Portal. When it's registered with the email, it comes to the management console on Microsoft Intune. We can manage all the devices from the portal, and users are very satisfied with no issues. They only require assistance with daily routine tasks, but otherwise, everything runs smoothly.

It’s already a strong application and management tool, and the team is continuously improving it. Everything is progressing smoothly, and our policy allows for certain configurations to be made easily.

There could be some improvements regarding additional features and integrations in Microsoft Intune. Microsoft Intune works with Entra ID. If there is an option for a client with 100 PCs or laptops that are not on the Entra ID domain, it would be good. It should work without a domain. Microsoft Intune works with the Entra ID domain, with the domain ID, with the email ID. There could be some kind of feature that supports a workgroup environment or a separate environment without the Entra ID.

I've been working with Microsoft Intune for five years.

Our customers have not faced any issues with the stability of Microsoft Intune; it's very stable. When they change devices such as laptops and mobiles, we need to register again and remove from the portal, their MFA, and other configurations. Otherwise, it is fine with no significant issues. It's very reliable and scalable.

In terms of scalability, Microsoft Intune performs exceptionally well. This solution is scalable. 

As technical professionals, we rarely need support. We handle issues ourselves, but whenever there's a need, we raise a ticket with Microsoft to get issues resolved and convey solutions to the client. If we have solved the issue through the Microsoft portal, we raise a ticket and provide the input from Microsoft to the client regarding what the issue was.

Positive

Our customers evaluated other tools before working with Microsoft Intune, as they migrated from ManageEngine and other management devices to Microsoft Intune. They saw advantages that led them to choose Microsoft Intune and Entra ID, so they migrated all the infrastructure and found it better than other management tools.

For tech-savvy individuals, the process is straightforward. You simply need someone with technical expertise to handle the portal, making device registration easy. There’s nothing complicated about it. 

Microsoft Intune is not too expensive; it is bearable for the clients and fits in their budget.

I would recommend Microsoft Intune to others. It is a very good and scalable solution. Every person, client, or company that has infrastructure with more than 100 or 200 devices will find it very easy to manage all their devices, mobiles, laptops, PCs, and network devices from the same dashboard and panel. All the information in the portal and dashboard makes it good for them.

I would rate Microsoft Intune a nine out of ten.