Microsoft Intune Reviews

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.

Our primary use case is using Microsoft Intune MAM, which is the mobile application management. We are using basically it for application management type needs.

We are using a model for productivity through Microsoft Intune. For example, we are using Microsoft Themes to share all our contents and we connect that with Skype. We also use the Microsoft PowerApps, to help developer apps on a mobile. All of these functions are managed by the Microsoft Intune. 

One of the most valuable features is the overall UI. It's really easy to access, so user interface is very good. Secondly, the enrollment is a nice feature. It is easy to move into the Intune company portal with minimal steps to do so.   In addition, the storage solutions are a nice feature that can be used together with other Microsoft products such as OneDrive and SharePoint. A nice sidebar feature of this is that you can actually restrict the people to mark or store data inside a device and you can bound them to store it in only a white drive and then you can an create an overall encryption around that. For other companies you need to use a container, but not with Microsoft.

I think that in the future Microsoft Intune should have an EMS (Enterprise Mobile Security) feature added. 

Yes, there are a couple of issues with stability. The issues have to do with adoption. Also, organization has to change. 

Our company has not quite reached a level where this is an issue. 

Technical support is good. They have a free kind of support ecosystem, one is the premium support and one is the channel support. In both the ecosystems, the response is, good. Obviously,  if you have the premium support, you get a response within a shorter amount of time.  But I have found that even if you're doing the standard support also, you will get an immediate response. So, overall, the support is very good. For now there's no challenges coming from the technical support.

It is really easy to integrate and manage all Microsoft products with Microsoft Intune.

There is a cost benefit of using Microsoft Intune because of the packaging with other Microsoft products. 

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.

It has a useful device management feature.

I guess they have been working a lot on the current features, but the active directory core features like group policy management are still missing. It would be better if I could integrate it with my core group policy.

I would like to have a group policy in my current environment, which has strict control, but those things are still missing. Although it has maximum compliance and security, it's not available on-premise.

Integration with other products could also be better. If I want to integrate with AirWatch, I have to do a lot of manual stuff and a lot of middleware changes. Technical support could also be better.

I have been using Microsoft Intune for the last three years.

The support is not very good. It's very poor. At least at implementation time, Microsoft should support or should have a team who can support instantly or rapidly. But the process remains the same for the support, and I have to call, and I have to wait for four to eight hours, especially if I'm migrating from AirWatch, Mobility, or some other applications.

AirWatch is a bit complicated, especially during a disaster or when something happens. Their technical support is very poor, and Intune is far better.

The initial setup is easy. We can complete the Intune implementation in one hour, but for the base configuration, we require Microsoft support. Because at the end of the day, it's a cloud product, and we don't have many resources on it.

The price is reasonable, but they should lower it a bit to make it more competitive. It's cheaper than AirWatch and other products, but I still feel like Microsoft can make a base version or with Exchange online or a la carte only Intune version which will be useful. A customer who doesn't want to go full-fledged E3 or E5 can take out or consume an Intune solution only for their purpose, and we want to target that customer.

On a scale from one to ten, I would give Microsoft Intune a nine.

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.

We use Microsoft Endpoint Manager for patch management and software and application deployment. We also use it to engage with the user to be flexible and encourage them to use our organizational tool in their home or country, along with Microsoft 365 features and VDI.

Microsoft Endpoint Manager's patch management has been the most helpful to us. However, Microsoft Endpoint Manager has a lot of features. We could use it for cost management, inventory, and security purposes. But, bottomline, its best feature is patch management.

No tool is 100% perfect. An issue we have run into with Microsoft Endpoint Manager is that we cannot patch third-party products like Adobe and Chrome with it.

I have more than 10 years of experience with Microsoft Endpoint Manager. 

Microsoft Endpoint Manager is scalable. We have not run into any issues. 

The initial setup was not easy for me.

The pricing is reasonable. Microsoft Endpoint Manager is not expensive overall, especially for small environments. But for enterprises with more than 6,000 or 7,000 users, it can start to get a little expensive.

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 it for mobile device management. Android devices, iOS devices, Windows devices, computers, and so on are managed with the help of Microsoft Intune.

It's easy to manage and easy to configure.

We use it to completely manage the devices and access policies. We have app protection policies as well. So when it comes to any person who is outside my current organization, he won't be able to access anything if he's not authenticated. That's a really great feature because data security or data privacy will still be there.

I see room for improvement with respect to China and Android devices. If we get Intune for China for the Android devices, it would really be a win-win situation. The devices we are using to manage devices in China are partial MDM and not complete MDM.

China blocks Google and Google Play Store, which makes installation challenging. Microsoft Intune is a company software, which has to be installed to the app portal or Microsoft Software Center.

With barcoded scanners, it works really well in countries where Google is not blocked, but again, it's a challenge when we have to install Microsoft Intune where Google is blocked.

I've been working with Microsoft Intune for roughly three years.

It's deployed on the cloud itself, and we have 10,000 plus users.

Technical support is not great. If you open up a case, it may remain there for a long time. I believe that they may have a lot of customers and that's why we don't get the response immediately. Also, with these difficult times with COVID-19, they may be facing other challenges.

We used AirWatch and switched because we were facing a lot of issues with the product. Some things were really great, but some things were not.

Maintenance took a lot of time because it was on-premises. Every month, we had to do upgrades and patching of all the servers.

Too much information was provided regarding the initial setup, and it was too difficult to understand sometimes. You would have to read each and every article and try to understand exactly where and what you need to deploy. That's a bit challenging, but if you have seen the videos or attended Microsoft's training, then it's easier.

I attended the training and was able to configure and understand really well. However, if you give it to a layman, then it would really be a challenge.

Hardly any maintenance is required, so a few people will be able to handle the occasional issues and iOS upgrades.

Pricing depends on the features. Microsoft offers special packages if there are more than 10,000 users, and you may be able to get a reduced rate.

Microsoft Intune is a great product, and you should use it. You can do wonders with this particular product. So, on a scale from one to ten, I would rate it at eight.