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.

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.

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.

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.

We are using Microsoft Intune to check device compliance issues, enrolling, patching policies, and deploying applications in end-user devices. We check device status in our Microsoft Intune portal. 

We are using managed policies through Microsoft Intune. We deploy applications through Microsoft Intune. We deploy Windows versions and patches through Microsoft Intune.

Microsoft Intune helps to maintain compliance, deploy applications in end-user devices, and patch Windows updates.

We are protecting our environment by implementing security policies through Microsoft Intune. We can create policies and manage them. We can block access in our users' profiles so they cannot access anything apart from the company site. We have also blocked sites. They cannot install any third-party applications. We have blocked that to secure the user's profile and the system.

The most important feature of Microsoft Intune is that you can patch or allow access to the end-user profile without opening the Active Directory in the jump server. You can access Microsoft Intune in a browser portal and access all functions. You can check all the details of the user's profile and system details. You can find out why a device is under non-compliance, check it, and find the root causes. You can also enroll devices at your own end. 

We can do any updates in Windows through Microsoft Intune. However, due to access limitations, we are unable to deploy certain security features on end-user devices. 

I have been using Microsoft Intune for the last one year.

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

It is scalable. I would rate it an eight out of ten for scalability.

We have a lot of clients with 800 to 900 users in multiple countries.

I would rate their support a seven out of ten.

Positive

The initial setup is easy.

Microsoft Intune does not require any maintenance from our end.

It is very safe. All companies are moving to the cloud, and Microsoft Intune has approximately 30% to 40% market share.

Microsoft Intune is the best solution available. We can connect with any device and handle all queries, which sets it apart from other tools available in the market. Most companies are ensuring that Microsoft is their partner as it provides the best solutions. Microsoft Intune is the most growing tool in the market currently.

All MNCs prioritize the security of their products, tools, and users. Microsoft Intune helps maintain this security by deploying necessary patches and implementing policies effectively.

I would rate Microsoft Intune a nine out of ten.

My use case for Microsoft Intune involves working in the breaking fixed line.  I receive tickets when customers encounter errors or have doubts about the tool. I can explain the tool to clients, or I'll analyze the error. For example, if someone tries to use BitLocker but their device doesn't encrypt, I start my analysis of the policy the client created and try to fix the error.

The best features of Microsoft Intune are Windows Update rings. This is superior because you can schedule updates for quality, security, or OS system updates. It is beneficial because we can schedule work hours or after work hours to implement the updates. It helps me better understand client issues and increase my response time to deliver solutions to problems.

The areas that have room for improvement in Microsoft Intune include the Autopilot process. The ESP profile could be easier to use as many clients complain about it because if we don't deploy the ESP, the Autopilot doesn't work properly. These two configurations should be together when you create the Autopilot profile rather than separated.

Another tool that needs modifications is script deployments. When trying to deliver PowerShell scripts in the organization to apply wallpapers, it's very complicated to see if they return errors or how they show in the devices. Changing that would help significantly.

I have used Microsoft Intune for a year and three months. I have been working for three years in the Microsoft line support. Before Microsoft Intune, I was the Exchange engineer from the support line too.

I have experienced downtime, bugs, and glitches. I rate it a seven because when we have bugs or instability in Microsoft Intune, we need to wait for the backend from Microsoft Intune to resolve issues and we can't deliver solutions to clients because we need to wait for action plans and related processes.

In my organization, I am the only one who works with Microsoft Intune. When I need to use my environment to test, I create approximately 20 users and start to deploy. In my role, I receive tickets from organizations that have thousands of devices requiring issue resolution in Microsoft Intune.

From one to ten, I would rate the technical support at a 10.

I cannot compare Microsoft Intune with other solutions or vendors on the market because the only time I saw Microsoft Intune work with another solution was when I received a ticket about Mac OS where the organization used MDM Jamf to manage devices and started using Microsoft Intune. They tried to migrate to Microsoft Intune. This is the only collaboration I have seen between Jamf and Microsoft Intune.

Microsoft Intune saves eight hours per day. During my work hours, I use my time to study and run tests on configurations I'm curious about and try them out in my environment.

The pricing for Microsoft Intune is very reasonable because organizations can pay without complaints. Microsoft Intune isn't sold standalone only. Organizations can buy Microsoft 365 Business Premium, which includes Microsoft Intune with the license. It's a reasonable price to use Microsoft Intune.

I recommend Microsoft Intune to other users because it's a great tool to manage the environment. You can use it on one machine to deliver it to others. When you enroll these devices, the IT professional's life becomes easier to manage these machines because we can do everything remotely. I would rate Microsoft Intune overall as a nine out of ten.