Microsoft Intune Reviews

We use Microsoft Intune to deploy the software to Windows and iOS for the campus and to isolate any intrusion.

We can centrally control the software and the settings of the devices on the multi-platform using Microsoft Intune.

The most valuable feature of the solution is compliance. We have one MDM that works with Windows, iOS, and Android.

Microsoft Intune has a latency response time issue. The latency has room for improvement.

iOS devices have certain features that are not supported, which is not beneficial for end customers in terms of open deployment and device control.

I have been using Microsoft Intune for around three years.

Microsoft Intune remains stable if it is deployed correctly.

Microsoft Intune is scalable.

The initial setup is not complex. We started by setting up the environment on the cloud, then configured the devices and profiles. However, certain aspects of the deployment required the assistance of engineers.

The implementation was completed in-house.

I give the solution a seven out of ten.

We used Microsoft Intune because it is the only solution that can also support iOS.

In cases where a device encounters compatibility issues or technical problems preventing it from receiving the MDM profile, maintenance may be required. The maintenance is acceptable.

I recommend the solution to others.

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.

I use Intune for endpoint management. We manage our workstations via Intune because we have remote users on and off the corporate network. It's deployed across over 500 Windows workstations. We're also trying to incorporate cell phones, but we haven't reached that point as yet.

Intune reduces the load on our on-prem Active Directory by having everything go to one Intune panel. That way, we can configure group policies, deploy applications, and manage devices. It has really improved our operations. In the past, the device had to be on our corporate network, but now we can provision a device remotely.

I like the group policy management feature, which performs application monitoring and device enrollment.

It would be nice to have a location tracker for the mobile device management tool. I'm not sure if it exists but hasn't been configured or if it's missing, but we've been unable to utilize the location features.

I have been using Intune for about two months.

Intune is pretty stable. It's also great for helping us maintain compliance in our environment. If it's a hybrid deployment, you should be fine as long as the sync is running. 

Intune is easy to scale because it's in the cloud. There are no limits on what you can manage.

Microsoft support isn't too bad, but it depends on the department you called. Intune support is better than support for Defender for Endpoint. I would rate it about a six out of 10.

Neutral

I was previously using on-premise Active Directory with group policy management. Intune puts your dashboard and panels in the cloud, but they sync with the on-prem Active Directory. Most of the management is done from in the cloud. All we need is internet access to manage the devices.

Setting up Intune was straightforward. Microsoft provided all the materials we needed, and we had support from their team. We had about five guys working on the solution. It can be from one to five guys, depending on the scale of the solution. 

We went through the reseller.

The price isn't too bad

Yes, we've tried ManageEngine and SolarWinds.

I rate Intune 8.5 out of 10. My advice to future users is to perform a proper inventory before enrollment. This is essential cost-wise. You need a good idea of how much it will cost per month so you don't overrun your budget. 

Microsoft Endpoint Manager is simply a desktop, a laptop, a smartphone, or a tablet. An endpoint is exactly what it sounds like. Microsoft, on the other hand, makes use of that tool.

Endpoint allows you to deploy the operating system level. It enables the packaging and deployment of applications. It enables you to secure systems with BitLocker and incorporate things with Active Directory.

We are a consulting firm.

Our clients use it to simplify desktop builds and to maintain the patch management on their servers and desktops, as well as to have an easy mechanism for both rolling out BitLocker, which is a Microsoft tool and publishing new updates for their various software packages.

Microsoft is investing significantly more in the cloud. For our use and our clients' use, and again, our clients who use Endpoint number over 500, with an increase of 1,000 users. It is effective. It significantly reduces the overhead associated with providing support. It actually works quite well.

The installation could be improved to be simplified.

I have been working with Microsoft Endpoint Manager for the last 12 months.

We are Microsoft partners. 

We have been working for well over a decade with SCCM, and now with Microsoft Endpoint Manager.

They are deployed both on the cloud, and on-premises.

Microsoft Endpoint Manager is quite stable.

Microsoft's cloud has a capacity of 100,000 users. Depending on what you are dealing with, it's highly scalable, depending on how and where you deploy it.

It's from Microsoft. However, we are a Microsoft Premier partner. As a result, we are quite familiar with the product. Again, there isn't much of a need for it. However, our clients call us if they run into problems, which happens very rarely.

You do not have to maintain the Microsoft Endpoint that is built into their cloud, it's a cloud-based service. Locally, there is now maintenance every 16 months if you are deploying the local endpoint or creating a hybrid to Microsoft's cloud. You have to upgrade if you are deploying the local deployment. The current build changes every 16 months, but the upgrade is a very low skill set, you don't need anyone to upgrade it.

SCCM is no longer known as SCCM. It's known as Endpoint. Microsoft no longer recognizes that product. Endpoint refers to both the local and cloud-based installations. And, prior to their acquisition by Dell, we were a long-term partner with Quest. We've had clients use Quest products, but we haven't.

According to Microsoft, SCCM is no longer in use. Microsoft Endpoint is the new name for the current build. You can now deploy an Endpoint structure locally or pull Endpoint from Azure.

SCCM is no longer active.

I have worked with both Microsoft Endpoint Manager as well as Quest in the last 12 months. We have clients running the Quest Software.

The most recent Quest software we've seen is the Exchange PTS, or mail migration tool. That is probably the tool that we've had clients deal with twice. However, that is apples to oranges in comparison to SCCM.

It is the mail migration utility. According to my understanding, Quest recently sold that to a different company. So it's an old Quest product.

The initial setup is complex.

