Microsoft Intune Reviews

We deploy Microsoft Intune for clients and give them support for 

The main use cases for Microsoft Intune among our customers currently include migrating a client that was initially with Dell; they were using a Citrix solution along with other solutions. We migrated all the infrastructure on Azure, and they have almost 400 to 500 users. We have registered users' laptops and desktops with Microsoft Intune. I integrated them with Entra ID and Active Directory authentication. We are providing them support with managing all the devices, including their laptops, mobiles, and PCs with Microsoft Intune, along with all the policies and other configurations.

The most useful features of Microsoft Intune for our customers include centralized management; administrators can access all device reports, which devices are expiring MFA, which are not using MFA, device details, and other important information. All details about users and devices can be accessed through a centralized portal and dashboard. That is the main feature.

Regarding user experience, Microsoft Intune is very user-friendly. We need to register the device with Microsoft Intune through the Company Portal. When it's registered with the email, it comes to the management console on Microsoft Intune. We can manage all the devices from the portal, and users are very satisfied with no issues. They only require assistance with daily routine tasks, but otherwise, everything runs smoothly.

It’s already a strong application and management tool, and the team is continuously improving it. Everything is progressing smoothly, and our policy allows for certain configurations to be made easily.

There could be some improvements regarding additional features and integrations in Microsoft Intune. Microsoft Intune works with Entra ID. If there is an option for a client with 100 PCs or laptops that are not on the Entra ID domain, it would be good. It should work without a domain. Microsoft Intune works with the Entra ID domain, with the domain ID, with the email ID. There could be some kind of feature that supports a workgroup environment or a separate environment without the Entra ID.

I've been working with Microsoft Intune for five years.

Our customers have not faced any issues with the stability of Microsoft Intune; it's very stable. When they change devices such as laptops and mobiles, we need to register again and remove from the portal, their MFA, and other configurations. Otherwise, it is fine with no significant issues. It's very reliable and scalable.

In terms of scalability, Microsoft Intune performs exceptionally well. This solution is scalable. 

As technical professionals, we rarely need support. We handle issues ourselves, but whenever there's a need, we raise a ticket with Microsoft to get issues resolved and convey solutions to the client. If we have solved the issue through the Microsoft portal, we raise a ticket and provide the input from Microsoft to the client regarding what the issue was.

Our customers evaluated other tools before working with Microsoft Intune, as they migrated from ManageEngine and other management devices to Microsoft Intune. They saw advantages that led them to choose Microsoft Intune and Entra ID, so they migrated all the infrastructure and found it better than other management tools.

For tech-savvy individuals, the process is straightforward. You simply need someone with technical expertise to handle the portal, making device registration easy. There’s nothing complicated about it. 

Microsoft Intune is not too expensive; it is bearable for the clients and fits in their budget.

I would recommend Microsoft Intune to others. It is a very good and scalable solution. Every person, client, or company that has infrastructure with more than 100 or 200 devices will find it very easy to manage all their devices, mobiles, laptops, PCs, and network devices from the same dashboard and panel. All the information in the portal and dashboard makes it good for them.

I would rate Microsoft Intune a nine out of ten.

For my clients, I had to perform application management and device management on Android, Windows, and a bit of iOS. My last experience with it was a few months ago.

From my perspective, the best features of Microsoft Intune are that it is straightforward and easy to use, except when dealing with complex issues. Generally, you can quickly achieve good results, and it works well. It simplifies the lives of administrators when using deployment and all the policies that you can employ. Microsoft Intune simplifies the deployment of devices, making it easier than before when people spent more time deploying and mastering devices and phones. Now it is easier, and you have some good features to protect the company's data directly out of the box, which is beneficial.

In the future, I would like to see improvements in Microsoft Intune, especially related to policies and GPU. Something that reduces the need to dig through several menus and helps to find information more easily would be helpful. I also find it complicated for Apple devices since you need an Apple business number to manage them in Microsoft Intune, which requires contacting Apple or the reseller. There are some features that should be added to Microsoft Intune, especially concerning the CCM. Some features you cannot accomplish in Microsoft Intune are arriving each day, so I am not worried about this part. The engine wind process and the Win32 application packaging in Microsoft Intune could be enhanced.

I have been working with Microsoft Intune for several years, though not on a daily basis.

Overall, I assess the stability and reliability of Microsoft Intune as good. I do not remember having difficulties, except for local issues due to firewalls, which are not related to Microsoft Intune. Generally, it works.

Microsoft Intune scales well with the growing needs of organizations, as I have used it in large companies without specific problems.

Prior to adopting Microsoft Intune, I did not use any different solution for similar needs. The company I work for was already using Microsoft Intune, so I did not have to do a market study or check what other solutions could be available.

Regarding deployment, I find it acceptable. Once you have gotten used to it the first time, it may be a bit complex, but once you have done it once, it is fine. You can repeat it afterward, and the learning curve is low, so it is easy to use it and to learn and master it.

