Microsoft Intune Reviews

My use case for Microsoft Intune is to secure data and manage apps on devices such as Windows, Macs, and Android mobiles, effectively managing both organizational devices.

The best features in Microsoft Intune include secure authentication, which I find very favorable, and the fact that we can remotely push applications. For instance, if a user needs any application installed on their device, they will raise a ticket, and we will push the application from Microsoft Intune, which will automatically appear on the device in 30 to 45 minutes, making it easy for users to download. The interface is user-friendly, allowing us to easily find options for apps and devices, and we can quickly locate user details and asset information.

Our company's relationship with Microsoft Intune is that HCL is using it to provide services, and we are from administration supporting the end users, equipped with admin rights and a certificate to do so, and we configure and push applications to their Windows devices.

The enterprise application management feature helps in app discovery, deployment, and automatic updating, as updates are automatically identified within the interface, allowing us easy access to application security groups.

I do use the Cloud PKI feature.

I use Copilot to easily identify corrections needed, for example, if we need to send an email, it will automatically correct it in a formal way, and it also helps provide instant troubleshooting assistance.

I use advanced endpoint analytics for managing secure data and controlling apps from the console.

Microsoft Intune helps to easily detect and remediate anomalies in endpoints; it is very straightforward to identify all issues through the interface.

There is room for improvement in Microsoft Intune's understanding and user experience as the interface is easy to navigate for deploying applications and finding user information, but I think there should be a reduction in dependency on on-premises infrastructure and focus on artificial intelligence and automation to improve further.

I have been using the solution since 2022, with my experience lasting until 2025 onwards.

I absolutely use Copilot.

I utilize the enterprise application management feature.

The deployment for Microsoft Intune is easy; everything can be understood easily, and we can deploy everything without challenges, making it user-friendly.

It only takes 30 to 45 minutes to deploy Microsoft Intune.

In my opinion, the pricing for Microsoft Intune is somewhat expensive, but I do believe it is a reasonable price.

I would compare Microsoft Intune very favorably, and I can confidently refer end users to use it.

My deployment model for Microsoft Intune is entirely cloud-based and is on Azure Cloud.

Mostly, we have nearly 2,000 end users using the solution.

The solution requires maintenance; we mostly deploy applications and drivers, and if there are any patches, we can also deploy them from Microsoft Intune.

I would rate this review a 10 out of 10.

I work with Microsoft Intune full-time as an integrator. I work on M365 portfolio applications, which are major use cases for Microsoft Intune. Microsoft Intune is for end device management where I handle Windows device management, AutoPilot enrollment, and policies and compliance management for the end devices.

Cloud-based device management is the best feature for me as it impacts my company the most; it is much easier than the previous Configuration Manager or SCCM. Administration and management can now be easily accomplished anywhere, anytime through the Microsoft Intune portal.

Two methods are available: I can accomplish all administration management through the portal, and the same thing can be accomplished using Microsoft Intune Management Shell, which is the command prompt and API.

Microsoft Intune brings all of my endpoint and security management tools into one place.

From a security standpoint, I can manage both BYOD devices and corporate devices; one will be Azure registered devices and another one is Entra ID joined devices. Joined devices will be the corporate devices where end-to-end complete security, compliance, and management is fully owned by the corporate. In the BYOD case, any device can be plugged in and registered to Microsoft Intune platform, which is compliant and compatible with corporate standards. Once that device is registered to Microsoft Intune, security, configuration, and compliance will be applied as per corporate requirements.

I am using Microsoft Intune Endpoint Privilege Management feature. This feature affects user productivity in the company because when a new user joins the company, the same device can be reused at a later time; I can wipe it or reset it, and the entire user profile and applications will be removed from the device so the same device can then be reused for new users.

I am using the advanced endpoint analytics in Microsoft Intune suite; it is another feature. Previously, logs and analytics were available from the local device perspective, but now everything from the end device is sent to the Microsoft Intune portal. Log Analytics and Endpoint Analytics workspaces can be configured to determine what datasets can be fetched by the portal. It is much easier depending on the requirement and need, and analytics requirements can be configured so everything is available in a central repository that can be easily monitored, viewed, and can also be integrated with Power BI for advanced reporting and data manipulation.

