Microsoft Intune Reviews

Our primary use case of Microsoft Intune was initially to provide a more cohesive update platform. Our organization was trying to move away from SCCM as far as updating our device platforms across Windows devices. We chose Intune because it had a simplified way to configure Windows Update, view reports, and manage devices for updates. We expanded its use for configurations, moving from a hybrid join scenario to CloudJoin, which offers advantages for hybrid work and on-premise settings.

Everything has worked better since we started using Intune. Our devices use Intune for their authentication SSO process, which is also something that Intune integrates with, so we get fewer SSO prompts for our devices. There's more consistency in the configuration. 

Our configuration profiles used to be all over the place. For example, there's a lot of legacy in Active Directory. Going through Intune has helped us enforce settings, which has improved device security and functionality. When you apply something through Intune, you know it works. You don't have to worry about a legacy setting from Active Directory that was uploaded by somebody seven years ago. With Intune, you can see that a device has a setting, and you can be confident that the device is configured how you want.

The most valuable feature of Microsoft Intune is the extensive reporting that is available. The platform's transparency allows us to see when a device has been configured correctly and what it is receiving. 

We haven't implemented it yet, but Intune provides a cohesive platform for passwordless authentication. The single pane of glass is also huge. We were using SCCM with a third-party management platform. We took down five servers and consolidated everything into Intune. The ability to migrate everything into one platform greatly reduced our server footprint. It was effortless. We onboarded all 12,000 of our devices to Intune in a week.

Our users don't notice it, which is probably a good thing. If you don't notice something interacting with your computer, that's good from a user perspective. When we deploy stuff through Intune, it's silent. We recently deployed a bunch of potentially impactful settings to our users and tried to align devices with Microsoft's best practices. Nobody noticed.

Sometimes the syncing is inconsistent. I'm confident that the devices are checking in every eight hours, but sometimes the devices aren't picking up the settings as quickly as I would expect. Some features haven't been updated in a while, and Microsoft doesn't seem interested in developing them. Unless you talk to an engineer, you don't know whether there will be an update.

There are communication issues, so you might start working with a feature without knowing if it will be deprecated six months from now. Some reporting areas still need development. For example, I noticed that the reporting for driver updates is still confusing. 

We have been using Microsoft Teams since the middle of 2022 when we started rolling it out to our Windows devices.

Microsoft Intune has been very stable. There has been only one incident with an outage on the Microsoft side, but it is rare to have significant outages.

Microsoft Intune is a scalable platform with room for growth. Over the past year, it has significantly developed, with onboarding Mac OS devices now an option. Microsoft has put effort into making Intune manage macOS effectively, surpassing some other providers.

I rate Microsoft support eight out of 10. Microsoft Intune's customer service is generally efficient. When a support ticket is submitted, it directly reaches someone with Intune support expertise, unlike other Microsoft products where assistance may be delayed. Elevation to the right person is swift, though I haven't needed to submit many tickets because Intune functions well.

We previously used SCCM and a device management platform called Remedy in tandem. We switched to unify our mobile device management under one platform and eliminate internal servers. Intune functioned as that single pane of glass for us. Additionally, Intune is more functional and user-friendly than SCCM or Remedy, making it an obvious choice.

The ease of setup depends on your scenario because there are many ways to deploy Intune. Our setup was straightforward because our devices were already in Active Directory, so we could add them using a GPO. After that, we had to do some fine-tuning. We first onboarded our mobile devices and moved our Windows devices to it once the Windows management side matured a little. It took about a week to deploy the solution.

We did not engage a reseller or consultant for our migration. The migration was handled internally without external help.

I can't speak to specific ROI numbers, but there is a noticeable reduction in man-hours spent on support and troubleshooting. Applications are deployed through Intune, and we see fewer tickets for common issues because we can resolve them through the solution.

We did not incur additional setup costs for Intune, as it was already included in our E5 license.

We didn't evaluate other solutions; choosing Intune was obvious as the next step.

I rate Microsoft Intune eight out of 10.

Public Cloud

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.

Public Cloud

Microsoft Azure

My main use case for Microsoft Intune is to enforce endpoint security policies, manage device compliances, and deploy applications across Windows, Android, or iOS devices.

