Microsoft Intune Reviews

I have been working with Microsoft Intune and other platforms such as MDM for the last three years. I worked for a competitor company, SOTI, which is an MDM-based company where I dealt with MDM, MAM, and other related functions. My experience includes enrolling devices and hands-on work with iOS, Android, MacBook, and Windows. I have developed good knowledge in these areas.

Currently, I am managing devices using other tools such as 42Gears and Jamf. When customers approach us wanting to enroll devices and implement policy restrictions, I use Microsoft Intune to add those restrictions. I handle scenarios where customers want to enroll devices and establish policy restrictions in their environment.

Remote control is the feature I like the most. I take control of devices so that we can work hands-on and create access with giving access restrictions. These are the features I value most, and pushing packages from the backend is also important.

With Advanced Endpoint Analytics, we can proactively detect and remediate anomalies in endpoints. This is an enterprise management tool. Any applications coming directly from the organization can be installed and deployed in the environment through device management so that customers can use them.

Microsoft Intune is handy. It is directly compatible with Active Directory, making Microsoft Intune more preferable.

When installing packages in higher versions, I faced some legacy issues.

Packages on different identity provider platforms that are not supported present challenges for package installation. Packaging issues are areas where I found legacy problems in Microsoft Intune. The initial deployment of Microsoft Intune is not straightforward and depends on the package being installed.

I have been using Microsoft Intune for about one year.

During system upgrades or downgrades, maintenance is required. When upgrading the system, I need to coordinate with customers or other people. During this time, Microsoft Intune will not be operational. In the meanwhile, we can upgrade or downgrade the system according to customer requirements or any new updates coming to Microsoft Intune. We need a maintenance window during this process.

Scalability sometimes depends entirely on the application being pushed in the backend. I would give it an eight out of ten. For scalability, I would give it an eight since there are times when we encounter errors while pushing applications in the environment. Sometimes it is entirely dependent on the compatibility between the application version type and the Microsoft Intune version type.

I have worked with SOTI, which is one of the MDM companies and a similar product to Microsoft Intune. I used MobiControl MDM at that company.

The overall complexity of the installation is easy. It depends on the package being installed. In the minimum, it takes approximately ten to fifteen minutes. The installation time depends on the packages being installed. If done through the cloud, it is manageable and one person can handle it.

I have read all the job descriptions and have developed deep knowledge with Microsoft Intune. I do not use it in daily operations, but I have good practice with it. I have used Autopilot, not Copilot. Autopilot works when we push updates in the backend and they are automatically applied across entire devices through Active Directory or other backend cloud systems. I am not certain about the business perspective aspect, so I will not answer regarding that since those decisions are taken by business holders. Most of the time I resolve issues on my own. My overall review rating for Microsoft Intune is eight point five out of ten.

Microsoft Intune is used for mobile device management, specifically for MDM. The implementation was done in-house without working directly with Microsoft or local partners.

Microsoft Intune offers almost everything that an MDM solution has to offer, and recently the gap between Mac computers and other devices has been closed. The ability to push software to end devices is particularly valuable.

I am using the Enterprise Application Management features of Microsoft Intune Suite, which includes software deployment and related functionality. Since Microsoft Intune is used predominantly for MDM, when anybody enrolls through the company portal, their mobile device automatically goes through a BYOD process and enforces all required app and security settings at a very fine granular level. For example, users cannot copy content from Outlook or Edge to WhatsApp or other third-party tools.

Microsoft Intune needs to support out of the box Apple Managed Device and Apple Business Managed Device with zero-touch deployment capabilities, which is something competitors provide.

I would appreciate a blueprint feature for company-owned devices, not BYOD, where the blueprint would automatically configure everything from scratch. This could be modeled similarly to what exists for Apple business enterprise solutions, allowing for a copy-paste approach.

I have been working with Microsoft Intune for the past seven to eight years.

I have not noticed any issues with the stability and reliability of Microsoft Intune, though this does not mean there has not been any downtime. There could have been downtime, but it has not been noticeable.

Microsoft Intune is brilliant for scalability and is excellent for scaling purposes. While my organization has a relatively fixed user base, I am aware from experience that this product scales effectively.

The technical support and customer service team of Microsoft are really good. With premier support from Microsoft, my experience has been brilliant.

For mobile management, I have used BlackBerry in the past.

