Microsoft Intune Reviews

Intune is a cloud-based solution for MDM and endpoint management.

The most important thing for me is the autopilot feature. Other products have this capability but they have to first integrate with Azure. Because Intune is a Microsoft product, you don't have to do anything explicitly to get this feature working properly.

Microsoft really needs to improve the reporting in Intune. It doesn't come anywhere close to VMware Workspace when it comes to their reports. I am sure that Microsoft will improve but at the moment, they are underperforming in terms of reporting.

There is a feature called dynamic groups, which populates users and computers based on a query that is written, and it runs at some interval. I would like to see this updated more frequently so that the users don't have to fair for too long before computers appear in the group.

I would like to see the ability to deploy custom packages as a Windows 64-bit package, as opposed to the Windows 32-bit, which is the only one available now. Although it can run in 64-bit mode, I would like to see this supported natively.

I have been working with Microsoft Intune for about two years. I have changed companies since that time and we are now evaluating Intune for use in my new organization.

Intune is a stable product and it has improved a lot over the past year. This is something that Microsoft is always working on, and I think that it will continue to improve.

We have not had the chance to test scalability. We will have the real results when it is put into the field.

I have not been directly in contact with the support for Intune. Rather, when I have needed assistance, I went through a partner channel.

I set up Intune without any assistance.

The price of Intune is included with the license for Office 365, so we don't have to pay anything extra for it.

We are currently evaluating both Microsoft Intune and VMware Workspace, and we will choose the one that best suits our use cases. Our plan is to implement one of these products in a couple of months.

One of the conditions is that we have to make sure that it supports all of the devices that we have in the enterprise. For example, we have Windows, Mac, Android, and iOS devices that need support.

Second, we need to have the autopilot experience for the users running under Windows. If somebody joins the company and they are provided with a laptop then we need to have it set up correctly. Normally, when it ships from a vendor such as Dell, Lenovo, or HP, it will come with their software pre-installed. Given the current situation with employees working at home, the laptop ships directly to where they live. At this point, with autopilot, they should be able to log in using their cloud credentials as soon as the device is switched on.

Once logged in, all of the details will be picked up from Azure, including the policies, updates, and other mandatory software such as Skype, Zoom, and Microsoft Office. Essentially, it eliminates all of the laptop setup and configuration that used to happen inside the organization.

Intune supports autopilot natively through Azure, and VMware Workspace is on par with this as well.

Next, it should have good reporting features. All products are able to generate reports, but we should be able to customize them in the way that we want.

We also have to have good security, where we can push all of the security configuration and policies that our organization has. This will differ based on the department. For example, security in banking or finance will be different from the security in manufacturing.

Finally, we should be able to deploy applications all over the cloud.

I think that in comparison, VMware Workspace is a more mature product than those offered by competing vendors. It has been developed very intelligently. The UI is good, with fancy graphics. They also have Smart Groups, and a different way of deploying applications, which are very good features.

VMware Workspace also has a slight advantage over Intune when it comes to managing multiple hierarchies. Intune does not support this type of structure, where you can have sublevels. For example, I can have a root-level like Europe with sublevels such as the UK, Germany, and France. 

The suitability of this product depends on your environment, requirements, and use cases. If you have a reporting-extensive company, for example, then you may need to look for other products. Similarly, if you are a multi-hierarchy organization with a presence around the globe, then Intune may disappoint you.

Given all of the factors and things to consider, including features and cost, I would say that Intune has a slight edge over competing products.

I would rate this solution a seven out of ten.

Primarily we are rolling the product out because we want to be able to have remote access and control over our desktops and laptops from external locations.  

The most valuable aspect of the product when it is in production is the basic thing it was made to do. We want to be able to allow access to various applications remotely which we can not otherwise do with remote workers.  

This type of question may be premature because we have just started rolling it out now. We have not had a chance to work with it to capacity at this stage. I think, so far the implementation is all a bit shaky and should be better planned and better supported. The deployment seems to not be as simple as what I would have hoped that it would be considering it is a Microsoft product.  

When it is fully rolled out, we will see where the other shortcomings actually are. However, this difficulty in rolling the product out is a significant stumbling block.  

We just started testing the product several months ago. The technical team is working toward trying to roll it out to production in about the month. As that is the case, we are not really using it yet in production. We have got only about half-a-dozen of the 4,000 projected users working with it currently.  

Again we have not really tested and deployed the product broadly across the company at this stage. But it is exactly because we have not seen the kind of stability and performance we were expecting that we have not completed the roll out.  

