Microsoft Intune Reviews

Being able to use it to control phones is the most valuable feature. 

It's a developing product, so there's lots of room for improvement. There's a lot of stuff we couldn't do because Google and Apple prevent you from doing a lot of the stuff you'd like to do. 

Microsoft documentation is a bit hard to get around, so having more control over devices would be good.

I've been using Intune for about a year or so.

We had no problems with stability.

It's hard to find the information to work out what you need to configure, but it's easy once you get to know how to work it.

The pricing is pretty good.

I would rate it an eight out of ten.

We use Microsoft Endpoint Manager for patch management and software and application deployment. We also use it to engage with the user to be flexible and encourage them to use our organizational tool in their home or country, along with Microsoft 365 features and VDI.

Microsoft Endpoint Manager's patch management has been the most helpful to us. However, Microsoft Endpoint Manager has a lot of features. We could use it for cost management, inventory, and security purposes. But, bottomline, its best feature is patch management.

No tool is 100% perfect. An issue we have run into with Microsoft Endpoint Manager is that we cannot patch third-party products like Adobe and Chrome with it.

I have more than 10 years of experience with Microsoft Endpoint Manager. 

Microsoft Endpoint Manager is scalable. We have not run into any issues. 

The initial setup was not easy for me.

The pricing is reasonable. Microsoft Endpoint Manager is not expensive overall, especially for small environments. But for enterprises with more than 6,000 or 7,000 users, it can start to get a little expensive.

I'm a solution architect. When I put up a new solution for managing devices, I prefer to put it on Microsoft Intune.

At the moment, Autopilot is the most valuable feature.

The main disadvantage seen today is regarding Linux clients. We have a lot of development resources that have Linux on their clients, and we can't manage them on the same platform, as we do with other clients such as macOS and Windows. So, it should have support for Linux clients. It should also have better support for macOS.

I have been familiar with it since it was released. 

It is very stable.

It is scalable.

It depends on the technology for which you ask them for support.

We are also working with VMware Workspace ONE. When comparing these two products, I prefer Intune.

It is simple. It is easier than easy.

It is reasonable. When you have Microsoft 365 E3 or E5 license, it is already licensed in that license. So, you could say it is free.

It is quite easy to get people who understand the technology. For other platforms, at least in Sweden, there are not so many technicians who understand the technology.

I would rate it an eight out of 10.

We use the policies and the features to quickly access devices and make policies for users working in another country, but their device is from Brazil.

The most valuable features are that users can make screenshots, and devices only need the minimal version of iOS.

The major problem with this product is that there can be delays in the deployment of new policies.

I have been working with Microsoft Intune for almost two years.

I would rate this solution as nine out of ten.

We are a system integrator who provides services to a variety of customers. I have provided this solution for a couple of my customers.

Microsoft Intune is primarily used to apply compliance requirements, install updates, and prevent users from sharing data because it is, part of the EMS, not just Intune.

For the price, the features included with Microsoft are appealing.

That is subjective because I haven't used anything other than Intune for MDM and MAM. We were fairly satisfied, I would say, but there are always a few things that our customers mention, such as this was simple.

Compatibility is another point raised by the customer. Microsoft is always a little behind when it comes to compatibility.  For example, Microsoft does not support Linux. or, any other platforms offered by other vendors.

The remote screen support and remote assistance were two features that we greatly missed in Intune. According to our customers who use Workspace ONE, it is available. For example, you can get remote assistance for an iPhone, which is somewhat reliant on a third-party solution, for Microsoft. We were not able to do that for testing purposes, we faced some challenges. We had to purchase an additional subscription from Teams Viewer.

Microsoft Intune lacks the ability to provide seamless remote assistance or remote control.

I have been familiar with Microsoft Intune for approximately three to four years.

Getting assistance from Microsoft is a difficult task, as we have noticed over the last few years that service is deteriorating. 

It's deteriorating in the sense that you don't get the proper resource the first time you call, message, or email. You should wait or inquire first. Normally, the person you are aligned with is usually someone who works on the front lines. On occasion, we may ask the support team to connect us with the appropriate individual or escalate the ticket.

This is my personal experience with Microsoft. I can't compare it to anything else.

Based on my conversation with my customer, they say that VMware Workspace ONE is easier to install.