We use Microsoft Intune to automatically onboard corporate laptops through Autopilot, enforce BitLocker encryptions, and deploy security baselines while controlling access to corporate resources using compliance policies.

Microsoft Intune positively impacts our organization processes by providing standardized device management, improving endpoint security, and reducing manual workloads. This provides centralized visibility into device health, compliance status, and security postures, making it very easy to manage and secure endpoints.

We are getting good compliance and we are able to save time, with workload reduction between 40 to 60 percent. We are also getting very good security. These represent significant time-saving and money-saving aspects for the organization.

The best features Microsoft Intune offers include its ability to combine endpoint management, compliance enforcement, and security control within a single cloud-native platform.

Combining endpoint management, compliance enforcement, and security controls in one platform has helped me day-to-day by simplifying daily operations because having everything managed from a centralized platform makes it easier. For example, if a device becomes non-compliant due to disabled encryption or missing critical updates, Microsoft Intune can immediately detect it and apply the appropriate policy, restricting access to corporate resources through conditional access. This is very useful.

Apart from the initial setup that requires expertise to implement and fine-tune it, which could be simplified, everything is very seamless and has stable features.

I have been working in my current field for almost two years.

Microsoft Intune's AI capabilities support governance and security by helping to identify non-compliant devices and security gaps. The recommendations are very useful and also improve security postures.

It is a very reliable solution and provides very accurate outcomes.

My advice would be for anyone considering Microsoft Intune to go for this solution. Additionally, my advice would be to start with clear endpoint management and security planning before deployments and take advantage of each feature. I would rate this product overall as a 9.

Public Cloud

Microsoft Azure

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.

Public Cloud

Microsoft Azure

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 Azure

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 current organization uses device management, deployment of packages, and releasing updates to Windows, Linux, and Mac machines.

Microsoft Intune is being used in my organization.

Microsoft Intune helps when we are preparing devices, as it automatically registers them with Microsoft Intune and self-installs the Intune packages, allowing us to manage that device entirely through Microsoft Intune later.

For Windows, it is easy to deploy Microsoft Intune, but for Mac, it is somewhat difficult, and it is impossible for Linux.

I appreciate how Microsoft Intune deploys Windows-related policies, application deployment, and the application rules that we can create for Windows, which I have automated extensively. I am very satisfied that when any user comes into our organization and we provide the user ID and password, the setup will auto-complete with basic applications and security installed automatically, making the device ready within approximately ten to fifteen minutes. This reduces my manual workload to configure that device significantly.

Microsoft Intune saves me around eighty percent of the manual configuration time for devices.

There is room for improvement in Microsoft Intune regarding Linux and Mac compatibility because some limitations exist. For instance, if I want to install any third-party application on Mac, the process is very complex, requiring multiple deployments and creating an application deployment policy before the Mac rules deployment. It would be easier if, like Windows, it automatically rolled over to the devices without much intervention. Linux presents a major concern as our organization grows and our technical team considers moving to Linux systems for better stability for developers. We are thinking about how we can manage or mitigate the risk for our organization.

The main area of improvement in Microsoft Intune is compatibility. If everything works well, then pricing can be a negotiable point later on, especially if there are multiple users in a large organization. Features that help reduce manual tasks would be particularly helpful.

I have been using Microsoft Intune in my current organization for one and a half years.

I would rate Microsoft Intune's stability around eight out of ten because there are some glitches we face, and we have escalated them to the internal team, who are working on them.

I rate Microsoft Intune's scalability around ten. I have not faced any scalability issues thus far.

I have not connected to the support portal for Microsoft Intune-related issues until now, so I cannot provide a rating for that. I have done everything my own way, so I cannot comment on the support process. The support for Microsoft Office products has been very good, and I hope it remains the same for Microsoft Intune.

I have tried Jamf and forty-two Gears among other platforms. Due to limitations in Microsoft Intune, I cannot do a direct comparison because other platforms provide better services for Mac, Windows, and Linux while pricing is very high compared to Microsoft Intune. If Microsoft Intune provides basic features that can manage endpoints across all operating systems, that would be very helpful.