I work with Cloud PKI in Microsoft Intune. Many options are available, from the BIOS level to the operating system platform level; everything can be managed from the single, central portal which is Microsoft Intune. Many monitoring options and integration options are available to all the other M365 portfolio SaaS applications. Cloud PKI helps to manage the complexity of certificate infrastructure.

I have worked on UEFI and trust hierarchy based on end devices like laptops or desktops; I have a platform key certificate, PK certificate, and DB certificate. This is at the very core of any end devices and defines what applications can be installed or allowed to install on the end device, trusted by the PKI architecture, which is ideally a UEFI secure boot concept where only trusted applications can be installed onto the end device. Anything listed in the revoked DBX database, known malicious vulnerabilities, cannot be installed or will be blocked from getting installed on the devices.

I am using CoPilot in Microsoft Intune; it can be enabled or is available for the Microsoft Intune portal and all of the M365 application space. I can input my questions and CoPilot provides the best possible answers or methods on how the target can be achieved. I extensively use it for PowerPoint presentations; I provide some very basic inputs and CoPilot gives me a well-structured presentation in different formats. CoPilot is available in Microsoft Intune side, Word, Access, Excel, and everywhere CoPilot is enabled; it is next-generation AI that Microsoft is bringing. CoPilot helps to protect my environment by simplifying my IT and security operations. CoPilot helps with this simplification by identifying the content of the document, such as whether it is internal or confidential, whether it can be shared or if it is a restricted document.

Automations in Microsoft Intune can be more elaborated; KQL (Kusto Query Language) is available, but if multiple automation options were readily available, which would include PowerShell, KQL, JSON, and different interpreters like VS Code or Python readily available from Microsoft Intune, it would help administration and management much better.

I have been dealing with Microsoft Intune for almost four or five years.

Microsoft Intune is stable because since it is part of the Microsoft product suite, it provides 99.9999 SLA downtime.

I rate customer support from Microsoft as outstanding because anytime I can raise my concerns directly through the portal and I get a quick response from Microsoft.

Positive

Before Microsoft Intune, I was using something called Configuration Manager, which is an on-premise solution. Configuration Manager is again Microsoft, the Microsoft Configuration Manager, which is an on-premise solution, not from the cloud. Now everything has been migrated, and everything is from the Azure cloud; Microsoft Intune is part of the Azure cloud solution.

I find Microsoft Intune quite affordable. I rate this solution nine out of ten.

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.

I am a consultant and architect of Microsoft Intune, and previously I was also an internal customer of Microsoft, using Microsoft Intune.

I work with Microsoft Intune to manage cloud-only devices, mainly Windows, and this includes the migration process from hybrid join to cloud-only environments, enforcing policies via configurations and scripts, and implementing the RBAC model to set up permissions for different roles for customers.

Additionally, I implement macOS with iOS and iPadOS in fully managed mode and personally owned mode, such as BYOD. I am currently focusing on automation, attempting to build a solution that maintains governance, ensuring customers can focus on specific parts of Microsoft Intune and automate the monitoring of compliance of devices and their status.

I tried using Microsoft's Copilot in Microsoft Intune, specifically the Security Copilot, but I have not gained experience with real-world examples. I made an attempt to set up the onboarding agent diligently and managed the device offboarding process.

The most valuable feature of Microsoft Intune for me is its fully cloud-based nature, allowing me to work from anywhere, whether I am using my mobile phone, Windows, or macOS devices, so I can access it from any place at my convenience.

The specific feature that makes me choose Microsoft Intune over other tools is its integration with Microsoft services, specifically the connection with Entra ID, Azure, and collaboration tools. This is the main reason I recommend Microsoft Intune as the proper MDM solution for any company, although I am aware of alternatives such as Jamf or Zebra systems that cater to different needs.

My assessment of the user experience of Microsoft Intune is that it is sometimes good and sometimes poor, depending on Microsoft's infrastructure. There have been outages affecting not only Microsoft Intune but also connected services such as Entra ID, which can be frustrating, especially when demonstrating features to customers and encountering issues.

While there are many aspects that can be improved, such as log visibility and the accessibility of detailed information, I recognize that Microsoft Intune does have room for improvement.

Other areas of Microsoft Intune that could be improved include the enrollment process for Windows devices, which remains quite simple. Customers have expressed a desire for more customization options during enrollment, such as adding custom steps. This capability was possible in the previous Microsoft Endpoint Configuration Manager, leading to questions about why Autopilot does not offer the same functionality.

