Microsoft Intune Reviews

We are using Microsoft Intune for the management of desktops and laptops because we have a business where we don't have all users in the office. Many of them work from home from different countries. Management of the devices was almost impossible with the tools that we were using before, such as ServiceDesk. We are using Office 365, and we are Microsoft users in a Microsoft environment. After that, we decided to grow with Microsoft Intune. Initially, it was planned to better manage the devices and serve as a deployment tool.

Microsoft Intune has definitely affected IT productivity in our company. We shortened the time for issuing new PCs and changing PCs. It enforced our security and deployment of the Gold Build. We were waiting for that; it shortened that time significantly, and we got our security certifications regarding that very fast after we bought it. Junior technicians and help desk staff had much less time to spend on the deployment of the PCs.

We are using the endpoint privilege management feature and find it very useful and good.

The thing I appreciate most about Microsoft Intune is that the management of the devices was very simplified. We have all machines connected to it at all times, whether they are in the office or working from home. The greatest thing is that we create unique deployments for security, which we call the Gold Build Windows 11, and the deployment of that operating system with all the security settings that we set up for our business is very easy; it is much simplified compared to before. We created everything that we needed on Microsoft Intune, and all you need to do is just set up a new PC or an existing one, put it on the network, and let Microsoft Intune do everything else in order to have a completely full machine with everything you need from one place. Everything that you need to change, when we decide to change something, is in one place and will be deployed immediately.

Reporting can be better. Only global administrators can see detailed reports at the moment, and I don't want to use the global admin. We have only two global administrators in the USA and Europe, and it should be available for the global reader role because currently, when I need to do some reporting, I have to send a request for the global admin report.

We didn't have any complaints in terms of user experience, from administrators or from users. The only problem for us was that we had different access levels for the administrators, and that was very hard to accomplish. That was the one part that we were keen on and contacted support. It's not so granular. That was the problem.

One thing that I don't appreciate in deployment is that it needs to be put in the group of the machines over the security group; you cannot put it into only one PC.

I started using Microsoft Intune in my last company, and I have been using it for almost two years.

We didn't have any issues regarding stability.

Microsoft Intune is very scalable.

It's a great suite for big companies that have over 3,000 users and many devices to manage. It's great from the management point of the devices, and also users; it's collaborative with Office 365, and the pricing is for companies that have more than 3,000 users.

We contacted them when we had the issue with the serial numbers of the machines. Microsoft support was not very responsive, and it took approximately one and a half months to get on a call to clear what the problem was. Every time they changed technicians, we had to explain the problem again. We were explaining for one and a half months without getting help. We ultimately resolved the problem ourselves. They are not responsive and not intuitive in giving solutions.

We used Service Desk Plus previously. At the moment, we are using other management tools, but very soon, we will go for Microsoft One. Between Service Desk Plus and Microsoft Intune, I prefer Microsoft Intune because of its pricing and features.

In terms of app discovery, deployment, and automatic updating, it's great; although sometimes, it's very hard to find the deployment version of the applications for Microsoft Intune because some software companies do not create them. For example, we find it much simpler in other software, such as Datto. We use Datto for remote access and deployment of some specific applications, but for most applications, we use Microsoft Intune. 

The initial deployment was not difficult for me. The project took one month to deploy.

We saw the benefits of Microsoft Intune after some time. We had some issues, and we contacted support at Microsoft. We used a lot of non-brand machines, and that was the issue. We couldn't enroll them in Microsoft Intune because they didn't have serial numbers, and unfortunately, Microsoft couldn't help us on that. We solved the issue by ourselves by writing down in the BIOS our internal number with a script, and that was the solution. After we crossed that bridge, it was much better.

We had a very small team; three engineers were doing the implementation.

The overall pricing of Microsoft Intune is good for companies that have big IT budgets, 3,000 or more users and devices.

We started using Copilot, but we stopped the usage of AI at the moment in our domain. We want to make it more granular in terms of who can use it. Our end users cannot use it. It was a request from our clients to set that up at this point, and we have an IT department in the company that will make improvements. We took Copilot professional licenses, and it's very good.

It is important for us that the capabilities of the Intune Suite are integrated with Microsoft 365 and Microsoft Security for both cloud and co-managed devices. We are still in hybrid mode, but within Intune, Office 365, and Azure, we will soon be in the cloud, totally independent of anything on the ground.

I would rate Microsoft Intune an eight out of ten.

We primarily use Microsoft Intune for managing laptops, cell phones, and mobile devices. We aim to have control over corporate data when it is on personal or company-owned devices. This control is crucial for ensuring data protection, especially when a device is lost or goes missing.

