Microsoft Intune Reviews

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.

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.

Its primary use case is mobile device and workstation management.

It is a platform, so there is not really a version per se.

It allows our clients to have the confidence to centrally manage policies for security. It helps them in securing the organization from a technology aspect.

It is scalable, and it is fairly portable for customers, particularly for those who are already involved in the Microsoft stack.

Its configuration is fairly complicated. You have to do quite a bit of discovery to be able to deploy it for a customer. You have to ask them a lot of questions. So, its initial deployment is the biggest challenge. They should make it easier to deploy with the use of Wizards or something else. During the deployment stage, there could be profiles for the customers who are particularly wanting to use certain feature sets of Intune.

I have been using this solution over the past year and a half.

Its stability is pretty high. Once you get it deployed, it typically works pretty well. You might have the occasional snafu, but overall, it works pretty well.

There are no issues with scalability. It is cloud-based, and we've not seen any issues or limitations regarding scalability.

We have a handful of clients who use Intune. We're seeing more and more adoption. It's not widespread yet, but it's growing. We look for opportunities where this is a good fit for the customer.

We've had organizations as small as 20 to 25 users. We've had organizations with 200 to 300 users. It is used across the board.

We haven't had to use technical support, so it'd be hard to evaluate that.

There are some customers that have switched from other products, and typically, it's because they just couldn't get the other product to work. Miradore is one in particular that many of our customers had, and I like them

Its initial deployment is probably the biggest challenge. It is complex because Intune encompasses so many features and things that you can do with it, and it is so broad in scope. There are a lot of different things you can do with it, and there are a lot of different ways in which you can deploy it, which makes deploying it for a particular customer's environment complicated. It takes some time. I would rate it a three out of five in terms of the ease of setup.

We've had deployments that took weeks. We've had some simpler deployments that took days. So, it varies. The product is so big, and it encompasses so much. So, it depends on what the customer is implementing. One of our most recent customers wanted to use it for a lot of things. So, it was pretty complex. It took us time to get all the devices onboard and registered and so forth.

We might have multiple people working on a deployment, but that doesn't mean it takes that many. Overall, it doesn't take that many people to deploy it, but it typically takes a higher technical level person to deploy. You don't need a bunch of folks, but they have to really know what they're doing.

I don't have any statistics, but from a qualitative assessment, there is absolutely an ROI. Customers on Intune seem to keep it and be happy with it. It does offer significant security advantages for customers. We've seen customers really happy with the product once it is up and deployed.

Microsoft offers some licensing where it's included at no extra cost when customers are already using the licenses. In such a case, it's a really good value. If you have to buy the licensing for it, it's probably on par with other solutions. It isn't substantially more or less expensive. The great thing is that it is included in some of Microsoft's licensed packages. So, some customers don't have to spend additional money for it.

Typically, most providers that support Intune do charge a management fee of some sort or some fee. Certainly, we're no exception.

I would advise making sure that you look for vendors that have a lot of experience in deploying Intune. Make sure that you're working with an experienced vendor with a lot of experience. There is a fair amount of change and improvement in the application. It is constantly being changed and updated, so you really have to get somebody who is familiar with it.

Overall, I would rate it an eight out of 10. The challenges with deployment lower its rating a little bit.

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.

The solution is deployed on cloud.

Autopilot is a great feature. Most users are looking for zero-touch deployment. 

There are many things that could be improved in Microsoft. Reporting and troubleshooting for the application deployment could be better. It's very difficult to understand. 

It's also very difficult to monitor where exactly the error is and the kind of scripting we're trying to deploy. PowerShell scripting is even getting a delay compared to other applications or policies. Usually if we deploy the configuration profile, there is an immediate sync and it will be applied to the devices, but it's not happening on PowerShell. This is an apparent option for PowerShell that is not working properly, so that again needs to be rectified. The reporting is a major drawback in Microsoft in Intune. They're not properly reported on the console.

I have about seven years of experience with Microsoft. I have been working with Intune for the past four years.

The solution is stable, but the reporting steps could be improved. The product has been released for more than six years, but some complete information is required.

The solution is scalable.

Technical support is very active. We used to interact mostly with Microsoft, so we had a lot of issues from the Intune side, so we were often troubleshooting steps. The technical side is pretty good. Whenever it's required, they will immediately schedule a call. I would give them a 9 out of 10.

Initial setup is of average difficulty. It requires a lot of people. We need to have an Azure AD license, so some AD integration is required. A kind of firewall is included.

