Microsoft Intune Reviews

The solution can be primarily used for mobile management. We're using the solution to enroll Windows 10 devices.

The policies on the solution are very good.

The process of enrolling devices is a useful aspect for us.

The features that allow us to control the devices are helpful.

The initial setup is not hard at all.

Technical support, in general, has been quite helpful.

We've found the configuration capabilities to be quite good.

So far, the solution is fast and has an intuitive interface.

The feature that allows us to import the business application from the configuration manager to Intune is not very good at this time. They should be getting better in the application input on that platforms. It's an aspect that could use some improvement.

Other than that, I can't recall the solution lacking any features. Overall, we've been happy with the offering.

I've used the solution in the last 12 months. We've been using it for one year, more or less. It hasn't been a very long time just yet.

The stability of the product is quite good. there are no bugs or glitches. It doesn't crash or freeze. The performance is reliable. 

We do plan to increase the use of the solution over the coming year. Our intention is to scale a bit. We don't plan on switching products anytime soon.

I've dealt with technical support in the past, and I'm quite satisfied with them. They are knowledgeable and responsive. I have no complaints.

We did not previously use a different solution. We've only ever used Microsoft Intune for these current use cases.

We found the initial setup to be quite easy and straightforward. It's not complex. If a company wants to set it up themselves, they shouldn't have an issue doing so.

The deployment didn't take very long. It was a pretty quick process overall. 

I can't speak to any aspect of the pricing. It's not something I handle. I don't deal with licensing and therefore don't know if it is expensive or reasonably priced.

I've been testing the solution. I'm a customer and an end-user. My company does not have a business relationship with Microsoft.

In general, I would rate the solution at an eight out of ten. We've been happy with the capabilities overall.

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 it to manage our mobile phone in the business, and we also use it to manage our Windows PCs.

It's managed through our IT company, so they have the latest version. I have admin access to it, but I haven't had time to be in the portal so much.

We have one person based abroad, and it was a lot easier to get him standardized than it would be if we had to get his computer shipped down and configured that way.

For our office workers who are not based in Norway, when we order the PC, we can do some of the settings for them. These are standardized settings. We can set them up exactly as they are in Norway so that they're the same. 

The reports that are generated aren't so great. They don't give a lot of meaning so far, but that could be down to user knowledge than the actual reporting side of things. I'm not a big user of it, but I was a bigger user of MaaS360, and we used to be able to run weekly and monthly reports. In the case of any deviations. we'd get a warning immediately. That's not so easy to do or to get in place for Intune. This could be just a user issue, but when I compare both, that's the only thing that's lacking for me.

I have probably been using it for eight months.

So far, we have had no issue. We only have an installer for one user abroad, and he hasn't had any issues. It is stable there, and the phones also work fine. 

It is scalable. We can add more users, and there are no extra costs.

We're probably not the best users of it. We have one person based abroad, and we are probably going to have more.

We go to our own IT support, and they contact them. I'm not familiar with the deal that they have. They're a big IT team over here. They probably have an agreement, and they're prioritized in the queue for Microsoft Intune. There has been no downtime, and we haven't had any issues so far.

We've switched over from MaaS360 to Intune. We took the decision that Intune is better for Windows and IBM products.

I personally preferred IBM. I always outsourced the IT, but I preferred IBM. I liked the interface with IBM. I like being able to push out and seeing which updates were not available and which ones had to be pushed out. It was a lot easier to use. So, I preferred IBM, but I'm not really using Intune. It's outsourced to our IT.

It was quite extensive, and it took a few days for them to set it up.

We have outsourced IT for it. They did it themselves.

It's monthly for us, but it's built into the license cost that we pay our IT each month. It's maybe 129 Kroner per head, which translates to £10.

There are some additional costs. Our IT had to set up and configure their own server, so there is an extra cost for that, but I'm not sure what that costs.

I would advise setting aside the relevant time because it is time-consuming. It probably needs to map to all your devices so that you have a proper overview of all different applications that are needed on PC and mobile. I wasn't really involved in the migration. So, I only know what they needed, and from their side of things, I had to gather the information based on our MaaS360 database.

I would rate it a seven out of 10.

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.

We have some security policies pushed to our laptops, and we use Microsoft Intune to mainly monitor if they are up to date. The reason why we use it is to keep the patch levels on par for our end points. 

Now, we have an automated registered inventory of all our laptops, and we know exactly which software needs to be updated.