Microsoft Intune helps us avoid issuing everyone company-owned devices. We provide a stipend, allowing users to bring their own devices. This approach gives us leverage against other MSPs. It also enhances collaboration because clients already covered by specific licensing can optimize their usage of Microsoft Intune.

Intune's integration with Microsoft 365 is exceptional. It allows a cohesive management experience for users, especially for a small MSP like ours. The automated deployment and configuration using Autopilot and the ability to secure data on lost devices are particularly helpful features.

The solution's user experience is so simple I can give a two-page PDF on how to enroll a cell phone or device, and they can follow it. Automatic enrollments help us migrate large numbers of users.  We take it slowly with them, but they are surprised at how easy it is to enroll a device.

We're still preparing to turn on Copilot in our environment for testing, but we need to sort our security more. We're doing a demo of Copilot, and we're checking out the features. We use another tool to pull the device data, but having everything in a single pane of glass makes more sense. We have to pull this information from four windows now, so having everything in one place is simpler.  

Training will be much easier for us than training someone on 20 different. Giving someone a few videos and having them start going through it will be more straightforward. I'm excited to see the growth of Copilot with Intune.

I would like Intune to natively support easier report generation. This improvement would enable less experienced staff to run reports more efficiently without relying on additional tools or functions.

We have been using Microsoft Intune for at least six years.

Microsoft Intune is reliable. Devices do not frequently go offline, and any connectivity issues usually stem from the user's side, such as a device being turned off.

Microsoft Intune allows us to scale device management efficiently. The system is easy for both technical and non-technical users to navigate, supporting a wide range of devices without complications.

I rate Microsoft customer service six out of 10. While some technicians go above and beyond, there is inconsistency, and connecting with the most helpful representatives is occasionally challenging.

Neutral

We initially used AirWatch for mobile device management before Intune matured. Eventually, Intune’s integration with Microsoft 365 became advantageous, allowing us to consolidate systems and migrate clients using alternative solutions back to Intune.

The setup, especially for mobile devices, has become entirely automated. Devices sync with accounts like Apple Business Manager or Samsung Knox, eliminating the need for hands-on configuration. From there, you can deploy everything by device or user login. 

Before, we used to bring them into our office. We would configure it and ship it out. We now pushed that back to the client and someone in charge of cell phone policy. Once they're powered on and signed in, everything else is taken care of.

We consulted Pax8, our partner, during the implementation for insights on licensing and Intune integration. Their support, coupled with information from Microsoft Ignite, helped address hybrid enrollment challenges.

We've seen a positive return on investment. The ease of use, along with automated features, proved beneficial when handling lost devices. A client successfully restored their wiped iPad and laptop, showcasing the system's efficiency.

Our company uses a flat rate model called stress-free IT. This model aligns with the necessary licensing, making it easy to cover features like Intune and conditional access, which are integral to our service offering.

We evaluated AirWatch (VMware AirWatch) and other mobile device management solutions before consolidating our clients under Intune due to its superior integration with Microsoft 365.

I rate Microsoft Intune nine out of 10. 

The primary use case is endpoint management.

The organization I'm with now is pushing towards cloud management. They want to move away from on-prem and hybrid to pure cloud.

We use some security management through Intune, but we have another product for that.

We were using a different product to manage machines. I had a lot of different organizations I was managing. I started seeing the benefits of machine level or the cloud management through Intune as we started pushing it to clients that were using the proper licensing, like 365 Premium. The management aspects of that were fantastic compared to what they had or didn't have at that point. So it was a pretty immediate benefit in using Intune.

The biggest asset is the range of device management options available with Intune, whether it is a Windows device, a Linux device, a Mac device, or mobile devices. There are numerous options available. Within Windows devices, the depth of management is very nice.

I grab the logs through the events in Intune. We do some of the security through there, but we're evaluating whether to migrate wholly into the Microsoft ecosystem for security or keep it separate.

We do manage some applications through Intune. I think they make that very simplistic and easy to maintain.

I only have under 400 endpoints that I'm managing right now with this organization. The reporting aspect of it has been very nice because I've been able to keep an eye on devices that may or may not be functioning properly. I need to explore some of that automation deeper.

We use Cloud PKI extensively for deploying certificates.

There are a lot of great functions that have been implemented, especially conditional access and zero trust. Intune really does nail that quite well.

We're more productive with Intune. The management of devices makes it a lot easier, and it's faster to deploy devices with Autopilot.

Intune helped us to consolidate vendors, which is helping reduce attack surface.

The reporting dashboard is really limited. You have to use something like Power BI and Graph to get better reporting. I wish they would implement new dashboards and widgets for the dashboard in Intune. The report updating period is very slow, taking upwards of over an hour to confirm if a policy is deployed after check-in.