I need to regularly maintain the patching system in Microsoft Intune because there is no automated system to approve packages and deploy them to the machines. However, it is easy because I only need to create a Microsoft Intune Win package file and then upload it to the respective application that I want to deploy or update on all the devices. I upload that application, and it will do so automatically. I have to regularly maintain and monitor every device to ensure all applications are up to date with updated packages deployed to Microsoft Intune.

Microsoft Intune is moderate in pricing. It is not cheaper or expensive but meets the requirements we need.

I do not use the Enterprise Application Management feature in Microsoft Intune yet, but we are planning to implement it.

I am not using the Advanced Endpoint Analytics feature currently, but I am planning to add more features in a couple of months, as we are in discussions with vendors.

I recommend implementing Microsoft Intune, especially if your organization relies on a Windows environment, as it is easy to manage. However, if multiple operating systems are involved, I suggest using another platform offering better support for those environments based on their technicalities and features. I would rate this review an eight out of ten overall.

Public Cloud

Microsoft Azure

As an administrator and user of Microsoft Intune, we have implemented several key features. Currently, we are using it for Windows updates across the whole company, pushing updates through Microsoft Intune. We also use it for the mass deployment of new applications.

Additionally, for security and access, we implement conditional access controls through Microsoft Intune. We have completed corporate device configuration and starting new journey on bring your own device (BYOD) management.

We use enterprise application management features in Microsoft Intune, with most applications integrated without multi-factor authentication previously. We need to control the number of devices accessing our environment to prevent data breaches or PII issues.

The most useful features in Microsoft Intune are the policy enforcement and conditional access. These features make our operations easier from a company perspective. Each company has its own policies, which are often only written in documents. By using Microsoft Intune, we can enforce these policies throughout the organization, binding everyone together instead of just having documented policies.

Microsoft needs to strategize its licensing structure. When using Microsoft Intune, we bought a small scale of controls, only controlling part of the devices, though Microsoft Intune can do much more. The Intune Suite offers more features, allowing extensive integration with either internal or cloud environments without requiring third-party licensing. However, each feature has a separate license, making logistics and cost management difficult if not strategically bundled together.

I have been working with Microsoft Intune for at least 2 years.

I would rate technical support from Microsoft a nine out of ten.

Positive

We previously used System Center Configuration Management (SCCM). With SCCM, out of 10,000 staff members, only 2,000 to 3,000 received updates and deployments. The updates were slower, and using SCCM caused more network congestion as updates were pushed through the internal network. With Microsoft Intune's cloud-based deployment, users can receive updates and application deployment almost everywhere, and they get updates almost daily. This keeps machines up to date and helps reduce vulnerabilities.

It's easy. In terms of cloud, I am mainly focusing on Azure. There are other divisions that handle AWS and also Huawei Cloud.

While managing Microsoft Intune, we experience some glitches in our hybrid environment with on-premises Active Directory. If the on-premises system has an issue, it can synchronize to the cloud with additional problems. This requires resolution on both sides, which is difficult. It's not Microsoft Intune's fault; it's due to our environment. For companies wanting to use Microsoft Intune, it's better to avoid a hybrid deployment and join everything to the cloud.

In terms of automatic updating with Microsoft Intune, users sometimes complain about needing to restart for weekly updates. Updates are automatically pushed to devices for security purposes. Microsoft Intune helps us manage these updates automatically, unlike SCCM, which requires manual work.

We conducted workshops with Microsoft to ensure we hosted management internally instead of paying third parties. We mobilized our internal team, which has allowed us to avoid additional costs related to external services.

All security solutions worldwide are expensive. Microsoft has allowed a small scale of features within Microsoft Intune for cost-efficient solutions. If you want the full suite, you need to invest more to gain better security features. It's not necessarily more expensive. You need to choose which features to buy. For basic features, Enterprise Mobility + Security E3 (EMS E3) is the lowest pricing Microsoft can offer.

We plan to explore Microsoft Intune Cloud PKI more, as it's not just a replacement for the CA server on-premises. It's a game changer for SSL certificates, eliminating reliance on third-party solutions such as GlobalSign and DigiCert. We plan to implement Wi-Fi with certificate integration, though this is currently just a vision, as we need to purchase it.

