Microsoft Intune Reviews

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

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

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

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

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

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

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

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

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

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

I have been using the solution for four years.

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

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

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

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

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

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

I don't have specific ROI data points. 

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

I wasn't involved in the RFP process. 

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

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

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

My main use case for Microsoft Intune is device management, policy enforcement, and securing endpoints across users in the organization.

Recently, I used Microsoft Intune to enforce device compliance policies including disk encryption, screen lock, and antivirus checks so only compliant devices could access company resources, which helped reduce risk from unmanaged endpoints.

We also use Microsoft Intune to automate device onboarding with predefined security baselines and app deployments, so new users get a fully secured and ready-to-use setup from day one.

The best features Microsoft Intune offers that stand out the most to me are centralized device management and policy automation since everything can be controlled from a single place. Strong security features including compliance policies and conditional access help protect data and restrict access to only trusted devices.

Policy automation in Microsoft Intune has saved a lot of time for my team by removing the need to manually configure each device as policies are applied automatically during onboarding. It also ensures consistency across all the endpoints, so every device follows the same security standards without manual checks. Additionally, automatic app deployment and update resources reduce repetitive tasks and keep devices secure without much intervention.

Microsoft Intune has positively impacted my organization by improving overall security posture, ensuring only compliant devices can access company resources and reducing risks from unmanaged endpoints. It also streamlined device management and onboarding, saving effort from the IT team and improving user experience with fast setup.

We saw approximately forty to fifty percent reduction in manual device setup time with Microsoft Intune as onboarding became fully automated. Security incidents related to non-compliant devices drop noticeably since only compliant endpoints can access resources. Onboarding a new user's device now takes less than an hour compared to several hours earlier.

Microsoft Intune could be improved by providing more detailed and easier-to-navigate reporting and troubleshooting, especially when diagnosing policy failures. The interface can feel a bit cluttered at times, and some configurations are not intuitive to locate.

Better real-time feedback on policy deployment status with Microsoft Intune would make troubleshooting much faster, and improved integration visibility across different Microsoft security tools would help manage everything more efficiently in one place.

I have been working in my current field for approximately two and a half years.

Microsoft Intune is stable, and I have not experienced any downtime issues; however, I have not encountered any reliability issues either.

Microsoft Intune's scalability is one of its strong points as it handles growth quite easily without needing major changes to infrastructure. In real-world use, organizations can manage thousands of devices smoothly through automation and centralized control. It is cloud-based, so as users and devices increase, I just scale licensing rather than worry about hardware limits, and policies continue to apply consistently across all endpoints. Overall, it scales well and is suitable for both small teams and large enterprises without much extra effort.

Customer support for Microsoft Intune has been decent overall, with multiple support options including documentation, chat, and enterprise support, which help resolve most issues. In my experience, basic issues get resolved fairly quickly, but for more complex cases, the response time can be a bit slow and sometimes requires multiple follow-ups. While documentation is helpful, it is not always up to date, so troubleshooting can take extra effort in some situations.

Earlier we relied on manual configuration and basic on-premises tools, which were time-consuming and hard to scale, so we switched to Microsoft Intune for centralized management automation and better security control.

We saw a clear return on investment with Microsoft Intune as device onboarding time reduced by approximately forty to fifty percent, saving significant IT effort. Support tickets related to password resets and device setups also dropped noticeably, reducing workload on the support team. Overall, it helps us manage more devices without needing additional resources.

We saw a clear return on investment with Microsoft Intune as device onboarding time reduced by approximately forty to fifty percent, saving significant IT effort. Support tickets related to password resets and device setups also dropped noticeably, reducing workload on the support team. Overall, it helps us manage more devices without needing additional resources.

My experience with Microsoft Intune's pricing, setup cost, and licensing is that pricing is reasonable as part of the Microsoft bundles, so the setup cost was minimal and licensing is straightforward. It can feel a bit expensive if you only need limited features.

We evaluated a few options including VMware Workspace ONE and MobileIron before choosing Microsoft Intune because it integrates better with the Microsoft ecosystem and is easier to manage in our environment.

