Microsoft Intune Reviews

My main use case for Microsoft Intune is endpoint protection and policy enforcement.

I use Microsoft Intune for endpoint protection by securing the endpoints, which are the most vulnerable devices and entry doors for any attacker. Securing the endpoint, particularly because users' mobile devices are taken home as well, helps us to mitigate the risk. Additionally, I check the compliance of every mobile device's endpoint that users take home, ensuring the data we hold is secure.

The best feature Microsoft Intune offers is the compliance check. It checks all your operating system, your antivirus, and all the posture checks it performs. If the device is compliant, then only it can get access; otherwise, it gets blocked. This is something I value the most.

Microsoft Intune has definitely improved our security policies posture.

I measure that improvement with the better compliance rate, as securing endpoints is the most important aspect in today's AI infrastructure. The compliance has been good and improved.

I think Microsoft Intune is the best product, and I do not find any improvements yet; it is good for me.

I have been using Microsoft Intune for around two years.

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

I choose ten because all my work and my requirements for this application have been fulfilled, and overall, it is a good product. From my perspective, ten is a perfect number.

Regarding Microsoft Intune's AI capabilities, I think it is a good product, and definitely, you should give a hands-on and proof of concept for this; it is good.

I believe the accuracy and reliability of Microsoft Intune's AI output is good; I have not used it much, but it is good.

If you are looking for endpoint protection and compliance, Microsoft Intune is definitely a go-to product. You should definitely give the hands-on or at least a proof of concept in your environment to check whether it stands on your requirement or not. It is a good product, and definitely, it should stand, but at least conduct a proof of concept. My overall rating for this product is ten out of ten.

My use case for Microsoft Intune is device management.

The best features in Microsoft Intune that I appreciate the most are the strong security, encryption, and operating system version.

Microsoft Intune can save a lot of time and resources. My estimate is that it saves approximately 50% of the time.

In Microsoft Intune, error messages are an area that has room for improvement.

Regarding error messages, I would like to see more detailed logs added. Additionally, the policy management was somewhat complex.

I have been using Microsoft Intune for about two months.

I would rate its stability as 8 over 10.

I would rate the scalability of Microsoft Intune as 9 over 10.

I would rate the technical support for Microsoft Intune as 8 over 10.

The deployment took some days. I did not have very large challenges implementing Microsoft Intune; they were small, and we resolved them shortly.

My thoughts on the pricing are that it is cost-efficient.

My advice for others looking to implement this product is to consider that Microsoft Intune is a scalable and cost-efficient solution. I would recommend it.

I primarily use Microsoft Intune for work, managing devices and user account management, mobile device configuration, policies, and general Microsoft Intune functionalities.

I use Microsoft Intune Suite's cloud PKI for certificate management.

My level of managing the PKI and helping with the complexity of certificate infrastructure is still at a beginner stage. I do not do a lot of that; I use it for work and have used it for the past few years, but I have not reached the stage where I have to deploy certificates, so I have not been able to use that feature yet.

I work with Microsoft Intune through 365; it is the cloud service.

I do not have the Advanced Endpoint Analytics feature enabled for myself with Microsoft Intune; I am currently on Microsoft Intune and do not see that feature.

The best features from Microsoft Intune are the ability to manage multiple devices and the ability to deploy multiple policies to devices across the system, which is a very impressive feature. Being able to manage other groups and tenants within the system are also impressive features in Microsoft Intune that I have learned.

I find Microsoft Intune very user-friendly.

Generally for the organization, Microsoft Intune has been a good investment for managing a lot of the company resources, saving a lot of money compared to using the on-premises version of the software.

I would say the interface and dashboard summarizing the devices' status and compliance could be improved. I think they could organize some of the dashboard information to be more compact and more insightful than the way it is right now.

What I think would make Microsoft Intune a 10, apart from the interface and dashboard I mentioned, is the other features within it.

I have been working with Microsoft Intune for three years.

Microsoft Intune is reliable; there has not been any downtime during my usage, so I think it is very reliable compared to what I actually use it for on a day-to-day basis.

It is easy to scale up Microsoft Intune when I need to expand the usage.

I have not used any different solution prior to adopting Microsoft Intune; I came on board about three years ago, learned the software, and since then, I have only used Microsoft Intune.

Microsoft Intune has Copilot integrated into it, but I do not use Copilot for any particular tasks.

There is no complexity in the deployment from Microsoft Intune.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Neutral

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