I have been working with Microsoft Intune for almost six to seven years.

I assess the stability and reliability of Microsoft Intune as being in good shape. It is evolving continually every month with new capabilities and fixes, which is beneficial for all users. I see a promising roadmap ahead, indicating that it is well-managed by Microsoft.

The stability and reliability of Microsoft Intune are crucial for me and my customers, as many of us rely heavily on Microsoft services. Any disruptions greatly impact operations, but fortunately, Microsoft has effective SLAs for its services, so we are not faced with hypothetical scenarios regarding poor performance.

In terms of scalability, I find Microsoft Intune to be an excellent tool for managing devices, designed for simplicity, making it user-friendly from an administrative perspective. With capabilities for scripting and application configuration, it works well for managing hundreds to thousands of devices.

While it supports macOS and iOS, the inclusion of Linux support would enhance its capabilities, considering Linux devices often lack visibility in IT management.

I have communicated with Microsoft Intune's technical support a few times, and my experience has been that I first need to explain my case to L1 support, which can be time-consuming before reaching someone with the necessary expertise, such as product management.

The worst experience involved a limitation related to Windows 11's multi-kiosk capability, which Microsoft confirmed was by design. Conversely, my best experience involved quick communication with a senior-level contact regarding a governance issue in Czech Republic, which was resolved efficiently.

Based on my experience with technical support, I would rate them a six out of ten.

Before adopting Microsoft Intune, I had the opportunity to work with Jamf, which focused on Apple devices, but I have not used other similar tools.

I participated in the initial setup and deployment of Microsoft Intune in different environments, including my own, and I found that the deployment was straightforward. Microsoft's documentation provided clear guidance, which I appreciated.

As for return on investment with Microsoft Intune over the years, I find it difficult to quantify because there remains a need for personnel to manage Microsoft Intune, from L1 to L3 support. It appears that it does not reduce staffing costs, and while AI may offer different advantages, Microsoft Intune alone does not alleviate staffing expenses.

Currently, I do not use Microsoft Intune Suite's Cloud PKI and have only theoretical knowledge about it, as I have not had the opportunity to implement it with a real customer or personally interact with it.

I am not currently using the enterprise application management features of Microsoft Intune Suite due to the strength of the global Microsoft Intune community and the abundance of existing tools such as Enterprise App Management, making it difficult to persuade customers to adopt it.

I also do not use the advanced endpoint analytics in Microsoft Intune Suite, although I understand its KQL language and data usage, similar to the enterprise application management features. Customers are not utilizing it.

Regarding Microsoft Intune's pricing and licensing, I find the default option, particularly Microsoft Intune Plan 1 included in most Microsoft licenses, to be reasonable for managing devices.

However, I consider Microsoft Intune Suite, which includes features such as Cloud PKI and Advanced Analytics, to be quite expensive, making it difficult to justify the cost to customers with large user bases, although I am pleased that Microsoft Intune Suite will be offered partially in E3 and fully in E5, which is a positive development.

Before choosing Microsoft Intune, I did not evaluate other options because Microsoft is so prevalent in the industry.

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

My use case for Microsoft Intune involves remote access and mobile management. The purpose is to improve our operational efficiency.

The best features of Microsoft Intune that I appreciate most include its comprehensive management capabilities and user-friendly interface.

I do use the cloud PKI feature in Microsoft Intune, which enhances my management of the certificate infrastructure effectively. In cloud PKI, it helps me manage my certificate infrastructure by ensuring secure operations and streamlined processes.

I also use Microsoft Copilot as it offers significant value in enhancing my experience with Microsoft Intune. My experience using Copilot has been very positive as it integrates smoothly into my workflow. Copilot helps protect my environment by automating security processes and facilitating timely updates.

I am also using the enterprise application management feature in Microsoft Intune for better app discovery and deployment. I use the application management feature extensively within Microsoft Intune for automatic updating and deployment.

There are areas that have room for improvement in Microsoft Intune, particularly regarding integrations.

I have been using Microsoft Intune for about three years.

The stability of Microsoft Intune is relatively high, and I would rate it a 9 regarding downtime or bugs.

For scalability, I would also rate it a 9 as it adapts well to our growing needs.

From one to ten, I rate Microsoft Intune's technical support as 8, indicating it meets my needs satisfactorily.

Positive

I utilize a different solution for some aspects of endpoint management, which offers additional functionalities.

