Microsoft Intune Reviews

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 switched to Office 365 applications and we already had an Office 365 license that covers Microsoft Intune. We decided to use Intune for our Mobile Application Management solution.

I only use Microsoft Intune for Mobile Application Management for the management of Office 365 apps. Additionally, we have Microsoft Intune integrated with Workspace ONE.

We have used conditional access policies to prevent users from copying internal resources or internal data to external devices. This has helped protect our organizations from being compromised.

The conditional access policies that we set up are very useful.

Microsoft Intune could improve by being more user-friendly and having it geared toward device management. The graphic interface is not very good.

The VPN option within Intune is not as intuitive as the one available in Workspace ONE. We're trying to implement a VPN tunnel for SharePoint sites. This will allow users trying to access internal resources, such as SharePoint, and other Office 365 data, but it doesn't work as well as Workspace ONE. 

We are in the POC stage of the VPN tunnel. We only have a development tenant for the tunnel. We plan is to implement that in production and get rid of Workspace ONE, if it meets our needs.

I have used Microsoft Intune within the past 12 months.

The solution is stable.

I have found Microsoft Intune to be scalable.

We have over 5,500 users using this solution.

The technical support from Microsoft could improve, it is not as good as the Workspace ONE support. It is difficult to contact Microsoft support.

I have used Workspace ONE, and I would highly recommend it over Microsoft Intune.

The initial setup was complex, and the full deployment took us one year.

We did the deployment ourselves. There is little maintenance required, we have to only update policies. We have a mobility architect that set up most of the backend and we did work with a Microsoft resource for this process.

I have received a return on investment, the solution is inexpensive.

There is a license required to use this solution. However, it was part of a bundle package. 

Microsoft Intune is far less expensive than other solutions, such as Workspace ONE.

We are only using Microsoft Intune because it came with our Office 365 license.

I rate Microsoft Intune a five out of ten.

Our use case is relatively typical; we primarily use the product for managing Windows laptops, pushing policies, and some configurations. 

The ability to send configurations to our systems is valuable, particularly as we don't have a regular Windows AD server. Our current environment doesn't have a Windows AD, which limits our ability to push GPOs. However, this is where the solution can step in and help us push policies.

The reporting could be improved, as it's pretty poor compared to other products of this type. 

Patching needs improvement, as it hasn't been working well recently. 

We've been using the solution for over two years. 

The solution is very stable. 

The scalability is there, and it's automatically based on the number of users in the back end, so we don't even need to think about it.

The tech support is excellent, and I give them a nine out of ten.

Positive

At my old organization, we used Microsoft System Center Configuration Manager (SCCM), which is more of an on-prem system. Microsoft seems to have recognized that everyone is moving to the cloud, and I expect they will bring SCCM's capabilities onto Intune as a kind of product upgrade.

SCCM is a more versatile tool than Intune; we can't patch third-party applications in the latter, which is a significant headache.

The deployment was pretty straightforward; the solution came in a prebuilt configuration, and we just needed to enable it in our Azure domain.

As the product is cloud-based, we don't have to do any maintenance as a customer. 

Intune is available as an individual product, but it also comes with Office 365 Premium or an Enterprise license, and the price varies for each version. 

I rate the solution eight out of ten. 

Those considering the solution should look into it because it may already be part of your license or available with a small upgrade. Once upgraded, you have a tool and don't need to bring in another one. The deployment is simple, there is no other third party and no agents to be deployed. You also have a dedicated console that provides visibility and management, which is very easy to handle.

I am an IT support engineer. I take care of all IT projects in my organization. I have implemented Intune and onboarded thousands of devices over Intune. I'm not an end-user. I am supporting our employees with IT policies.

I can reach devices or computers over the internet. I don't need to worry about the network connectivity between the offices. I can manage any device. That is the most important part. 

The Mobile Application Management (MAM) policy is also valuable. I can control applications, and I can secure applications by using the MAM policy. It is very effective and very helpful in protecting our users' data on mobile devices such as iPhones, Android phones, etc. I can apply policies, and I can protect user data.

I can also deploy the software and applications and do configurations. Windows autopilot is there. It is like self-provisioning on employees' computers. That is also an important part.