There are significant differences between Microsoft Intune and BlackBerry products, both in terms of cons and pros. From a security perspective, Microsoft Intune is brilliant, and while BlackBerry is very good with security, Microsoft Intune offers operating system based containerization provided by iOS, whereas BlackBerry has its own proprietary containerization. This proprietary approach gives security teams a sense of safety. These are some of many differences, though my knowledge of BlackBerry is dated and I cannot provide extensive detail.

The deployment of Microsoft Intune eight years ago was pretty straightforward. Enabling it provided instant access, and I did not face any problems. The setup was very intuitive.

Microsoft Intune is definitely cost-effective because I have an E5 license that includes this product. If I were not using it, it would not be cost-effective, but since we are actively using it, it is becoming cost-effective.

Microsoft Intune comes along with the E5 license package.

Microsoft Intune Suite's cloud PKI for certificates is not being used.

Copilot in Microsoft Intune is not being used, though Copilot is used generally as an interface with Office applications, including the Office extension with Word, Excel, and PowerPoint. For example, I can tell Copilot to create a presentation and it will generate something for me. Copilot is not being used for security purposes.

Microsoft Intune is used with Azure cloud, and there is also an integration with SCCM.

Microsoft Intune has only an administrator experience rather than a user experience interface, and it is pretty adequate. Microsoft Intune is user-friendly.

There are a couple of aspects that Microsoft Intune could make easier. I would appreciate a blueprint feature for company-owned devices, not BYOD, where the blueprint would automatically configure everything from scratch. This could be modeled similarly to what exists for Apple business enterprise solutions, allowing for a copy-paste approach.

The decision to implement Microsoft Intune was made because of the E5 license. The overall review rating for this solution is 6.

It is not restricted to a single purpose. It involves a combination of taking control of systems and handling the configuration for clients. We have multiple projects for enhancing Microsoft 365 security for clients with multiple use cases. 

We are a consultancy. We take projects from clients and get them ready for business use.

Within a single MDM solution, Microsoft Intune provides everything. It is time-efficient and cost-effective because with a single license, we are getting multiple options.

The best feature is that it's a Microsoft product, so if anything goes wrong, we get quick support for anything required. 

Remote system functionality allows us to sit anywhere and take control of any device via remote management. We can enhance security for clients' laptops with built-in Microsoft Defender, which is available with the Microsoft Intune license.

We use it for reporting purposes through endpoint analytics. When pushing scripting, there are two types available: remediation script and reservation script. Through endpoint analytics, you can push defender policies to clients. It helps with reporting, inventory updates, and monitoring tenant status health.

There are areas for improvement. When pushing anything from Microsoft Intune, the sync timing is 48 hours. While sometimes it takes 5 to 10 minutes, the official period given by Microsoft is within 48 hours, which can be time-consuming for policies, applications, or patches.

Another issue occurs when deploying large applications of 10GB or 15GB - they sometimes crash due to network issues. Additionally, there are some security-related issues that need improvement. Microsoft will likely address these areas as product development continues.

I have been using Microsoft Intune for three years.

I would rate it an eight out of ten for stability. 

The scalability of Microsoft Intune is increasing because organizations are testing it. As a Microsoft product, it is the best-rated solution for device management globally. Organizations continue to expand their use cases of Microsoft Intune day by day.

We manage approximately 60,000 Windows devices, 10,000 Android devices, and 5,000 to 6,000 iOS devices, totaling around 80,000 to 90,000 devices.

I would rate them a ten out of ten. When we need assistance and raise a ticket, we always get good support for our issues. When anything goes wrong, we get in touch with Microsoft engineers to resolve the issues.

Positive

In the current market, there are several Mobile Device Management (MDM) solutions available. I also work with Jamf, which is particularly effective for managing Apple devices. Microsoft Intune provides excellent management capabilities for Windows and Android devices as well. The user experience is generally smooth, and users typically encounter very few issues. Overall, it's a strong solution in the market.

Microsoft Intune is unique in providing management for all operating systems, including macOS, Linux, Android, and iOS. Jamf only handles Apple ecosystems. Jamf excels in Apple ecosystem management with sync periods of one to two minutes for policies and applications, and their security and algorithms are very fast. However, for overall management of all operating systems, Microsoft Intune is the best solution, allowing management of four operating systems with a single license.

Microsoft Intune definitely saves time because we don't need to look for managing Android devices with other MDM solutions or Apple devices with Jamf.

It depends on the environment. Cloud deployment is easier because everything is hosted on the cloud. On-premises environments can be more difficult as each organization has its own setup.

