Microsoft Intune Reviews

My main use case for Microsoft Intune is device management and policy enforcement and securing remote corporate endpoints across Windows and mobile devices.

I use Microsoft Intune daily to push security policies, deploy apps remotely, and manage employee laptops without needing physical access.

The biggest advantage for us has been centralized management, especially with hybrid and remote teams where manual device handling isn't practical anymore.

The best features Microsoft Intune offers include centralized device management, seamless Microsoft 365 integration, remote app deployment, and strong compliance policy controls.

I rely the most on the policy and compliance management because it lets us secure and standardize devices across the organization with minimal manual effort.

The automation capabilities of Microsoft Intune have also saved a lot of admin time, especially for device provisioning and routine policy updates.

Microsoft Intune has positively impacted our organization by improving our security posture and making device management much more efficient, especially for remote users and distributed teams.

Microsoft Intune could improve its reporting and troubleshooting tools since diagnosing policy sync and deployment issues can still feel a bit complicated at times.

Better customization, reporting dashboards, and more detailed error messages would make administration and troubleshooting much easier for IT teams.

I have been working in my current field for one year.

Overall Microsoft Intune has been stable in my experience for day-to-day endpoint management, although occasional sync delays and policy deployment inconsistencies do happen in large environments.

Microsoft Intune scales really in my experience, especially for managing large numbers of remote and hybrid devices across multiple locations, although performance can slow down a bit with large policy deployments.

Customer support for Microsoft Intune has been decent overall, but response times and issue resolution can vary depending on the complexity of the problem and support tier.

I previously used traditional on-premises endpoint management tools but switched to Microsoft Intune for better cloud-based management, remote support capabilities, and tighter Microsoft 365 integration.

I have reduced device setup time from a few hours to under 30 minutes and significantly cut down the number of manual support tickets related to compliance and software deployment.

I saw ROI fairly quickly through reduced manual device management work, faster onboarding, and fewer support tickets, which saved my IT team several hours each week.

The licensing can feel a bit expensive initially, but since Microsoft Intune is bundled well with Microsoft 365 plans, the overall value has been reasonable for the features I use.

I am only a customer and do not have any partner or reseller relationship with Microsoft.

I also evaluated VMware Workspace ONE and Jamf Pro before choosing Microsoft Intune, mainly because it fit better with my Microsoft ecosystem.

If you are already invested in the Microsoft ecosystem, Microsoft Intune is definitely worth considering, but plan your policies and device groups carefully early on to avoid management complexity later. Microsoft Intune has been a solid platform for modern endpoint management, especially for organizations supporting remote or hybrid work environments. I would rate this product an 8 out of 10.

I use Microsoft Intune for all kinds of operating systems, including Mac, Windows, and Android. For these operating systems, I use compliance policies and deploy apps.

What I appreciate about Microsoft Intune is that it is easy for me to deploy software to an environment with 600 laptops. I can deploy the software and it installs directly on all 600 laptop devices. This is why I use Microsoft Intune, and I also use many Conditional Access policies. With these Conditional Access policies, I can determine if a device is compliant or not.

The portal of Microsoft Intune is slow for me, but otherwise I think it is an acceptable product.

What I would like to see improved in Microsoft Intune is that the portal runs slowly for me. If I have deployed software, I can only see it after 20 minutes, so the reporting is quite slow. Additionally, some of the portals take a considerable amount of time to load. For example, it is difficult to see the assignment overview because I have different configuration profiles and different policies, and I cannot see directly to which groups the profile is assigned. I have to click open manually and then I can see it is assigned to this group, but I cannot have a wide overview of policies that are assigned to the group.

I have been working with Microsoft Intune for about three to four years.

I have not experienced any downtime or performance issues with Microsoft Intune. There is no downtime.

Microsoft Intune is effective for small organizations and also great for large organizations, so it scales well.

We have not expanded our usage.

My experience with the customer service and technical support teams of Microsoft depends on the situation. Sometimes the service is good, and sometimes it is really bad.

Prior to adopting Microsoft Intune, I was not using another solution to address similar needs. We started directly with Microsoft Intune. I used Microsoft Deployment Toolkit before that, and before that all work was done manually. Then we transitioned to Microsoft Intune.

