Microsoft Intune Reviews

We use Intune for device management to ensure mobile devices such as laptops and tablets comply with our organization's regulations and requirements. We have some on-prem resources and operate a hybrid, primarily cloud-based environment.

We have seen many benefits from using Intune, especially in security. We have fewer company data leaked to the public as our security is tighter, and our company network is safer.

The ability to wipe data from and reset devices is one of the most important and valuable features. If a device is reported stolen, we can freeze it or wipe the data from it, preventing data leakage.

The solution offers excellent visibility into all devices connected to the network and whether they are safe or compromised.

There are some issues using the solution with macOS and iOS, and it offers limited granular control with them. Intune works better on Windows and Android. 

I've used the solution for two to three years as an end user and an IT admin.

Intune is very stable. 

The solution's scalability is excellent, though it could be improved regarding macOS and iOS.

We've reached out to Microsoft technical support many times, and they have always helped resolve our issues promptly and efficiently; I rate them ten out of ten.

Positive

We previously used Microsoft System Center Configuration Manager (SCCM) for group and on-prem policies, which we also pushed out to devices. We switched because Intune is more modern and cloud-based, so it fits our organization better.

As an IT admin, I was involved in the deployment of Intune as a consultant. The implementation was very straightforward as we're an experienced team of security professionals consisting of two IT admins and an IT manager. There was also a test environment for our benefit, and moving that over to a production environment was seamless.

We carried out the implementation internally. 

We definitely have an ROI with Intune, and the benefits are compounding. Security is a non-negotiable area; our business has to be secure, and our sensitive company data has to be protected from malicious actors. The security of company resources is always an ROI for the business, so it's essential.

The product is relatively pricey, but considering its benefits, I'd say it's fair. The benefits outweigh the expensive licensing fees, especially for large organizations, but medium-sized and smaller businesses may be unable to afford it.

We didn't consider other options; we wanted a Microsoft product, as it's great to add to our existing suite of business applications, and the integration is more seamless than it would be with third-party products.

I rate the solution ten out of ten. 

We implemented the solution to solve security concerns; users access our company resources from outside the network, and we must ensure the devices they connect from are safe. As an admin, I have complete visibility into devices connecting from outside and can ensure they are safe and secure.

My advice to those considering the solution is to be aware of its capabilities, limitations, and their business needs. These factors will allow you to determine if Intune is the best device management tool for you. Depending on the environment, you may have to combine Intune with an older technology to manage all company devices.

I work for a company as an administrator for Office 365, and I use Microsoft Intune in this capacity.

We implement this solution in conjunction with Microsoft IIS.

It is an enterprise mobility tool that is used for mobile application management and mobile device management.

This product allows us to restrict users who have access to the system, or to Office 365. We have to enroll the devices and give the users rights as directed by our management or security department.

The interface is friendly and well organized.

The security features should be improved.

I have been working with Microsoft Intune for two years.

We have more than 1,000 employees in the company, and there are about 500 users for this solution. Typically, it is used by managers and higher-ups.

We have not yet had to open a support case with Microsoft. To this point, we have solved any problems ourselves. As such, technical support has not been a concern.

We did not use another similar solution prior to Intune.

The initial setup is not complex.

The length of time required for deployment depends on the number of people in the environment. It also depends on how adopted people are with this type of technology. Six months is enough to complete a full deployment.

Some of our deployments are on-premises, whereas others are on the cloud.

Our in-house team was responsible for deployment. Based on our license, we have the option to engage with a partner but we haven't used them.

When it comes to security solutions, it is difficult to calculate the return on investment. This is because it is somewhat like car insurance, where car buyers are protected if something happens. If there are no incidents then you don't see it but you're still protected.

This cost is approximately $30 USD per user per month.

This product is included with our Microsoft 365 E3 subscription.

My advice for anybody who is looking into this product is to try it before they buy it. Microsoft offers a program that allows them to do this.

I would rate this solution a nine out of ten.

We use it for proposing solutions to customers and for co-management of the end-user devices, as well as for unified endpoint management. We also use it for mobile device management.

Internet-based access with security is what I have found to be most valuable.

It is also a stable and scalable solution. We have not had any issues with technical support as well.

The initial setup is straightforward too.

Currently, for a new customer or when a device refresh occurs, I can introduce Microsoft Intune as a unified endpoint management solution. However, for an existing customer who has an SCCM it would need to be upgraded to an MECM first before I can introduce Microsoft Intune.

Microsoft even recommends it as a co-management solution because even if I need to go for UVM as a unified endpoint, I need to rebuild all the missions, which is not practical. So, they need to look into it and provide an easy and flexible moment to UEM.

I've been dealing with Microsoft Intune for at least fours years.

Stability-wise, it is good and stable.

It has very good scalability.

We have had no issues with technical support.

The initial setup is easy. Deployment usually takes around eight weeks of time, including pilot testing. We do requirement gathering, designing, and building, so it takes us a minimum of eight weeks.