In terms of maintenance, it requires patching. We do the updates before pushing them to the clients. We test on our test devices. Once we find it is okay, after one or two weeks, we deploy in phases.

Compared to other MDMs, it is cost-effective because it is included in the O365 or Microsoft 365 license. It is cheaper compared to others.

It is a partner purchase. We have a relationship with OEM.

We have the Copilot license with a Microsoft 365 E3 or E5 license, though we are not using it directly through Microsoft Intune. Everything is manual for us currently. 

Based on my experience, I would rate Microsoft Intune a nine out of ten, leaving room for improvement. We recommend it because it's the only solution for managing all operating systems. It's also user-friendly for both IT systems and users with licenses.

My main use case for Microsoft Intune is endpoint management and security, where I use Microsoft Intune to manage devices, deploy applications, enforce compliance policies, and maintain security configurations across Windows endpoints.

A common example of how I use Microsoft Intune for endpoint management and security in my organization is onboarding a new laptop, where I use Microsoft Intune to enroll the device, deploy required applications such as Microsoft 365, apply security policies, and enforce compliance settings automatically. This ensures the device is ready for use and meets company security standards without requiring manual configuration by IT.

In addition to device management, I also use Microsoft Intune for compliance, monitoring, and application lifecycle management, which helps to maintain a consistent device posture and quickly identify devices that fall out of compliance, supporting both security and operational requirements.

The features I find most valuable in Microsoft Intune are device management, compliance policies, application deployment, and integration with the Microsoft security ecosystem. Windows Autopilot is another feature that stands out because it simplifies device provisioning and helps to deliver a more consistent onboarding experience for end users.

Windows Autopilot has made device onboarding much easier for my team; instead of manually preparing laptops, I can ship a device directly to the user, and once they sign in with their corporate credentials, the required applications, policies, and configurations are applied automatically. This reduces setup time, minimizes the manual effort for IT, and provides a more consistent experience for users, regardless of their location.

Another feature worth mentioning is the compliance and reporting capabilities, which give visibility into device health, security status, and policy compliance from a single console. I also appreciate the flexibility of managing devices remotely, which has been particularly useful for supporting users in different locations without requiring hands-on IT involvement.

Microsoft Intune has positively impacted my organization by giving a centralized way to manage and secure devices across the organization, improving consistency in how devices are configured, updated, and monitored, and making it easier to support remote users as many management and troubleshooting tasks can be performed without needing physical access to the device.

One noticeable outcome I have seen since using Microsoft Intune is a reduction in the time required to provision and configure new devices, as policy applications and security settings are deployed automatically, making the onboarding process much more streamlined. I also see fewer support requests related to device configuration because users receive a more standardized setup from the start.

One area where Microsoft Intune could be improved is troubleshooting, as it sometimes takes time to identify the exact cause when application deployments or policy assignments do not work as expected. I would like to see more simplified reporting and clearer visibility into policy conflicts, especially in larger environments where multiple configurations are applied to the same device.

Another area I will mention is application management; while deploying Microsoft applications is generally straightforward, managing and troubleshooting some third-party applications can require additional effort. I would also like to see more proactive recommendations around device health, compliance, and deployment issues so that administrators can identify and address potential problems earlier. Overall, the platform is strong, but these enhancements would further improve the day-to-day administrative experience.

From a governance and security perspective, I think Microsoft Intune is very strong, as it allows me to enforce compliance policies, manage device configurations, and integrate with conditional access to help ensure that only compliant devices can access company resources. Regarding AI capabilities, I see the value more in the intelligent insights and recommendations rather than fully automated decision-making, with features that highlight security risks, compliance gaps, or device health issues helping administrators to prioritize actions and improve overall security posture.

In my experience, the AI-driven insights and recommendations in Microsoft Intune have generally been accurate and useful, providing a good starting point for identifying compliance issues, security risks, or device health concerns. That said, I still treat them as recommendations rather than automatic decisions.

In my organization, Microsoft Intune is deployed as a public cloud service, and since Microsoft Intune is cloud-native, I use it to manage devices, applications, and compliance policies across different locations without relying on on-premise management infrastructure. This approach has worked well for supporting both office-based and remote users through a centralized management platform.

I primarily use Microsoft Azure as the cloud provider, which provides a seamless foundation for device management, identity, and compliance, as Microsoft Intune is closely integrated with Microsoft Entra ID and other Microsoft security services.