It's expensive.

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

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

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

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

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

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

Microsoft Intune is a comprehensive solution for mobile application management and mobile device management, securing various endpoints like Windows, Android, and Apple devices. It excels in managing BYOD scenarios, employing work profiles to segregate personal and company data, and ensuring device configuration and compliance with company policies.

Intune provides a centralized management solution, although its suitability depends on specific needs and comparisons with alternatives like Jamf, Kandji, or ManageEngine. Overall, Intune is a sufficient solution for general use cases requiring essential device management and data security.

The Intune Analytics section is quite useful, especially for Windows upgrades on remote devices. We frequently utilize it to assess compliance and gather analytics on upgradable devices, including TPM and Secure Boot support, and memory capacity. This allows us to identify devices that meet the requirements for Windows 11 and proceed with deployment accordingly. It's particularly valuable for managing Windows 10 to Windows 11 upgrade scenarios.

Copilot for Microsoft 365 is a valuable tool that I use daily for creating proposals, summarizing Teams meetings, and generating content in Word and PowerPoint. It's even helpful in Outlook on occasion. Additionally, both Bing Enterprise and the standard Copilot in Edge are particularly useful when integrated with Customer Data Protection. This integration allows Copilot to securely access company data, including emails, presentations, and documents, to provide relevant recommendations and answers to queries.

Intune secures Bring Your Own Devices through network access management and work profiles, separating personal and company data. Additionally, it utilizes Defender for Endpoint for device security and facilitates deployment. Features like cloud app security, Microsoft Purview, and data loss prevention further enhance security and compliance, depending on the Microsoft 365 package, protecting both devices and data.

Privilege Access Management sits mostly on Entra ID and is deployed through Intune.

The primary challenge lies in managing employee devices, particularly differentiating between personal and corporate devices. Personal devices often face pushback against deploying security measures, while corporate-owned devices can be managed more securely and effectively. For instance, if a corporate device is lost or stolen, Intune enables remote wiping to protect company data.

Intune has helped in integrating Windows Update for Business to ensure machines are compliant. It provides functionality for workflow management on devices and separating company data from personal data. It is also used for deploying security and compliance capabilities depending on the Office 365 package used.

I find Microsoft Intune valuable primarily for its Windows management capabilities, along with its Android Enterprise and Apple device management for mobile devices. The mobile application management features enable BYOD support and work profiles on personal phones, enhancing security and control. Additionally, Intune excels in configuration and compliance management for Windows 10, ensuring devices receive timely updates and adhere to organizational standards.

While Intune effectively handles basic functionalities such as device management, data separation, and updates, it may present challenges with update times and limited advanced features.

Intune is not the most user-friendly mobile device management platform available. Compared to Jamf, AirWatch, or VMware Workspace ONE, it is not as intuitive or easy to navigate. 

The primary challenge with Intune's enterprise application management feature is its focus on the Microsoft application stack. This limitation makes managing third-party applications difficult, as there is no centralized store or streamlined process for batch operations. Intune lacks the robust support for third-party applications.

Microsoft frequently changes its offerings, so features previously included in Intune might now require Intune Suite. For example, managing device certificates, once an Intune feature, now requires this separate package. Essentially, Microsoft releases new features but places them in Intune Suite, requiring an additional purchase for functionality we might expect in the standard Intune license. This ever-evolving strategy means staying current with Intune can become costly.

I have been using Microsoft Intune for almost five years.

Microsoft's product support can be inadequate, with slow response times and unsatisfactory resolutions impacting the overall user experience. This contrasts with Jamf's support, which is generally perceived as superior due to its responsiveness and effectiveness.

Neutral

Microsoft Intune's costliness stems from licensing fees and the overhead associated with its management, user experience, and device remediation. While its licensing costs are high, the platform's limitations in manageability and user experience customization further contribute to the overall expense. Unlike Jamf, which offers greater flexibility and remedial capabilities, Intune's intrusive, yes or no approach limits user customization and potentially increases support needs. Therefore, determining Intune's true cost of ownership is subjective and depends on how these factors are measured.

I have evaluated Jamf, Kandji, ManageEngine, and VMWare Workspace ONE.

I would rate Microsoft Intune a six out of ten. Its management is not user-friendly, and device additions can take up to 24 hours to synchronize, unlike Jamf, which updates within 15 minutes. This delay is problematic for immediate remediation actions, such as removing harmful content or addressing device exposure, where a 24-hour wait is unacceptable.