My advice for others looking into using Microsoft Intune is to start with clear device and security policies before rollout to avoid rework later. Take advantage of built-in templates and automate onboarding to reduce device setup time. Test policies on a small group first to avoid unexpected issues at scale. Also, ensure you understand the licensing and integrations with other Microsoft tools to get the most value.

Microsoft Intune is a strong and reliable solution for endpoint management, especially within the Microsoft ecosystem. If planned and configured properly, it can significantly improve security, streamline operations, and reduce manual effort. I would rate this solution an eight out of ten.

Microsoft Intune policies, remote wipe, and using corporate and private profiles are valuable features, but MFA is the most valuable feature as it ensures that the end user is authentic. After authentication, logs can help us diagnose further. Previously, we didn't know who was using the devices, with every person having 3, 4, or 5 mobile devices registered to their email. We didn't know which device was live or not. With MFA, it is very helpful to identify which one is the last authenticated device. We can also restrict the number of devices using Microsoft Intune.

From an end-user perspective of Microsoft Intune, I haven't experienced any challenges since installation. However, some customers have reported experiencing slowness when using lower versions of the Android system. This observation has been reported to the distributor team, and they are working on it. Hopefully, this issue will be resolved in the next release.

As we have only been using it for six months, it might be too early to identify other areas for improvement. 

We recently started using Microsoft Intune. We just completed about six months of usage.

It is very stable.

We have plans for expanding our business at least 5 to 10% in the next financial year with Microsoft Intune. With most people opting for hybrid work and not coming to the office five days a week, working from home or branch offices, the requirement will definitely grow.

It is too early to provide comprehensive feedback regarding the technical support for Microsoft Intune. We have basic support included in the plan. We have not opted for the advanced support ticket facility. We haven't utilized support services as we haven't faced any issues in the last six months. Without any support scenarios, we cannot comment on response times or resolution quality.

Neutral

We were not using any other solution. The requirement for such a solution came from the data breach incident. After that incident, it was brought to our notice that we needed an MDM solution to protect our data. 

It's very smooth. It's done with two to three clicks. It's very easy.

After installation, Microsoft gave us a vulnerability assessment. Our IT administrators handled the necessary tasks based on the recommendations. The patch management, pushing of patches, and manually updating applications are helpful. They inform us when auto update is off, alerting us to turn on application updates when vulnerabilities are found.

We have not evaluated the measurable benefits since the deployment of Microsoft Intune. With only six months having passed, we need more time to observe and evaluate the returns.

It comes with the E5 plan. We bought the E5 plan from Microsoft.

From a price perspective, the E5 plan we opted for includes features we aren't fully utilizing. Our basic needs were offline Office for end users and cloud-based emails. When we inquired about MDM specifically, they offered separate plans, such as MDM Basic and others. We compared all options and migrated because paying separate license fees for Office and Microsoft 365 mailbox would be more complex. While it is somewhat costly, the major benefit is that we can select licenses only for those using personally owned devices rather than the entire organization.

We had an incident in our organization where we found a data breach in a mobile device, specifically on a personally owned device that employees were bringing in. To protect against this, we evaluated multiple products, including IBM, Microsoft, and ManageEngine. We chose Microsoft Intune as we were already existing Office 365 users. It was easier for us to upgrade the plan from our existing one to E5. It came with a bundle where we received all the services we wanted: private profile, secure download, prevention of sharing corporate data, and access to corporate data. It is easier for us to manage everything from a single console.

ManageEngine's MDM solution was less expensive and of good quality based on our evaluation. However, we couldn't proceed with it because their management console was different, and we were already using Office 365 with a 100 GB mailbox. Migrating all emails would have taken considerable time and risked potential email loss.

Microsoft Copilot is integrated with E5, and some users are utilizing it for writing emails and creating presentations. Copilot is an effective AI engine that helps predict known vulnerabilities and facilitates notification management and task scheduling. 

For endpoint protection, we use Acronis through a separate console, which we've been using for 3-4 years with satisfaction. We are not using Microsoft Defender Advanced Security as it cannot currently integrate with third-party solutions. 

I would rate Microsoft Intune a nine out of ten. It is very stable. The GUI is very good and efficient. Everything is fine. The only issue is with the Android devices.