My advice for others looking into using Microsoft Intune is to start with a pilot group before rolling Microsoft Intune out across the organization, as this helps to validate the device. I would rate this solution a nine out of ten.

The main use case for Microsoft Intune is for approximately 150 end users in a nonprofit organization where I have implemented it.

The best feature of Microsoft Intune is that it managed the endpoints. Microsoft Intune is the endpoint management tool that allows us to keep the apps updated, push the app to the endpoint, and manage them. Management became easier with Microsoft Intune.

I switched away from Microsoft Intune because it cannot manage the MacBook very well.

I have used Microsoft Intune for approximately five years.

Microsoft Intune is stable.

Microsoft Intune is a scalable solution.

Microsoft has no support available. There are only two or three support options, and Microsoft never has support for that. They only provide documents.

Negative

We are not using Microsoft Intune anymore. I used Microsoft Intune last year, and then we changed to something else.

My experience with the deployment of Microsoft Intune is easy. Microsoft has very detailed instructions, and everything is on the cloud, which makes the deployment easy.

Good documentation was available.

The pricing for Microsoft Intune is cheap with no additional cost.

We moved to Enable. Enable can manage all the devices really well, including the MacBooks.

I did not use the cloud PKI with Microsoft Intune. I used Copilot but not Copilot for Microsoft Intune last year. Copilot did not help at all with Microsoft Intune for us. The main benefit of Microsoft Intune is that it comes with Microsoft, which was the major reason we tried it. Microsoft Intune was reliable for us mostly. I gave this review a rating of 5.

The main use cases are that we are using Microsoft Intune in a co-management environment. We do have SCCM also in place, but currently we are managing limited workloads shifted to Microsoft Intune, such as configuration policies, and all devices are enrolled in Microsoft Intune. The patching is still going on from the SCCM end, but we are planning to migrate the patching workload to Microsoft Intune in the near future. Application deployment is currently under plan and I'm testing some use cases. There are many add-ons Microsoft has added in the Microsoft Intune suite so that we can have multiple third-party patches. We can package applications in a quicker time as part of the plan.

Advanced endpoint analytics provides granular information about devices in Microsoft Intune, facilitating easier troubleshooting at system and application levels. 

It is a SaaS solution. Firstly, as an internal administrator, I appreciate that we don’t have to manage the entire infrastructure, which is a significant advantage. Moreover, since this is a Microsoft product, it is designed with seamless integration in mind. While it supports various platforms like macOS, Android, and even Linux, the primary users are typically on Windows systems. The brand recognition of Microsoft adds value, and because both the operating system and the solution come from Microsoft, we face fewer challenges compared to using third-party products. With third-party solutions, integration issues may arise, requiring multiple discussions with vendors or Microsoft. Having everything from Microsoft leads to a more convenient, built-in solution. Additionally, there are numerous advantages related to patch management and setting maintenance windows.

Another noteworthy point is that Microsoft frequently introduces new features. It’s impressive that updates and service releases occur almost every month, providing useful enhancements for both the company and the overall Intune administration experience. This consistent flow of new features ultimately benefits our organization.

The introduction of Copilot is one of the latest enhancements, although it has been in public preview for quite some time. Another noteworthy advancement is the Autopilot device preparation policy. The latest version of this policy has reduced many burdens since the management is now cloud-based, eliminating the need for hardware hashes. Devices no longer need to be registered for Autopilot or have their hardware hashes uploaded in this new environment.

Additionally, there have been numerous improvements in Windows 365, including advancements in cloud PCs and provisioning policies. Microsoft has also introduced automatic device preparation policies for Windows 365. Furthermore, Intune continues to receive many enhancements. For instance, TPM support has been added, which aligns with approved concepts. Though the Copilot integration is not functioning as expected at the moment, Microsoft is still actively working on its development, as communicated to me. Lastly, I also wanted to mention the Local Administrator Password Solution (LAPS) as an important capability that is being improved.

The user experience of Microsoft Intune is excellent because it's a SaaS solution altogether. There is no need to take a burden of the infrastructure part because everything is Microsoft controlled and it's a good solution for endpoints. It's performing exceptionally at present.

Configuration profiles or policies function very well. We can accomplish a lot with the configuration profile itself, instead of opting for other packaging methods or on-prem GPO group policies. Everything can be managed through the background, but it’s all accessible within the settings catalog. The settings catalog in the configuration profile is a much better alternative than going for the administrative template and creating everything from scratch. The settings catalog is doing an excellent job in this regard.

