Microsoft Intune Reviews

My main use cases for Microsoft Intune are to manage devices, remotely wipe lost devices, and enforce device security.

Microsoft Intune has definitely reduced management burdens. It has helped us significantly. 

Microsoft Intune has changed my customers' abilities regarding app discovery, deployment, and automatic updating. They use it extensively.

The feature of remotely wiping devices in Microsoft Intune is what I prefer the most. When employees come and go, we can remotely wipe devices. This is what we primarily use it for.

In terms of the admin experience, it is straightforward, but the Windows enrollment experience could be improved. Sometimes, for enrollment, we have to reset devices and re-enroll them. Just configuring Windows, Azure, or Active Directory doesn't enroll the devices. We need easy enrollment for Windows.

Microsoft Intune can be improved by integrating Lighthouse and making it easier for partners to manage customer devices. They have remote help in Microsoft Intune, but they charge a license for it. For partners who manage thousands of devices, they should not charge, as it could be integrated with Lighthouse to provide remote support and better help customers.

It is at times slow. It takes time in the backend whenever we push out enterprise apps or reset devices.

I have been using Microsoft Intune for approximately five years.

Microsoft Intune meets my needs for scaling and is scalable.

It's good. We pay for premium support, so we receive good support.

Positive

We also experimented with Google's solution before choosing Microsoft Intune. The main difference was that Google only supports Chromebook and doesn't handle Windows, so we use Microsoft Intune for Windows.

The return on investment when using Microsoft Intune is good. It has been helpful for us and our customers. 

It's bundled with Business Premium and an E3 license, which is beneficial. If you have to pay extra, it's pricey, but with the bundled package, it's acceptable. They recently increased the Business Premium pricing, which we don't appreciate. The price increase and yearly commitment are causing some problems for us.

We considered TeamViewer. We went for Intune because it is included with our Business Premium licensing, so we don't have to pay extra for it.

I would rate Microsoft Intune an eight out of ten. To make Microsoft Intune a perfect ten, they could provide remote help for partners with Lighthouse, make it easier to enroll all devices, and make it faster.

Public Cloud

Microsoft Azure

Our primary use case for Intune has been securing our desktops. We now also use it to secure our servers, which started about a year ago.

Before, we used to reactively track down issues and fix security holes. Now, we're more proactive, stopping threats before they occur rather than reactively removing them afterward. This change helps stop the spreading of security issues.

Intune's integration with Defender and other security solutions is valuable because it offers a view into different security vulnerabilities and enables us to secure them more effectively. It's easy to use. There isn't a huge learning curve. It doesn't take long to get in and figure out where everything is. 

The application management feature's automatic updates help a lot, especially when we need to push updated scripts and apps to our desktops. We can update quickly instead of getting everybody to download and install it. 

Intune's server management could be better. If it could incorporate more features from System Center into Intune's Configuration Manager, it would be beneficial.

I've been using Microsoft Intune for about seven years.

There are no problems with Intune's stability. 

Scalability is great. We've had no issues scaling it across different environments, managing multiple Office 365 tenants and servers with no problems.

We used System Center Configuration Manager before moving to Intune. It's essentially an upgrade that allows us to manage both desktops and servers.

The initial setup had some issues, primarily with understanding scattered documentation, but it was resolved without much difficulty.

We deployed Intune in-house with our internal IT staff.

We are saving at least two or three hours a day since implementing Intune.

I don't have any information on pricing, setup costs, or licensing.

We did not evaluate other options before choosing Intune.

I rate Intune 10 out of 10.

We separate users on mobile phones from users on other spaces. 

I really appreciate the features in Microsoft Intune, including the Intune Suite Cloud PKI. 

The main benefits that Microsoft Intune provides for me include data safety.

My main pain point for Microsoft Intune is the contact part. Not all Android or iOS applications have access to integration, for example, contacts. 

Another area I would want to improve in Microsoft Intune is the pricing. 

I have been working with Microsoft Intune for four to five months as a new user.

I would rate the stability of Microsoft Intune as fairly stable.

I have no issues with the scalability and ability to expand Microsoft Intune.

I have never contacted technical support from Microsoft.

Positive

We solely work within the Microsoft environment. 

The setup of Intune is easy; however, getting used to it is not.

We purchased the solution directly from Microsoft. I find the price for Microsoft Intune too high, which represents an area for improvement in Microsoft's pricing model.