If we can not seem to get even half a dozen users working with the product in a way we consider stable, the scalability is in question. It should not be.  

As far as the set up, we only have the first half-a-dozen technical people on the product just to do a pilot. We have had issues with it. This is the reason we have not even deployed it for the users' space yet to deploy to a larger test group. I would expect the deployment would be a bit easier. That could eventually be a changing factor in what we do moving forward.  

I have rolled our company onto a 365 E5 licensing scheme. We are not on E3 anymore so we do not need to. With an E3 license, you would have to consider licensing the product.  

We did not really look at any other competition. We are a Microsoft 365 E5 customer and the product promises the capabilities that we need and is available without additional cost. It just made sense to try to use this part of the suite.  

On a scale from one to ten where one is the worst and ten is the best. I would rate Microsoft Intune as about a six. I am not totally impressed with the complexity of the rollout. 

We are moving from our parent company's tenants to our own, using the product to manage devices. 

I like the tool's integration with Apple. Anyone who creates an ID in Intune will get an Apple ID. 

The product needs to upgrade itself when the server is overloaded.

I have been using the product for a month. 

The product is very scalable. 

We have weekly calls with the Microsoft team, who are very attentive. 

Our parent company makes the deployment process very complex by using non-Microsoft tools. 

We rely on a vendor team to complete the deployment. 

The product is easier to manage and integrates with our ecosystem. It has made our organizational security posture simple. We can leverage the security policies in Azure and create our policies in MDM. I rate it a ten out of ten. 

It is used mainly for application deployment.

We are using it in our company and we also recommend it to our customers.

It has improved our organization a lot, especially because Intune is improving so much. It makes it a lot easier to deploy applications now, and there's less packaging work for us.

Among the most valuable features are the Company Portal that is built into Intune, and the update rings so that we can manage what types of future updates the devices get.

The solution could be improved by the opportunity to connect third-party application databases, such as Chocolatey or another setup store, to Intune.

I have been using Microsoft Intune for approximately four years. I have built approximately 100 tenants and I manage environments with roughly 20,000 workspaces.

The product is very stable.

It's also really scalable.

At my current job site, we have roughly 8,000 devices, which includes about 2,000 mobile devices, such as phones and tablets. They're used around the whole municipality. At that client, we are not looking to increase usage because they don't have many more workspaces, but our company is looking to get more customers and expand our usage of Intune that way.

The technical support is good, once you get somebody who knows what they're talking about. Reaching the right person is really difficult, but once you have the right person, it goes smoothly. It depends on the agent you get and which area you are connected to. If you're connected to a United States office straightaway, you will probably get better help than if you get connected to one of the locations in India.

Neutral

We also use Liquid. We are part of their development program and we helped them develop their software. We also have Liquid in the field, but that's mainly for use cases with social internet and launching applications from websites, which is a little bit more difficult using Intune.

In terms of deployment, what is difficult about Microsoft is that you need to have a broad knowledge of Azure and the other components because the endpoint manager is just a small part of your workspace. You need to have that experience and there's a lot of custom work for every single client. There isn't really an automated way, like a template base, within Microsoft, to fully deploy endpoint environments.

I help our customers with the design and deployment. Normally it includes making a list of all the applications they have within the company and seeing how much work it is for us to deploy an environment and how much application work is within it. In that way, we see which strategy fits them the best. Because there are a lot of on-premises applications that are really difficult to fit into a cloud environment, we will look to build more of a hybrid solution than a fully cloud-based solution.

We usually need three or four people for deployment.

Maintenance involves keeping up to date with the application. The only downside is that if you upload an application today, it doesn't download an update that comes out next week. That means you need to package and deploy it again.

We have most definitely seen return on investment in all of our projects. We still get a stable margin, but because of the price increases, it gets more difficult to sell it.

We don't get Intune as a separate module. Most of the time, we use it within an enterprise agreement like E3 or E5. Those licenses are at a good price, but what is annoying is that every single year they go higher. That makes it more difficult to get a company to take a full license. It will be really hard to manage, for us, if the prices keep going up every single year.

Currently, we pay €44 for an enterprise E3 license. There are no costs in addition to the standard licensing fees.

My advice would be to take your time and test what you deploy, due to the fact that sometimes a policy that you deploy with Intune can come into effect two or three days after a device is installed. Sometimes, testing for one hour is not really accurate. You need to test for a minimum of three days before you can actually see the results.

There are some improvements needed, but overall, it's a very solid product.

