Microsoft Intune Reviews

The solution is deployed on cloud.

Autopilot is a great feature. Most users are looking for zero-touch deployment. 

There are many things that could be improved in Microsoft. Reporting and troubleshooting for the application deployment could be better. It's very difficult to understand. 

It's also very difficult to monitor where exactly the error is and the kind of scripting we're trying to deploy. PowerShell scripting is even getting a delay compared to other applications or policies. Usually if we deploy the configuration profile, there is an immediate sync and it will be applied to the devices, but it's not happening on PowerShell. This is an apparent option for PowerShell that is not working properly, so that again needs to be rectified. The reporting is a major drawback in Microsoft in Intune. They're not properly reported on the console.

I have about seven years of experience with Microsoft. I have been working with Intune for the past four years.

The solution is stable, but the reporting steps could be improved. The product has been released for more than six years, but some complete information is required.

The solution is scalable.

Technical support is very active. We used to interact mostly with Microsoft, so we had a lot of issues from the Intune side, so we were often troubleshooting steps. The technical side is pretty good. Whenever it's required, they will immediately schedule a call. I would give them a 9 out of 10.

Initial setup is of average difficulty. It requires a lot of people. We need to have an Azure AD license, so some AD integration is required. A kind of firewall is included.

In Jamf, it's not like that, so we have a single console and we can implement it. But here, we have multiple because it can be integrated and co-managed. I can't say it is very easy to deploy. For very small-scale industries, then it's definitely easy if you have minimal user devices or user IDs. If you're looking to deploy the solution on a corporate-level, and if they have multiple tenants, in that case, it is definitely complex.

If you are looking for it to be co-managed, there'll be an SCCM and an AD team. Otherwise, one or two engineers is fine for Itune.

I would rate this solution 7 out of 10. 

If you are working as a SME, anybody can do the major part of troubleshooting and configuration. Even someone who isn't certified will be able to do the configuration and implementation part. Logs are required to troubleshoot.

Intune is the best tool going forward because everyone is moving to the cloud. If you have a cloud environment, it will be easy for a service provider to provide support. The solution can also be easily integrated to other tools.

There are so many additional features included in Intune that it's very easy for the users, corporate, and for companies to manage the devices. Even if the device is out of office, even if it is not domain-joined, it will be easy for us to manage for the client, or for the companies to manage it.

Our main use cases with Microsoft Intune are about how we automate the deployment. Auto-pilot is a feature that we normally recommend. Another piece is about the package deployment, where we recommend, or have helped, customers in deploying and converting their Win32 application. These are the two main areas in terms of automating the enrollment and Win32. Another use case in terms of the Apple, which is being used more by the customers, is where we recommend them to go for the zero touch process by using the AD.

Intune's feature that I have found most valuable is its auto-pilot feature. The main thing is that it keeps building it. Also Intune's capability in terms of Mac, which is slowly increasing, although the customers are moving towards vMOX and leaving the Intune just because of its limited capability with Mac, though it has already been enhanced. More features include the conditional access and the app production policies with respect to BYOR devices. These have been increased a lot in terms of security.

In terms of what can be improved, I am looking for better enhancements regarding Apple management, not only on the mobile device, but also on the laptop.

Other than that, it already has good capability with Windows, and it is already very good for the mobile device. The only area that is missing is for the Mac products.

I am using Microsoft Intune for the last two, three years.

In terms of maintenance, since it is a cloud product, it automatically gets updated by Microsoft. So there is no maintenance required for the upgrade part. But definitely the maintenance part that we track is the software asset management - that the devices are there and that the patches are deployed on a timely basis. We also do maintenance on the dashboard reporting feature in terms of whether the devices are compliant or not compliant.

In terms of performance, devices will be automatically enrolled and all the applications will be deployed. So it will be ready to use once they log in with their Azure-ready credentials. That is zero touch for them. In terms of having integrations in place with other tools, any issues they face will have proactive or automated actions to resolve their issues, instead of raising them and going through the long process of raising a ticket and the resolution.

Scalability is good.

In my experience, the customers who are mostly going for the Intune are small, medium and large companies. We have seen a mix. These days we have seen a large base of customers having more than one device. So it could be suitable for any size company.

Not too much to say on support. It is pretty fast. But in some of the instances we did not get much or a proper resolution where we had to troubleshoot a lot. But in most of the cases, support was good.

Initial setup is a simple process. It is a cloud solution. It is easy to deploy and easy to integrate with other tools as well. If we have to integrate with on-prem or Azure-ready through an AD connector, it is easy. Also, it is capable of integrating with other tools.

