Microsoft Intune Reviews

We use Microsoft Intune for device and identity management, providing end-user support, determining device hardware placement, collecting diagnostic logs, deploying patches, distributing software and feature updates, and managing quality rings. This platform enables us to manage over 20,000 devices across our organization effectively.

Intune provides a centralized platform for managing our security, allowing us to establish compliance rules and implement restrictions based on corporate security approvals and project requirements. For instance, we can disable print screens or activate screensavers after specific intervals to enhance security.

Intune offers a positive user experience, and we can monitor each user's activities.

We use Microsoft Intune's Enterprise Application Management feature to manage Forcepoint DLP, Endpoint DLP, privileged identity management, Cisco MD, and other enterprise applications according to organizational needs.

Within half an hour of being added, a device syncs with Intune, enabling policy synchronization and providing immediate benefits. Intune also offers troubleshooting assistance for any device linked to it.

Intune helped increase our IT team's productivity.

I like Intune's ability to manage roles, maintenance tasks, compliance settings, and patch development for all endpoints.

The information we receive at the device level needs improvement. For instance, we can gather data on 10K devices but not 4K ones. I want to access information about devices that currently aren't included. Twenty percent of the workload integrated into the cloud from collected data represents inapplicable scenarios. I want Intune to decrease this by at least ten percent.

I have been using Microsoft Intune for two and a half years.

We have also used Nexthink, which can connect more devices, but Intune allows us to collect more detailed information.

I would rate Microsoft Intune ten out of ten.

Microsoft Intune has been used in organizations ranging from US entities to Indian companies, with onboarding of systems in numbers ranging from 300 to over 7,000. We migrated from on-premise Active Directory to Microsoft Intune during COVID for remote work support.

As a user, I believe that Microsoft Intune is a superior tool that addresses many issues compared to previous methods, such as using a local Active Directory. As an administrator, I have a broader view of the system, allowing me to monitor whether users are online or offline, track their last activity, and manage various aspects effectively. This is a significant improvement over older methods, where we often had to inform users that certain activities were not approved due to insufficient access levels.

Microsoft Intune streamlines remote system access and management without a physical environment. I started my career in Active Directory configuration and Group Policy. In those roles, we provided systems to end users. When users went home and encountered issues such as password changes or other policy problems, troubleshooting those issues became quite challenging without physical access to the systems. However, using Azure and Intune has helped us resolve most of these issues. With these tools, we no longer need a physical infrastructure to manage systems, as we can push policies remotely and maintain control over the devices. This capability is a significant advantage of the cloud environment, as it allows us to streamline processes and provide remote access without reliance on physical setups.

Additionally, Microsoft Intune gives us a broader perspective, enabling us to manage policies for both users and systems through cloud portals. This approach allows us to deliver solutions much more quickly than the methods we previously used.

Reporting remains an issue, with challenges in providing comprehensive reports. For instance, while we can generate detailed reports for individual users—such as examining sign-up, sign-in, or audit logs—we struggle to produce aggregate reports for the organization. For example, if a user encounters issues logging into the system, we can monitor that specific case and provide detailed information. However, if the organization wants to know about multiple users experiencing problems with multi-factor authentication (MFA), we cannot compile a comprehensive report that highlights how many users faced this issue or identify the overall cause, such as a policy change. This limitation in Microsoft Intune is a significant drawback; we cannot produce overall reports on an organizational level. 

Another issue is that when configuring and deploying Microsoft Intune, some processes experience delays due to the cloud environment or other structural elements like the local area network and internet dependencies. I believe that if Microsoft Intune could operate through both agent-based and non-agent-based approaches, it would improve communication between cloud services and local systems. For example, the policies could first be downloaded to local systems, and once everything is ready, the deployment could occur. Currently, with Windows updates, we have control over when to deploy them, and we can see the status of the deployment, whether successful or failed. A more effective approach would be to allow for manual deployment initiation rather than automatic triggers. By implementing this, we could validate that the updates are properly downloaded and available on the local systems before proceeding with deployment. This streamlined process would enhance our ability to manage updates effectively.

Pricing can be challenging for startups or smaller companies. While larger companies have budgets for cybersecurity, smaller ones may struggle with recurring costs of cloud-based solutions like Microsoft Intune.

I have been using Microsoft Intune for five to six years.

We haven't encountered any specific session outages or similar issues, but one drawback of this cloud environment is that we cannot accurately inform the end-user or management about when the exact policy will be applied and when the results will be visible. The nature of cloud deployment means that the rethinking process can take about 30 to 45 minutes, and in some cases, it can take a few days, as we've experienced.