It is advisable to prepare for the complexities of Intune and consider Jamf for better support and manageability if working alone. If you plan to use Microsoft Intune, be prepared for manageability and potential delays in changes and support responses.

Our primary use case for Microsoft Intune is endpoint management across our enterprise, particularly for Windows and mobile endpoints.

Intune simplifies compliance. The ability to manage software updates and policies on endpoints has helped us meet contract requirements.

We like Intune's mobile device management features. When we migrated from another solution to Intune, onboarding our mobile devices was straightforward. Intune is pretty transparent for the end user. They have a customer portal, and I've never had complaints about it. 

The enterprise application management feature allows us to identify systems outside our standard security baseline and limit their access to company resources until they are updated and approved.

The interface is not as modern as some competitors in terms of single pane of glass visibility across the entire landscape. It has a very Azure vibe and may not be as graphically appealing as other products.

I have used Intune for around two years.

There are no complaints about the stability. It works one hundred percent of the time.

There are no concerns about scalability, especially coming from an on-premises solution. We no longer need additional hardware and infrastructure.

I rate Microsoft support eight out of 10. We haven't needed support much, but what we've gotten has been good. 

Positive

Previously, we used MobileIron for mobile devices, which is our primary use case for Intune. We switched to Intune mainly because it was included in our standard E5 license, providing cost savings and managing everything under a single pane of glass.

The initial setup was straightforward with minimal support required from Intune's side.

No external integrator, reseller, or consultant was used. All implementation was handled in-house.

We have seen a small return from the native integration with our Microsoft systems and Intune's reporting. 

With our standard E5 agreement with Microsoft, there have been no pricing concerns. Introductory professional services, like a fast-track service, were included with our E5 membership, and there have been no additional costs.

We evaluated Workspace ONE and Jamf for mobile management but stuck with Intune because it's included in our license.

I rate Microsoft Intune eight out of 10. It's a great solution, but there is room for it to become a more polished product.

The feature that we need occasionally but is really important is the ability to remotely wipe a device, control it, and perform similar functions. Being able to update devices is extremely important. Especially when people do not bring their devices in, we need to be able to reach out and update them over the internet.

Microsoft Intune does a great job of helping protect our environment. Particularly for mobile devices, it is great because our team is able to reach those devices and control the data that is on them.

I am not involved in the day-to-day with Intune, but we have gone with a different product for updating mobile device software. We do not integrate many of our mobile devices that are not Microsoft-based devices, such as Dell laptops, with Intune. We are using KACE from Quest to update our systems. We find that Intune is good with smaller mobile devices, the ones you put in your pocket. That is where I find Intune to be the best.

We had Microsoft Intune for a while, and we finally successfully deployed it.

Microsoft Intune scales effectively with growing needs.

We have not had to extend usage, but we are looking at Microsoft Intune for all kinds of new mobile devices that come out all the time. We will be expanding to cover those.

The support I get from Microsoft is very good. I have had a good experience with it. I would rate them a seven out of ten, which is pretty high in my book.

Neutral

Prior to adopting Microsoft Intune, we had KACE, but it could not handle mobile devices effectively. That is where Intune really shines.

I wasn't involved in the day-to-day deployment of it. I heard some pain points. The main thing is the learning curve.

It took time to implement. It was not the best product starting out of the gate. We were having difficulties getting our mobile devices integrated, but now we are doing much better. I was not in charge of the Intune deployment, but I am aware of some of the challenges they have been experiencing. It was really hard to integrate all the mobile devices. We integrated Surface devices properly, but our mobile workforce has many Apple iPhones, and those did not work quite as efficiently. We have got it all completed now. It is going smoothly.

Overall, the user experience with Microsoft Intune has a learning curve, but they are doing much better with it now. We had a really small help desk department, so they were stretched thin, but we have hired enough people now that we are able to get Intune deployed and working properly. We are in good shape.

We haven't moved a lot of our infrastructure to the cloud or Azure. We're still very much on-prem. We're a water district. We process water. A lot of our assets are physical, and they need to be secure. However, a lot of business applications are more Internet-connected. We have some cloud applications as software as a service.

We have seen a return on investment from Microsoft Intune. The main advantage is being able to manage the mobile devices at a good cost. Microsoft generally prices things pretty competitively, except for Azure, which is very expensive.