As an administrator and user of Microsoft Intune, we have implemented several key features. Currently, we are using it for Windows updates across the whole company, pushing updates through Microsoft Intune. We also use it for the mass deployment of new applications.

Additionally, for security and access, we implement conditional access controls through Microsoft Intune. We have completed corporate device configuration and starting new journey on bring your own device (BYOD) management.

We use enterprise application management features in Microsoft Intune, with most applications integrated without multi-factor authentication previously. We need to control the number of devices accessing our environment to prevent data breaches or PII issues.

The most useful features in Microsoft Intune are the policy enforcement and conditional access. These features make our operations easier from a company perspective. Each company has its own policies, which are often only written in documents. By using Microsoft Intune, we can enforce these policies throughout the organization, binding everyone together instead of just having documented policies.

Microsoft needs to strategize its licensing structure. When using Microsoft Intune, we bought a small scale of controls, only controlling part of the devices, though Microsoft Intune can do much more. The Intune Suite offers more features, allowing extensive integration with either internal or cloud environments without requiring third-party licensing. However, each feature has a separate license, making logistics and cost management difficult if not strategically bundled together.

I have been working with Microsoft Intune for at least 2 years.

I would rate technical support from Microsoft a nine out of ten.

Positive

We previously used System Center Configuration Management (SCCM). With SCCM, out of 10,000 staff members, only 2,000 to 3,000 received updates and deployments. The updates were slower, and using SCCM caused more network congestion as updates were pushed through the internal network. With Microsoft Intune's cloud-based deployment, users can receive updates and application deployment almost everywhere, and they get updates almost daily. This keeps machines up to date and helps reduce vulnerabilities.

It's easy. In terms of cloud, I am mainly focusing on Azure. There are other divisions that handle AWS and also Huawei Cloud.

While managing Microsoft Intune, we experience some glitches in our hybrid environment with on-premises Active Directory. If the on-premises system has an issue, it can synchronize to the cloud with additional problems. This requires resolution on both sides, which is difficult. It's not Microsoft Intune's fault; it's due to our environment. For companies wanting to use Microsoft Intune, it's better to avoid a hybrid deployment and join everything to the cloud.

In terms of automatic updating with Microsoft Intune, users sometimes complain about needing to restart for weekly updates. Updates are automatically pushed to devices for security purposes. Microsoft Intune helps us manage these updates automatically, unlike SCCM, which requires manual work.

We conducted workshops with Microsoft to ensure we hosted management internally instead of paying third parties. We mobilized our internal team, which has allowed us to avoid additional costs related to external services.

All security solutions worldwide are expensive. Microsoft has allowed a small scale of features within Microsoft Intune for cost-efficient solutions. If you want the full suite, you need to invest more to gain better security features. It's not necessarily more expensive. You need to choose which features to buy. For basic features, Enterprise Mobility + Security E3 (EMS E3) is the lowest pricing Microsoft can offer.

We plan to explore Microsoft Intune Cloud PKI more, as it's not just a replacement for the CA server on-premises. It's a game changer for SSL certificates, eliminating reliance on third-party solutions such as GlobalSign and DigiCert. We plan to implement Wi-Fi with certificate integration, though this is currently just a vision, as we need to purchase it.

Microsoft Intune focuses on device management, including MDM (mobile device management) and MAM (mobile application management). Microsoft Intune can control various devices, but we currently focus on four operating systems: Android (with Google Play Store) and iOS for mobile devices, and Windows and macOS for computers. Our recommendation for Microsoft Intune would be to use it for managing device resources and ensuring policy enforcement according to company guidelines. Each device must maintain current security to prevent attacks or vulnerabilities.

I would rate Microsoft Intune an eight out of ten. I recommend Microsoft Intune and suggest purchasing it along with Microsoft 365 Suite or Azure, as the Intune Suite is essential for managing everything from antivirus to policies and accessing the environment.

We use Microsoft Intune as an MDM solution for all of our Windows laptops and some of our company mobile phones. This serves as an endpoint solution we use so we can control the users' laptops or phones and have access to things on their devices.

Without Microsoft Intune, there would be a lot of cybersecurity attacks happening. We need to use Microsoft Intune so we know which devices can access all of our company resources. If they don't have Microsoft Intune, we automatically deny them from accessing company-sensitive information, so it serves as a layer to protect all of our assets.