Microsoft Intune focuses on device management, including MDM (mobile device management) and MAM (mobile application management). Microsoft Intune can control various devices, but we currently focus on four operating systems: Android (with Google Play Store) and iOS for mobile devices, and Windows and macOS for computers. Our recommendation for Microsoft Intune would be to use it for managing device resources and ensuring policy enforcement according to company guidelines. Each device must maintain current security to prevent attacks or vulnerabilities.

I would rate Microsoft Intune an eight out of ten. I recommend Microsoft Intune and suggest purchasing it along with Microsoft 365 Suite or Azure, as the Intune Suite is essential for managing everything from antivirus to policies and accessing the environment.

Hybrid Cloud

Microsoft Intune policies, remote wipe, and using corporate and private profiles are valuable features, but MFA is the most valuable feature as it ensures that the end user is authentic. After authentication, logs can help us diagnose further. Previously, we didn't know who was using the devices, with every person having 3, 4, or 5 mobile devices registered to their email. We didn't know which device was live or not. With MFA, it is very helpful to identify which one is the last authenticated device. We can also restrict the number of devices using Microsoft Intune.

From an end-user perspective of Microsoft Intune, I haven't experienced any challenges since installation. However, some customers have reported experiencing slowness when using lower versions of the Android system. This observation has been reported to the distributor team, and they are working on it. Hopefully, this issue will be resolved in the next release.

As we have only been using it for six months, it might be too early to identify other areas for improvement. 

We recently started using Microsoft Intune. We just completed about six months of usage.

It is very stable.

We have plans for expanding our business at least 5 to 10% in the next financial year with Microsoft Intune. With most people opting for hybrid work and not coming to the office five days a week, working from home or branch offices, the requirement will definitely grow.

It is too early to provide comprehensive feedback regarding the technical support for Microsoft Intune. We have basic support included in the plan. We have not opted for the advanced support ticket facility. We haven't utilized support services as we haven't faced any issues in the last six months. Without any support scenarios, we cannot comment on response times or resolution quality.

Neutral

We were not using any other solution. The requirement for such a solution came from the data breach incident. After that incident, it was brought to our notice that we needed an MDM solution to protect our data. 

It's very smooth. It's done with two to three clicks. It's very easy.

After installation, Microsoft gave us a vulnerability assessment. Our IT administrators handled the necessary tasks based on the recommendations. The patch management, pushing of patches, and manually updating applications are helpful. They inform us when auto update is off, alerting us to turn on application updates when vulnerabilities are found.

We have not evaluated the measurable benefits since the deployment of Microsoft Intune. With only six months having passed, we need more time to observe and evaluate the returns.

It comes with the E5 plan. We bought the E5 plan from Microsoft.

From a price perspective, the E5 plan we opted for includes features we aren't fully utilizing. Our basic needs were offline Office for end users and cloud-based emails. When we inquired about MDM specifically, they offered separate plans, such as MDM Basic and others. We compared all options and migrated because paying separate license fees for Office and Microsoft 365 mailbox would be more complex. While it is somewhat costly, the major benefit is that we can select licenses only for those using personally owned devices rather than the entire organization.

We had an incident in our organization where we found a data breach in a mobile device, specifically on a personally owned device that employees were bringing in. To protect against this, we evaluated multiple products, including IBM, Microsoft, and ManageEngine. We chose Microsoft Intune as we were already existing Office 365 users. It was easier for us to upgrade the plan from our existing one to E5. It came with a bundle where we received all the services we wanted: private profile, secure download, prevention of sharing corporate data, and access to corporate data. It is easier for us to manage everything from a single console.

ManageEngine's MDM solution was less expensive and of good quality based on our evaluation. However, we couldn't proceed with it because their management console was different, and we were already using Office 365 with a 100 GB mailbox. Migrating all emails would have taken considerable time and risked potential email loss.

Microsoft Copilot is integrated with E5, and some users are utilizing it for writing emails and creating presentations. Copilot is an effective AI engine that helps predict known vulnerabilities and facilitates notification management and task scheduling. 

For endpoint protection, we use Acronis through a separate console, which we've been using for 3-4 years with satisfaction. We are not using Microsoft Defender Advanced Security as it cannot currently integrate with third-party solutions. 