Microsoft Intune is pretty reasonable. We have difficulty with Azure, which is probably why we have not put many assets in Azure. Everything we put there is very expensive. Because we have so much on-premises equipment and assets, we put many items on-premises for that reason, and only if something absolutely has to live in the cloud, we put it there.

Before choosing Microsoft Intune, they did look at other options. I do not remember what was on the short list of what we were evaluating, but we have been using Intune for a while. Getting it deployed just took time.

I have played around a bit with Copilot for Microsoft Intune, but I use it more on O365. For Intune, I am not sure if we are using it. We do not use Advanced Endpoint Analytics as much because we have many other security tools. I find Microsoft to be good at the front end, especially for Exchange and similar applications. For inbound items, it is the first line of defense. We have many other layered defenses, with Microsoft being one of those layers.

I would recommend we stick with it. It has been great. I would rate Microsoft Intune a seven out of ten.

I am an IT consultant, and I mainly advise my customers on how to implement Microsoft 365 solutions like Microsoft Intune within small and large companies.

First of all, the integration with the rest of Microsoft's products is a major win. Secondly, it comes from a vendor for which we manage most of the operating systems, which is a big plus. 

As a software-as-a-service, it is updated monthly, meeting all the new functionality provided by the operating system vendors. If I don't have an endpoint management solution, I must go to each computer individually to harden systems, install software and data. 

Comparing this to having an endpoint management solution, the efficiency gain may be up to 80%.

The biggest challenge Microsoft has with its own product is supporting all the versions of its own product as well. A major challenge is making all the products work within device management solutions like Intune. It would be beneficial if Microsoft removed support for older products much earlier in the process. 

However, given that they have paying customers, it's not something they can easily do. Ideally, we would have a product capable of managing the latest versions of the operating systems without having to deal with outdated systems.

I have been using the product actively for about five to seven years.

Customer service is not really good. I would give it a six out of ten. The main issue is the time it takes to get someone involved who truly understands what the product does and what the real issue is. I do realize that my support requests are the more advanced ones. 

Neutral

Getting used to working with a product like Intune is easier if I'm already familiar with other Microsoft products, as many companies are. The adoption rate is quite fast. Other vendors provide good solutions as well. Ultimately, it depends on what I am accustomed to. If I have worked for 20 years with VMware technology, then adopting the VMware endpoint management solution might be easier than switching to Microsoft Intune.

It really saves time and resources. As mentioned earlier, I need not go to each machine to update it and install software when using a device management solution. The efficiency gain might be between 60% to 80% compared to other products. If compared to another product I am accustomed to, the results may vary.

As a consultant, I advise customers and help them implement it. In addition, I offer a service where customers purchase configuration updates from me on a subscription basis. I ensure the Intune environment and other products remain up-to-date. 

Microsoft is doing a good job in this area, and many customers who ask for my help already pay for the license. Cloud PKI has similar issues, where other vendors provided that functionality before. Customers who needed it previously adopted third-party solutions. 

Now, Cloud PKI has been available for a year, serving as a good alternative provided by Microsoft, although many customers continue to stick with solutions they had already adopted. 

My overall rating for this solution is eight out of ten.

We use Microsoft Intune for mobile device management, which includes both endpoint and mobile devices.

The feature I find most valuable in Microsoft Intune is being able to configure policies and push them directly to mobile phones.

Being able to remotely wipe mobile phones in case they are stolen or misplaced is very important for us.

We're hoping we'll be able to deploy patches quickly once fully deployed. 

It's a cloud solution and you can easily scale. 

Currently, I have not seen any areas I want to improve in Microsoft Intune. We haven't gone far into using it. We still rely mostly on SCCM. We are trying to transition mobile device management and endpoint management from SCCM to Microsoft Intune, so we are still in the process of doing that. I haven't actually explored all the functionality of Microsoft Intune. Probably when we do that, I will have more to say about it.

A feature I would want to see added in Microsoft Intune is the ability to manage other non-Microsoft devices.

I have been using Microsoft Intune for probably three years.

Microsoft Intune has been stable and reliable.

It is a cloud solution, and you can easily scale as your needs grow.

Whenever we have had challenges, we were able to get Microsoft support on time. Not all technicians are knowledgeable of the Microsoft solution, so they have to work on that as well. Some technicians are good and give you the best support you can get, but some of them are not there yet.

Neutral

It has always been Microsoft solutions prior to adopting Microsoft Intune.

Microsoft Intune is deployed on the Azure cloud. I wasn't part of the deployment as it was already in use when I came to the company. 

