Microsoft Intune Reviews

We use Microsoft Intune for our internal security policy and team management. 

The synchronization of Intune with other Microsoft solutions is a valuable feature.

The reporting and cost have room for improvement.

I have been using the solution for two years.

Microsoft Intune is stable.

The technical support is good.

Positive

The initial setup is straightforward. We used our own certified people for the deployment.

The implementation was completed in-house and we implement it for our clients.

Microsoft Intune is a bit expensive compared to the competition.

I give the solution a seven out of ten.

Most of our clients prefer Microsoft Intune over other solutions because of the seamless integration with other Microsoft solutions which most organizations use.

The solution is easy to maintain. 

I suggest using the demo of Microsoft Intune before making a decision.

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.

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 use Microsoft Intune to secure our mobile access when you're assessing your data from your mobile. Additionally, we use the solution to limit people from transferring files to people that are not part of our domain, and secure company data from exposure.

The one feature we find most useful is the Mobile Application Manager. There are two types, we have the complete MDM and the Mobile Application Manager(MAM). We don't give our users phones, it is their own personal phone, and we need to allow them to have access to the company detail on their phone. We need to create a balance between their own personal data and the company data. We deploy the  Mobile Application Manager for them so that we won't be able to interfere with their own personal data.

We are always working with Microsoft on improvements. Improvement is not something that is static, we are always looking for a dynamic way of working with Microsoft. We have a support and enterprise agreement with Microsoft. Every quarter, we review the performance of all our solutions and then we ask for further improvement.

In the next release, I would like a feature to be able to properly lock down the device. For example, if an attacker or somebody steals the phone, you can be sure that the pin cannot be broken.

I have been using Microsoft Intune for approximately four years.

I have found Microsoft Intune to be stable.

Microsoft Intune is scalable.

The installation is not complex.

I would advise others to ensure that the technical people are well versatile and trained, especially the technical people that will implement Microsoft Intune.

I rate Microsoft Intune a nine out of ten.

Basically, the Intune solution is to provide services for MDM and mobile application management. In addition, support or ticket to control Windows 10 devices is provided.

We provide this solution to our clients.

More integration with monitoring tools is needed.

I have worked as a solution architect for Microsoft Intune, for the past six or seven years, and when you consider my overall experience, it is more than two decades.

On-premises is not absolute. You can integrate co-management, but you must first integrate with, ACCM. We are currently providing both solutions.

This is a stable solution. The performance of Microsoft Intune is good.

Microsoft Intune can be scalable.

As a solution architect, I have more than 50 customers.

I have not reached out to Microsoft's technical support. So far, we have not had to.

I am also familiar with CyberArk.

Intune is essentially a SaaS solution. Although Intune is a SaaS solution, it can be integrated with the ACCM. You can integrate a co-management solution in two modes, or you can integrate only the cloud. As a result, the cloud is mostly used by small and medium-sized businesses. However, for enterprise customers, we must use co-management, the team, the ACCM, and Intune.

Maintenance isn't that based on the volume. For example, if you want to go with 500 devices, you need to size the people accordingly. If you want to implement 5,000, 10,000, one lakh, or one million people, you must size the people accordingly. As a starting baseline, we need to assign one person to manage every 5,000 devices.

Every customer used to purchase licenses based on their needs. 

They used to buy a license as part of a package, possibly on a yearly basis, but they never went for pay-as-you-go, but they used to buy for a year, three years, or something like that.

Intune is the best, in my opinion. CyberArk is primarily used for identity purposes. For example, if you want to protect your password, enable local administration, or enable the lapse solution, CyberArk was the best tool at the time. However, if you want to manage your mobile devices as well as your Windows 10 devices, Intune is the best option.

Both goals are completely different. If you want to manage and control your devices, Intune is the best option.

I work with Microsoft technology. I always strongly recommend Intune.

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

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.