I have been closely observing these products and regularly testing their functionality in my test environment. I provide feedback to Microsoft based on my observations. Additionally, I write blogs and conduct training sessions for my colleagues and other candidates. If I were to pinpoint an area for improvement, I would highlight reporting issues. Back in 2020, there were significant problems with report accuracy, particularly regarding web patching. However, Microsoft has made substantial improvements in the reporting for Windows Update for Business and has added various advantages.

We hope for greater flexibility and advancement. We appreciate the introduction of functionalities like Copilot, the Intune enterprise app catalog, and analytics features such as remote help, but there are concepts like hot patching that we believe could enhance the overall experience.

I have been using Microsoft Intune for over seven years, starting with SCCM and then moving to the SaaS solution.

There have not been any significant stability and reliability issues with Microsoft Intune.

Microsoft Intune definitely scales up when it comes to integration and development requirements. It is reliable with the features currently available. 

Looking forward to the next 10 years, there should be substantial development available in the portal or the Microsoft Intune admin center to be more helpful for organizations. With additions such as Copilot and based on feedback from users, MVPs, and tech enthusiasts, the product continues to develop in ways that make it more useful for companies, users, and admins.

I would rate the technical support of Microsoft a nine out of ten. While I haven't faced many issues in the enterprise environment, the overall support I received for cases raised in my personal tenant has been satisfactory. They responded and provided the expected feedback, even though it was free of cost.

Positive

We have also been using SCCM. We do have functionalities, such as the Cloud Management Gateway (CMG) in SCCM, but as technology continues to evolve, we need to gradually shift towards Intune. I believe this will be more feasible for future requirements. If we don’t make this move now, in one to two years, or perhaps within five years, it will be essential to transition at least your endpoint devices to Intune.

We did not have any challenges because we already had SCCM in place, which is functioning effectively in our environment. It is like a parallel migration. Currently, all devices are co-managed, and since they are in a common space, we haven't encountered many complications. However, it would be beneficial if Microsoft could introduce more flexibility in this area, such as enabling the bulk enrollment of all devices at once. That would be great.

The deployment process is streamlined, requiring only a few clicks for installation, with most settings pre-configured. If an application isn't available in the enterprise app catalog, requests can be made to Microsoft for pre-packaging.

From an Intune perspective, I haven't faced much difficulty with enrollment or onboarding devices. Given that we already have a management tool in place and it’s working as expected, there’s been no disruption to business operations. Overall, I would say the process has been quite smooth.

Regarding cost effectiveness from the Microsoft Intune product, there is definite value. With an enterprise license for Windows 10 or 11, we have the capability to incorporate those features into Microsoft Intune without requiring an additional license for management. This represents a significant benefit.

While Microsoft products can be expensive, they offer valuable functionality. With Microsoft Intune Suite license or standalone license for enterprise app catalog, there are predefined third-party apps available that are pre-packaged. The enterprise app catalog, though license-based, provides numerous third-party applications with auto-update options. Ivanti brings significant capabilities in third-party application updates and patching.

Comparing Microsoft Intune with products such as Jamf and Ivanti solutions, there are distinct differences. For third-party patching, Ivanti is particularly helpful. 

Copilot recently moved to general availability and Microsoft is expecting substantial user feedback. While it requires an additional security Copilot license which can be expensive for enterprise environments, it offers capabilities such as compliance checking and application installation on multiple devices with simplified query creation.

Regarding enterprise application management, the enterprise app catalog environment includes both Microsoft-owned and pre-packaged third-party applications. 

It’s a feasible solution. If you already have many endpoint devices, this solution is particularly suited and is not dedicated solely to servers. If you have servers, you can leverage the existing SCCM solution and any other solutions already in place. The biggest advantage is that you can still manage your workload with co- management. You can start with the co-management scenario. Gradually, you can move your workloads and do enrollment. First, enroll the devices into Intune, and then slowly transition your workload based on the specific scenarios or test cases you've evaluated.

Since the pandemic in 2020, many devices are now mobile, and most companies are operating in a hybrid environment, with some even functioning entirely remotely. In these cases, it's challenging to bring devices, like laptops—which are essentially mobile devices—into the organization's office to connect to the internet and receive the necessary policies.