The deployment of Microsoft Intune was fairly easy, though it had its complexities as well.

It took me weeks to deploy Microsoft Intune fully, balancing the setup with existing systems.

I estimate I have seen a return on investment of about 20%, highlighting the value provided by Microsoft Intune.

Microsoft Intune has saved me about 30% of my time through streamlined processes and efficient resource management.

The pricing of Microsoft Intune, considering its features, is cost-efficient.

In terms of overall pricing, I find it to be fairly priced, reflecting its capabilities.

Considering the features, I recognize its pricing is competitive within the market.

I compare Microsoft Intune to other solutions based on its features and performance, indicating its advantages.

When comparing with other solutions I have used, I find Microsoft Intune to be quite effective.

To others looking to implement Microsoft Intune, I recommend them to evaluate through a proof of concept before finalizing their decision.

I would rate my overall experience with Microsoft Intune a 9.

My use case with Microsoft Intune is mostly hardening our devices, but I'm also using it to set up some ASR rules. I think because we set up Windows LAPS, which required creating a new role, I would say I would stay with hardening and ASR rules.

With Microsoft Intune, we're using Autopilot and it makes deployment much easier. We are currently starting to use the Company Portal feature in Microsoft Intune.

In my five years of experience with Microsoft Intune, I appreciate that its behavior is different than other MDMs. I would say that we're setting up hardening on our Windows devices and because Microsoft Intune is a Microsoft product, it behaves much better than other MDMs on Windows.

It's really the beginning phase. When I worked at Samsung, I set up some managed Play Store, and it was pretty easy because you could upload or import your application and add it to the Microsoft Intune console and it appears in the Microsoft Manage Store. The process is probably the same right now.

App discovery sometimes works with Microsoft Intune. I think sometimes it's missing something, but in general, I would say it's pretty easy to find what I need.

Microsoft Intune is customizable. I know there are some custom settings that can be set, but it requires ADMX creation. That's why it would be much easier to use. There's a lot of API, and I think there is space for some additional features, not just some, but a lot of additional ones.

Microsoft Intune saves me time with automations, running processes, and access by about fifty percent, because I don't have to set up everything via registry editor.

Regarding JAMF, I would say JAMF is only good for Apple devices, as it's an Apple product, and the same is true for Microsoft Intune. Everything works perfectly with Microsoft using its own product. I would say right now that Microsoft Intune is one of the best solutions. I'm not a big fan of the IBM solution or Citrix. Regarding VMware, I haven't used it for three or four years.

I think it would be good to have many more policies in Microsoft Intune and stop using remediation scripts. It would be much more helpful.

I've been using Microsoft Intune for over five years.

I would rate the stability of Microsoft Intune a nine because there are no outages or issues. There are really not many issues within my whole career with Microsoft Intune.

I rate scalability a nine. It's pretty feasible.

My whole team is saying that they would rate technical support a three or four out of ten. Sometimes, I think it's good to mark it as a six because sometimes they are waiting for an issue to be resolved somehow, and sometimes we are able to overcome our issue. I would say five because sometimes after our support ticket, they change their documentation. Instead of helping us, they just change a few words in their documentation. They send us documentation saying to check it because it's by design.

I mean, they don't help us at all sometimes. They're just sending documentation and changing documentation and then sending us the article that says to check it. In their article, they described that it's a behavior and it won't be changed. This is how it should behave.

Positive

With Microsoft Intune, the user experience was difficult at the very beginning because I worked at Samsung and I enrolled Android devices. I have to say that Microsoft Intune was one of my least favorite MDMs because I just didn't get used to its UI. But that was the very beginning. I think now it's pretty easy, and I would say this is a really good MDM.

The initial deployment of Microsoft Intune is pretty easy to start. It really depends on how much I have to deploy because some environments need some additional things. But it usually takes days.

I'm not the one who is doing maintenance.

Our company was bought by another, and we're currently trying to persuade them to use Microsoft Intune with an E5 license. I think I will definitely recommend to them that it's worth it to use Microsoft Intune.

We currently have an E5 license, and using all of those features was really good. I'm not the one who's actually buying it. I think it should always be lower than its current price. It's really hard for me to say how it compares to other prices.

I don't use the advanced endpoint analytics in Microsoft Intune. We actually don't use it much because Microsoft Defender is taking care of it mostly. There's Defender for Endpoint.

