Microsoft Intune Reviews

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. 

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.

Our primary use case for this solution is to implement conditional access policies to restrict mobile users from accessing emails until their devices comply.

Intune should be much more granular in terms of supporting more devices. It is mainly only supported for Samsung knox devices. If you want to restrict the user, and not to turn on the camera and such, most of the policies that I found were more supported only towards Samsung knox devices. But, some policies are supported for Android 4.0 operating systems. Most of these policies are only for Samsung knox. I wish there was more diversity regarding other Android devices. In our country, there are multiple vendors, such as: Samsung, Huawei and more. I would prefer other solutions if I'm implementing restricting the devices in terms of applying the policies.

It has many features, but the most prominent is that other mobile device solutions support more polices. Much more diversion is needed in implementing the policies in different kinds of devices. As I have worked, it has not supported too many policies for android devices. Every 3rd or 4th policy that was supported is for Samsung knox devices. So, most people prefer to use Intune if they want to implement conditional access policies to restrict customer exchange online or exchange user formats emails until their devices comply.

You can publish Apps on the devices and take inventory of the devices, but it's all about the companies who were interested due to implementing conditional access policies to restrict  users. They want to restrict the users in order to access emails until their device is secure and then comply with the security policies of the organization.

Most of the customers expect that most of the policies will be there for Android, to implement the policies. Unfortunately, most of the policies that I found are for Samsung knox devices, that is specific to a device or specific to a vendor. That's why most of the customers have a hard time with Intunes, because most of the policies they see is for Samsung knox. They want Intunes to support Android devices. If it is supported by other Android devices, then it's very complicated because if you want it implemented, you have to use some custom equipment. There are a very limited number of policies that are applied, and all generate other devices like Samsung knox devices.

Most of the customers in the business do not use Intune because it doesn't support that much policy for Android. Here in Pakistan, most of the end users are using Android devices. Windows is out of the question. They don't use Microsoft mobile phones. Most of the popular devices are iOS, and the ultimate users are Androids. I think 80% of the users are using Android devices here and less than 20% are using iOS devices.

So, the customer is expecting to apply policy on Android devices and it's not generated specific to a vendor like Samsung knox, so they don't buy it, and they don't consider it.

Yes, it is a stable solution. There were a few stability issues, but most of us are happy with the stability of the solution.

I do not think scalability is an issue.

It was not easy, but not too complex. If an engineer knows what he or she is doing, then it is not difficult.

The product is offered as part of a Microsoft standard bundle. The pricing can be competitive to VMware Airwatch, and IBM MaaS360.

We considered VMware Airwatch and IBM MaaS360. 

From my experience if the requirement is to lock down the Android devices through Intune, then I should advise to look at the different policies that are available for Intune before doing the implementation. Because, if the policies do not meet the requirements of the organization to lock down the devices or to apply the policies on the devices, then it does not make any sense. So, for Android devices in particular, if you are implementing Intune then you should first look at the policies that are available in Intunes and then try to evaluate and do proof of concept.

We use this for management of all mobile devices.

We would like to see support for Chrome and/or devices for Chromebooks.

I have been using this solution for about three years.

The solution is stable.

The solution is scalable. We currently have tens of thousands of users within our organization using the solution.

I think customer support is quite good, we have enterprise support and premier support agreements.

Initial setup was straightforward.

Potential users should run a proof of concept. This can be done easily because Microsoft is offering a free trial period of one month.

I would rate this an eight out of ten.