Microsoft Intune Reviews

We are primarily using the solution for managing the devices. Some employees are using their own devices and some employees are using company-owned devices. Basically, we use it to control company data and personal data, we are keeping them separate and we are managing those devices such as Windows computers, Mac and mobile phones, iOS, Android, et cetera, via Intune.

The product is very useful in terms of Windows Information Protection. Our employees, if they try to leak data will not be able to as the data is encrypted. Intune keeps our data encrypted. If you send me an email, that email is stored on my personal OneDrive. I cannot store that email in my WhatsApp, for example. I cannot store my data anywhere else. The data protection on offer, therefore, is great. 

The initial setup is very easy.

We can use the solution with the Active Directory, which has many policies. We can restrict and protect devices accordingly. 

The solution can scale.

The stability is great.

The cost of the solution is great and was recently lowered to make it even more affordable. 

Intune has a lot of great features and we have yet to utilize 100% of their offering. 

Day-by-day Intune is improving. It has a roadmap for how it will continue to improve over time. 

They need to improve their technical support and make sure Intune is covered under their SLAs.

Our company is very new. We've only been around for about seven months. In that time, we've used Microsoft Intune. It's been less than a year. 

The solution has been stable so far. There are no bugs or glitches. It doesn't crash or freeze. It's reliable. 

The solution can scale as needed. We are satisfied with its scalability capabilities. 

Technical support is not that great. The basic support comes with a Microsoft subscription, however. Intune support from my experiences, the basic support they have, does not have any SLA.

They're working on it only during their business hours and our country is in a different time zone and has different business hours. Our country office's start time is 9:00, however, the business is coming from China. China begins at 7:00. We're getting six hours, maybe, of time where we can get support if we need it - and the basic support on offer is not good.

The initial setup is not overly complex or difficult.

The initial setup was very easy as Microsoft has a setup guide similar to what you would expect if you set up 365. If I'm following the set-up guide, it's very simple. You just click along. 

Previously the price was $4 per month per user. Now it's $2.25 per user per month. The cost is really affordable.

I'd rate the solution at 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 switched to Office 365 applications and we already had an Office 365 license that covers Microsoft Intune. We decided to use Intune for our Mobile Application Management solution.

I only use Microsoft Intune for Mobile Application Management for the management of Office 365 apps. Additionally, we have Microsoft Intune integrated with Workspace ONE.

We have used conditional access policies to prevent users from copying internal resources or internal data to external devices. This has helped protect our organizations from being compromised.

The conditional access policies that we set up are very useful.

Microsoft Intune could improve by being more user-friendly and having it geared toward device management. The graphic interface is not very good.

The VPN option within Intune is not as intuitive as the one available in Workspace ONE. We're trying to implement a VPN tunnel for SharePoint sites. This will allow users trying to access internal resources, such as SharePoint, and other Office 365 data, but it doesn't work as well as Workspace ONE. 

We are in the POC stage of the VPN tunnel. We only have a development tenant for the tunnel. We plan is to implement that in production and get rid of Workspace ONE, if it meets our needs.

I have used Microsoft Intune within the past 12 months.

The solution is stable.

I have found Microsoft Intune to be scalable.

We have over 5,500 users using this solution.

The technical support from Microsoft could improve, it is not as good as the Workspace ONE support. It is difficult to contact Microsoft support.

I have used Workspace ONE, and I would highly recommend it over Microsoft Intune.

The initial setup was complex, and the full deployment took us one year.

We did the deployment ourselves. There is little maintenance required, we have to only update policies. We have a mobility architect that set up most of the backend and we did work with a Microsoft resource for this process.

I have received a return on investment, the solution is inexpensive.

There is a license required to use this solution. However, it was part of a bundle package. 

Microsoft Intune is far less expensive than other solutions, such as Workspace ONE.

We are only using Microsoft Intune because it came with our Office 365 license.

I rate Microsoft Intune a five out of ten.

We use Microsoft Intune for match management for the more than 1,000 computers we have in our organization.

Before using Microsoft Intune we were having trouble when people were not coming to the office and they were working from remote locations. We did not have any control over their devices. Since the introduction of Microsoft Intune, we have had the problem completely taken care of. 