The most important thing is reporting. They should improve their reporting. They should give a free hand to users. In SCCM, I can create my own reports. For example, in SCCM, I can create an inventory report for my PC or for all PCs, but in Intune, we don't have an option to create any report. Microsoft claims that Intune is a successor of SCCM, but SCCM is more powerful than Intune. So, they should develop Intune more and make it equivalent to SCCM. Then, their product will be great in the market.

If I want to deploy an application, I cannot add multiple schedules. I can add only one schedule, and I need to rely on that. Adding multiple schedules over a period of time is not possible at this time.

I cannot evaluate any setting before deploying anything. In SCCM, we have the Compliance Baseline feature. If I want to check any service or anything else, I can do that, but in Intune, that is not available. There are very few compliance policies. They say whether your device is compliant or not, but if they don't provide enough and better compliance policies, why should I be compliant with those policies? They should give more options for the compliance policies so that we can choose something better, and we can make our devices comply with those policies. 

It lacks in terms of analytics. Analytics and all such things are not good, which again comes down to the reporting part. It should be better in terms of analytics and reporting. 

It also lacks in terms of automation. If we want to automate some of the things, we need to spend more time on automation. Other tools in the market are giving better automation graphically. So, they can work on that part.

Their support should also be improved. They don't know about their own product.

I have been using this solution for the last six months.

It is very stable. So, whatever features they provide are working great. There are no problems with those features.

My experience with them was very bad. They don't know about their own product. I know better than them by going through their articles and other resources. When I ask them anything, they come up with silly answers. They are making me feel frustrated. I have had a very bad experience with their support.

Its initial setup is very easy. We don't need to deploy any servers anywhere. With just a few clicks, we can set up Intune. We just need to set the MDM authority, and we need to set the automatic enrollment. That's it.

Most of the mobile device management tools are giving the same facility. I don't have experience with VMware Workspace ONE, but I have been reading about it. VMware Workspace ONE also gives similar features in a slightly different way, but the objective of all such tools is the same. 

I would rate Microsoft Intune a five out of 10 because they are still developing it.

We use the solution to manage the Microsoft apps on company-owned devices. 

The product has eased the deployment of Microsoft apps to the devices. We can manage it properly. We can control it and push the updates. Another company helped us with the deployment. However, we can do it internally. 

Microsoft Intune's most valuable feature is easy management. It also keeps our devices secure. 

Microsoft Intune needs to improve the initial login process.

I have been working with the product for two years. 

Microsoft Intune's stability is good.

We have seen ROI with the tool's use. 

We don't have to worry about security after deploying Microsoft Intune. We can manage the security of our data and apps on the devices by using a single authentication mode. I will use it again if I have to make a choice. I rate the product an eight out of ten. You need to consider user experience when making the choice. 

Mobile device management is the main thing for which we are using it. My role is to review the implementation.

Mobile device management is most valuable.

We only have major classifications for iOS and Android, but there are different brands that have different cycles of updates. If they can fine-tune it to make it more brand-specific, that would be even better.

I've been using this solution for three and a half years.

It's stable. I'd rate it an eight out of ten in terms of stability.

It's very scalable. I'd rate it a ten out of ten in terms of scalability.

It was deployed for an environment with multiple locations. There are about 500 end users. Our clients are mostly small-sized organizations.

I'd rate the previous vendor with which we had the contract a ten out of ten. We now have a new vendor. They haven't yet started.

We used BlackBerry. We switched because that was getting outdated, and it didn't have all the features that Intune has. Intune is continuously being improved because of the cloud service.

I reviewed its implementation. It was straightforward. There were some technical difficulties in getting it started, but after we resolved them, it was easy. There were some architectural issues we had to resolve because we had legacy architecture.

It was a consultancy service that was provided by us. There were about five people involved. One was a specialist; one was an architect. There were two different engineers having different specialties, and there was a project manager.

We have an engineer who works on the maintenance. There is a team of two engineers to manage Intune as well as Office 365.

There were quite a few, but this was the main solution that we looked at because Microsoft solutions integrate well with other Microsoft solutions.

I'd advise getting rid of legacy stuff. You need to go to the new architecture and new OS. The infrastructure should be matching for the Intune implementation. Otherwise, you will have a problem. That's what we faced. We had to upgrade all our operating systems.

Overall, I'd rate Intune an eight out of ten.

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. 

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.