I would rate Microsoft Intune a nine out of ten. It is very stable. The GUI is very good and efficient. Everything is fine. The only issue is with the Android devices.

Public Cloud

Microsoft Azure

We use Microsoft Intune as an MDM solution for all of our Windows laptops and some of our company mobile phones. This serves as an endpoint solution we use so we can control the users' laptops or phones and have access to things on their devices.

Without Microsoft Intune, there would be a lot of cybersecurity attacks happening. We need to use Microsoft Intune so we know which devices can access all of our company resources. If they don't have Microsoft Intune, we automatically deny them from accessing company-sensitive information, so it serves as a layer to protect all of our assets.

I appreciate how easy it is to deploy certificates to end users to get control over their device with Microsoft Intune; that's what Microsoft Intune is known for, and that's what we use them for.

The user experience of Microsoft Intune is pretty easy. Initially, the user has to download a certificate, so when we first give them a certificate to download, they download it on their side, and once they verify themselves, we have access to their phone or laptop, which works pretty effectively.

We are using Microsoft Copilot with Microsoft Intune. Microsoft Copilot helps us with the deployment of Microsoft Intune. Previously, things were more difficult to manage, especially when certificates expire, as they need to be pushed out every year. Sometimes we forgot that, and then people's laptops stop working, so Microsoft Copilot helps us stay on track.

Microsoft Copilot is equally as important as Intune. The go hand in hand as it works in conjunction with Microsoft Intune to affect the deployment process.

Microsoft Intune can be improved by making it even more seamless for users to download their certificates. Currently, we have to push it out to their laptop and they have to do some work on their end, but if we could integrate it so it's seamlessly done and the end user doesn't even know that Microsoft Intune is on their laptop and it's just naturally there, that would be even better. This is especially true for Apple devices, such as Apple phones, where you have to push it out and the user has to accept or deny whether Microsoft Intune can have access to these applications. If it were easier for us to do it automatically without getting permission, that would be beneficial, but in today's environment, we have to get permission to access data.

To make it a perfect ten, it would be helpful if there was a better way to troubleshoot user issues, as I've had a few users with corrupt files before and had to redeploy it without knowing the root cause.

We have been using Microsoft Intune for eight years.

I would rate Microsoft Intune a nine out of ten for stability and reliability. We've never really had any issues with it in the past, and if we have, it's maybe one or two random people where their certificate is corrupt or something's wrong, so we just need to go back and redeploy it, which is not really a significant issue.

Microsoft Intune scales very effectively with our growing needs. The only requirement is more licenses, so once we get more licenses, we're able to deploy them more quickly.

I haven't needed to contact customer service or technical support, which is a good sign. Since I haven't had to use them, I have no experience with their quality of service.

Positive

We did not use a different solution. We started with Intune.

My experience with the deployment of Microsoft Intune was good. Initially, I didn't know much about it, so I had to review all the documentation, complete training, and watch videos to get familiar. Once I got a grasp of things, I tested it on my phone and laptop, and when it worked, I felt comfortable deploying it to more people. I eventually deployed it to about 7,000 machines as it scaled up.

The biggest return on investment for using Microsoft Intune comes down to protecting security. We are protecting all of our assets and using it as an endpoint MDM solution, which fulfills our needs.

Microsoft Intune costs about $7 per user per month, which is somewhat on the pricier end. That said, it's a reliable product, so it's fair. If it were less expensive, we would be able to roll it out to more people, so it's definitely something we're considering.

We use Microsoft Intune for Windows products and Jamf for Apple Mac products. I'm not sure if Microsoft Intune works for Macs. If they do, that's something we'd be interested in exploring.

I prefer Microsoft Intune because Jamf is not the most reliable solution based on my personal experience.

We do not use Microsoft Intune Suite's cloud PKI.

We also do not use the Enterprise Application Management features of Microsoft Intune Suite.

I haven't examined the Advanced Endpoint Analytics in the Microsoft Intune Suite yet. That said, we do have it; I just haven't had the opportunity to review it.

I rate Microsoft Intune a nine out of ten.

On-premises