Regarding my experience with the deployment aspect of Microsoft Intune, I find it quite easy. I use Autopilot to deploy the devices. In the beginning, I had many issues with it, but now it seems much more stable, so I do not encounter issues with deploying new devices to Microsoft Intune.

I work with the Autopilot V1 model, not the V2 version, for Microsoft Intune.

I did not consider any other options or solutions available in the market before selecting Microsoft Intune. I chose it because it was included in the licensing. I tried Jamf before for macOS, but now it is also included in Microsoft Intune, so I only use Microsoft Intune.

I do not use Microsoft Intune Suite's Cloud PKI yet.

I am using Copilot for Microsoft 365, but not Copilot Studio or Copilot for Microsoft Intune.

Given my extensive experience with Microsoft Intune, my advice for other organizations considering it is to use the new filters in Microsoft Intune. Instead of dynamic groups, it is better to use these filters because they are faster. I would rate this product 9 out of 10.

I mostly use Microsoft Intune for device management and application deployment.

From my perspective, I appreciate the scalability in Microsoft Intune and the portal management, which is extremely intuitive and very simple to use.

Regarding the user experience of Microsoft Intune, I do not have any negative feedback. Users take the solution very well.

If you ask me about improvements, I would like to see some additional features in Microsoft Intune in the future.

Nothing is perfect, so there is room for improvement in every product. I would like to see more customization in Microsoft Intune or some features such as more connectors.

Apart from the full management agreement, I do not think there are any other aspects that can be improved in Microsoft Intune.

I have been using Microsoft Intune for about two years.

I assess the stability and reliability of Microsoft Intune positively.

Regarding the scalability part, Microsoft Intune is very scalable.

The process of scaling up and scaling out was smooth and easy.

I have some knowledge about the customer service and technical support teams.

Regarding my experience apart from Microsoft Intune, I have worked with other mobility management solutions, but I did not consider any other options in the market before selecting Microsoft Intune.

The experience with the deployment of Microsoft Intune is very easy for me because I have worked with Microsoft solutions for five years. The portal management is very intuitive and not difficult.

I use only Microsoft Intune and do not use Copilot at the moment.

I purchased Microsoft Intune through a local partner.

Enterprise Application Management has changed my abilities significantly when it comes to app discovery, deployment, and automatic updating.

I do not know much about the pricing, setup cost, or licensing part of Microsoft Intune. I am using the Enterprise Application Management features of Microsoft Intune.

I would advise organizations considering Microsoft Intune to ensure they understand their needs. Other companies should consider their specific requirements before choosing Microsoft Intune.

I have one remark about the application management for the Android version. Often, the Play Store opens and leaves the possibility to download to the user, which is not good. It is not the policy to create inside the configuration, and there is a problem with synchronization often for the Android version.

I gave this review a rating of 9.

From my previous experience and my current experience, I deploy Microsoft Intune for all the devices in the company. In my current company, Copilot is being used by all the users to do their work. I can also use automation tasks for Microsoft Intune. I combine the use of Microsoft Intune with Microsoft Purview, Sentinel, and Defender to maximize cybersecurity protection.

For the PKI, most of the products are now using the cloud. My daily task is managing and monitoring things on the Microsoft web page. We have not fully stopped using Sophos because some other office licenses will expire at the end of this year.

The most valuable features for Microsoft Intune are direct control over devices. I can set the policy for USB and data transferring for all company devices. This makes device management easier. It is user-friendly because most companies use Microsoft products, making the interface and features quite good, although the price is higher than other products.

It is much easier to deploy software updates and Windows updates globally because of the cloud base. Thus, I can manage from anywhere, making it quite convenient for me.

The areas that Microsoft Intune can upgrade include BYOD devices. I am currently facing issues with BYOD devices, receiving many alerts about software updates and corrupt files, although I have already whitelisted them. Microsoft Intune should update or upgrade their interface or system to reduce false positive alarms.

I have been working with Microsoft Intune for three to four years.

Initially, almost every day I would chat with technical support for the initial deployment to find solutions for problems, such as false positive alarms.

I give Microsoft Intune a seventy percent rating for scalability because it is much easier for me to manage the 500 or more devices in the company, deploying updates for software and Windows.

Almost every day during the initial deployment, I would chat with technical support for solutions.

They did not give me a suitable solution to solve the false positive alarms.

Negative