While I have not tried to install VMware Workspace ONE myself, I don't find Microsoft Intune to be difficult to install.

No one can compete with Microsoft when it comes to price, and the features it is offering.

They bundle different things with EMS. 

EMS, which is a suite that includes Intune, along with some other products is still extremely competitive with other competitors. 

At the moment, I'm comparing it to VMware Workspace ONE.

I was comparing Microsoft Intune to VMware Workspace ONE, or EMS as it is more commonly known.

I would rate Microsoft Intune an eight out of ten, but when you add in the rest of the products, such as AIP and Azure Premium, I would say nine.

I use Microsoft Intune for mobile device management applications.

The solution could improve by having better integration with Apple.

I have been using Microsoft Intune for approximately two years.

The stability of Microsoft Intune is good.

We have 9,000 users using this solution in my organization.

The implementation was straightforward and it took approximately two months.

The reseller of the solution has helped us with the implementation.

We have five engineers that are maintaining this solution.

I would advise others this solution is easy to implement in the organization.

I rate Microsoft Intune an eight out of ten.

Compliance and the policies that can be set are the most valuable features.

It should be simplified. I've worked with many different mobile device management solutions, and Intune is one of the more complex ones. It could be more simplified, and some of it is related to the wording that is being used, such as a configuration profile versus a policy. They really should have had different names to make it less confusing.

I haven't really seen any negative on that yet.

Tech support is pretty decent for Microsoft. A colleague of mine had previously talked to them about Intune. As a partner, we also get counseling time with them. We get advisory services with them where we can speak back and forth with them on projects. We can ask them how would we implement it and what are the pros and cons. Sometimes, they came up with things that we weren't even thinking about or they confirmed what we were finding. I was on a call earlier this week, but it wasn't specific to Intune in this case. We found out something was not possible, and they confirmed it for us, which actually saved us hours of additional research. As far as I know, the advisory is only for partners.

One of the pieces of advice is to become very familiar with the cloud environment. In general, always think in the big picture, not just in the isolated issue or item that you want to accomplish. That's because Intune or Azure, in general, is just so over-encompassing. You really have to think about the big picture and not just about the simple project that you're trying to focus on. Otherwise, it will come back to bite you if you didn't plan it right.

There are some MDMs out there that are simpler and easier, perhaps even better to use. It also depends on the application. It depends on if you've got all Windows devices, all Apple devices, or all Android devices. It also depends on if you have a combination. If you've got all Apple devices, there are a couple of products out there that are probably the best MDM, but they won't help you at all with Windows or Android because they're not designed for that. Intune is trying to be all-inclusive to everything. In some ways, that's an Achilles heel too.

I would rate Intune a seven out of 10. 

Generally, we use it with banking, finance, or government entities, usually medium to large customers. We also have smaller customers who are dealing with sensitive private data and therefore are interested in running Intune on top of their Office 365 licensing.

I like the fact that it's integrated with the rest of the Microsoft products, so customers can manage it from their Office 365 portal or Azure portal.

If you could replace SCCM completely with Intune, that would be fantastic so that you don't have to run SCCM with Intune as an extension.

They could also make it easier to use because there are some other products that may be easier to use in terms of the look and feel of the dashboard.

The stability is quite mature here in Australia.

The scalability is quite good.

The technical support is really good. First level support is just your normal desktop level, but the second or third level is much deeper. It's pretty good

Usually, if I log a call in the morning, I may get a call in the afternoon to sort it out through screen share. Sometimes, it's someone in Shanghai that takes the call, and I speak Chinese, and they speak Chinese, so I'm pretty happy with that.

If the customer is already operating on a cloud environment, then it's easy, but if a customer has a hybrid environment, then it can be complex.

If they've got people who are now working home that previously used to work in the office and they still want them to use their work laptops at home, it gets complex. You would need to start looking at registering the devices into Azure AD, which then leads to Azure AD premiums. Therefore, you would need to find out from Microsoft whether to add the device into Azure AD, to register it, that you would also need MDM or an Intune license added on top.

If you're ever going to buy an Office 365 environment, then pricing is reasonable given all that it does, but if you're not, then you might find the pricing expensive.

I would recommend that they check it out thoroughly because things are moving very quickly with Microsoft, and we get better support now, given Australia's a hero country of Microsoft.