You have to appreciate two points with Microsoft Endpoint Manager. Microsoft Endpoint is based in Microsoft's cloud, 365 Azure. And Microsoft has simplified it quite a bit. They also work well with Intune. Many of their services are complementary to the solution. Autopilot is being sent out. You can have a machine auto-built from a remote location, or you can order an Autopilot deployment from your HP, Dell, or Lenovo. They've simplified it considerably since the old days, but there is still a technical element. For those with a technical nature, it is quite simple. Anything is simple if you understand the product.

You should probably consider cloud deployment before local deployment because Microsoft has made significant investments in the cloud. The local deployment is still in place. Microsoft's cloud comes with a lot of extra features that are free of charge. Furthermore, if you deploy it locally, you must own SQL, whereas, in the cloud, SQL is not required.

I would rate Microsoft Endpoint Manager a nine out of ten.

We are deploying and rolling all kinds of devices - our laptops, our tablets, our smartphones. We are using it locally here in Holland, in the Netherlands, and we are expanding the use to all business units abroad.

There are a lot of features and use cases. We can use it for health status, access control, deploying, et cetera. There are many features for using it.

Technical support is good.

We have found the solution is capable of scaling.

The stability has been good.

It should be easier to define policies and comply with those policies.

The initial setup is complex.

We aren't lacking any features at this point. 

The stability is good. We haven't had issues. There are no bugs or glitches. It doesn't crash or freeze. It's reliable. 

As a SaaS, it's scalable. However, we don't really work on scaling it up.

While the solution is pretty ubiquitous, most people in the company don't realize they are using it. While the custodians use it, the end-point users are unaware of it.

Technical support has been helpful and responsive and we are happy with the level of service on offer. 

Previously, we used MobileIron. Some of our business units also use Cisco Meraki and several others. We are working towards using one or two globally. We're moving to Microsoft as part of our larger global strategy.

The implementation process is very complex due to the global use of the product. It started small. They used naming conventions just for the home country, so we had to deal with redesigns of the naming conventions for global use. Yeah.

In terms of the deployment itself, it's software as a service. The product itself is immediately available, however, onboarding devices is a huge effort. That's mostly the case at this moment. We used Microsoft Intune, before that we used MobileIron, and we did migration for MobileIron to Intune, so we had a quick start originally. 

We renewed our contract with Microsoft about a few months ago. It's pretty simple to renew. We have various licenses for Microsoft including, for example, for Office, Defender, et cetera. I'd rate the pricing and ease of renewal at an eight out of ten.

The solution is a SaaS and therefore, we are on the latest version of the solution right now. 

I'd advise new users to start with a good, high-level design, functional design, from about the naming of conventions, policies, categories, device categories, et cetera.

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

I am using Microsoft Intune for supporting clients with mobile devices.

The most valuable feature is the policy CSPs.

The closest Microsoft Intune can be to GPOs, the better. There needs to be more granularity on application deployments. However, they have done better recently with the application deployments.

I have been using Microsoft Intune for approximately seven years.

Microsoft Intune is scalable. You can add Defender ATP and other inbuilt features.

The technical support from Microsoft is not good, they take a long time to respond to a case and they do not update you on what is happening on a case.

I've been on multiple deployments. The range from the pilot can take from a couple of weeks to a full-scale deployment, which can be a couple of months to a year. The longest I have been involved in was eight months.

The clients pay for a license and each can have a different type of license, such as an E3 or E5.

I have found sometimes Microsoft Intune does not work and it can be very unresponsive.

The honest truth is that Microsoft Intune is the future. Even though it's not the finished article, because it changes every week, the earlier you adopt it, the fewer hassles you will have down the line. The more you wait, the bigger the problem you might end up having trying to migrate.

I rate Microsoft Intune an eight out of ten.

We use this for management of all mobile devices.

We would like to see support for Chrome and/or devices for Chromebooks.

I have been using this solution for about three years.

The solution is stable.

The solution is scalable. We currently have tens of thousands of users within our organization using the solution.

I think customer support is quite good, we have enterprise support and premier support agreements.

Initial setup was straightforward.

Potential users should run a proof of concept. This can be done easily because Microsoft is offering a free trial period of one month.

I would rate this an eight out of ten.

We primarily use the solution for mobile device management and security controls.

The most valuable aspect of the product is data loss prevention. That's really a benefit of the platform in general.

The solution appears to be stable and scalable. 

The biggest improvement could be in the implementation, the ease of the implementation of it. They should make it easier to order it, however, that's generally true for everything from Microsoft.

I'd love to be licensed in Microsoft. I'm trying to do that, however, I can't find a training program that will fit with my schedule. Everything requires you to be on-site for a week, as opposed to on-demand training. A big improvement would be having some on-demand training that is quality and not just a sales pitch.

I'd like to see mobile device wiping to be better. That feature is a critical feature. If that could be enhanced, I would be grateful.

We've been dealing with the solution for a year and a half to two years. 

My understanding is the solution is stable, however, I can't say if that is the case for enterprise-level deployments. 

The solution is scalable to a point. I don't have a good insight on enterprise-level deployments and therefore cannot speak to how much it can scale.

I've never reached out to technical support. I wouldn't be qualified to comment on their level of service. 

The initial setup can be a bit difficult. I'm not certified in any way for Microsoft. 

I cannot speak to how many people are required for deployment or maintenance tasks. 

I'm a managed service provider. We work with a distributor who's a reseller. We have clients that use this product regularly.

I'd advise new users to do their research on Microsoft products and understand what's included and what's not included in the packages they already have.

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