I appreciate how easy it is to deploy certificates to end users to get control over their device with Microsoft Intune; that's what Microsoft Intune is known for, and that's what we use them for.

The user experience of Microsoft Intune is pretty easy. Initially, the user has to download a certificate, so when we first give them a certificate to download, they download it on their side, and once they verify themselves, we have access to their phone or laptop, which works pretty effectively.

We are using Microsoft Copilot with Microsoft Intune. Microsoft Copilot helps us with the deployment of Microsoft Intune. Previously, things were more difficult to manage, especially when certificates expire, as they need to be pushed out every year. Sometimes we forgot that, and then people's laptops stop working, so Microsoft Copilot helps us stay on track.

Microsoft Copilot is equally as important as Intune. The go hand in hand as it works in conjunction with Microsoft Intune to affect the deployment process.

Microsoft Intune can be improved by making it even more seamless for users to download their certificates. Currently, we have to push it out to their laptop and they have to do some work on their end, but if we could integrate it so it's seamlessly done and the end user doesn't even know that Microsoft Intune is on their laptop and it's just naturally there, that would be even better. This is especially true for Apple devices, such as Apple phones, where you have to push it out and the user has to accept or deny whether Microsoft Intune can have access to these applications. If it were easier for us to do it automatically without getting permission, that would be beneficial, but in today's environment, we have to get permission to access data.

To make it a perfect ten, it would be helpful if there was a better way to troubleshoot user issues, as I've had a few users with corrupt files before and had to redeploy it without knowing the root cause.

We have been using Microsoft Intune for eight years.

I would rate Microsoft Intune a nine out of ten for stability and reliability. We've never really had any issues with it in the past, and if we have, it's maybe one or two random people where their certificate is corrupt or something's wrong, so we just need to go back and redeploy it, which is not really a significant issue.

Microsoft Intune scales very effectively with our growing needs. The only requirement is more licenses, so once we get more licenses, we're able to deploy them more quickly.

I haven't needed to contact customer service or technical support, which is a good sign. Since I haven't had to use them, I have no experience with their quality of service.

Positive

We did not use a different solution. We started with Intune.

My experience with the deployment of Microsoft Intune was good. Initially, I didn't know much about it, so I had to review all the documentation, complete training, and watch videos to get familiar. Once I got a grasp of things, I tested it on my phone and laptop, and when it worked, I felt comfortable deploying it to more people. I eventually deployed it to about 7,000 machines as it scaled up.

The biggest return on investment for using Microsoft Intune comes down to protecting security. We are protecting all of our assets and using it as an endpoint MDM solution, which fulfills our needs.

Microsoft Intune costs about $7 per user per month, which is somewhat on the pricier end. That said, it's a reliable product, so it's fair. If it were less expensive, we would be able to roll it out to more people, so it's definitely something we're considering.

We use Microsoft Intune for Windows products and Jamf for Apple Mac products. I'm not sure if Microsoft Intune works for Macs. If they do, that's something we'd be interested in exploring.

I prefer Microsoft Intune because Jamf is not the most reliable solution based on my personal experience.

We do not use Microsoft Intune Suite's cloud PKI.

We also do not use the Enterprise Application Management features of Microsoft Intune Suite.

I haven't examined the Advanced Endpoint Analytics in the Microsoft Intune Suite yet. That said, we do have it; I just haven't had the opportunity to review it.

I rate Microsoft Intune a nine out of ten.

I have several use cases for Microsoft Intune. The first one involves a company with 300 Zebra devices that wants to secure these devices and provide a better experience for end users. Microsoft Intune has a significant advantage because it is free, and when you combine the advantage of security with a free package, it creates a powerful solution for a company.

I have several clients today using Copilot. Microsoft has changed the name of Microsoft Office to Microsoft Copilot for users. I have already used and implemented several use cases of Copilot. I believe that for a company to succeed with Copilot, they must have good change management in place. If you don't have clear objectives and defined use cases, Copilot is very difficult for users to adopt.