A lot of companies are switching to hybrid environments because of COVID, and Microsoft Intune can be deployed in a hybrid environment.

However, because Microsoft Intune doesn't totally replace SCCM, I would rate it at seven on a scale from one to ten.

We use Microsoft Intune to manage mobile devices or tablets, or Windows devices from anywhere. Intune is the best solution through which we can completely manage mobile devices and Windows devices. There are two options for that. We can manage or directly control the whole mobile device and provide security at the application level—for example, MDM and MAM.

I like that it's very good and very simple. I found that we just needed to have a proper subscription for an Intune tenant, and from the subscription, if we have the right role assigned, like the global admin role or the owner role, we can use Microsoft cloud resources. With the help of that, we can do many things like setting up Microsoft Intune in the cloud to create our virtual machines. All these can be done, and the steps are very simple. I really liked it.

I like features like Windows Auto-Enrollment. I like it very much because whenever you supply it to the end-user, it will be ready to use immediately. The end-user only needs to provide the user credentials, and then they are good to go. I also really like Cloud PC, which was recently launched on Azure.

The documentation about the custom image setup could be better. Although Microsoft provides the steps to configure Intune or set up or deploy Intune, it doesn't have much information related to custom images. 

If you ask, "how can we deploy the custom image?" There is no information. The steps they mention ask you to connect to your on-premises environment or create your own image on the cloud itself once there is connectivity. But I needed to go to multiple websites to get all this information. I had to figure out how to upload the custom image if you want to use the on-premise custom image for Cloud PC. If you have the proper subscription, you must have the right access, like global admin or owner. Then you can add your custom image to that. There are no steps mentioned over there.

Microsoft Intune doesn't have Chrome browser support. I would like to have that support because they will want it if we pitch the product to clients.

I have been working with Microsoft Intune for over four years.

It's definitely a reliable solution. They are also providing real-time security, and that's very good.

It's easy to scale up, and that's one of the major highlights of this particular product.

The initial setup is straightforward. To set it all up, we need to connect to the OEM and then provide all the hash information and more. Everything should be pre-configured on the laptop, and then the user is good to go.

We implemented this solution. Maintenance completely depends on us. It depends on what service we want. We have to decide if we want to manage it on our own or whether Microsoft should manage everything. We can decide that. We can deploy applications through the management console. If you don't want to take care of its backend, everything can be managed through Microsoft. That's very good, and I think it's very simple.

They have categorized the licenses according to the size of the business. So, if it's a smaller organization, we can choose the license accordingly. If it's a big organization, then we can choose accordingly. Everything is clearly mentioned, and we can decide. It's suitable for all kinds of infrastructure, and that's very good.

I would tell potential users that Intune is a very good product and everything is cloud-based. If you want, you can use it as a pay-as-a-service. That is also very good, and it provides a very simple unified platform to manage everything from the single management console. It also provides a report for many things like how many end-users are using it and what applications they are using. We get a very good report, and we can manage it very well. 

Along with mobile device management, you can also use it for Windows management. Microsoft has combined Microsoft Endpoint Manager, Microsoft Configuration Manager, and Microsoft Intune into a single console. 

On a scale from one to ten, I would give Microsoft Intune an eight.

We use this solution for mobile device management.

One of the main features of the solution is it allows the management of many devices in different ways.

When Microsoft Intune is used with different android devices it does not always work as it is supposed to.

The enrollment in Microsoft Intune is based on user accounts and not devices. It can be different to maintain different profiles for the same user. It cannot work together with other solutions. For example, if you have a normal user having a mobile phone, and they also have a tablet that they use that is managed from another MDM solution, such as Airwatch, the two can not cooperate if you are using the same Microsoft account on those two devices. They need to allow enrolment through the device IDs.

We have been working with this solution for one year.

The solution is stable.

We have not had any issue with the scalability.

We have approximately 7,000 users using this solution.

I do not think it is ever straightforward to use a Mobile Device Management System. Especially in our case, we were enrolling a lot of different devices that were already in use. That is always complicated and I do not think the fault is with Intune. It is complicated because Android can be used by different manufacturers, such as Huawei, Samsung, or Sony, and all of them can be very different.

I rate Microsoft Intune an eight out of ten.