The user experience is good. There are a few things that I wish could be tweaked. Whereas with other management systems like Jamf and JumpCloud, you can set the check-in interval times so you can push policy faster. We don't have that option with Intune, so I think that's the biggest failing so far. It can take a while for policies to push out to users.

I have been using Intune for about three years now.

Very rarely have I seen it crash, maybe twice. However, if Intune is not available, the 365 environment might not be available, causing a major ordeal.

Customer service used to be better. In the last couple of years, support has not been very good, even with Premier and Premium support. It's been very hit-or-miss. However, when you get a knowledgeable support engineer, they are very good and helpful.

Neutral

I've used Jamf, JumpCloud, Mosyle 360, and Automate. I switched when I started to see the benefits of machine-level or cloud management through Intune.

Intune from zero has a learning curve, however, it's not overly difficult. It's important to have a basic understanding of what you're doing.

I've set up environments by myself. It's better to have a small team to verify policies and come up with solutions.

I know what's included in 365 Premium offering, and it's a good deal. On an enterprise level, they break out features I'd really want, which complicates access. It is a good value, especially for smaller organizations.

I've used Jamf, JumpCloud, Mosyle 360, and Automate in the past.

Make sure you have a test environment or test devices. Don't push a policy out to all devices unless you absolutely understand what it's going to do.

My advice to someone considering Intune is that if they're already using 365 products, then this is a great system to lean on and to deploy to your organization. If you're in another organization's ecosystem, like Google or Amazon, then I may not necessarily think it would be the best option.

We use it for Android device management. We also work with Autopilot configuration and application deployment. We use Microsoft Intune for WiFi profile deployment and zero-touch migration from Windows 10 to Windows 11.

I used Microsoft Copilot with an Excel file containing more than 2,000 workstations with many models. For just the Lenovo manufacturer, we have 20 models. I uploaded this file to Copilot so it could indicate if a model and workstation were compatible with Windows 11 or Windows 10. We deploy many applications with the enterprise. In Tunisia, we have laws that prevent uploading documents or sensitive data to Microsoft Copilot, which creates restrictions on its use. 

The most valuable feature is that we can manage workstations or Android devices remotely without needing the device to be connected to our local network. This means even if users are on vacation or working from home, we can control it and deploy applications, deploy all features with Microsoft Intune.

The enterprise application deployment is another key feature. We have deployed many applications. Our last project was with our minister of education where there were more than 20,000 new devices that we needed to manage for education. We have many applications that students work with on a daily basis, so we use the enterprise application for deployment of all those packages and software. It helps save manual work.

Microsoft Intune is not as fast and extensive as traditional solutions such as SCCM and others. In SCCM, which is another Microsoft product, there are many logs that we can detect and monitor the deployment of the image, software, and inventory. In Microsoft Intune, there is significant slowness, and there needs to be more logs when we deploy software, parameters, or scripts to troubleshoot problems and errors in the interface, workstations, and Android devices.

Another feature that needs improvement in Microsoft Intune is device preparation. Microsoft Intune is for management. We cannot prepare devices from scratch or bare metal.

They should optimize their licensing. They should include some features for free and the others for a price. Currently, everything comes at a cost.

Microsoft Intune also needs to improve its scenario documentation. While Microsoft articles cover basic scenarios for deployment, they don't address advanced scenarios such as massive deployment, retiring applications, or updating applications.

I have been working with this solution for more than one year.

The solution is stable without any problems with stability or availability. The portal is always ready for configuration when accessed. The only issue is the slowness previously mentioned. When deploying a strategy from Microsoft Intune, sometimes it takes one to two hours to show that the strategy is deployed on the device.

It's scalable. We just need to add more licenses.

There is inadequate support for Microsoft Intune, especially if the problem is on the device. When tickets are opened regarding device problems rather than portal or configuration issues, the support becomes slower and takes considerable time for troubleshooting. They seem to give less importance to device-related problems compared to portal or configuration issues.

Negative

It's a lot easier than the traditional solution where we had to prepare a virtual machine, SQL server, install an agent, etc. It's a SaaS. We can use it as a service. We only need to access the Intune portal, configure the base configuration with the name of the company, and configure the baseline. It's very simple. The only problem is that there is slowness and no place to find logs to identify where the problem is. It is hard to identify if it's in the workstation or the configuration that I made in Microsoft Intune. 

For the basic configuration, it takes approximately one to two days.

It's a part of Microsoft 365 and E5 licenses.