I used Sophos previously. We are still using both Sophos and Microsoft Intune since some other office licenses will expire at the end of this year. There are pros and cons between Sophos and Microsoft Intune, but my company chose Microsoft Intune because many users are familiar with Microsoft products.

The initial setup for Microsoft Intune is not so complicated, but the hardest part is creating and assigning policies and rules. We kept receiving false positive alarms during the deployment, requiring adjustments to create new rules for Microsoft Intune.

Both an internal team and vendor are involved because my company has offices in several other countries such as Cyprus, Jordan, and Dubai.

We considered using Microsoft Azure but chose AWS instead because of the price difference.

I already mentioned using Microsoft Purview, Entra ID, Sentinel, and Defender for maximizing cybersecurity with Microsoft Intune. My overall review rating for Microsoft Intune is seven out of ten.

We do use Microsoft Intune internally in our company. We handle the distribution software, collect metrics for app usage, and create policies to make the device compliant for Microsoft Intune.

The features that we use very frequently include collecting information about the software installed and determining which software is allowed from our company or not. This is our main feature for now.

We have different departments in our company, and the configuration and distribution of Copilot is another team's responsibility. We use it, but we do not have any part of that process.

We handle the distribution software, collect metrics for app usage, and create policies to make the device compliant for Microsoft Intune.

The features that we use very frequently include collecting information about the software installed and determining which software is allowed from our company or not. This is our main feature for now.

The interface is easy, but it is not user-friendly when evaluating the overall user experience of Microsoft Intune.

The settings are confusing, and it is not always clear where I apply the configuration because we have to open various pages to see where we are applying the settings that we have configured.

We are using Microsoft Intune for about two years.

Microsoft Intune is acceptable and adapts well. I give it an eight regarding scalability.

The technical support of Microsoft Intune rates as an eight when rated from one to ten, where ten would be the best support.

We have addressed other questions and other possible customization, and it is satisfactory because our company also has support from Microsoft directly in our company. This makes it easy for us to ask questions and request features that can be useful in our company.

Positive

Before choosing Microsoft Intune, we did not evaluate other options other than BigFix.

The initial setup and deployment of Microsoft Intune is easy to participate in.

We actually used service technicians from Microsoft to deploy Microsoft Intune. We hired Microsoft technicians to do that.

The technical team from Microsoft are good technicians, and we can see that they are comfortable with the process.

Before choosing Microsoft Intune, we did not evaluate other options other than BigFix.

I am involved in solutions, and we have Microsoft Intune and BigFix in our company.

We are administrators and end users of this solution. However, it is not the priority application because our priority is BigFix.

We are separated into different areas in Microsoft Intune. We have many solutions in Microsoft Intune, but for now, we are only creating policies, managing devices, and installing software because other teams handle other configurations.

We are using Microsoft Copilot in Microsoft Intune. I cannot make any comments about whether Copilot in Microsoft Intune helped protect our environment because Copilot is another department's responsibility.

We had the BigFix platform before Microsoft Intune. We chose Microsoft Intune in the first place because most of our components and services are moving to Microsoft. Microsoft Intune is adding to all the services that we now have from Microsoft.

My overall review rating for Microsoft Intune is eight.

I use the solution across my full enterprise. That means for me roughly 4,000 devices, with 2,000 being desktops, 2,000 being laptops, and then maybe another 2,000 mobile devices.

The most valuable feature I have found is the access control. It integrates with Endpoint Manager. The reason for that is that it has allowed me to customize my organization's policies.

The security posture is very good. It's very customizable. 

Overall, my user experience with Microsoft Intune has been great. It's offered a very smooth transition and I'm very positive on the product.

I am just starting with Microsoft Security Copilot. My experience with Copilot, and Microsoft Intune Copilot in general, has been incredibly positive as it's a skill multiplier for daily operations.

It's an absolutely critical application that I use every day. 

Intune helps with app discovery. It's a game changer as it provides so much overall visibility.

I have analytics available. It's a wonderful tool, and I love the amount of data it's able to extract. 

Intune is reducing our attack surface and improving our security posture.

Microsoft Intune has potential for improvement; I would like to see a lot more customization in the reporting tools.

I have been using the solution for four years.

My assessment of stability and reliability is that the uptime is fantastic, and I haven't had any issues.