It is easy to use and easy to roll out with low impact on users.

It is stable and scalable as well.

Also, the central administration con dashboard is very easy to use and provides very good oversight on all that needs to be monitored.

The pricing could be improved.

As for additional features, full integration with Microsoft Office 365 would be great.

We have been using Microsoft Intune for half a year or so.

It is a stable solution.

Microsoft Intune is a scalable solution, and we have about 142 users.

We've still got a few more end points to roll it out on, but our increase will be in functionality. Now, we're only looking at updates, but in principle, we can actually push security policies as well.

The initial setup was straightforward and easy to roll out.

Our own technical staff implemented it, and it took about one month.

I would advise that you educate your staff first before rolling it out. Give them ample education and training on how to implement it and on how it's going to be used.

The biggest lesson I learned from using Microsoft Intune is that the central administration con dashboard is very easy to use and provides very good oversight on all we want to monitor.

I would rate Microsoft Intune at nine on a scale from one to ten because it's so easy to use and easy to rollout with low impact on users.

We are VMware and Microsoft partners, so we offer services around their products.  

We are using Intune internally but we are leveraging it for our customers as well. That is a different story. One part of Intune is within our company, but we are also providing services around Intune and Workspace One for our customers.  

For us, Intune is on the public cloud. For our clients, it depends on the requirements and it varies from customer to customer. Some clients' requirements are deployed in private cloud mode or the hybrid setup. It depends. Requirements differ from industry to industry. If a company is BFSI (Banking, Financial Services, and Insurance), then they will be looking for a private cloud solution. If it is something which is not BFSI or maybe some industrial interest, they might go with the public cloud.  

In the end, most of our instances are in the public cloud unless there is some compliance requirement. Otherwise, the accounts are mostly in the public cloud to conform to regulations.  

Intune is used essentially to facilitate the ability of enterprise organizations to manage their endpoints. It is for end-user computing or UEM (Unified Endpoint Management) solutions.  

One of the major advantages of using Intune is for our ISO (International Organization for Standardization) certification. We have to meet requirements for ISO 27001 and 27002 and part of that is that we need to have a proper control mechanism for endpoints and the users who are using those endpoints. The other requirement is that we need to manage the workforce. We have to manage their time to understand how long they have been working, how long their device was on, when they were working, et cetera. So we use some other products that compliment Intune to gather the data on that.  

For example, we have something called Time Doctor. We use it to monitor how long people have been working. We get reports that detail how long their devices have been on. Then there are different ways we can leverage these results and statistics. For example, we can compare the uptime of the device and uptime of Time Doctor. With that, we can understand how long an employee was working on something, but how much more time the machine was up in addition to the work period. That shows the period of time that he or she was not using Time Doctor.  

The other thing is we can remotely access a device. For example, say we have to do some troubleshooting because a user is having an issue. We can remotely log in via Intune to troubleshoot the issue, as long as the device is accessible. Obviously, that can only happen if there is no issue with the internet and connectivity and services. But we can remotely access the device and troubleshoot the issue securely.  

Those are some of the different use cases.  

I guess in our company we are using most of the features in Intune. What we use it for is to control the endpoints. We publish some selected applications and the end-users are only able to download and install those applications. They are not allowed to install or use any other applications other than what we provide. We do compliance checking. We run assessments periodically on the endpoints using Intune, and Intune generates reports. Sometimes we need those reports to qualify for our ISO certifications.  

It is a similar thing for customers as well. There is a different requirement but it is a similar idea. For example, if we are engaged with an oil and gas company, they have back-office stations and point-of-sale solutions. In this case, those are Windows systems. What they used to do is they had to manage those solutions manually. They had a contract with some third party. The third-party would go on the sites if there was an issue or something, and maintenance and delivery were all manual. They did not have any EMS (Endpoint Management Solution) at all. The only thing they had was something called a radiant configuration management server. That was only used for configuration purposes, not for maintenance or other troubleshooting.  

The concern and the requirement over delivery was raised because of COVID. No one was able to go to the sites to do the troubleshooting, maintenance, and delivery. The only solution that they had was to engage with us to deploy these solutions on their endpoints. They did not all go with Intune, some went with Workspace One, which is also a UEM solution. So they wanted us to deploy UEM on AWS public cloud, then connect it, wire their MPLS (Multi-Protocol Label Switching) network to the end-point spots and box devices in order to manage them.  

The generic answer to what can be improved is that I hope that the reporting needs to be a bit more interactive.  