Based on my experience, I would rate Microsoft Intune a nine out of ten because many of the latest add-ons are being incorporated. However, I'm not giving it a perfect ten because there are still areas that need improvement. We are also expecting some additional features. While the current capabilities in Intune are good, we hope for greater flexibility and advancement. If these improvements and features are implemented, it could become a completely reliable solution—something close to a perfect ten—for both end users and organizations.

I use Microsoft Intune for daily operational tasks such as device and onboarding, enrollment, adding new devices or mobiles using Autopilot or manual enrollment, policy management, application deployment, and user access control. These are my main use cases for Microsoft Intune in my day-to-day work. The main advantage of Microsoft Intune is that it does not require much time to prepare a single device for a single user. It usually takes twenty to thirty minutes, and no IT touch is needed for it.

A few best features according to me are that Windows Autopilot's zero-touch deployment stands out because we do not require any IT person to configure anything for the user base, along with centralized device management and application deployment. These are my best features.

The zero-touch deployment with Autopilot makes my life easier by allowing us to ship laptops directly to the user, where the user logs in via their mail, and the device automatically configures. For example, we have created policies according to the group, so we create a user on that group, and there is no need for manual imaging or complete setup, so it is done via zero-touch deployment.

For application deployment, we can deploy an application on hundreds of devices without touching the device, which helps me with massive operational efficiency. Access control is also a good example because we have created users based on a tier group, which helps me a lot.

Microsoft Intune impacts my organization positively by saving significant time via faster onboarding; there is no requirement for manual imaging or setup. It takes two to three hours per device manually, but via Autopilot, it is zero-touch deployment and takes thirty minutes for onboarding. Another aspect is centralized management; we have a single console for all devices, whether mobile or Windows, which reduces the dependency on on-site IT support and provides faster issue resolution.

I have not faced any significant issues until now, and Microsoft Intune is good. It can improve for new users; in the starting phase, we found that the logs are too complex or scattered.

I have been using Microsoft Intune for the last three years.

Microsoft Intune is stable.

Microsoft Intune's scalability is generally very strong; it can handle thousands to hundreds of thousands of devices.

Before, we were using Active Directory on our on-premises network, so according to that, the cost is a little bit high. We did not use any solution previously before adopting Microsoft Intune.

If we go manually, it usually takes two to three hours, but via Microsoft Intune, it usually takes twenty to thirty minutes per user. The on-site IT team can focus on other tasks.

The pricing is a little bit high.

We did not evaluate other options before choosing Microsoft Intune.

If we go manually, it usually takes two to three hours, but via Microsoft Intune, it usually takes twenty to thirty minutes per user. The on-site IT team can focus on other tasks. I strongly advise others looking into using Microsoft Intune because of its features.

I have been using Microsoft Intune for the last three years in my infrastructure. I use Microsoft Intune to manage all my devices via a single dashboard on the basis of groups.

For device management, I use application management control to determine which apps can access corporate data, restrict third-party apps, and handle all related tasks. Security and compliance enforcement is done via Microsoft Intune only. For security rules, I implement password strength, MFA, and encryption policies.

Microsoft Intune is deployed in our public cloud, and I use Azure as the cloud provider.

The best features that Microsoft Intune offers in my experience are MDM, MAM, mobile application management, and automated policy deployment.

The core Microsoft Intune capability of MDM allows me to enroll and manage devices including Windows, iOS, Android, Mac, and Linux, which enables me to manage them securely and compliantly at scale. Additionally, the logs, compliance reporting, and reports have been invaluable.

Microsoft Intune has positively impacted my organization by providing many benefits. The headache of IT management has decreased, and it has provided stronger security with less friction. Much faster device setup and onboarding has helped me in various ways.

Customer support can be improved and simpler policy management can be implemented. All the features I have mentioned are great and helped me rate the solution highly, but there are areas for improvement. For example, troubleshooting could be made easier, and simpler policy management can be achieved.

I have been working with this solution for more than four years.

Microsoft Intune is stable.

Microsoft Intune is highly scalable, and scalability is one of the strongest advantages.

Customer support is good, but it can be improved.

I was not using any different solutions before Microsoft Intune, as I was directed to upgrade to Microsoft Intune without evaluating alternatives.

Before using Microsoft Intune, device onboarding and setup usually took hours or a full day. Now via Microsoft Intune, I can complete this process in minutes.

I am partnered with Microsoft for implementation.

Microsoft Intune has provided me ROI on both money and time saved. Additionally, fewer IT personnel are required now.

I have not evaluated any other options before choosing Microsoft Intune.