We primarily use the solution for both deployment and operating system deployment, and also as security for patching.

Its most valuable aspect is it is very connected with the Microsoft ecosystem. 

The solution is stable.

It has the capability to scale.

The monitoring and reporting are okay.

It's only good for a Microsoft environment. While it works very well for Microsoft users but if you have other kinds of operating systems, it's very painful to use.

They need to take into consideration the Linux operating system and not only the Microsoft operating system.

The solution needs better patching across applications.

I've been dealing with the solution for seven or eight years at this point. It's been a while. 

The solution is stable. The performance is good. There are no bugs or glitches. It doesn't crash or freeze. it's quite reliable for the most part.

In terms of scaling, it can scale more or less. It is scalable, however, you need a bigger infrastructure to achieve this scalability, which is not the case with other products.

Technical support is pretty good. We are mostly satisfied with the support on offer. 

We've used Microsoft Endpoint Manager and Ivanti Endpoint. With Ivanti, it's a much more open system for different kinds of IT infrastructure. Whatever the operating system, whatever the application, it's good. It's easier also to deploy as well. You don't need a big infrastructure to deploy Ivanti Endpoint. The ability of Ivanti to have an extension for the ITSM solution is good.

If you consider a Microsoft bundle in the operating system, it's pretty interesting in terms of pricing. If you're considering it as a standalone, it's difficult to sell, due to the price. 

We use both cloud and on-premises deployments. 

We're quite satisfied with this product.

I would rate the solution at a seven out of ten. We've mostly been happy with the product.

We're using Microsoft Intune for MDM (mobile device management).

It's also used for securing devices. This solution also lets you access your corporate data on mobile devices. You can secure and ensure that whatever data you're accessing and using from mobile devices is in a secure channel, that the data is between your end user and your cloud provider.

There are certain policies you can set up, that can go on both the device level and application level.

What I like most about Microsoft Intune is that it's agile and easy to deploy. I also like that it covers the maximum number of policies.

Microsoft Intune is doing well. They're adding endpoints, so it's good that they're covering that, and they're more stable. What I'd like to see in their next upgrade is more in the context of today's security policies and what's needed, for them to keep adding features based on that, e.g. boosting security, so they can keep on adding security features, and that is the best they can do.

We've been deploying Microsoft Intune to customers for four years now.

Microsoft Intune is a stable solution.

I find Microsoft Intune scalable.

The technical support for Microsoft Intune was knowledgeable.

The setup for this solution was straightforward. It was quick and it was easy, but it would still depend on the policies.

You have to pay for a Microsoft Intune license. It's a user-based subscription. You can go for a monthly or a yearly payment. It's up to the customer.

We have the maximum number of clients using Microsoft Intune. For deployment and maintenance, it depends on the customers and the number of devices they have, and the policies, e.g. they can have one, two, or three resources for deploying and maintaining this solution.

I'm recommending Microsoft Intune to people who want to start using it. They can go for it for one reason: the Microsoft ecosystem. My advice to people who are looking into implementing this solution is for them to know first what they want to achieve from it, before they make their decision.

My rating for Microsoft Intune is eight out of ten.

The primary use case is to manage devices that are dedicated to processing as well as managing work stations and sales devices. I'm an Intune engineer and administrator and I implement this solution.  

This is a great solution for anyone wanting a modern endpoint device management solution.

I'd like to see an ability to deploy more ways of management, managing devices and processing the policies. 

I've been using this solution for three years. 

This solution is stable. 

The scalability is good. 

The initial setup is very simple. 

Licensing costs are based on the number of devices being used. 

Indeed, it's a correct solution for any client who wants to use this modern endpoint device management solution.

I rate this product nine out of 10. 

We use it for mobile device management. 

Intune is on a public cloud because it works on Office 365.

It provides control over all mobile devices that are being connected to the corporate network.

Data leak prevention can be integrated into it. Currently, it does not have data leak prevention.

We have been dealing with Microsoft for the past three decades, and we have been using Intune from the time it came to the market.

It is stable.

It is absolutely scalable. It is for enterprises.

It is world-class. It is the best.

Its setup is easy. It is a Microsoft solution, and everything is easy with Microsoft.

Its price is in the medium range. It is acceptable because you're paying for the features. I am not aware of any additional costs.

It is a wonderful product. I would advise others to go for it. It is definitely helpful for an enterprise. It has been improving constantly. When they introduced it, it was only for Microsoft, and now, even Apple has been included. They're doing well.

I would rate it a nine out of 10.