In our company, we have been using Intune for the past three years.  

I think Intune has been in the market for a long time now. That maturity makes it pretty much stable because it has been through so many iterations.  

Until now, we did not have any concern with respect to scalability within whatever we have done either for our organization or for our clients. We have done installations for bigger companies, for smaller workforces within bigger companies, but not for the larger endpoints. We do not know how well it scales in every direction and if scaling will cause any problems. We have not come across those things.  

In our organization, we probably have 250 to 300 people who are using the product. We will probably increase that usage in the future, but it depends. We were planning to introduce Microsoft ATP with Intune for advanced threat protection, which compliments the security part. Because Intune does not have advanced threat protection capabilities on its own this resolves that issue. There may be other considerations in the future that influence the importance of Intune to what we need it for and how we proceed.  

We are Microsoft partners and we have a different support model with Microsoft than a typical client will. We have not had any issues with our support team and they have worked well with us up to this point. We have a different channel than the partners who need to communicate with Microsoft another way.  

It is a tricky thing to answer exactly what I have used that either was prior to or a substitution for Intune. That depends on different things and factors. First of all, Workspace One is definitely highly scalable, that I know. Workspace One also has a lot of integration options wherein we can have a lot of peripheral tools. Workspace One actually started with only UEM, but it is now not limited to UEM only.  

Intune, is only a UEM. So Workspace One has one integration as UEM, but it has many other things. Apart from that, it has Workspace One Intelligence, it has Workspace One Assist, et cetera. There are four different parts that can be integrated with Workspace One and they can work together for a highly scalable, highly secure, and highly analytical solution.  

Microsoft also has solutions. It is just that they are different solutions implemented in a different way. For example, ATP (Advanced Threat Protection) Microsoft is for advanced threat protection. WAD is for virtual desktops. They do not have the same type of tight integrations as Workspace One. All of these Microsoft products work separately. In Workspace One, all the products compliment each other and all the products can be combined more like modules under Workspace One. They can push their findings to Workspace One Intelligence where all data intelligence can be done. Auto remediation can be done. We can get findings from VMware because now Workspace One security is there to make sure that this is secure under the umbrella. VMware Carbon Black is also the same in that it can send its findings to Workspace One Intelligence. So the integration is the part that is handled differently. Workspace One has many features. Microsoft also has those features. It is just that it is a different way to orchestrate. In Microsoft, it is not under one umbrella. In VMware, that is under one umbrella, which is Workspace One.  

The pros and cons are different because both approaches have their own advantages and disadvantages. Both have solutions for each of the functions. For example, each has advanced threat protection and all those capabilities. If you stay working with that family of solutions, you do not have a problem.  

Now say, for example, a company went with Workspace One because they wanted to leverage UEM. They adopted some other modules as well with it to create solutions for problems or needs that they want to solve. They have to have Workspace One for this solution and they can not work with it separately. That might be a cost factor because they can not work with one tool only, they have to make the license for two products because they do not work separately.  

For Microsoft, since the products are completely separate, customers can choose which one to go with and only use that. They can go with only one product, or they can add any of the others. They do not need to have the central component to bring them together.  

So that might be an advantage or disadvantage in using one product or the other depending on the use case.  

We did not experience any complexity in the initial deployment and there was no problem with the installation, I do not think. The complexity definitely depends on what you are trying to accomplish. I do not remember exactly because I do not directly deal with deployment anymore. I am actually leading it. We have a team that deploys the product. I do not look over their shoulder to know how much time it takes exactly and what factors it requires for successful deployment.  

We did the deployment by ourselves without the help of consultants or vendors, that I know. We are system integrators. We have the capabilities to do things for customers. We did it ourselves. The only thing is, we have a separate team for the Microsoft product installations. Especially for something like Microsoft Intune, we need to have a special expertise. Something called Microsoft Windows, virtual desktops, all of that needs someone to install it who is intimate with the application. Microsoft Azure is something that can be used for different Microsoft technologies and solutions. We have a different team that we will put on the implementation of these products depending on the requirements.  

The pricing for Microsoft Intune is reasonable. Our clients are satisfied.  

If someone is looking to have a more integrated result, they are looking for many other things like EDR (Enhanced Data Detection and Response). It is probably better to go with Workspace One because they have that under one banner. Obviously, if there is something under one banner, the integrations are simple, they are seamless, and they complement each other.  