I strongly advise others to use Microsoft Intune for managing company assets and security posture. I would rate this solution a 9 out of 10.

My Microsoft Intune use case does not involve custom packaging or PKI. I have deployed Microsoft Intune cloud for all of our endpoints, which includes laptops as well as our corporate-issued cell phones.

It's great for device management. Using hte Micorosoft Defender suite using some Intune features allows us to deploy those security tools a lot quicker than we would otherwise. Without Intune, you'd be running from machine to machine, or you could be issuing individual policies. You may have to create a task sequence in SCCM. All those things delay where our clients wanna get to, which is a safer, happier future, and Intune allows them to get there a little bit quicker.

Time to live - how fast can we move a client from a higher-risk state to a lower one, and how can InTune facilitate that. It's a great roadmap for deploying policies. 

We're able to deploy security policies through it, it's essential towards our hardening, not just internally as a company, but for our clients.

Using Copilot in Microsoft Intune allows me to quickly search for devices that are most out of date that have a security feature about to expire or need patching to prevent their OS from becoming stale. It allows me to search for unwanted apps that might be installed. I can do that naturally in the user interface, but having that chatbot in the top right, especially if I'm not in Intune every day, is really helpful. If I'm using Intune every day, I know where to go, but for that first time, Copilot is beneficial. When I need it to compute anything for me, Copilot is there.

I have been playing around with the analytics features of Microsoft Intune. I mainly use Microsoft Intune analytics for taking that data that exists and bringing it into Power BI dashboards to make it visible to our clients, showing them all the operating systems in their environment and where the latest patches are, and then from there creating plans. The insights, even though we're talking about charts and graphs, are super valuable to customers who might not otherwise know what's in their ecosystem or the current state of things within their ecosystem.

It allows you to also search for unwanted apps that might be installed. Now you can go do that naturally in the user interface. Having that little chat bot in the top right, especially if you're not in Intune every day, is really helpful. Obviously, if you're using Intune every day, you know where to go. However, for that first time, Copilot helps. And then if you needed to actually compute anything for you, obviously, Copilot helps as well.

We've used the advanced endpoint analytics to take existing data and bring it into our BI dashboards and from there, create plans. The insights are super valuable to customers who might otherwise know what's within their ecosystem.

Not having to reimage machines every summer is a huge, huge task that's gone. Limiting trips to a physical help desk has been saving us a lot of time.

Enrollment into the Microsoft Intune service can still get easier, especially for legacy-managed systems, such as how we get it from a GPO or an SCCM configuration into Intune. A lot has been done, but there can always be more. Regarding third-party migrations from other MDM solutions, customers want to get into Intune because they own it already as part of their Microsoft Suite, so helping with that crosswalk would be desperately needed and would make it faster for customer adoption, leading to greater satisfaction.

There was a steep learning curve when I did it; however, they've fixed a lot of the bugginess. It just works now. It's nice. 

I started using Microsoft Intune back in 2016. I was there for multiple generations of it where it started, and then watching it really take off in 2018, 2019, to it now being the de facto device management platform in the industry.

I assess Microsoft Intune's performance or reliability as being about 99.9% uptime.

I find Microsoft Intune to be unlimited in scalability. I'm not worried about it and I think the same applies for our customers too; I don't think they are worried either. Intune can handle a lot.

Customer service and technical support for Microsoft Intune are very good. As a partner, I'm treated well. I already know the product, so the questions I ask tend to be more precise. I could see if someone is completely new, they would have to learn the questions to ask. For me, I have no issue. When something arises, I get a pretty good answer.

Positive

I have considered and used some CrowdStrike security tools that we had on phones to try to do some of that. Fortunately, that's all gone and it's all Defender and Intune managed devices now.

Intune is part of the Microsoft suite. So if you're using parts of the Microsoft suite, it makes sense to use all of it versus having to go to, like, another thing. Right? There are too many things within Microsoft. There are a million other things that when you start mixing up, like, I'm gonna get this from here and that from there. And it's really hard to ask people to be professionals at multiple different product suites.

We have the solution deployed to all of our devices. 

The biggest improvement in my endpoint management since implementing Microsoft Intune is not having to re-image machines every summer, which is a huge task that's gone, along with whatever my re-image cycle was, and then limiting trips to a physical help desk.

The pricing structure for Microsoft Intune is not complex. It's very simple because it comes with the Microsoft Suite whether it's E3 or E5, and it automatically includes Intune. I think there could be better documentation on what that actually means. We end up in many conversations about whether we are appropriately licensed for various features. I think the answer is always affirmative, but people want to confirm because they don't want to deploy things that they don't own for their own compliance.