We did not compare the solution to any other vendor.

We are using SharePoint as object storage, and for file storage, we are using Azure for verification and authentication services. I would not be able to tell you more about what we are using on the back side, however, Microsoft Intune is being used.

I personally am not working with the integration of Copilot with Microsoft Intune.

I can recommend Microsoft Intune for everyone, whether they are small, mid-size, or enterprise-level companies.

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

Intune is suitable for everyone. It's good for companies of all sizes. I'd recommend Intune to other users.

Public Cloud

Microsoft Azure

I use Microsoft Intune for endpoint management. I administer Intune for many clients, and I also use Bring Your Own Device (BYOD) application protection policies.

The most valuable feature of Microsoft Intune is its scalability. It helps reduce hands-on IT support, especially with remediations. Since it is a cloud solution, there is no need for on-premises infrastructure to support endpoints. Endpoint Analytics is considered very useful, although it can be slow. Endpoint Privilege Management greatly increases productivity by allowing admin rights to be assigned to individual applications.

The platform is incredibly slow and could be more responsive. Specifically, when making changes to security policies, I would like to see those changes take effect more quickly.

I have used Microsoft Intune since more than 2019, so approximately three years.

For me, the deployment is not complicated, but it is a complicated process overall.

Microsoft Intune is generally stable but slow. I would rate its stability at eight out of ten.

I would rate Microsoft Intune's scalability ten out of ten. Being a cloud solution increases its scalability.

The technical support for Microsoft Intune is slow to respond and not great. I try to avoid using it because of its slowness. If you can get through to technical support, it is great, but the triage process is lackluster. I would rate their technical support five out of ten.

Neutral

I previously used Symantec Altiris. I switched to Microsoft Intune for native cloud support, as Altiris was not native at the time with cloud support.

Using Microsoft Intune saves costs by reducing the need for hands-on IT support. It has improved our ROI by lowering licensing costs due to the consolidation of vendors.

I rate Microsoft Intune eight out of ten because it is improving all the time. The biggest lesson is that all solutions must be integrated, especially in the journey to the cloud. It is important to keep up-to-date with changes in Intune to ensure all adaptations are utilized.

Public Cloud

Other

Currently, we use Intune for endpoint security and deployments. We're migrating from SCCM to Intune cloud-first technology. We use it to deploy applications, CSPs, and conditional access.

Previously, we used on-prem SCCM to deploy applications we built manually. After migrating to Intune, we automated and streamlined the process of deploying applications with Autopilot. I can do more with my day. I can manage more applications and ensure that they're updated without monitoring and manually starting that process all over again.

My director used to say that we need to have cattle, not pets. You need to care for and manage pets, but you only need to feed cattle and put them out to pasture. Once you deploy it, you just let them out to pasture, and they update themselves. It's streamlined and so easy.

I've been exploring the Intune Suite, which includes Security Copilot and enterprise application management. EAM is a godsend. I can manage my third-party applications without having to worry about it. I

I set up a proof of concept for the advanced analytics. It was very streamlined. I like the information I got from it. For example, when we were troubleshooting an application, it told me possible scenarios and commonalities between group one and group two and what could be the issue. It is great in that aspect, but we decided ultimately we didn't want to go with it.

We're still learning how Copilot fits into our environment and setting up a POC for Security Copilot. We're trialing Copilot for a subset of users to get a baseline of how we're gonna be using it. I use it to manage my day, meetings, teams, and chats. It keeps me organized.

There are challenges with Intune, specifically in reporting. Many third-party companies offer single-pane-of-glass reporting that shows you what your update environment looks like, how your patch is doing, application status, etc., but Intune's reporting is not intuitive. You can connect to Azure, monitoring, and the workbooks, but it's not streamlined. 

The user experience is still a little difficult. In the first version of Intune, everything is all over the place. It wasn't organized, and things weren't categorized. They changed the name in six months, and we had to relearn everything. 

I have used Microsoft solutions for about 15 years.

I am very impressed with the stability of Microsoft Intune. There hasn't been an instance where things just weren't working. While there may be service alerts or outages, it doesn't significantly impact our operations.

I rate Microsoft support five out of 10. Customer service is inconsistent. Sometimes, the support provided is excellent, and the representative is knowledgeable, while other times, the service needs improvement.

Neutral