Regarding scalability, there are no issues. We successfully scaled from 4,000 to over 10,000 employees without major changes. I don't foresee any significant issues in this regard.

While we encountered some initial problems during the early days of deployment, the frequency of these issues has decreased. Most troubleshooting can now be handled on our end. I would rate them an eight out of ten.

Positive

We previously managed 4,000 to 6,000 systems globally using Active Directory before migrating to Microsoft Intune during COVID.

The initial deployment and installation are quite comparable to other tools, but it offers more flexibility, especially since most systems operate on Windows. While the deployment or configuration might take a few days, once we finalize the planning phase, the onboarding process becomes much smoother. We can effectively onboard the system with or without user assistance. A significant advantage is that we can complete migrations remotely, minimizing user dependency. For context, we previously used Active Directory to manage 4,000 to 6,000 systems globally. We migrated to Microsoft Intune and other security solutions during the COVID-19 pandemic, when many organizations transitioned to remote work. During that time, we began the migration process, which included transferring user profiles. Typically, it took about 38 to 45 minutes to migrate a system from on-premises Active Directory to cloud-based Intune, assuming the user had minimal data in their profile. If the profile contained more data, the migration time could vary, but the average was still around 45 minutes for one system.

Regarding maintenance, while new deployments may not require a specialized person on-site, ongoing security improvements or updates to organizational policies need to be handled carefully. These adjustments are not something that a Level 1 engineer can manage alone. Proper planning and execution by specialized engineers are essential to implement these changes effectively.

On the pricing side, the cost for tools like Microsoft Intune can be challenging for early-stage companies that cannot afford such expenses. For smaller companies, the comparison often leads them to choose a local Active Directory, as it involves a one-time cost for purchasing and configuring servers. With Windows Server's built-in Active Directory feature, there are no additional costs for customizing policies. In contrast, Intune is a cloud-based solution that requires a recurring monthly payment. Moreover, the price increases with every additional endpoint, which wasn't the case before.

This cost structure could pose challenges for startups that are struggling financially. However, companies aiming for a fully secure environment and those with a dedicated cybersecurity budget can plan to implement Intune effectively. In summary, I would say that Microsoft Intune is the best product for established companies. It can be quite difficult for new companies without a cybersecurity budget to manage the associated costs.

I would rate Microsoft Intune a ten out of ten.

Microsoft Azure

Its price is reasonable. It is a part of our M365 suite.

I have not been satisfied with it, and I am planning to change it soon. There are a lot of updates coming from Microsoft that suddenly affect our security policies. With each update, a new feature is introduced. However, there's often no clear advice regarding these changes. If we encounter a problem, we have to rely on the Microsoft Community to discover that a new feature has impacted our security policy, at which point we need to make adjustments. That's why I plan to position our operations around an agnostic tool.

Overall, Intune is quite complex, especially if you have conditional access associated.

They can cover Apple iOS in the future to enhance its functionality.

I have been working with Microsoft Intune for more than 5 years.

The kind of issues I face include a lot of updates coming from Microsoft that all of a sudden affect our security policies.

Technical support by Microsoft is okay.

Neutral

We are not using Microsoft Intune for patch management. We are looking into Kaseya. I am satisfied with Kaseya, which is why I would like to further evaluate standardizing Kaseya across the organization. I don't want to utilize Microsoft Intune because I prefer an agnostic solution rather than one that is heavily reliant on a specific brand.

Its deployment was neither easy nor difficult.

I don't have any problem as far as cost is concerned. It is bundled with our license. 

I would rate Microsoft Intune a seven out of ten.

Mainly, the use cases I get are device migration and completely applying Microsoft Intune policies, security policies, Intune patches, deployments of applications, etc. I work as a consultant, and I guide companies. I consult companies on moving from one platform to another, specifically focusing on complete migration to Microsoft Intune.

I have used the Microsoft Intune suite cloud PKI. I am using Microsoft Co-pilot for my use but have not used it for customers.

There are many features in Microsoft Intune. For personal mobile devices, MDM is what I most prefer. Microsoft Intune is reliable, scalable, and user-friendly.

Currently, Microsoft Intune's focus is mainly on Windows, but they can make much more improvement in terms of other platforms. 

Automatic updating is a problem sometimes. When there are applications not from Microsoft, we have to upload updates every time to update those applications.

It can be improved in terms of reporting. There is a problem with reporting; if you want to extract a report, sometimes you have to use the Microsoft Graph API. Microsoft Intune does not provide as many reports as needed. The reporting needs improvement, as currently, we have to use other platforms or the Microsoft Graph API for better reports. If the Microsoft Intune console itself provides reports regarding device management, it would be much better.

