Microsoft Intune Reviews

Primarily we are rolling the product out because we want to be able to have remote access and control over our desktops and laptops from external locations.  

The most valuable aspect of the product when it is in production is the basic thing it was made to do. We want to be able to allow access to various applications remotely which we can not otherwise do with remote workers.  

This type of question may be premature because we have just started rolling it out now. We have not had a chance to work with it to capacity at this stage. I think, so far the implementation is all a bit shaky and should be better planned and better supported. The deployment seems to not be as simple as what I would have hoped that it would be considering it is a Microsoft product.  

When it is fully rolled out, we will see where the other shortcomings actually are. However, this difficulty in rolling the product out is a significant stumbling block.  

We just started testing the product several months ago. The technical team is working toward trying to roll it out to production in about the month. As that is the case, we are not really using it yet in production. We have got only about half-a-dozen of the 4,000 projected users working with it currently.  

Again we have not really tested and deployed the product broadly across the company at this stage. But it is exactly because we have not seen the kind of stability and performance we were expecting that we have not completed the roll out.  

If we can not seem to get even half a dozen users working with the product in a way we consider stable, the scalability is in question. It should not be.  

As far as the set up, we only have the first half-a-dozen technical people on the product just to do a pilot. We have had issues with it. This is the reason we have not even deployed it for the users' space yet to deploy to a larger test group. I would expect the deployment would be a bit easier. That could eventually be a changing factor in what we do moving forward.  

I have rolled our company onto a 365 E5 licensing scheme. We are not on E3 anymore so we do not need to. With an E3 license, you would have to consider licensing the product.  

We did not really look at any other competition. We are a Microsoft 365 E5 customer and the product promises the capabilities that we need and is available without additional cost. It just made sense to try to use this part of the suite.  

On a scale from one to ten where one is the worst and ten is the best. I would rate Microsoft Intune as about a six. I am not totally impressed with the complexity of the rollout. 

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.

My primary use case for this solution is for MDM. We use it to manage our devices and phones. We want to make sure that data is not stolen from the devices of our staff. Staff members often bring their own devices to work, and we need to manage that.

The aspects I find most valuable are the managing the data and applications. I can also restrict the users to install any applications. I can also wipe the data if the phone was misplaced or stolen. These are the basics for me.

I would like to be able to track the phone. I am not sure this is a feature that is readily available.

I find that this is a stable product and it is convenient for our business.

I have no issues with scalability because I have already used it for our organization and we have it for around 40 phones, and it seems to be suitable for our needs.

Until now, I have not really used the technical support.

I have previous experience with VMware Airwatch. But, I find that the integration is better with Microsoft Intune because we are already using Azure as a domain. It is a much easier integration with the Microsoft products.

I have no comment on pricing of the solution.

We have previous experience with VMware Airwatch.

I would advise other colleagues to use Microsoft Intune.

We use the solution for endpoint management, which includes security and compliance. 

We are a remote company, and the product helps us manage the global endpoints. It helps us natively manage the endpoints in the cloud from anywhere. 

Microsoft Intune's most valuable feature is Autopilot. 

We faced issues with macOS support. The product should have better inventory and asset management. 

I have been using the product for four to five years. 

Microsoft Intune is stable. 

My company has 200 users. 

Microsoft Intune's deployment is straightforward. 

We did the deployment in-house. 

I liked the tool's pricing until P2 came into effect. I am unsure about the current value versus the cost of the new licensing model. 

Microsoft Intune has improved access to devices for remote wipes. We can act quickly whenever someone leaves a company or a device gets stolen. It offers more visibility into our IT group. 

The tool's cloud-focused availability has improved the organizational security posture. It has helped to save time. We can do a lot more with a smaller team.

I rate the product 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 moving from our parent company's tenants to our own, using the product to manage devices. 

I like the tool's integration with Apple. Anyone who creates an ID in Intune will get an Apple ID. 

The product needs to upgrade itself when the server is overloaded.

I have been using the product for a month. 

The product is very scalable. 

We have weekly calls with the Microsoft team, who are very attentive. 

Our parent company makes the deployment process very complex by using non-Microsoft tools. 

We rely on a vendor team to complete the deployment. 

The product is easier to manage and integrates with our ecosystem. It has made our organizational security posture simple. We can leverage the security policies in Azure and create our policies in MDM. I rate it a ten out of ten. 

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.

We are deploying and rolling all kinds of devices - our laptops, our tablets, our smartphones. We are using it locally here in Holland, in the Netherlands, and we are expanding the use to all business units abroad.

There are a lot of features and use cases. We can use it for health status, access control, deploying, et cetera. There are many features for using it.

Technical support is good.

We have found the solution is capable of scaling.

The stability has been good.

It should be easier to define policies and comply with those policies.

The initial setup is complex.

We aren't lacking any features at this point. 

The stability is good. We haven't had issues. There are no bugs or glitches. It doesn't crash or freeze. It's reliable. 

As a SaaS, it's scalable. However, we don't really work on scaling it up.

While the solution is pretty ubiquitous, most people in the company don't realize they are using it. While the custodians use it, the end-point users are unaware of it.

Technical support has been helpful and responsive and we are happy with the level of service on offer. 

Previously, we used MobileIron. Some of our business units also use Cisco Meraki and several others. We are working towards using one or two globally. We're moving to Microsoft as part of our larger global strategy.

The implementation process is very complex due to the global use of the product. It started small. They used naming conventions just for the home country, so we had to deal with redesigns of the naming conventions for global use. Yeah.

In terms of the deployment itself, it's software as a service. The product itself is immediately available, however, onboarding devices is a huge effort. That's mostly the case at this moment. We used Microsoft Intune, before that we used MobileIron, and we did migration for MobileIron to Intune, so we had a quick start originally. 

We renewed our contract with Microsoft about a few months ago. It's pretty simple to renew. We have various licenses for Microsoft including, for example, for Office, Defender, et cetera. I'd rate the pricing and ease of renewal at an eight out of ten.

The solution is a SaaS and therefore, we are on the latest version of the solution right now. 

I'd advise new users to start with a good, high-level design, functional design, from about the naming of conventions, policies, categories, device categories, et cetera.

I would rate the solution overall at an eight out of ten.