In terms of deployment, having things in the VM or physical VM or physical system in place and the ports enabled, as the main infrastructure is all in the cloud, is only part of connecting with the Azure already and the AD connectors, and does not take much time. With full testing, it takes one day if all things are in place.

Their price is really good. That is the reason customers move here, because as part of the Office 365 package, they always get the E365 as well, which makes it easy for them to manage their devices without having additional licenses for Intune.

That is the best part.

The main differences between Intune and other products are, like I mentioned, in terms of the Mac. If the customers are majorly moving and adopting Mac laptops while they are using the Intune, they are leaving for other platforms, like Workspace ONE and vMOX. That is the reason for moving and the major difference I have seen these last couple of months. But at the same time, if there is not much dependency on Mac devices, they are moving from other platforms to Intune, also.

My advice to anyone considering Intune would be to definitely test it and have devices enrolled at least in a pilot phase. They will get feature compatibility, the policies, and the auto-pilot feature. So, I would recommend to do at least a POC, and then decide.

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

We use it to manage our mobile phone in the business, and we also use it to manage our Windows PCs.

It's managed through our IT company, so they have the latest version. I have admin access to it, but I haven't had time to be in the portal so much.

We have one person based abroad, and it was a lot easier to get him standardized than it would be if we had to get his computer shipped down and configured that way.

For our office workers who are not based in Norway, when we order the PC, we can do some of the settings for them. These are standardized settings. We can set them up exactly as they are in Norway so that they're the same. 

The reports that are generated aren't so great. They don't give a lot of meaning so far, but that could be down to user knowledge than the actual reporting side of things. I'm not a big user of it, but I was a bigger user of MaaS360, and we used to be able to run weekly and monthly reports. In the case of any deviations. we'd get a warning immediately. That's not so easy to do or to get in place for Intune. This could be just a user issue, but when I compare both, that's the only thing that's lacking for me.

I have probably been using it for eight months.

So far, we have had no issue. We only have an installer for one user abroad, and he hasn't had any issues. It is stable there, and the phones also work fine. 

It is scalable. We can add more users, and there are no extra costs.

We're probably not the best users of it. We have one person based abroad, and we are probably going to have more.

We go to our own IT support, and they contact them. I'm not familiar with the deal that they have. They're a big IT team over here. They probably have an agreement, and they're prioritized in the queue for Microsoft Intune. There has been no downtime, and we haven't had any issues so far.

We've switched over from MaaS360 to Intune. We took the decision that Intune is better for Windows and IBM products.

I personally preferred IBM. I always outsourced the IT, but I preferred IBM. I liked the interface with IBM. I like being able to push out and seeing which updates were not available and which ones had to be pushed out. It was a lot easier to use. So, I preferred IBM, but I'm not really using Intune. It's outsourced to our IT.

It was quite extensive, and it took a few days for them to set it up.

We have outsourced IT for it. They did it themselves.

It's monthly for us, but it's built into the license cost that we pay our IT each month. It's maybe 129 Kroner per head, which translates to £10.

There are some additional costs. Our IT had to set up and configure their own server, so there is an extra cost for that, but I'm not sure what that costs.

I would advise setting aside the relevant time because it is time-consuming. It probably needs to map to all your devices so that you have a proper overview of all different applications that are needed on PC and mobile. I wasn't really involved in the migration. So, I only know what they needed, and from their side of things, I had to gather the information based on our MaaS360 database.

I would rate it a seven out of 10.

Mostly the pricing can be improved. If you are using the solution with EMS E3, then it's very expensive, but if you are using it in combination with a lot of products, then it can be cheap. Microsoft doesn't sell Intune separately. That's another consideration. The third thing would be how to view the use case because Microsoft doesn't release any documentation on how to view it when you adopt Microsoft EMS. 

Their technical support could also be improved.

It is very stable.

It's scalable because this is a cloud solution only. They don't have it on-premises.

With Microsoft technical support, they only fix Teams and when they are open, they're mostly trying to close again at the quickest time. Sometimes, the solutions given are not very good.

It depends on the use case. If you only focus on Mobile Device Management, then it is very easy to setup. You just have to define the use case in the context you want to protect. If you are talking about how to integrate with the lock analytics and how to classify data in context, then this is another thing.

The main difference between Intune and Workspace ONE is the quality integration between Microsoft products and Office 365, which means that Intune is part of a solution; you are not only using Intune, but you have to think about its ecosystem. For example, with EMS, it will have at least three products. The first is Azure ID Premium, which is the IAM solution (Identity and Access Management), so there are use cases where you might need to use IAM. The one difference between EMS and Workspace ONE, since Workspace ONE doesn't focus on identity management, is that it only has the access part. It can leverage all identity management, like with the directory or any of the identity solutions. 