I use Microsoft Copilot for additional questions. If there are some difficulties in enrollment or configuration, it's always good to ask Copilot and it helps navigate me to the proper troubleshooting. I would rate this product an eight overall.

We have IT solutions in this organization, but it's different. It's AWS, majorly.

I am dealing with AWS S3 storage services myself, and apart from this, we have multiple services which we are using, the different instances of VM, virtual machines. Majorly the VMs and the storage part we are utilizing. We are planning to use Route 53 as well for the network.

I don't think we have been dealing with something Amazon Virtual Private Cloud. We are just launching the VMs, the instances, and utilizing it for the services. The storage services we have been using in it to store our data.

The user experience of Microsoft Intune is very friendly and the interface is very good. It's very easy. Although Microsoft keeps on changing the console, you log in today and you will find something, and then after two months you log in and you will see the options change. That's how it is, but then again, it's quite interesting. It's always nice to explore things in it, always nice to connect and do things. It's not very difficult for me; I don't find it very difficult. Somebody who has worked on SCCM or these products can easily use Microsoft Intune. If they understand the technology, they will be able to use it. It's very good. Microsoft Intune is very good in terms of support as well. We get very good support from Microsoft. Overall, my experience is awesome.

We have utilized Copilot in Microsoft Intune very well.

My experience with Copilot was good. There are always some chances to do some enhancement and improvement, and of course, there is a lot of competition in the market as well against the AI tools we have, the open AI tools we have, and the chatbots we have. Definitely, but it is very good. It is very nice.

I see room for improvement with Microsoft Intune because the only thing is that under the policies, there are certain policies which are very deep dive. Somebody has to understand it very particularly, then only they should implement it. That's the only thing. Some demo videos would be available on the portal, that would be helpful. If somebody has to do some implementation of any new policies, how would they do it? The person has to search somewhere how this policy works, and that will help. A small demo would be available in the portal itself. That would be helpful if Microsoft itself can launch some demos.

So far, I think the things are going smooth with Microsoft Intune. I do not see any conflicts with that, any additional features. In terms of comparing with the other cloud providers, the things are smooth. But when it comes to AWS, they have a bundled package of security and everything in one portal, including the billings part as well. Whereas in Microsoft, it is separate. A bundle package would be helpful. Although with AWS, we can get it through Marketplace, in Microsoft it is subscription-based. That is also good, but if I compare with both of them, then console-wise, of course, Microsoft Intune has very good features and everything in terms of endpoint devices. But in terms of the virtual machines connect and onboarding the virtual machines and syncing them, it is a bit tricky. One improvement that is needed if I compare with AWS where it's pretty easy.

I have been working with AWS for three months already, but this organization has been working on AWS for the past one and a half years or more.

During the onboarding of Microsoft Intune, we faced the problem that the policies were not getting synced. Sometimes, even after removing the devices from the domain and then re-onboarding the devices, joining the domain again, the sync was not happening. For example, there was one case where the devices were already synced, everything was synced, the user was logged in, and then suddenly when we handed it over, when somebody left the organization, we handed over the asset to another, assigned it to somebody else. In that case, that syncing was not working. It was taking a lot of time. It was very difficult. We removed it from the domain, we formatted the machine completely, then again installed the fresh image. Everything we did, it took time. Then ultimately, we had to take the help from Microsoft. It got resolved, but that was a difficult situation.

Microsoft Intune support is very good. We get very good support from Microsoft.

Ultimately, we had to take the help from Microsoft. It got resolved, but that was a difficult situation.

Positive

Before this, I was working with Microsoft in my previous company, where I was using Microsoft Intune and other services of Azure and Microsoft.

My experience with the deployment of Microsoft Intune was a bit tricky. It was tricky. But the overall experience was good because there was a lot of learning and enough support from Microsoft in terms of deployment as well.

I haven't used Microsoft Intune Suite Cloud PKI. We haven't used it. But we were having the Citrix environment, so we were launching the Microsoft Intune services in it, connecting our services, and connecting our virtual machines on Microsoft Intune, onboarding the VMs on Microsoft Intune. That's how we were using it, through Citrix.

I need to check that with the engineer regarding something Amazon DCV.

I would rate technical support at least a nine.

I would rate Microsoft Intune at least eight to nine overall.

I would rate it at least eight out of ten. My overall review rating for Microsoft Intune is eight.

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.