What I appreciate most about Microsoft Intune is the design and simplicity for an administrator. If you use it for the first time, you will not encounter many difficulties. The terms of Microsoft Intune are very simple with Android and iOS options, which is a significant advantage. The second advantage is that it operates in the cloud, allowing you to work anywhere and anytime with only an internet connection. You can work in Microsoft Intune from New York, Australia, or around the world. You don't need a VPN or other complications. I have worked extensively with VMware Workspace ONE, and while it is simple, if you require high security with Workspace ONE, you must have a VPN and a company computer. With Microsoft Intune, you don't need a professional computer; you can work as an administrator with your personal computer.

Using Cloud PKI is a significant advantage for securing devices. Today, with so many devices in the world, if you want to control your mobile phone, it is necessary to deploy a certificate on the device. In Microsoft Intune, you can enroll any device, and deploying certificates is a very strong security feature.

What I dislike about Microsoft Intune is the time it takes Microsoft to develop a feature. Microsoft takes a long time to develop features for clients. Microsoft Office does not have much reactivity for the client because clients want features quickly, but Microsoft takes considerable time. I have clients today who are migrating from Domino to Microsoft and from Google to Microsoft. When the client requests a feature, Microsoft agrees, but it takes a long time—one year, two years—while the client needs the feature immediately.

I have used Microsoft Intune for seven years. It is not only Microsoft Intune but also Microsoft 365 and extensive work with Microsoft Intune, though I don't use only Microsoft Intune exclusively.

Microsoft Intune has never crashed for me. It always works without fail.

Microsoft support is very straightforward. You have support available, and you can call or send an email. I have already had tickets and have not experienced any significant problems. I have had issues with VMware Workspace ONE support where they did not provide good answers, but that was a different product.

I have contacted Microsoft several times. I currently have multiple tickets. One ticket is for a new feature that Microsoft deployed in the console, but it is not active. The feature is displayed, but it doesn't work, so a ticket must be opened. I believe I have approximately one ticket per month, which is not difficult or hard. The quality of support is good. If I compare it with Workspace ONE, the quality is very good. If you want to rate it, I would give it a 9 out of 10.

Positive

I have used VMware Workspace ONE and MobileIron by Ivanti before Microsoft Intune. These are the three solutions I have used: Microsoft Intune, VMware Workspace ONE, and MobileIron.

For deployment of Microsoft Intune, I believe a project chief is necessary, along with an administrator and a consultant. Three persons are required to deploy Microsoft Intune. You don't necessarily need many persons because you don't have servers to manage; it's all in the cloud. You don't have to manage servers or file data servers. All functionality is in the cloud. Previously, a company might have needed 10 persons to manage Workspace ONE, but with Microsoft Intune, you need only two or three persons. For a company, this is a significant advantage. In my company, Le Groupe Novah, we are a reseller of licensed Microsoft products, and we are the first reseller of IBM products.

The pricing for Microsoft Intune requires consideration. If you use Microsoft Intune, I believe it is necessary to use all Microsoft applications. You want to use Microsoft Intune with Microsoft Office, but if you use only Microsoft Intune, it is not a good deal for a company. You should use all Microsoft applications to achieve good pricing. For small clients, the pricing today is very expensive. In my company, where I work as an administrator of digital workspace, for small companies it is a very significant budget for Microsoft. However, a company with 30,000 users can achieve good pricing. But for a small company with 10 or 20 users, it will be challenging financially.

I have used Cloud PKI for Microsoft Intune certificates. I have used it with Microsoft Certificate Access by connecting Cloud PKI to Microsoft Intune. When you enroll a device and want to access Microsoft applications such as Outlook, you must have a certificate. I have already used this Cloud PKI configuration and have connected several PKI systems. My company has a partnership with TD SYNNEX, which is T-D-S-Y-N-N-E-X. My overall rating for Microsoft Intune is 9 out of 10.

I am using Microsoft Intune for device management, device enrollment, policy compliances, application management, patch updates, and security protection.

The user experience in Microsoft Intune is very useful for maintaining work-life balance. Employees are managing their work through the Microsoft Intune application on mobile devices and through Android. This is very flexible for employees who work in the corporate sector.

I am using Copilot in Microsoft Intune for the creation of policies. While writing policies, I use Copilot for Microsoft Intune to generate automatic tasks for these scenarios and conditions. This has been very helpful to the employees. In some organizations, it has been blocked for security reasons.

