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.

We use Microsoft Intune for controlling and managing all of our in-house and remote devices. It allows us to deploy applications to all devices.

The most valuable feature of Microsoft Intune is having all our devices compliant with our policies.

The solution can have some compliance problems in general and the end-point user can bypass easily the company policies in Intune.

I have been using Microsoft Intune for approximately three years.

I have not had any problems with the stability of Microsoft Intune.

The solution is deployed for end users and all of our devices.

Microsoft Intune scales well.

I have not used the support from Microsoft Intune.

I have not used a similar solution to Microsoft Intune.

The solution is worth the money for us.

We have the business premium licenses for the solution.

I rate Microsoft Intune a nine out of ten.

We're an MSP, and our primary use case is for fleet management; our entire fleet is handled through Intune, so all our mobile devices are logged in through the Azure portal, and we can manage our apps that way. We've been able to lock down our devices and control our field of frontline workers.

The solution allows us to keep track of an extensive device fleet so we know where they are and whether they're secure and compliant. Those that aren't compliant enter a pool, and our tech staff work to rectify that. Intune improved our organization by helping keep our data secure.

The security-related tools are excellent; these features allow us to secure devices, lock them down, and ensure compliance.

Due to the abundance of features, there's a lot to organize, which makes managing and setting up the solution challenging. The setup is immense, and it would be good to see improvement in this area.

The stability could be improved. 

We've been using Intune for around six years. 

Intune is a stable platform for the most part, though Microsoft can still make some improvements in this area. 

The solution is very scalable. 

Microsoft has slow technical support; getting through to anyone typically takes a day or two. Once we get through, then the support is good.

Neutral

The deployment is relatively straightforward; we send out an email, and our users click the link; it downloads the tool to their phones, and they can log in using their credentials. If it's set up correctly, then the deployment is easy.

The solution requires a small amount of maintenance; I have one full-time member of staff to maintain 420 total devices split between two of our clients. 

The cost is handled through our Office 365 license, so I have yet to be able to compare it directly with other tools in its class.

I rate the solution seven out of ten. 

My advice to those evaluating Intune is that you need to know Azure. This isn't a product you can jump into without prior Azure knowledge.

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 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.

When using Microsoft Intune our main focus was on Office 365. Our Azure Active Directory was only held up for users. When we had implemented the endpoint user management in our workstations in a cloud environment, then we started to use Microsoft Intune on an everyday basis, such as remote connection, deploying workstations, Autopilot, and deploying applications. It is a great tool.

Microsoft Intune is a cloud solution. For an on-premise solution, you have SCCM from Microsoft. However, it is old and it will be an obsolete tool soon. There are other solutions such as ManageEngine. Microsoft Intune tool is in the cloud and we can manage everything. You can manage Azure AD, Intune, and not only mobile hand devices, such as iOS or Android, the main focus is on workstations. This is what makes the solution powerful.

I expect Microsoft Intune to have more features in the cloud because there are two major functionalities that we need to be added. This is software metering and license management. These functionalities, for now, must be on-premise. For this purpose, we have set up a SQL Server and I hope that in near future this option will be in the cloud in Microsoft Intune.

I have been using Microsoft Intune for approximately two years.

The stability of Microsoft Intune is great.

Microsoft Intune is highly scalable. When you configure your network connection, there are a lot of firewalls and you can optimize your internet speed. Everything works great. You can tune up some repository sizes with Microsoft because if you have large applications, such as AutoCAD, when you upload the images to the cloud it takes some time and it needs more space.

We had four people in my company that used Microsoft Intune on approximately 100 systems.

The technical support of Microsoft Intune is good.

I previously used BEAM for client management from an American company and SCCM from Microsoft. Additionally, I used ManageEngine and Lansweeper. Lansweeper was a light tool with similar functionality. We use it in combination with TeamViewer.

We have projects all over the world. It took us four months to implement Intune Microsoft Intune for approximately 100 clients in three countries. We implemented it in many locations, such as Germany in three cities, Croatia, and Bosnia, there is a total of 50 locations. Microsoft Intune is easy to work with.

The initial setup is not simple, you need a specialist to be involved that has the appropriate experience. This is not a solution where out of the box you run the executable file on your system and hit next, next, to finish the installation.

Microsoft Intune requires specialists to implement the solution. We used an external team of two engineer specialists that was dedicated to the project. I helped too because I have experience in plant management.

There is a license required to use the solution. If you're core users in Office 365, for example, you have Outlook email and E3 license, this is only email. You have to buy an EMS license to have Microsoft Intune. It is expensive.

I would recommend the solution to others.

I rate Microsoft Intune 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.