We looked at Tanium and Recast for servers and management but ultimately chose to stay with Intune.

The initial setup was made easier with online resources. After setting up some basic components and connections, everything was interconnected seamlessly.

We used a consultant for further development after it was configured. CDW was used to help refine the setup.

There is a return on investment, particularly with the Enterprise Application Management and the efficient deployment features of Intune. It has given me more time in my workday.

Experience with pricing and licensing was challenging. Understanding Microsoft's licensing costs can require certification, making it difficult to know exactly what is needed versus what is available.

I would rate Intune seven out of 10. As much as I sing Intune's praises, I would like more improvements, especially in the reporting. We need to standardize how we use the solution. For example, just in October, we had the update rings completely fleshed out. Then, I went on vacation, and when I came back in October, it had completely changed with new names and new scenes. There are lots of strategic hoops to jump through, but it's a solid solution.

Hybrid Cloud

We do use Microsoft Intune internally in our company. We handle the distribution software, collect metrics for app usage, and create policies to make the device compliant for Microsoft Intune.

The features that we use very frequently include collecting information about the software installed and determining which software is allowed from our company or not. This is our main feature for now.

We have different departments in our company, and the configuration and distribution of Copilot is another team's responsibility. We use it, but we do not have any part of that process.

We handle the distribution software, collect metrics for app usage, and create policies to make the device compliant for Microsoft Intune.

The features that we use very frequently include collecting information about the software installed and determining which software is allowed from our company or not. This is our main feature for now.

The interface is easy, but it is not user-friendly when evaluating the overall user experience of Microsoft Intune.

The settings are confusing, and it is not always clear where I apply the configuration because we have to open various pages to see where we are applying the settings that we have configured.

We are using Microsoft Intune for about two years.

Microsoft Intune is acceptable and adapts well. I give it an eight regarding scalability.

The technical support of Microsoft Intune rates as an eight when rated from one to ten, where ten would be the best support.

We have addressed other questions and other possible customization, and it is satisfactory because our company also has support from Microsoft directly in our company. This makes it easy for us to ask questions and request features that can be useful in our company.

Positive

Before choosing Microsoft Intune, we did not evaluate other options other than BigFix.

The initial setup and deployment of Microsoft Intune is easy to participate in.

We actually used service technicians from Microsoft to deploy Microsoft Intune. We hired Microsoft technicians to do that.

The technical team from Microsoft are good technicians, and we can see that they are comfortable with the process.

Before choosing Microsoft Intune, we did not evaluate other options other than BigFix.

I am involved in solutions, and we have Microsoft Intune and BigFix in our company.

We are administrators and end users of this solution. However, it is not the priority application because our priority is BigFix.

We are separated into different areas in Microsoft Intune. We have many solutions in Microsoft Intune, but for now, we are only creating policies, managing devices, and installing software because other teams handle other configurations.

We are using Microsoft Copilot in Microsoft Intune. I cannot make any comments about whether Copilot in Microsoft Intune helped protect our environment because Copilot is another department's responsibility.

We had the BigFix platform before Microsoft Intune. We chose Microsoft Intune in the first place because most of our components and services are moving to Microsoft. Microsoft Intune is adding to all the services that we now have from Microsoft.

My overall review rating for Microsoft Intune is eight.

Our use case for Microsoft Intune is managing end-user endpoints, specifically Windows desktops. It is not limited to Windows desktops as it can also manage Mac OS desktops, laptops, and mobile devices for both Android and Apple iOS. 

In terms of needing Microsoft Intune to manage devices, first, there is a requirement that devices must be joined to an Azure domain, either hybrid joined or purely joined. 

From my perspective, purely joined is really the only viable way of setting up an environment. Once devices are joined to Azure, access to Microsoft group policy is no longer available. Because group policy is not accessible in Azure, another way to manage and control devices is necessary. This alternative method uses Microsoft Intune Windows profiles. 

When setting up devices using Microsoft Intune, Windows profiles can be established which perform most of the same functions that Microsoft Group Policy did in a local Windows Active Directory environment. Microsoft Intune can manage and control machines and install software. It allows for Windows provisioning on machines and enables autopilot deployment with pre-packaged installations. When a user receives the machine, sets it up, and turns it on, it connects to the domain and begins installing software, becoming ready within approximately half an hour, which represents a significant time savings for IT departments.