From a solution perspective, I always recommend that you go for it. From a scalability aspect and on managing the devices over the internet and ensuring that the security of the devices for customers is always taken into account, we always recommend to Microsoft Intune.

On a scale from one to ten, I would rate this solution at nine.

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're using it for endpoints or mobile devices. We are mainly using it for endpoints. For mobile devices, we are mainly using Workspace ONE.

The key benefit of Intune is its integration with the Microsoft ecosystem. 

Onboarding of endpoint devices is not straightforward. The onboarding process was a little heavier than I thought it would be. That's the key improvement area. Obviously, the more control you have over the devices, the better it is. 

I have been using this solution for about three years. I use it on a weekly basis.

I didn't have any issues.

It is easy to scale. Getting used to using it instead of SCCM is an interesting shift because you don't manage policies the same way. There is a difference, so the scale of that is also interesting to address.

We probably have more than a hundred users.

Their tech support is decent. Sometimes, getting to your first contact can take a little bit longer, but after that, it's pretty good.

Previously, we were using Workspace ONE, but it was cost-prohibitive. We moved because of Microsoft's ecosystem. It was a business decision. The integration of the systems made it easier to stay with something like Intune.

It's not trivial, but it's okay. It's not too complicated. You do have to make sure you read your documentation, and you get an idea of what you're trying to do.

It's reasonable. They're not giving it away, but it's reasonable.

If you can get help from Microsoft or if you can use the fast-track process, it would definitely be worth your while.

I would rate it a seven out of 10.

We have some security policies pushed to our laptops, and we use Microsoft Intune to mainly monitor if they are up to date. The reason why we use it is to keep the patch levels on par for our end points. 

Now, we have an automated registered inventory of all our laptops, and we know exactly which software needs to be updated.

It is easy to use and easy to roll out with low impact on users.

It is stable and scalable as well.

Also, the central administration con dashboard is very easy to use and provides very good oversight on all that needs to be monitored.

The pricing could be improved.

As for additional features, full integration with Microsoft Office 365 would be great.

We have been using Microsoft Intune for half a year or so.

It is a stable solution.

Microsoft Intune is a scalable solution, and we have about 142 users.

We've still got a few more end points to roll it out on, but our increase will be in functionality. Now, we're only looking at updates, but in principle, we can actually push security policies as well.

The initial setup was straightforward and easy to roll out.

Our own technical staff implemented it, and it took about one month.

I would advise that you educate your staff first before rolling it out. Give them ample education and training on how to implement it and on how it's going to be used.

The biggest lesson I learned from using Microsoft Intune is that the central administration con dashboard is very easy to use and provides very good oversight on all we want to monitor.

I would rate Microsoft Intune at nine on a scale from one to ten because it's so easy to use and easy to rollout with low impact on users.

It is used for mobile device management. We use it for mobile phones and even PCs. We have its latest version.

Its protection policies are most valuable. It protects mobile devices as well as individual apps.

It is pretty scalable, and its documentation is also pretty good. It is also pretty straightforward to deploy.

They need to add more group policies. I know that they are already working on it, but this is something that I would like them to do quicker. Intune currently does not have many group policies that you can deploy. It is quite limited in terms of group policies. For example, if I want to disable the password manager on my browser, I can get support in Google Chrome, Internet Explorer, and Edge, but not with Firefox. It would be ideal if they can add some of these things.

Its reporting, which is very limited at the moment, also needs improvement. I can see basic information, such as how many devices are enrolled, but I can't get customized information. It will be great if they can add report customization.

Its stability needs to be improved. Sometimes, when you register a device in Intune, it doesn't show up instantly on the engine portal on the admin side. There are sync issues between the admin side and the user side.

They need to provide better support for complicated issues. They also have a long turnaround time for resolution in regards to overall escalation.

I have been using this solution for three years.

It needs improvement in terms of stability. Sometimes, when you register a device in Intune, it doesn't show up instantly on the engine portal on the admin side. There are sync issues between the admin side and the user side. It is not very stable. Sometimes, it works instantly, and sometimes, something goes wrong, and you get stuck there. It is not consistent.

It is pretty scalable because you can also integrate on-premises stuff. You can also integrate it with SCCM.

When I contact technical support, I normally find the junior engineers to be not that good. They're just good with the basic issues. If there is something complex, you have to escalate the case, but they take a lot of time to escalate it. After the escalation, they are able to fix the issue, but the overall time they take to solve an issue is too much. Sometimes, the solution is very simple, but the process of escalation takes too long.

I find it pretty straightforward, which could be because I have been working on this solution for three years. It mostly involves clicking the Next button. It will also depend on your requirements and policies, but it is generally straightforward.

Microsoft documentation is a very good place to start. They have done a great job for beginners who want to deploy Intune in their organization. They have done a good job in describing different scenarios in the documentation. I would advise starting with the documentation and doing some certification as well.

I would rate Microsoft Intune a seven out of ten.