I have been using Microsoft Intune for more than four to five years.

It is reliable.

It is scalable.

The support is not particularly good. Sometimes when you open a case with Microsoft, you end up resolving the issue by yourself. It depends on the type of support you have purchased. If you have taken the premier support, then you might get better preference; otherwise, it will take some time for the support to reply. I would rate their technical support a six out of ten.

Neutral

I have seen customers mainly switch from AirWatch to Microsoft Intune and also from Zoho to Microsoft Intune. Microsoft Intune is more user-friendly, but other platforms are better for creating certain policies.

It's not that difficult. It mainly depends on the device configuration. It depends on how the devices are configured and joined to the Azure tenant. It's more compatible with Windows devices.

On non-Windows devices, the policies that Microsoft Intune provides may be limited. For Linux, there are not many policy capabilities. For Windows, Microsoft Intune has full capabilities, making it easy to work with, even in hybrid environments.

The price of Microsoft Intune is reasonable. It depends on the capabilities you purchase and what features you want in Microsoft Intune, not only device management but also other security capabilities. If you want to have security features included in their licenses, then you have to buy the security license, such as the E5 license of Microsoft. There are different scenarios.

I am satisfied with Microsoft Intune. The enterprise application management features are fine, though they take some time to manage. I am not currently using the Advanced Endpoint Analytics in the Microsoft Intune suite, but I have seen them.

I would rate Microsoft Intune an eight out of ten.

Basically, I am using the whole family of Microsoft products regarding Microsoft Five. Intune is one part of these products. I started with mobile device management. Nowadays, I'm using Intune as a standard tool for managing endpoints - computers, laptops, mobile phones, cell phones, et cetera. I'm using Intune for managing all this IT equipment.

The best features include the management, which is quite good, and endpoints. 

When I want to publish some applications for my computers in a company or need to push some policy, I click several settings in the Intune console, making it very quick to publish on all computers and devices. 

The cloud base is perfect for me. I can use Intune in many ways. One very good way is when a company asks that all suppliers and colleagues can use their devices. Intune can be a benefit that allows your own device to work in a company environment via Intune. 

I can use Intune to set up their environment, and Intune will take care of company applications and security. This is something that could be beneficial for our employees.

When we implemented Intune, it would have been helpful if Microsoft had provided some videos or data about Intune. While there are lots of trials, having movies or guides on features would be very helpful for beginners.

I have been using Intune for more than ten years. In my previous job, I managed mobile device management through Intune. It's been around ten years that I've been using Intune.

There were several bugs with stability. I'd rate it nine out of ten.

Scalability is absolutely perfect. I'd rate it nine out of ten.

There is a local company in Slovakia, which is a platinum partner of Microsoft. When I have issues regarding Microsoft products, I raise a ticket with the local company, and they have a good relationship with Microsoft support. 

It's a two-level support system where the local company contacts Microsoft. This way of support is perfect for me, and all past issues were resolved. The support from Microsoft is excellent. 

Positive

In my previous job, we used MASP 60 from IBM. I had a good experience with another cloud-based management solution, however, I can't recall the company name. When companies use Microsoft products for computers, servers, and applications, it's the best option for these features.

The initial setup is quite easy. You have to pay only for the license, and you can start with the deployment. That's all.

This question is for the finance department, not for me. They do the calculations.

Every day, my colleagues and I manage mobile phones and computers with this tool, and we can't share our infrastructure without Intune. We manage computers remotely via cloud management. We do achieve a minimum savings of 20% with Intune since users can stay home. 

We use Intune for managing computers, cell phones, tablets, and more. However, there is likely a fifty percent potential usage in other areas within the company. This requires input from end users, not IT personnel. I find it crucial to communicate effectively with management and staff about implementing new technology. 

It's important to explain that while the users' cell phones are not personal, data on these devices is company-controlled. We set up the mobile application management bundle. Initially, users were confused and concerned about their phones. Strong communication with end users is vital for implementing new technology successfully. 

Overall, I rate the product nine out of ten.

Hybrid Cloud

We use Intune to manage devices and configurations on all platforms, including Windows, iOS, iPad, and Android. It also provides conditional access from the Azure portal. We have also used Intune to bifurcate data and data transfers. We have an Intune entry list that shows the device count and bandwidth of each, so we can manage the data flow from every device based on whether it's corporate or personal. 

Intune is flexible. If you want to move a device that was previously on-prem, we can bring it to the cloud and apply all the policies. This is helpful for even those organizations that were on-prem and not on the cloud. They can also come and use these features, which are pretty cool and would be handy to protect the data and manage the devices as well.