Microsoft's strategy of making every feature in Microsoft Intune paid needs optimization. Remote control is one of the basic features, not a luxury feature, yet we must pay for it. It should be free as users cannot use a solution to deploy configuration and applications without being able to assist users. Even for Android devices, remote control requires purchasing the remote help add-on.

I would rate Microsoft Intune a six out of ten. As a modern workplace consultant, I see everything moving forward to the cloud. However, many features in legacy solutions cannot be migrated suddenly to Microsoft Intune. It needs to be more reliable with better support for full cloud migration.

We use Intune to connect university staff and faculty to secure resources on their computers quickly.  

Intune is a force multiplier coming directly from Active Directory. We had to engineer over some limitations of Active Directory, and Intune resolves that by addressing known trouble areas. It allows us to do things quicker and more efficiently. 

We like Intune's Autopilot functionality, which enables one-touch deployment. Dynamic grouping is another feature we find valuable working in academia. We have people in buckets based on their roles in the university, such as faculty, staff, alum, or grad. Sometimes, they will fit into multiple places, and dynamic grouping helps with that. So far, using Intune has been easy and intuitive. Once everything is set up, our user base finds it much easier and more modern.

We've recently purchased Copilot licenses for Intune, but we've only had it for a week or two. It's a new deal for Syracuse, but it has been good so far. It moves quickly. You can see that it's constantly learning, and I love that. Today is the dumbest it will ever be. It's going to continue getting better and better. Even when we're wowed, we understand that more "wow" will come. 

It has some growing pains, but they are no different from anything new. We're implementing Intune on an individualized data set. So there's no way Copilot can know everything about every data set it's going to get, but it does grow pretty quickly, which is phenomenal. 

It would be awesome if Microsoft opened their API so we could filter more properties. If we have to do anything outside of Intune that requires a third-party solution to talk back to it, we're very limited in what we can do. Trust your people. We promise not to break your stuff. Open it up just a tiny bit wider.

We started using Microsoft Intune about a year and a half ago. We transitioned our fleet from Active Directory to Azure Active Directory. Then, we took that hybrid and shifted it into Intune for our MDM solution.

Intune is solidly reliable. Microsoft has some peaks and valleys that you need to get used to. Stability is essential when transitioning from on-prem to the cloud, where Microsoft manages your infrastructure. There have been a few drops in performance, but that's more growing pains from our rapid expression than an indicator of major problems.

Scalability is fantastic. 

I am a technician, so when I'm reaching out about problems I cannot solve myself, they tend not to be tier-one or tier-two problems. When I contacted Microsoft, they had the same expertise, if not more, which is phenomenal because I felt heard and my problem was solved. That is delightful because I have contacted support for other solutions. After trying several troubleshooting steps, I contacted them, and they asked me to restart something. I have gone beyond that point and tried to tell you where I am. 

Positive

We previously used Active Directory and spec ops for software deployment, with Active Directory handling computer and user management. Intune was a natural progression for MDM. For Mac users, we still use Jamf but plan to transition them to Intune as support for Apple products grows.

It is absolutely a positive investment. Everything we've gained from it makes my job easier day after day, and I see value in it as an engineer.

I am not involved in those discussions. We worked hard to acquire E5 licensing, and Microsoft collaborated well with the university to ensure everyone got what they needed.

We are a Dutch MSP delivering modern workplace solutions for all of our clients. We create tailor-made workspace environments for them.

It helps us to transform IT environments of our customers from on-premises to the cloud, focusing on both Azure and the modern workplace.

Windows Autopatch is the most valuable because it removes the burden of patch management. Intune's user experience is pretty smooth. The endpoint analytics works well if you know how to use it as a guess. Microsoft includes a little more added value by default. It's a great source of information. 

Intune should improve its software inventory to provide better metering of which software is used throughout the company. This is especially needed for reporting third-party software solutions.

I have been using Intune since 2017 or 2018.

Intune's stability is good and has improved a lot over the last year.

Scalability works well. It supports organizations with 200 endpoints and those with more than 15,000 endpoints.

I rate Microsoft support eight out of 10. Customer service is pretty good, partly because we have a contract with Microsoft. Transparency is good.

Positive

We used Active Directory group policies and ConfigMgr in the traditional way. However, most of our clients are already on Microsoft 365 Business Premium or the enterprise E3 or E5 stack, so it doesn't make much sense to use solutions from different vendors.

We are a reseller.

One of our clients migrated the model workplace based on Intune, achieving a 78 percent cost reduction, which is quite a lot. Even with the projects around it, they still gain cost benefits in the first year.

It's cost-effective because Intune is included in the E3 and E5 licenses. It's smart because it helps Microsoft sell the license.

I rate Microsoft Intune eight out of 10. There's always room for development.

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.