Right after we started using Microsoft Intune we were stuck with this pandemic of COVID-19, and 100% of the users were working from home. It was a good thing we started using it at that time, we were able to do the patch management even though 100% of the workforce were sitting at home.

We have a lot of on-premise server policies which we were struggling with because users get authenticated on the company network, but some elements would not take effect. However, with the implementation of Microsoft Intune, we do not have that problem anymore because the user only needs to be connected to the internet. They will get all the policies that we configure on a global scale.

These are the main areas that have changed the way we do administration tasks on the devices. Additionally, we have control over the applications, such as Mobile Application Management (MAM), we can control how the user can share the company data which we did not before. They could previously install a certain email application on their phone and then they could share it with anyone, but now we have the control; we can restrict it and we can even restrict the applications that they can use. We can stop them from sharing things on WhatsApp. We can only apply limits to the Microsoft platforms, such as Teams and Outlook.

The solution is easy to use.

The solution could improve its flexibility.

I have been using Microsoft Intune for one year.

Microsoft Intune is stable.

The solution is scalable.

We have approximately 1,200 users using the solution and for the operators or managers using the solution, we have approximately 15.

The support is satisfactory.

I have used ManageEngine Desktop Central and SCCM. When comparing SCCM to Microsoft Intune, when we used SCCM we had more control and visibility on what we deployed. There are certain cases where you do not want to deploy something. For example, there are security updates or quality updates that could have bugs or glitches that you see around the world. Another example is, every second Tuesday Microsoft patches will be released and you hear that some of them can have bugs or glitches, we can take them off the list and not proceed with that particular patch. This was possible in SCCM because you can select whatever patch you want before deployment. However, in Microsoft Intune that is not possible because Microsoft releases it across the world as one data piece. You do not have control over whether to select it or not, we have to accept it.

ManageEngine Desktop Central is very similar to SCCM, you can select what updates or patches you want. If you do not want one patch you do not have to select it. 

We migrated all the services to Microsoft platform cloud architecture. We went with Intune for the patch management, but we do have ManageEngine Desktop Central, which is capable of doing patch management.

The installation of Microsoft Intune was not difficult, it was smooth. Once it was set up it was up and running, we only had to configure the policies. Integrating was easy with Active Directory.

I did the implementation of the solution myself. We have a team of four to five that do the deployment of the solution.

There is a license needed to use the solution and we are on an annual license.

I would recommend this solution to others.

I rate Microsoft Intune an eight out of ten.

Microsoft Intune is a cloud-based solution, but it is installed on local desktops. It is part of Office 365 and because people are working from home it enables us to make the desktops more secure.

By using Microsoft Intune we can control which websites the users can go to and it provides a secure environment for our employees using their laptops that are having access from home.  We have installed Intune to control the user's environment minimizing the chances of any hacking.

Microsoft Intune is secure and integrates well with other Microsoft solutions.

I have been using Microsoft Intune for a couple of months.

Microsoft Intune is stable.

The solution is scalable since it is part of Office 365. Additionally, it is very scalable in the sense that you can have millions of users who are using it and check all the alerts that have been sent to the central system online. There you can check if any event of concern has occurred on any desktop on the online portal from Microsoft.

We have approximately 400 users and 500 devices using this solution.

We have not used technical support because we have a lot of employees with technical skills. However, if we do need to use technical support there is Microsoft partner support available.

The installation is very easy. However, to be able to configure it you will need special knowledge, such as training or self-studies to have a proper level of security. There are many settings one has to understand before being able to implement Microsoft Intune.

Microsoft Intune is very simple to install on a local desktop. You can use remote access and install the software. The configuring of the solution is done online on a portal and the policies are pushed to the desktop where Microsoft Intune is installed.

Microsoft Intune is moderately priced. There is a monthly license required to use the solution and it is approximately eight dollars per month.

I would recommend this solution to others.

I rate Microsoft Intune an eight out of ten.

I am an IT support engineer. I take care of all IT projects in my organization. I have implemented Intune and onboarded thousands of devices over Intune. I'm not an end-user. I am supporting our employees with IT policies.

I can reach devices or computers over the internet. I don't need to worry about the network connectivity between the offices. I can manage any device. That is the most important part. 