It's handy to manage all the hybrid devices that are on-prem and in the cloud. If a user accesses company resources on their work profile or their personal devices, they can register the device in Intune and access the company data. Intune is a crucial part of the overall structure because we can use it to analyze risks and threats coming into our organization and predict what will be vulnerable. It's necessary to analyze all those things from a security perspective.

Intune's advanced endpoint analytics require a separate license. We are keen to use that one because it comes with more features, flexibility, and control for admins over the devices. We haven't used it, but I've tested it on my tenant with a few devices

It is much easier for admins to use that cloud PKI infrastructure compared to when we had to set up all those things using our Skype profile from Intune. It's quite handy. It takes a little work on the admin side, but the whole structure is the same.

Intune drastically improved our productivity. Work that was previously completed in four hours could now be finished in one. It saved our IT admins many hours of work. Once we migrated from our on-prem servers to the cloud, the Cloud PKI saved us a lot of money. I don't know the numbers, but we are saving so much money because of this. 

The best part of Intune is application deployment. We can deploy an application to several users with a single click. We can use conditional access, granting access to users based on certain conditions, such as location, platform, etc. 

With the help of Microsoft Defender, we can bring each endpoint or node under  Intune's umbrella and manage it through Defender. The most effective feature for managing mobile devices is the compliance policy, which mandates that any user on a particular device should be compliant. It should meet the requirements the company sets and be upgraded. The user should meet all these security criteria we have implemented. 

Intune's app management can support our business operations. For example, if a user wants an Android app, we can deploy it through the Android store, but if we're talking about any MSI on a public-facing platform, we can convert it into Win32 and deploy it to the whole enrollment. Intune is quite flexible.

Compared to another Indian MDM tool I use, Intune provides more flexibility for security. The Microsoft name assures us that our data will be protected. Control over data is the main concern on the cloud.

The reporting causes problems because we're trying to gather data to present to the management, but we can't get the data they request. If a user has removed an application from his device, but it won't report it at exactly the right time. It takes time to sync from the device to the portal. Let's say we are preparing a list or deck for the number of compliant devices that meet all of the organization's requirements. In a real-time scenario, that device could be compliant, but it is showing as non-compliant on the portal. It sometimes hampers the overall decisions that we make on our end.

I have used Intune for four and a half years.

I rate Microsoft premium support nine out of 10. Their premium support is top-notch. They build a bridge to resolve the issues. Standard support varies, depending on the engineer you get. It could range from six to eight out of 10. 

Positive

Previously we used SCCM. It's a Microsoft solution, but Intune's user experience is much better because it's cloud-based and it's more cost-effective. 

Deploying Intune is pretty simple for someone who is experienced with the program. The admin needs to know the basics. Otherwise, it's user-friendly. The time needed to deploy depends on the network, but if everything is perfect, it only takes five to 10 minutes to deploy an application on a Windows device. An Android device is in a similar range. In some weird scenarios, it may take 15 minutes. It doesn't require much maintenance after deployment because it's cloud-based, so we don't need to update anything.

Intune cuts the amount of time we spend on these tasks in half.

Intune is a better value than SCCM or other management tools because we can integrate more with Intune. 

I rate Intune eight out of 10. I would recommend Intune to others. Microsoft offers many new handy features, such as the ledger and the ability to locally administer managed devices. It doesn't require much hassle to set up these things. It's worth the price.

Public Cloud

We are using Intune for managing endpoint devices with zero-trust principles. The devices are not domain-connected because most people work from home. We do not trust these computers, so we use Intune to deploy and enforce policies related to updates, software installation, and management of admin users.

When we are using Microsoft products on mobile devices, we are using Intune to enforce policies on them.

Our usage is very simple. We are using Intune to manage devices that we do not trust. We are using Windows 365, and we install all applications only on these virtual PCs in the cloud. We do not have anything on endpoint devices. Not even a simple document can be downloaded there. We just have an access point to Windows 365 machines in the cloud. We are a financial company. There are not too many enterprise applications that we can use. We prefer to use zero trust. This means no there is no data on company devices at all. It is only on the cloud machines. It is easier to control one perimeter than 10,000 or 20,000 machines. We can reduce the attack surface in this way.

Intune increases the productivity of our IT team. 

There is a reduced cost of ownership and management. We do not need a lot of additional training. Administrators can share roles because its interface is similar to other Microsoft solutions. With one or two days of training, administrators can start working with it. There are a lot of Windows specialists in the market.