Microsoft Intune is cost-effective, providing ROI through the time saved for support teams and people working with computers. The security features that come with it, along with its complete integration with Microsoft, make it efficient.

Regarding pricing, I have no complaints about the price of Microsoft Intune for my customers as it is included in their licenses, and they seem satisfied with that. It is worth the license price.

I would advise other organizations considering Microsoft Intune to take their time and to test thoroughly. You have to be careful with security and device protection, but I have not encountered specific difficulties using Microsoft Intune. I rate this review an 8.

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.

We use it to manage our mobile devices. It is being used for security, compliance, and deployment.

The user experience is good; we could work and deploy many controls through Microsoft Intune. It is easy to handle.

Compliance and security policy setup comes with the tool itself. Co-management allows us to have a single platform to handle different devices such as domain-joined endpoints.

We need more granular level control on on-premise resources management. If we have more control on device-level configuration policy setup, it would be beneficial. Since the devices are configured over the Internet, whatever policy we apply from the compliance portal does not reflect immediately on the endpoint. The Azure AD joined endpoints take considerable time to see the policy. We need to implement some controls immediately, but it takes time to sync the endpoints and get the policy applied. That is one of the concerns. 

I have been using Microsoft Intune for the past four years.

It is stable. We do face challenges from the downtime, but it is manageable with the support service agreement. 

Microsoft Intune scales with the growing needs of my organization.

We do get support, but we struggle in conveying the issues to the right support team to address our concerns.

Positive

Before Microsoft Intune, we did not use another solution. This is the only solution we have used for Windows. Since we are using Windows devices, it makes sense for us to use Microsoft Intune to manage our Windows devices and control and apply the baseline policies set by the organization.

I participated in the deployment of Microsoft Intune. We didn't have any challenges.

We manage our MDM devices through our top direct configuration, which is the only option we have with our environment for managing all Windows MDM devices through Microsoft Intune.

Every module has a different pricing model based on the license and the options we choose. The controls are available, but the pricing varies for each module. If you want to have complete control, you have to spend more on Microsoft Intune with different licensing modules.

I have not explored any alternate solutions so far.

I am using Microsoft Copilot in Microsoft Intune along with other office products such as Teams and email. I have not used Copilot in Intune, but it can be leveraged for technology-related troubleshooting.

We have endpoint protection with EDR solution and detection and prevention. We are utilizing the Microsoft E5 license. 

I would rate Microsoft Intune an eight out of ten.

My use cases for Microsoft Intune are to secure our mobile license and our platform.

What I appreciate the most about Microsoft Intune is that it's quick and easy to use from an authenticator perspective. There is simplicity in securing our platform. Microsoft Intune benefits my company because of its simplicity of use and cross-functional integration.

The user experience of Microsoft Intune is good because of its cross-functionality and simplicity of use.

Automatic updating is pretty rough. It doesn't give me as much control as I had in the past. With no ability to control release cycles, it's been more difficult for major IT organizations. They can give comfort to those who are using the utilities with predictability on when new releases are coming. There should be more predictability in the release cycle.

We don't feel we have any control over when new updates come out, and whether there are changes to the backend functionality or to the user interface. Updates just happen. When updates are visible to end users, organizations get the call, not Microsoft. Since we don't have a good amount of communication about when those come out or what the new features are before they're deployed, we're caught flat-footed. We have to get to our reps to see what the updates were. A much more proactive communication cycle, aside from just putting it out on Twitter, would be fantastic.

They can continue to improve security. Factoring in all the compatibility pieces and security components, there's more improvement to be done outside of Microsoft-specific products themselves. There are multiple operating systems out there. It has gotten better in the last couple of years. However, the reason that RSA and this big conference exist is that we need to have some cybersecurity capabilities above and beyond the standard that comes with the operating system, so an industry has formed around it, and with that, we can get more focused on that part of the product specifically.

I have been using Microsoft Intune for approximately six years.

The reliability and stability of the Microsoft Intune platform are pretty good. I can't say the same thing about Teams, but Microsoft Intune is really good.

Microsoft Intune scales absolutely with the growing needs of my company. When scaling, it's great.

The technical support for Microsoft Intune is really good. I would rate them a ten out of ten.

Positive

We migrated from a mobile and endpoint solution to Microsoft Intune.

Deployment of Microsoft Intune was pretty straightforward and easy.

The biggest return on investment when using Microsoft Intune for me is inter-compatibility with everybody.

It's a bit expensive from a licensing perspective, especially as we look to have organizations with tenants across the globe. Whether in multiple commercial environments or as a clear defense contractor, there are times when we have multiple different user accounts, and we have to pay per seat. It would be great in the future if we were able to automatically associate those types of things within the licensing model.

Before choosing Microsoft Intune, we considered other solutions about six years ago.

I would rate Microsoft Intune overall a seven out of ten. They could continue to improve on the security aspects. 

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.

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.