It is very easy to deploy Microsoft Intune because of the zero-touch possibilities. Without touching the device, we can manage our devices and configure the device policies and required configurations.

Using the Microsoft Intune portal and the company portal, we are configuring the devices for both Android and Windows devices. For Windows devices, we are using Active Directory to Azure AD join. For Android devices, we are using the company portal for the configurations.

I am using the advanced endpoint analytics in Microsoft Intune for analyzing. Because of security threat allocations, through Microsoft Defender, we are getting the threat intelligence allocations. This is a good built-in feature of Microsoft Intune and is very beneficial from a security perspective.

Microsoft Intune has almost all of the best features. For current situations and scenarios where almost all employees are working from home in a hybrid model, this tool is very useful for device management. This is a very good tool for device management without any restrictions, and we can manage our security data. The best thing about it is that it is a cloud-based device management tool.

As of now, no maintenance is required for Microsoft Intune. It is a very easy and understandable tool. For migrations, sometimes we experience some issues with OS deployment and the user experience side. It would be better to implement something on the GUI side.

The GUI in Microsoft Intune is perfectly good, but they are updating the terminologies. The application terminologies are changing. It would be good to use an updated version so employees can easily understand the terminology.

I have been using Microsoft Intune for four years.

I would rate the stability of Microsoft Intune very highly, as I see no downtime anywhere. Sometimes we need downtime because we need to update our portals and our software. The downtime is managed well, and that is good. No changes are needed.

Microsoft Intune is scalable, and I am giving it a nine rating.

I would rate the technical support of Microsoft Intune a nine.

Positive

It is very easy to deploy Microsoft Intune because of the zero-touch possibilities. Without touching the device, we can manage our devices and configure the device policies and required configurations.

As of now, Microsoft Intune's pricing is in the middle range. I think many people worldwide are using Microsoft Intune, and education institutions are also using it. It would be better to reduce some costs. Like Azure, in Microsoft Intune, we are taking the subscription on a monthly basis. If we are using it or not, it will automatically expire. My suggestion is to charge based on what we are using and for how long we are using the service.

Deployment of any OS or application in Microsoft Intune will take one or two hours only, based on the size and capacity of the application.

In my current organization, most of the members are using the client application of Microsoft Intune. In the client application, almost five thousand members are using it from my client in my project. Almost one hundred thousand devices are using Microsoft Intune.

The enterprise application management in Microsoft Intune has been very useful. When the automatic update option is selected, applications are automatically updated when the application company releases updates. We have the option to update, and if they release update features, they automatically update. Otherwise, they stay on the same feature which we deployed. This is better.

I do not have any objections to Microsoft Intune. It is a very recommended product and very useful. Microsoft Intune is a must and should be needed for this time, for this hybrid model period. The product is very useful, and I highly recommend this product for employees, education institutions, or device management. I would rate this product a nine overall.

My use case for Microsoft Intune includes managing a fleet of about close to 800 laptops and another 500 mobile phone devices like iPhones. We migrated to Microsoft Intune to control and reduce the MSP cost, as our provider was very old-fashioned. As the solution architect, I create plans to ensure cost reduction and process efficiency, particularly regarding Windows patching. 

There wasn't any visibility regarding our devices. Most of the time, we couldn't tell which devices were turned on and which weren't. This lack of clarity resulted in delays with patches, as some devices were not powered on. Overall, it was a mess. To address this issue, we centralized everything into Intune, and we've been handling the patching process since last year. Additionally, we removed Bitdefender and whatever version we were using, and we implemented BitLocker.

From Microsoft Intune, everything is automated. If you need to get the keys, it's super easy for users to obtain them, and someone from IT should also be able to access them. We use Intune because it supports a hybrid environment, allowing us to manage both on-premises devices and our cloud-based services. This means we can still utilize our Active Directory organizational units (OUs) through Microsoft Intune's policies.

Eventually, we plan to migrate everything to Microsoft Intune. However, if we acquire another company that is behind in technology, we might still leverage the traditional Active Directory approach. This would involve integrating their domain into ours, while at the same time continuing to use Microsoft Intune.