This solution is on the cloud. What is required currently by our organization is an internet-facing device. The challenges with on-premise have a lot to do with this pandemic. This is why we've seen Intune with the MDM background grow so fast — because we don't have any on-prem limitations. On the cloud, you can manage everything. You can push policies, maintain patches, and maintain security because everything interacts on the cloud. A VPN is not required. In the legacy method, you need to use a VPN for anything and everything. This increases costs.

For Windows services, there are multiple options within Intune to modernize it to be more internet-facing and dynamic. Intune also provides us with a lot of flexibility to manage Windows-specific devices. 

Mobile-wise, I like the MAM feature. It provides us with more control over the application identity levels. When combined with Azure, it provides us with multiple opportunities to design and construct a solution that meets a BYOD or CYOD model.

Regarding mobile devices, Intune is good, but there are other services that I would say are ahead of Intune from an administration and reporting point of view. These are a few things that could be improved from a mobile infrastructure point of view.

From a reporting point of view, it could use some work. If I need to push a profile, it's a challenge with Intune because first I have to go ahead, remove a user, then add him back; only then does it allow me to push or sync. If it synchronizes, it exits on a cloud-based synchronization time. With AirWatch, there is a function where you can push a profile directly on a device. 

Overall, Intune has improved from MDM. They have become EMM and now they're moving towards Unified Endpoint Manager. They're just beginning to compete in the market from a mobile point of view, but regarding Windows, they're great. 

I have been using Microsoft Intune for more than five years. 

I'd say it's 99% stable. Azure being in the background has impacted it a bit, but overall, it's stable. 

Currently, Intune is on track to exceed SCCM. In the near future, most companies will be using Intune. Currently, roughly 25% to 30% of companies use Intune. The rest of them, 40% to 50%, are still using SCCM and trying to evolve old solutions — this will change. This whole management model will completely change into a hybrid Intune model or a complete Intune model.

The vendor ships the machine directly to you. All you need to do is connect it to the internet. It takes around 30 minutes or 40 minutes depending on the configuration. After that, you're ready to go. Post setup, if you need anything, you can simply go to the built-in Intune company portal and shop from there. This saved us a lot of time.

Still, the initial setup was not straightforward. When we initially started with Windows, there were a lot of open items. There were a lot of things which were not there. Obviously, we couldn't just move a company directly from on-prem to cloud. There is complexity, there are some legacy procedures that we had to follow. At that point in time, Intune was not ready, but currently, there are a lot of options that can fulfill your security requirements, your network requirements, your application requirements, user accessibility requirements, and the user experience. All of these things are pretty much in the place now. To start with, it was not this way. 

When I started using this solution, it took me roughly one year and three months to understand how to build it, to do due diligence, etc. Now, I can migrate an organization within 13 days.

Implementation is a complete team effort. You have to understand a company from a network point of view, a security point of view, a compliance point of view, and a GDPR and HR point of view. These things take time to analyze; it's still maturing but it's a little bit better than what we had before. Now, after I have interacted with an organization, I can get it up and running within 15 or 16 days.

I never got a complete picture regarding how much we've saved thanks to this solution. Still, I think it's very significant. We stopped using a lot of services because we didn't need them anymore. We don't need a lot of resources — we don't need to procure them. We don't need a VPN solution, plus, shipping is all taken care of. 

I started my journey with AirWatch. It was primarily an MDM solution. According to Gartner, AirWatch and Microsoft are currently neck-and-neck. From an organization requirement point of view, regarding MDM, I'd say AirWatch is a step ahead of Intune.

For the last four years, I've only used Intune. I don't know how AirWatch has improved over the last four years. Still, simple things, like pushing a profile are much easier with AirWatch compared to Intune. From a UI point of view, it's really easy for an admin to go ahead and work using AirWatch. From a deployment point of view, there are multiple options for retaining user data. 

As long as it will not primarily be used for banking or security purposes, I would recommend Intune. If you work in a banking environment and are looking for a high-security solution, then I would recommend VMware, AirWatch, or Jamf. As I said, Intune is still developing. Maybe this will change after another year, but currently, regarding banking and security, AirWatch is a step ahead when it comes to mobile infrastructure policy. 

Overall, on a scale from one to ten, I would give Intune a rating of seven.