The Mobile Application Management (MAM) policy is also valuable. I can control applications, and I can secure applications by using the MAM policy. It is very effective and very helpful in protecting our users' data on mobile devices such as iPhones, Android phones, etc. I can apply policies, and I can protect user data.

I can also deploy the software and applications and do configurations. Windows autopilot is there. It is like self-provisioning on employees' computers. That is also an important part.

The most important thing is reporting. They should improve their reporting. They should give a free hand to users. In SCCM, I can create my own reports. For example, in SCCM, I can create an inventory report for my PC or for all PCs, but in Intune, we don't have an option to create any report. Microsoft claims that Intune is a successor of SCCM, but SCCM is more powerful than Intune. So, they should develop Intune more and make it equivalent to SCCM. Then, their product will be great in the market.

If I want to deploy an application, I cannot add multiple schedules. I can add only one schedule, and I need to rely on that. Adding multiple schedules over a period of time is not possible at this time.

I cannot evaluate any setting before deploying anything. In SCCM, we have the Compliance Baseline feature. If I want to check any service or anything else, I can do that, but in Intune, that is not available. There are very few compliance policies. They say whether your device is compliant or not, but if they don't provide enough and better compliance policies, why should I be compliant with those policies? They should give more options for the compliance policies so that we can choose something better, and we can make our devices comply with those policies. 

It lacks in terms of analytics. Analytics and all such things are not good, which again comes down to the reporting part. It should be better in terms of analytics and reporting. 

It also lacks in terms of automation. If we want to automate some of the things, we need to spend more time on automation. Other tools in the market are giving better automation graphically. So, they can work on that part.

Their support should also be improved. They don't know about their own product.

I have been using this solution for the last six months.

It is very stable. So, whatever features they provide are working great. There are no problems with those features.

My experience with them was very bad. They don't know about their own product. I know better than them by going through their articles and other resources. When I ask them anything, they come up with silly answers. They are making me feel frustrated. I have had a very bad experience with their support.

Its initial setup is very easy. We don't need to deploy any servers anywhere. With just a few clicks, we can set up Intune. We just need to set the MDM authority, and we need to set the automatic enrollment. That's it.

Most of the mobile device management tools are giving the same facility. I don't have experience with VMware Workspace ONE, but I have been reading about it. VMware Workspace ONE also gives similar features in a slightly different way, but the objective of all such tools is the same. 

I would rate Microsoft Intune a five out of 10 because they are still developing it.

Generally, we use it with banking, finance, or government entities, usually medium to large customers. We also have smaller customers who are dealing with sensitive private data and therefore are interested in running Intune on top of their Office 365 licensing.

I like the fact that it's integrated with the rest of the Microsoft products, so customers can manage it from their Office 365 portal or Azure portal.

If you could replace SCCM completely with Intune, that would be fantastic so that you don't have to run SCCM with Intune as an extension.

They could also make it easier to use because there are some other products that may be easier to use in terms of the look and feel of the dashboard.

The stability is quite mature here in Australia.

The scalability is quite good.

The technical support is really good. First level support is just your normal desktop level, but the second or third level is much deeper. It's pretty good

Usually, if I log a call in the morning, I may get a call in the afternoon to sort it out through screen share. Sometimes, it's someone in Shanghai that takes the call, and I speak Chinese, and they speak Chinese, so I'm pretty happy with that.

If the customer is already operating on a cloud environment, then it's easy, but if a customer has a hybrid environment, then it can be complex.

If they've got people who are now working home that previously used to work in the office and they still want them to use their work laptops at home, it gets complex. You would need to start looking at registering the devices into Azure AD, which then leads to Azure AD premiums. Therefore, you would need to find out from Microsoft whether to add the device into Azure AD, to register it, that you would also need MDM or an Intune license added on top.

If you're ever going to buy an Office 365 environment, then pricing is reasonable given all that it does, but if you're not, then you might find the pricing expensive.

I would recommend that they check it out thoroughly because things are moving very quickly with Microsoft, and we get better support now, given Australia's a hero country of Microsoft.

A lot of companies are switching to hybrid environments because of COVID, and Microsoft Intune can be deployed in a hybrid environment.

However, because Microsoft Intune doesn't totally replace SCCM, I would rate it at seven on a scale from one to ten.

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.

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.