Companies using Microsoft Intune are much better at managing their endpoints with far more visibility. The endpoint inventory is far more accurate and up to date. The Windows versioning for the endpoints is much better, and Windows stays current. Companies not using Microsoft Intune still rely on manual or prior methods of updating and inventorying, which are subject to gaps and inaccurate information.

The Microsoft Intune management console provides visibility into the current status of machines and deployed software. It can automatically update components within its capability, primarily Microsoft products. Third-party software updates, such as VLC media player, are not within Microsoft Intune's update capabilities. Some companies, such as Adobe, have packaged their software to be updatable in Microsoft Intune, though this is more the exception than the rule. Installing software in Microsoft Intune can be challenging if it is not already prepackaged.

The stability and reliability of Microsoft Intune is good. Microsoft takes everything in, and if users stay with Microsoft, everything works together effectively.

Microsoft support for Microsoft Intune is good. In my own use of Microsoft Intune, I did not spend significant time with support because the Microsoft documentation was adequate for our needs.

In a prior environment, when setting up Microsoft Intune, we utilized a third party for assistance. They contacted Microsoft on several occasions, and their needs were answered sufficiently.

We have a couple of companies using other options besides Microsoft Intune. One company is using Avanti Neurons.

I rate the documentation for Microsoft Intune very highly, approximately nine or ten out of ten. One of our companies is beginning to provision and establish a Cloud PK to replace their legacy on-prem ADCS server. 

I used Microsoft Intune extensively in setting up, running, and managing it for several years. In my current role, I don't have hands-on management responsibility for Microsoft Intune as much as responsibility for ensuring it secures the environment from a cybersecurity perspective. 

From an IT infrastructure team perspective, the experience with Microsoft Intune is good, although somewhat complex to navigate initially. From an end-user perspective, the experience is good as long as the infrastructure team has done their due diligence in setting it up to remove any obstacles from the user's setup of their own machine. 

I rate Microsoft Intune a ten out of ten.

My use case for Microsoft Intune is to deploy applications and enroll devices, pushing the apps to the devices.

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

The integration of Microsoft Intune with Microsoft 365 and Microsoft security for cloud and co-managed devices is flawless.

Microsoft Intune works smoothly for discovery, deployment, and automatic updates.

Microsoft Intune helps simplify our IT and security operations as it takes less time, and it's easier to use than SCCM.

Microsoft Intune is flawless for securing hybrid work and protecting data on company and BYO devices.

We are using Microsoft Intune's endpoint privilege management feature. For enforcing least privilege access with Microsoft Intune, we use Entra ID. It restricts unauthorized access, requiring roles to be activated to proceed with necessary tasks, enhancing security.

Microsoft Intune has positively affected my IT productivity, as the decisions made at the enterprise level show it to be a more efficient way than SCCM.

In Microsoft Intune, everything is great. The interface is user-friendly, and the reporting tool works in real-time. Uploading the content is fine as well.

There is room for improvement in server patch management and allowing direct uploads of EXE applications instead of needing to convert them to Intune format, which would save time.

I have been using Microsoft Intune for more than one and a half years.

We have not experienced any issues. I would rate the stability of Microsoft Intune a nine out of ten. 

We have approximately 90,000 devices in our organization. We have multiple locations across various regions of the world. In our IT team, there are about ten people working with Intune, with plans to add more.

I would rate the technical support for Microsoft Intune an eight out of ten.

Positive

Previously, we were using MECM. The reason for the switch to Microsoft Intune is that the organization I work for has migrated to Intune. Microsoft Intune is far more efficient and faster than MECM. The deployment would take a lot of time in MECM; Intune is quite faster.

We are still using SCCM for cloud PKI as it hasn't been migrated.

Deploying Microsoft Intune in the cloud was complex as the previous work needed to be deleted and recreated, which wasted time.

Microsoft Intune saves about 10% to 15% of time. For example, deploying a 2 to 3 GB application at an enterprise level typically takes around one hour to one and a half hours, but with Microsoft Intune deployment, it gets completed in 30 to 40 minutes.

Microsoft Intune saves us around 10% to 15% in resources.

We are using Microsoft Copilot in Intune as an AI tool; it doesn't protect much, but it is handy for our users.

I would recommend Microsoft Intune to other users, especially those using MECM or SCCM, because Microsoft is ending support for older solutions.

Overall, I would rate Microsoft Intune an eight out of ten.

Public Cloud