The second difference is in the integration with Office 365 because in the Office 365 ecosystem, you have a lot of products, like Azure Information Protection, which is focused on the labeling and classifying of data. Microsoft also has Defender DLP and Defender for Endpoint. These make up a total solution. Based on that, if you have a long-term roadmap, you can actually integrate it with other Microsoft security solutions, like Sentinel, which is a SIEM solution. When choosing Intune, the main difference is the ecosystem and the roadmap.

I would rate this solution a nine out of ten.

For advice, it depends on the use case you are trying to solve here. If we have a look at the use case for security, how would you control the mobile? How would you deploy? How would you protect them based on that? The lesson depends on the answers to those questions.

It helps me to safeguard my identities in terms of conditional access. If a person is using it from outside the office, there would be MFAs that are mandatory. However, the moment they're inside the office, they're probably not using it. There are MDM features, which are my corporate-owned devices. It can be used for MA features and for BYOD scenarios. I have tested it on VPN certification authentication and it works in those areas as well. 

The dashboard is good.

We find the solution to be mostly stable.

The scalability is good.

We've largely been happy with technical support.

This product works very well for companies already using the full Microsoft suite. 

There could be some more security without compromising productivity. They could provide some advisories that alert you as to whether the device is secure or not. They need to be able to show us if there is something malicious happening or not. It would be really nice to have something there that could protect us from malicious activities or ransomware. 

I'd like more reports and KPIs available. We'd like these to be visible so users can be assured their devices are secure. 

The initial setup is a little bit complex.

I've pretty much used the solution since its inception. I've used it from 2012 onwards. However, since 2015, it rapidly began changing the nature of its utilization. I've used it for the last five or six years under this new utilization.

There is always a noise when you are going to manage any endpoint devices, and noise is definitely there with this solution. However, I would estimate it is 70% to 80% is stable. You have to manage it, have to face daily operational issues, which we are doing.

If a company needs to scale the solution, it can do so. It's cloud-based, which makes it easy to expand as needed.

We've used technical support in the past. We have given them feedback. They are good. They keep improving and adding. They keep giving more insights around it. I really like the approach overall that they have.

I am familiar with a similar IBM-based product. If you have a Microsoft-based suite, InTune makes more sense, however, if a company uses something else - such as Google - IBM may be more suited. 

At an enterprise level, it is always a complex initial setup. However, with the cloud, if you use that and you start from scratch, it would be pretty simple plug-and-play. That said, the moment the data comes in from the enterprise, there are complexities as there's only one system you are going to have to handle multiple devices and users from 300 to 30,000 to 300,000. It depends on how you are going to handle it.

For per device, it is not much work to set up the solution as there are only one or two apps that need to be installed. For policy conservation and many other things, you require some time to think about what needs to be done. You usually, for example, create the profile, which takes a month's time - or a month and a half.

You do not need much of a team technical team for the deployment. You just require a couple of experts - at least one or two - who have a good understanding.  We have around ten people involved in active management of it, and that includes a 24/7 support team to help manage different devices.

We are able to implement the solution for our clients. 

There is a per-user-based license and that is a licensing mechanism. You can pay yearly or monthly.

I'm a user and a consultant. I deploy this solution for clients and migrate to it.

If a client is using a lot of Microsoft, it's a great product to have. It integrates really, really well with everything. However, if a company has a non-Microsoft suite, I wouldn't suggest this as an option. Google and IBM also have suites that might have better solutions that would work for non-Microsoft users.

I'd rate the solution at an eight out of ten overall. 

If they are already using Office 365, or they use Microsoft Cloud Service for their office needs, and if they are looking to secure their endpoint devices. Microsoft Intune, in my opinion, would be a good fit for them.

If you are already a part of the Microsoft ecosystem, it's easy in terms of adoption.

The Microsoft Windows Autopilot and Defender policies are the most valuable features of this solution. 

You can manage your endpoint's security, as well as your antivirus. 

You can utilize Microsoft services to roll out updates to your Windows clients. 

The Microsoft ecosystem and integration with each other excites me.

Microsoft Intune is straightforward.

Microsoft leads the way in terms of the ease of use of its Windows management services. I would say that a large number of customers, roughly 60 to 80 percent of the industry median, are on Windows devices rather than Mac devices. 

Typically, which systems are used in the real world by their employees.