We did not consider other options. 

I selected Microsoft Intune over other endpoint management products because it's part of the Microsoft Suite. If I'm using parts of the Microsoft Suite, it makes sense to use all of it versus having to use another solution. There are too many things within Microsoft; there are many other things when I start mixing up getting different components from different places, and it's really hard to ask people to be professionals at multiple different product suites.

I rate Microsoft Intune a nine out of ten, noting they could improve their Linux and open-source Android support.

My main use case for Microsoft Intune is to manage all the endpoints and use the conditional access policies to manage all the applications for Microsoft.

In my organization, we are using M365 with Microsoft Intune, and we do not want users to access their email on any non-managed devices, so we manage devices with Microsoft Intune and the Exchange, meaning online exchange mail is only accessible on Microsoft Intune managed devices. This is the use case we are following.

For Microsoft Intune, we also use it for patching our devices because patching is very critical for us, and Microsoft Intune helps us to get all the patches centrally without going to any further third-party sites. It is helpful, and it also gives me options to see the vulnerabilities on all the Microsoft Intune-joined devices.

The best feature of Microsoft Intune is the zero-touch device provisioning, which is very helpful to reduce the manual imaging, as we do not want any dependencies on local engineers to install the OS manually, and it is easy to manage our devices from remote sites. It also increases the compliance which we follow and helps to reduce the time to deployment, allowing us to customize the OS with the software our company uses, making it ready to go.

Microsoft Intune impacts our organization positively by reducing the time for our engineers, allowing them to focus on other important tasks. It provides a complete overview of all the endpoints managed by Microsoft Intune, showing which systems are critical, not critical, healthy, and not healthy, and how many devices comply with our organization's policies. It also reduces the risk of data being shared outside of our devices.

Microsoft Intune reduces the time of our engineers, cuts down costs for the deployment of our endpoints managed by Microsoft Intune, and helps to improve compliance and the security policies we wanted to apply on endpoints, which was not happening earlier. Now it is working fine.

For improving Microsoft Intune, it sometimes feels laggy, taking some time to implement any policies on machines. I understand it's dependent on the network, but some other device management applications implement changes more quickly. This lag is the only gap I see.

There should be an easy guide to getting started with Microsoft Intune. As an admin, I feel we need clear steps to follow based on the licenses we have purchased. Best practices for Microsoft Intune would help us utilize all its features fully, giving us confidence and better value for our investment. Currently, we have to figure it out on our own.

I have been using Microsoft Intune for four years.

Previously, without Microsoft Intune, we were using a manual method by booting all laptops with USBs after procuring them to our office. We installed the OS and all the applications, provided antivirus, configured the Outlook Exchange, and other user profiles, then sent those laptops via delivery to any remote users located anywhere in India. This process reduced the time and cost of delivery, as we can now send laptops directly to users without going through our office, and it has significantly reduced the time for deployment of applications, images, and configurations which can now happen remotely.

Sometimes, the AI gives options that are not available, making it difficult, leading us to search repeatedly. While the AI understands we have purchased only basic licenses, it typically provides generic answers related to the complete feature set of Microsoft Intune, making it tricky. This occurs only sometimes, as most of the time, the AI's output is accurate.

Microsoft Intune AI is one of the most valuable AI-driven capabilities within Microsoft Intune, with its integration with Microsoft Security Copilot and AI-based analytics for endpoint management, detecting compliance issues, application failures, risky devices, and deployment problems proactively. It helps us analyze compliance issues, and if we ask the AI to improve compliance or reduce application failures and risky devices, it provides answers that make managing Microsoft Intune easy.

For remote management, we use Microsoft's default application, Quick Assist, which is helpful as we do not have to depend on any third-party applications, making it easy. We can also use the remote wipe if anything goes wrong.

The cloud provider we use for deploying Microsoft Intune is Microsoft.

In my experience, Microsoft Intune licensing and pricing mainly depend on the size of the organization, security requirements, and whether it is purchased standalone or as part of the Microsoft 365 subscription. We are using M365 and Microsoft Intune together, with my organization preferring Microsoft Intune through Microsoft 365 E3 or E5 because it includes endpoint manager capabilities along with security and identity services. The setup cost feels lower compared to other software in the market.

I would rate this product an eight out of ten.