I do not think I will have a good answer for what advice to give because technically I have not used Intune myself for some time now. I have a team that works under me for this. I am at an architect-level position now. My perspective reflects that.   

On a scale from one to ten (where one is the worst and ten is the best), I would rate Intune as an eight at least if you are only talking about a UEM solution. Personally, I am not very concerned about the reporting part, so I will consider it at eight. But if someone is looking for extensive reporting detail that is easy to understand. Interactive reporting that will give them better-tuned results, then obviously the rating might go down.  

The only thing which I see that can be done to raise this product from an eight is to package Intune as a product under one umbrella. If that were to happen, it covers the whole of end-user computing and security solutions.  

At the moment, these are two separate things when using Intune. There may be another way to accomplish this under the one umbrella if you go with Intune. For example, if there is an add-on within Intune to leverage containerized security, auto containment, and all those things. This would be a more flexible solution if that were the case. At the moment, Intune is not required to be installed as a client. As a client in the system, it can communicate with servers and do some auto containments, endpoint detection, and response. If there was a separate solution that could be added as a paid solution to create the umbrella, you have created both solutions simultaneously.  

The main reason this problem came into the picture was because of this COVID pandemic. IT teams and security teams do not go well together normally. There has to be one solution which can offer both. It can be for both IT architects, IT technical support, and security support. That is the solution that can be leveraged for both security and end-user computing. It is simple.  

My company requires control over the deployment process of new computers, and we have set up some profiles for specific applications to configure the access policies and define permissions for certain objects or documents. That's the most common use case.

It's not working perfectly, but Microsoft's Autopilot offers great visibility into automated deployment solutions.

The reports aren't complete, and it's not easy to build custom reports. For example, Windows Autopilot isn't working well in cases where the computers don't have a good internet connection. Then the option is not good enough. Microsoft could add an integration for managing Intel vPro chipsets. That would be nice.

I started working with Intune three years ago.

I wasn't involved in some of the biggest deployments, but I think the solution is capable of handling various complex scenarios and architectures. We'll probably increase usage, but we don't have any plans in the near future.

Microsoft support is very good. 

I previously used a different management solution called SOTI MobiControl, but I didn't switch because Microsoft Intune was better. I just changed companies. 

Implementing Microsoft Intune is easy. Total deployment takes about one to two weeks. You access the portal, buy the subscription, and configure everything. We have three administrators managing the solution.

I'm researching VMware Workspace ONE, a new VM solution. I think it's interesting, but I don't have enough experience to give specific feedback about that tool.

I rate Microsoft Intune nine out of 10. I think my company needs to define the use cases for each user type and organization type. For example, we have to consider if the client has policies configured with Active Directory and assess to identify which policies are required in the new management solution then configure only the settings that they require.

I use Intune for endpoint management. We manage our workstations via Intune because we have remote users on and off the corporate network. It's deployed across over 500 Windows workstations. We're also trying to incorporate cell phones, but we haven't reached that point as yet.

Intune reduces the load on our on-prem Active Directory by having everything go to one Intune panel. That way, we can configure group policies, deploy applications, and manage devices. It has really improved our operations. In the past, the device had to be on our corporate network, but now we can provision a device remotely.

I like the group policy management feature, which performs application monitoring and device enrollment.

It would be nice to have a location tracker for the mobile device management tool. I'm not sure if it exists but hasn't been configured or if it's missing, but we've been unable to utilize the location features.

I have been using Intune for about two months.

Intune is pretty stable. It's also great for helping us maintain compliance in our environment. If it's a hybrid deployment, you should be fine as long as the sync is running. 

Intune is easy to scale because it's in the cloud. There are no limits on what you can manage.

Microsoft support isn't too bad, but it depends on the department you called. Intune support is better than support for Defender for Endpoint. I would rate it about a six out of 10.

Neutral

I was previously using on-premise Active Directory with group policy management. Intune puts your dashboard and panels in the cloud, but they sync with the on-prem Active Directory. Most of the management is done from in the cloud. All we need is internet access to manage the devices.

Setting up Intune was straightforward. Microsoft provided all the materials we needed, and we had support from their team. We had about five guys working on the solution. It can be from one to five guys, depending on the scale of the solution. 

We went through the reseller.

The price isn't too bad

Yes, we've tried ManageEngine and SolarWinds.

I rate Intune 8.5 out of 10. My advice to future users is to perform a proper inventory before enrollment. This is essential cost-wise. You need a good idea of how much it will cost per month so you don't overrun your budget.