What it lacks in terms of content management, is the addition of a few more features. When it comes to new or updated devices, I believe Microsoft is still falling short. It lacks the features necessary to integrate these types of devices, such as handheld added devices, which are commonly used in the eCommerce industry. For example, RF guns are used for scanning. They are commonly used to scan eCommerce packages, which Microsoft Intune needs.

Intune is behind the game, but it has been catching up in terms of the capabilities and features that it now has to offer.

Mobile security needs to be improved.

There should be more focus on mobile device security and integration.

I have been working with Microsoft Intune for three years.

The stability of Microsoft Intune is good. I haven't seen many global outages. In terms of stability, Microsoft is the best at what it does.

In terms of scalability, I believe Microsoft Intune is scalable, but it needs to add a lot more features in order to catch up with the competition.

When you have a pressing issue, there is a lack of response. I believe Microsoft support needs to work on the response aspect.

The initial response and the time it takes to assign a particular engineer to work with the team to resolve the issue needs to improve.

There are no challenges with the deployment of Microsoft Intune.

It's not much of a stretch to say that it's simple to integrate with third-party services. In terms of integration, Microsoft is good.

Microsoft's licensing is more flexible and adaptive than its competitors. In Microsoft, you pay for whatever you use. In terms of services, it is more evenly distributed. You only need to pay for one license to get access to a suite of products. From your office to your endpoint, you are essentially managing your endpoint. Everything is combined into a single console. somewhat more flexible.

I would rate Microsoft Intune a six out of ten.

We use Microsoft Intune for mobile device and desktop management, more properly referred to as endpoint management. 

I cannot think of any particular features which I consider to be most valuable. 

I have not come across any bugs or glitches as yet. Microsoft M365 boasts phenomenal reliability and stability. 

The solution is easy to scale.

I had several questions for tech support while setting up the policies. They answered these quickly. 

Prior to Microsoft Intune we used IBM MaaS360, but switched because the interface and configurability is horrible.

We did not encounter issues with the deployment. 

The price is very reasonable.

The solution is totally cloud-based.

I would guess that our entire staff is using the solution, numbering 20,000. 

My advice to others is that they do their due diligence before going with the solution. But, I would say that it is at the top of the list when it comes to the competition. I believe that it is actually in Gartner's top quadrant at the moment for mobile device management. 

The solution's integrative abilities are fine. 

As no solution is perfect, I rate Microsoft Intune as an eight out of ten.

Effectively, we are using Microsoft Endpoint Manager, which is a mix of Intune and CCM. I'm not sure if there's a specific category for that.

We are using it mainly for the office workers, for the regular laptops. On top of that, we got our fairly specialized devices on our factories, such as the tag down Zebra Scanners, the RealWear glasses - the augmented reality ones and the kiosks as well. Those are the main use cases.

The solution offers very good integration with broader enterprise systems.

The scaling seems to be okay.

It works well if you have a Microsoft environment.

The solution allows companies to capitalize on costs, especially if they are a Microsoft shop.

The product needs better management support, for sure, especially between non-Microsoft applications. It would be good, for example, to have some Chrome OS support.

The solution requires baselines within the web console. That's something that is missing. 

They need better delegation capabilities in the reporting.

The solution requires Mac support.

We've used the solution for about two years at this point. 

Recently, the scalability seems not to be very good. There are minor incidents appearing quite frequently. Besides that, from an overall standpoint, compared to Workspace ONE, it's much more stable.

The solution is scalable.

We have about 70,000 users on it.

We are using this solution extensively. We use it for daily routines. It's one of our core services. It's used by our end-users.

We are increasing it. We are willing to extend it in the near future.

We are not satisfied with technical support. Some improvements might be required.

We did previously use VMware. We tried mainly to reduce some costs. This product seems to come as a part of a bundle, which slightly reduces costs. Also, VMware had plenty of functionalities that were not necessarily fitting into our landscape. We were not able to capitalize on the cost of the process. They didn't have any great integrations with broader enterprise systems.

The initial setup was quite straightforward.

We do not need much staff for the maintenance of the solution. It's pretty low maintenance.

Our team handled the setup. Our internet team did it. We didn't need any integrators or consultants. 

We have a broader enterprise agreement which is set up as a four-year period.

In terms of extra costs, there may be some infrastructure costs, especially for the on-premise part of the solution.

I'm a service manager right now.  I'm a little bit within the scope of the consultant versus the advisor.

We're using the latest version of the solution.

Potential new users need to strongly assess their needs. If they are already on Microsoft stack, they shouldn't look for any other solution than that. If their daily usage or utilization or needs are varied and they have a variety of devices, not necessarily based on Windows or other standard platforms, they might consider a different solution, especially if they need Chromebook support.

I'd rate the solution at a seven out of ten.