Compared to my previous solution, it's incredibly easy, and it's scaled to the entire organization. Within a month, I had gone from zero to full deployment.

My experience with customer support or technical support is that they have been nothing but excellent.

Positive

Previously, I was using IBM to address the same issues. I made the switch since it was both more cost-efficient and Microsoft is best in breed.

The deployment was incredibly easy, and it's scaled to the entire organization; within a month, I had gone from zero to full deployment.

Intune has been helping us reduce the cost of devices per user and offers trusted effectiveness for maintaining the accuracy of those devices.

I don't have specific ROI data points. 

The licensing has been fantastic and the support we've received from Microsoft has been impressive.

I wasn't involved in the RFP process. 

I do not use PKI yet; it is on our task list, and it's on the list to get done, but it hasn't been completed. The reason it's on the list to get done is that I want everything in the same platform, just so everything integrates and supports each other.

My assessment of endpoint analytics is that it's a wonderful tool, and I love the amount of data it's able to extract; I can provide examples of how these features work.

On a scale of one to ten, I rate Microsoft Intune a ten.

Currently, we use Intune for endpoint security and deployments. We're migrating from SCCM to Intune cloud-first technology. We use it to deploy applications, CSPs, and conditional access.

Previously, we used on-prem SCCM to deploy applications we built manually. After migrating to Intune, we automated and streamlined the process of deploying applications with Autopilot. I can do more with my day. I can manage more applications and ensure that they're updated without monitoring and manually starting that process all over again.

My director used to say that we need to have cattle, not pets. You need to care for and manage pets, but you only need to feed cattle and put them out to pasture. Once you deploy it, you just let them out to pasture, and they update themselves. It's streamlined and so easy.

I've been exploring the Intune Suite, which includes Security Copilot and enterprise application management. EAM is a godsend. I can manage my third-party applications without having to worry about it. I

I set up a proof of concept for the advanced analytics. It was very streamlined. I like the information I got from it. For example, when we were troubleshooting an application, it told me possible scenarios and commonalities between group one and group two and what could be the issue. It is great in that aspect, but we decided ultimately we didn't want to go with it.

We're still learning how Copilot fits into our environment and setting up a POC for Security Copilot. We're trialing Copilot for a subset of users to get a baseline of how we're gonna be using it. I use it to manage my day, meetings, teams, and chats. It keeps me organized.

There are challenges with Intune, specifically in reporting. Many third-party companies offer single-pane-of-glass reporting that shows you what your update environment looks like, how your patch is doing, application status, etc., but Intune's reporting is not intuitive. You can connect to Azure, monitoring, and the workbooks, but it's not streamlined. 

The user experience is still a little difficult. In the first version of Intune, everything is all over the place. It wasn't organized, and things weren't categorized. They changed the name in six months, and we had to relearn everything. 

I have used Microsoft solutions for about 15 years.

I am very impressed with the stability of Microsoft Intune. There hasn't been an instance where things just weren't working. While there may be service alerts or outages, it doesn't significantly impact our operations.

I rate Microsoft support five out of 10. Customer service is inconsistent. Sometimes, the support provided is excellent, and the representative is knowledgeable, while other times, the service needs improvement.

Neutral

We looked at Tanium and Recast for servers and management but ultimately chose to stay with Intune.

The initial setup was made easier with online resources. After setting up some basic components and connections, everything was interconnected seamlessly.

We used a consultant for further development after it was configured. CDW was used to help refine the setup.

There is a return on investment, particularly with the Enterprise Application Management and the efficient deployment features of Intune. It has given me more time in my workday.

Experience with pricing and licensing was challenging. Understanding Microsoft's licensing costs can require certification, making it difficult to know exactly what is needed versus what is available.

I would rate Intune seven out of 10. As much as I sing Intune's praises, I would like more improvements, especially in the reporting. We need to standardize how we use the solution. For example, just in October, we had the update rings completely fleshed out. Then, I went on vacation, and when I came back in October, it had completely changed with new names and new scenes. There are lots of strategic hoops to jump through, but it's a solid solution.

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.

Positive

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.

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

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

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

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

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

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

I have been using Microsoft Intune for five years.

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

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

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

Neutral

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

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

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

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

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

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

I would rate Microsoft Intune an eight out of ten.

My main use case for Microsoft Intune is 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.