The question about return on investment with Microsoft Intune would probably be for the Solutions Manager, as they manage all the solutions and would understand if there has been a return on investment. I don't have any access to numbers around that. Once we're done fully migrating, I'll have a better sense of ROI in terms of time savings.

We're not using CoPilot and INtune. The Copilot we use currently is just for Office 365.

I am also not currently using Enterprise Application Management in Microsoft Intune.

Advanced endpoint analytics is tied to Defender for Endpoint.

Once we are done fully migrating to Microsoft Intune, I will compare that with what we currently do with SCCM. Currently, with our Microsoft Intune, it is limited in the sense that it focuses more on mobile device management and less on other endpoint management. Once we have fully transitioned into endpoint management, I can compare and see how it helps in terms of patch management and deployment.

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

Our current use cases for the solution involve consulting and implementing for many customers. Primarily, the majority of our customers are India-based, but we have a few customers in the US. We essentially help them with all their device management, end-to-end, including mobile device management.

We are mainly using CoPilot in Microsoft Intune for configuration and from a productivity point of view. Additionally, we want to standardize many of these processes so we do not have to reinvent the wheel when we go to different customers. This is the context in which we are using CoPilot to help us speed up in terms of reusable objects that we can generate and then deploy across customers.

It is an ideal solution for customers who are a Microsoft-shop. The ecosystem plays a big role, and there is support for a variety of devices. I do not see any problem because Microsoft Intune supports all sorts of devices and platforms, but if their ecosystem is much more Microsoft, it is even easier for us from a configuration and implementation point of view.

We are using the enterprise application management feature in Microsoft Intune. We support end-to-end, and we have customers ranging from small to mid-size and large enterprises. Depending on the customer's needs, it may change, but we do use it. Enterprise application management in Microsoft Intune primarily helps in terms of throughput and productivity.

We can cater to more customers with the limited capacity that we have. We do not have to hire many more engineers, especially with CoPilot and other tools. Also, standardizing some of these deployment options across customers helps us to scale easily.

The most valuable feature of Microsoft Intune is that it is more of a one-stop shop, providing an easier experience. The seamless experience and remote management for customers from our office with our engineers are the most convenient aspects. It increases productivity and helps us to scale and expand.

The user experience of Microsoft Intune is very good. For the last eight years, we have been using it effectively. It is probably one of the best experiences. I do not have any complaints or problems. My team quickly gets through it, and they understand it easily. Training becomes easier, especially when people move out and then get new people onboarded. It is a seamless experience.

So far, I have not heard any complaints because it is a pretty mature product. From my level of analysis, the feature I would prefer to see added to Microsoft Intune is extensive support. Anything that helps to diagnose the problem and solve it would be useful. Helping the engineers, especially with CoPilot, with ready or out-of-the-box solutions would make life a lot easier because that helps us reduce tickets and respond faster. They can support engineers to do their job better and in a much more proactive way. They can also suggest solutions so that we do not have to waste time. Being more proactive is essential.

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

Microsoft Intune is very stable. I have not experienced any downtime, crashes, or performance issues with Microsoft Intune at all.

Microsoft Intune scales with our growing needs. We are mostly catering to our customers, and scaling is never a problem. We have worked with customers with over 100,000 employees, so it performs exceptionally.

We support the entire M365 end-to-end, and Microsoft Intune is a part of that. We support all features and capabilities around Microsoft Intune. My team is technical. We give L1, L2, and L3 support, and we only escalate to L4, L5 when needed, which is a very limited situation. This happens only when new features and products are released, such as CoPilot, which we have not experienced before. Generally, my team is self-sufficient.

Positive

Its deployment is seamless. We have on-premises and cloud deployments. The cloud provider is Azure.

We have seen a return on investment. There are more revenue generation opportunities for us and productivity. Those are the two key aspects, along with customer satisfaction.

We have data points and metrics to calculate our return on investment, as we continuously track our internal stats, especially on the support side. We have to report back from the reports point of view, so we have many internal stats around it.

My experience with the pricing, setup costs, and licensing of Microsoft Intune has been good. As a partner, we always look for how we can generate more revenue from a consulting point of view, but I do not see any complaints from the customer side regarding pricing, so they are satisfied with it.

We have been using Microsoft Intune for a long time. We are a Microsoft partner, so we will stick with them.

I would rate Microsoft Intune an eight out of ten.