In Jamf, it's not like that, so we have a single console and we can implement it. But here, we have multiple because it can be integrated and co-managed. I can't say it is very easy to deploy. For very small-scale industries, then it's definitely easy if you have minimal user devices or user IDs. If you're looking to deploy the solution on a corporate-level, and if they have multiple tenants, in that case, it is definitely complex.

If you are looking for it to be co-managed, there'll be an SCCM and an AD team. Otherwise, one or two engineers is fine for Itune.

I would rate this solution 7 out of 10. 

If you are working as a SME, anybody can do the major part of troubleshooting and configuration. Even someone who isn't certified will be able to do the configuration and implementation part. Logs are required to troubleshoot.

Intune is the best tool going forward because everyone is moving to the cloud. If you have a cloud environment, it will be easy for a service provider to provide support. The solution can also be easily integrated to other tools.

There are so many additional features included in Intune that it's very easy for the users, corporate, and for companies to manage the devices. Even if the device is out of office, even if it is not domain-joined, it will be easy for us to manage for the client, or for the companies to manage it.

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.

Our main use cases with Microsoft Intune are about how we automate the deployment. Auto-pilot is a feature that we normally recommend. Another piece is about the package deployment, where we recommend, or have helped, customers in deploying and converting their Win32 application. These are the two main areas in terms of automating the enrollment and Win32. Another use case in terms of the Apple, which is being used more by the customers, is where we recommend them to go for the zero touch process by using the AD.

Intune's feature that I have found most valuable is its auto-pilot feature. The main thing is that it keeps building it. Also Intune's capability in terms of Mac, which is slowly increasing, although the customers are moving towards vMOX and leaving the Intune just because of its limited capability with Mac, though it has already been enhanced. More features include the conditional access and the app production policies with respect to BYOR devices. These have been increased a lot in terms of security.

In terms of what can be improved, I am looking for better enhancements regarding Apple management, not only on the mobile device, but also on the laptop.

Other than that, it already has good capability with Windows, and it is already very good for the mobile device. The only area that is missing is for the Mac products.

I am using Microsoft Intune for the last two, three years.

In terms of maintenance, since it is a cloud product, it automatically gets updated by Microsoft. So there is no maintenance required for the upgrade part. But definitely the maintenance part that we track is the software asset management - that the devices are there and that the patches are deployed on a timely basis. We also do maintenance on the dashboard reporting feature in terms of whether the devices are compliant or not compliant.

In terms of performance, devices will be automatically enrolled and all the applications will be deployed. So it will be ready to use once they log in with their Azure-ready credentials. That is zero touch for them. In terms of having integrations in place with other tools, any issues they face will have proactive or automated actions to resolve their issues, instead of raising them and going through the long process of raising a ticket and the resolution.

Scalability is good.

In my experience, the customers who are mostly going for the Intune are small, medium and large companies. We have seen a mix. These days we have seen a large base of customers having more than one device. So it could be suitable for any size company.

Not too much to say on support. It is pretty fast. But in some of the instances we did not get much or a proper resolution where we had to troubleshoot a lot. But in most of the cases, support was good.

Initial setup is a simple process. It is a cloud solution. It is easy to deploy and easy to integrate with other tools as well. If we have to integrate with on-prem or Azure-ready through an AD connector, it is easy. Also, it is capable of integrating with other tools.

In terms of deployment, having things in the VM or physical VM or physical system in place and the ports enabled, as the main infrastructure is all in the cloud, is only part of connecting with the Azure already and the AD connectors, and does not take much time. With full testing, it takes one day if all things are in place.

Their price is really good. That is the reason customers move here, because as part of the Office 365 package, they always get the E365 as well, which makes it easy for them to manage their devices without having additional licenses for Intune.

That is the best part.

The main differences between Intune and other products are, like I mentioned, in terms of the Mac. If the customers are majorly moving and adopting Mac laptops while they are using the Intune, they are leaving for other platforms, like Workspace ONE and vMOX. That is the reason for moving and the major difference I have seen these last couple of months. But at the same time, if there is not much dependency on Mac devices, they are moving from other platforms to Intune, also.

My advice to anyone considering Intune would be to definitely test it and have devices enrolled at least in a pilot phase. They will get feature compatibility, the policies, and the auto-pilot feature. So, I would recommend to do at least a POC, and then decide.

On a scale of one to ten, I can rate Intune an eight.