We work completely in a Microsoft environment. Its interface is similar to other Microsoft solutions that we are using such as Microsoft Defender. So far, for our administrators, it is easy to use. 

At the moment, we need more flexibility. We have some offices migrating to Windows 11 remotely. Sometimes, it is difficult to manage image installation because we have to collect some information before starting image deployment. Currently, Intune cannot collect the information needed for deploying new images.

We have been using Microsoft Intune for three years. I also used it for two years in my previous work.

Intune is a stable product with no significant issues. We have standardized hardware. We do not have a wide variety of endpoints.

Intune is quite scalable. We started with 3,000 machines, and we now manage 15,000 machines. Our endpoints will probably grow.

I have not interacted with Microsoft technical support personally, but I was satisfied with their support in my previous company.

Positive

I have not used any other solution in my current company.

We are using the public cloud for access, but everything is closed. There is no public access to infrastructure. Access is only through the cloud. There is no VPN or any other way.

I was involved in the security assessment in the beginning. The initial setup was quite easy because we did not look for very complicated functions. We did face some issues with the multi-user mode but resolved them. It took us about a month.

It requires maintenance. You have to review regular policies and adjust policies when something changes in the environment or you deploy new applications. Its maintenance is mostly done in-house. Only in a very complicated situation, we involve a third-party consultant.

We performed the deployment with the assistance of a third-party consulting company, not resellers. Three engineers from our team were involved.

Cost is not my department, but the product is included in the E5 license that we already pay for every user, so no additional cost is incurred.

We have not evaluated other options because Microsoft Intune is included in our E5 licensing. I would prefer to use the VMware solution, but that is not possible because Intune is included with our existing license. Buying any other solution will result in additional costs.

I recommend doing thorough homework and testing everything in a test environment. After ensuring that everything works fine, proceed with the final deployment.

It is not the best solution. It requires a bit more effort in management, but it works. It is not so flexible, but considering it is free for us, it is okay.

We are doing experiments with Copilot to see how we can use it. For some users, it is deployed, and we will be testing it actively. We are mainly using it to make emails, presentations, and documents better for the end users who will read them. We are an international company, and English is not the primary language for 99% of people. Copilot makes the documents more readable. We have not yet tested Copilot in Intune for security functions. We have SIEM and other security tools for insights. At the moment, we do not have a big need to start experimenting with Copilot in Intune. After we finish with the end-user use cases, we can switch focus on daily operations for IT teams.

Intune has not helped us consolidate vendors because we do the installation on the cloud. On endpoints, we have nothing.

I would rate Intune a seven out of ten because it is not so flexible.

Public Cloud

I primarily use Microsoft Intune for device monitoring, security, and cybersecurity. My role involves working with devices, monitoring, and enforcing security measures using Microsoft Defender, and synchronizing different security aspects. Microsoft Intune is utilized for tracking device locations, which is crucial for understanding where users are connecting from.

The most valuable features in Microsoft Intune for me are the security features, including Microsoft Defender. I use the device location tracking feature often to determine where users are connecting from. It is greatly beneficial to be able to look for devices, enroll them into groups, and apply management policies. The advanced endpoint analytics feature is effective in detecting potential threats and anomalies, allowing me to share graphical information for better communication and understanding. These capabilities have made a significant impact in my work, providing a comprehensive view of all devices and features in a single platform.

The user interface should be more user-friendly, as it can sometimes be challenging to navigate. Microsoft often relocates features, making it difficult to consistently find what I need. Stability could also be improved, as features tend to move, requiring additional effort to locate them again.

I've been using Microsoft Intune for six years.

I did not encounter any significant deployment issues. The process is straightforward and takes only a few hours.

Microsoft Intune is relatively stable, but I rate it a seven out of ten because features sometimes move, creating additional challenges.

Microsoft Intune is quite scalable, and I rate the scalability aspect eight to nine out of ten, with no major problems encountered.

Customer service and technical support are generally good, with an eight out of ten rating. Occasionally, it takes a while to receive responses from Microsoft, which could be improved.

Positive

I used VMware's cloud solution before Microsoft Intune, but it lacked many features. It was not user-friendly and prone to mistakes, leading me to switch.

The initial setup was easy, earning a nine out of ten for ease.

We occasionally partnered with integrators from countries like Latvia for implementation.

Using Microsoft Intune helps save on management and security costs.

Microsoft Intune is not particularly expensive, especially considering the security features. It costs approximately forty euros per user per month.

I previously evaluated VMware.

I recommend Microsoft Intune because it consolidates many features into one place, making it an efficient solution. I rate the overall solution ten out of ten.

Hybrid Cloud

Other