We work in the agricultural supply chain, but we prioritize technology. We have the world's fastest terminal for grain loading and unloading, located in Vancouver, Canada. We operate our own trains and are responsible for nearly 20% of Canadian grain exports.

I find Microsoft Intune most valuable for its user-friendly automation and ease of use compared to other tools. We also started using Azure Windows Update Manager for our servers. Microsoft Intune is automated, where you don't need to be an Active Directory guru to manage OUs. This ease has significantly improved our patching process, allowing users to have options on whether they want to receive updates immediately or delay them, which enhances user experience compared to when we used other tools that forced reboots during meetings. With these improvements, I estimate we've reduced our patching costs by over $100,000 a month, as the MSP previously had to troubleshoot various issues manually.

To improve Microsoft Intune, I suggest enhancing reporting capabilities, including better visualization and more export options for deeper analysis. Integrating Power BI reports would be beneficial, as it currently requires manual API interaction rather than having straightforward pre-built reports.

I have been using Microsoft Intune for about two years now.

I have an issue with my MSP who is providing Azure service and other things. I used to work at ExxonMobil, where when you called or sent an email, you would receive a response within an hour. However, with Microsoft, it takes a lot longer, and I’m not getting quick resolutions. Sometimes, I find myself bouncing around between different support groups. I believe that for smaller clients, there should be a special support system in place.

Neutral

We were previously using McAfee for security. At that time, we didn’t have Microsoft Intune. After we transitioned to Microsoft Intune, we used it to encrypt our devices. As a result, we removed Bitdefender, which was the McAfee equivalent, and started using the Microsoft version instead.

I was involved in the initial setup and deployment of Microsoft Intune. It depends significantly on how the initial Active Directory was configured, and we faced considerable challenges during the registration of a hybrid setup, as hybrid configurations are complex. While cloud setups are easier, hybrid is more cumbersome. It requires knowledgeable consultants or an adept IT team familiar with all features and registrations. Through three months of trial and error, we reached a setup that works for us.

We have a cloud engineer. We also have some analysts, so about four or five people were involved.

With these improvements, I estimate we've reduced our patching costs by over $100,000 a month, as the MSP previously had to troubleshoot various issues manually.

I've heard that they might take it away from the E3 license and charge us separately. I'm not sure if it's true or not. My E3 license covers Microsoft Intune, so I think we're good.

Microsoft Intune does not yet bring all endpoint and security management tools into one place as we are still integrating everything. We haven't yet started using Microsoft Endpoint Protection and are still relying on other tools such as Tenable.

The user experience with Microsoft Intune has improved significantly over time. When I started, there was a learning curve, but I find Microsoft to be consistently better than other vendors. I might be biased as I'm essentially a Microsoft shop being a Microsoft certified solution architect with six different certifications from Microsoft.

Using Microsoft Intune alongside Microsoft Office and integrating tools via Graph API allows for seamless extension within the Microsoft ecosystem, while integrating third-party tools can complicate management. My experience with Enterprise Application Management in Microsoft Intune includes managing some applications, although we haven't yet started with dashboards to show downloadable applications.

We use Microsoft Intune to manage Windows 11 upgrades, which proceed smoothly. With Microsoft Intune, I am managing devices, including mobile devices such as iPhones, but I plan to incorporate security endpoints soon, possibly next year. We conducted Windows 11 upgrades recently since the deadline for Windows 10 licensing is approaching. This project initiated last year with the focus on drive encryption, followed by transitioning rules from OU to Intune, and we are now proceeding with Windows upgrades.

We use the cloud interface of Microsoft Intune only, without utilizing any SDKs yet. 

I would advise adopting Microsoft Intune as soon as possible. It's crucial to manage a multitude of devices since efficient patching is essential for security. Outdated devices pose vulnerabilities for hackers. Microsoft Intune is a leading tool in this regard, as it passively pushes updates with minimal user intervention.

We currently have only our managers utilizing Co-pilot in Microsoft Intune by activating it specifically for them. I am familiar with Co-pilot, and I am also a manager. I have heard that the licensing for Microsoft Intune may be separated from the E3 license. Currently, I believe that my E3 license covers Microsoft Intune, enabling us to operate without concerns.

I would rate Microsoft Intune a nine out of ten.