Microsoft Intune Reviews

The solution is primarily used to manage iOS, Android, and also Windows 10 or Windows 11. It's to manage end-user devices.

The best thing about Intune for the customers is simply that it's included in the different plans of Microsoft 365. If a customer needs Office or collaboration tools, Intune is included. It's for free. If the company has another MDM, normally they are paying for it. This product is included in the license of Microsoft 365. We find that the customers, in general, want to change the solution, to move from another classical MDM to Intune due to the fact that they save money.

If you need only to load a specific profile and you don't have deep security functionalities, etc, Intune is very nice and good.

The initial setup is very simple.

If you need some restrictions or some integrations or you need integrations with security options, or if your mobile terminals are industry-special or ruggerized, bar code readers, printers attached, this might not be the best option. If your MDM has to be really specific, perhaps Intune is not the better option. You have to consider MobileIron or Workspace ONE or MaaS360 or similar.

They need to integrate more with security options. When the customers want some specific security functionality they begin to think about other platforms. 

The stability is very good. There are no bugs or glitches. It doesn't crash or freeze. It's pretty reliable. 

Scaling is simple. It depends on the licensing. If you have licenses for that, the only thing you have to do is to continue with the enrollment of the terminals. It's very easy. You have to assign the terminals to a group of users with different restrictions or policies and that's it.

With the CSP licenses, we as a cloud service provider, are obliged to provide services. With our service, we provide support to the licenses. When we sell licenses differently, in the LSP scheme, then we have to sell the premium service for the customers.

I don't use it directly. That said, I know the ratings of the services that we provide for our services. The only thing that I should say is that normally when we have an SLA with a customer for Microsoft, there is a specific response time that we can provide as a service provider. They do not consider that. They say, "Our service is this. This is our SLA." Then, our service level agreement is eight hours. 

Sometimes, when you offer a service level agreement with a customer, the support of the manufacturer or of the vendor is included. It's the only thing that, if you are providing services on an end-to-end basis, you have to consider. Sometimes, when you call Premier Support and you say, "Please, I need a solution before six hours," it doesn't matter for them. They say, "I have not six. I have eight, so don't call me if I'm in the eight hours."

It's very simple to set up. To set up the terminals, it's very easy. You have a manual, and it's very easy to follow. You can configure functionalities for specific users or a specific group of users or things like that. It's great.

The time it takes to deploy depends on the number of terminals and it also depends on the number of different groups. Perhaps you have to configure the different policies for different groups. That might take longer than a straightforward setup. In an installation with, for example, 1,000 terminals, it typically takes less than a month -three weeks or so.

I don't personally handle the deployment myself, however. I offer it to clients. I'm not the one to actually do the manual work of implementing it. 

The amount of people we need to deploy a solution depends on the number of terminals that we have to manage.

Some customers configure everything at the beginning and nothing changes over time. That said, we have other customers that they are continuously asking for changes. This group of customers will likely need three people more to handle maintenance. For every 1,000 devices, you typically need one and a half full-time employees.

In terms of ROI, it depends. If you have licenses included in your plan for M365, Microsoft 365, from the very beginning, if you have to sell that, it depends on the business case that you can do. It's different if you buy a CSP or LSP license.

One kind is considered as a cost and another is considered as an investment. The LSP is an investment. 

In the products and services space, from a pay-per-use perspective, I don't see a relationship between this product and ROI. 

There are different kinds of licenses. We sell two licenses from Microsoft, the LSP or the CSP. The service that we have with Microsoft is based on the CSP kind, so the payment is monthly, considered as an expense, not an investment o asset. It depends on if you buy a set of licenses only for Intune - which can be sold separately, or can be included in M365.

We are gold partners with Microsoft.

I would rate the solution at a nine out of ten.

For simple installations, for simple management, perhaps Intune is fine. However, for more complex installations, it might not be enough.

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're using it for endpoints or mobile devices. We are mainly using it for endpoints. For mobile devices, we are mainly using Workspace ONE.

The key benefit of Intune is its integration with the Microsoft ecosystem. 

Onboarding of endpoint devices is not straightforward. The onboarding process was a little heavier than I thought it would be. That's the key improvement area. Obviously, the more control you have over the devices, the better it is. 

I have been using this solution for about three years. I use it on a weekly basis.

I didn't have any issues.

It is easy to scale. Getting used to using it instead of SCCM is an interesting shift because you don't manage policies the same way. There is a difference, so the scale of that is also interesting to address.

We probably have more than a hundred users.

Their tech support is decent. Sometimes, getting to your first contact can take a little bit longer, but after that, it's pretty good.

Previously, we were using Workspace ONE, but it was cost-prohibitive. We moved because of Microsoft's ecosystem. It was a business decision. The integration of the systems made it easier to stay with something like Intune.

It's not trivial, but it's okay. It's not too complicated. You do have to make sure you read your documentation, and you get an idea of what you're trying to do.

It's reasonable. They're not giving it away, but it's reasonable.

If you can get help from Microsoft or if you can use the fast-track process, it would definitely be worth your while.

I would rate it a seven out of 10.

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.

It helps me to safeguard my identities in terms of conditional access. If a person is using it from outside the office, there would be MFAs that are mandatory. However, the moment they're inside the office, they're probably not using it. There are MDM features, which are my corporate-owned devices. It can be used for MA features and for BYOD scenarios. I have tested it on VPN certification authentication and it works in those areas as well. 

The dashboard is good.

We find the solution to be mostly stable.

The scalability is good.

We've largely been happy with technical support.

This product works very well for companies already using the full Microsoft suite. 

There could be some more security without compromising productivity. They could provide some advisories that alert you as to whether the device is secure or not. They need to be able to show us if there is something malicious happening or not. It would be really nice to have something there that could protect us from malicious activities or ransomware. 

I'd like more reports and KPIs available. We'd like these to be visible so users can be assured their devices are secure. 

The initial setup is a little bit complex.

I've pretty much used the solution since its inception. I've used it from 2012 onwards. However, since 2015, it rapidly began changing the nature of its utilization. I've used it for the last five or six years under this new utilization.

There is always a noise when you are going to manage any endpoint devices, and noise is definitely there with this solution. However, I would estimate it is 70% to 80% is stable. You have to manage it, have to face daily operational issues, which we are doing.

If a company needs to scale the solution, it can do so. It's cloud-based, which makes it easy to expand as needed.

We've used technical support in the past. We have given them feedback. They are good. They keep improving and adding. They keep giving more insights around it. I really like the approach overall that they have.

I am familiar with a similar IBM-based product. If you have a Microsoft-based suite, InTune makes more sense, however, if a company uses something else - such as Google - IBM may be more suited. 

At an enterprise level, it is always a complex initial setup. However, with the cloud, if you use that and you start from scratch, it would be pretty simple plug-and-play. That said, the moment the data comes in from the enterprise, there are complexities as there's only one system you are going to have to handle multiple devices and users from 300 to 30,000 to 300,000. It depends on how you are going to handle it.

For per device, it is not much work to set up the solution as there are only one or two apps that need to be installed. For policy conservation and many other things, you require some time to think about what needs to be done. You usually, for example, create the profile, which takes a month's time - or a month and a half.

You do not need much of a team technical team for the deployment. You just require a couple of experts - at least one or two - who have a good understanding.  We have around ten people involved in active management of it, and that includes a 24/7 support team to help manage different devices.

We are able to implement the solution for our clients. 

There is a per-user-based license and that is a licensing mechanism. You can pay yearly or monthly.

I'm a user and a consultant. I deploy this solution for clients and migrate to it.

If a client is using a lot of Microsoft, it's a great product to have. It integrates really, really well with everything. However, if a company has a non-Microsoft suite, I wouldn't suggest this as an option. Google and IBM also have suites that might have better solutions that would work for non-Microsoft users.

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

If they are already using Office 365, or they use Microsoft Cloud Service for their office needs, and if they are looking to secure their endpoint devices. Microsoft Intune, in my opinion, would be a good fit for them.

If you are already a part of the Microsoft ecosystem, it's easy in terms of adoption.

The Microsoft Windows Autopilot and Defender policies are the most valuable features of this solution. 

You can manage your endpoint's security, as well as your antivirus. 

You can utilize Microsoft services to roll out updates to your Windows clients. 

The Microsoft ecosystem and integration with each other excites me.

Microsoft Intune is straightforward.

Microsoft leads the way in terms of the ease of use of its Windows management services. I would say that a large number of customers, roughly 60 to 80 percent of the industry median, are on Windows devices rather than Mac devices. 

Typically, which systems are used in the real world by their employees.

What it lacks in terms of content management, is the addition of a few more features. When it comes to new or updated devices, I believe Microsoft is still falling short. It lacks the features necessary to integrate these types of devices, such as handheld added devices, which are commonly used in the eCommerce industry. For example, RF guns are used for scanning. They are commonly used to scan eCommerce packages, which Microsoft Intune needs.

Intune is behind the game, but it has been catching up in terms of the capabilities and features that it now has to offer.

Mobile security needs to be improved.

There should be more focus on mobile device security and integration.

I have been working with Microsoft Intune for three years.

The stability of Microsoft Intune is good. I haven't seen many global outages. In terms of stability, Microsoft is the best at what it does.

In terms of scalability, I believe Microsoft Intune is scalable, but it needs to add a lot more features in order to catch up with the competition.

When you have a pressing issue, there is a lack of response. I believe Microsoft support needs to work on the response aspect.

The initial response and the time it takes to assign a particular engineer to work with the team to resolve the issue needs to improve.

There are no challenges with the deployment of Microsoft Intune.

It's not much of a stretch to say that it's simple to integrate with third-party services. In terms of integration, Microsoft is good.

Microsoft's licensing is more flexible and adaptive than its competitors. In Microsoft, you pay for whatever you use. In terms of services, it is more evenly distributed. You only need to pay for one license to get access to a suite of products. From your office to your endpoint, you are essentially managing your endpoint. Everything is combined into a single console. somewhat more flexible.

I would rate Microsoft Intune a six out of ten.

I work for a company as an administrator for Office 365, and I use Microsoft Intune in this capacity.

We implement this solution in conjunction with Microsoft IIS.

It is an enterprise mobility tool that is used for mobile application management and mobile device management.

This product allows us to restrict users who have access to the system, or to Office 365. We have to enroll the devices and give the users rights as directed by our management or security department.

The interface is friendly and well organized.

The security features should be improved.

I have been working with Microsoft Intune for two years.

We have more than 1,000 employees in the company, and there are about 500 users for this solution. Typically, it is used by managers and higher-ups.

We have not yet had to open a support case with Microsoft. To this point, we have solved any problems ourselves. As such, technical support has not been a concern.

We did not use another similar solution prior to Intune.

The initial setup is not complex.

The length of time required for deployment depends on the number of people in the environment. It also depends on how adopted people are with this type of technology. Six months is enough to complete a full deployment.

Some of our deployments are on-premises, whereas others are on the cloud.

Our in-house team was responsible for deployment. Based on our license, we have the option to engage with a partner but we haven't used them.

When it comes to security solutions, it is difficult to calculate the return on investment. This is because it is somewhat like car insurance, where car buyers are protected if something happens. If there are no incidents then you don't see it but you're still protected.

This cost is approximately $30 USD per user per month.

This product is included with our Microsoft 365 E3 subscription.

My advice for anybody who is looking into this product is to try it before they buy it. Microsoft offers a program that allows them to do this.

I would rate this solution a nine out of ten.

We use Microsoft Intune to secure our mobile access when you're assessing your data from your mobile. Additionally, we use the solution to limit people from transferring files to people that are not part of our domain, and secure company data from exposure.

The one feature we find most useful is the Mobile Application Manager. There are two types, we have the complete MDM and the Mobile Application Manager(MAM). We don't give our users phones, it is their own personal phone, and we need to allow them to have access to the company detail on their phone. We need to create a balance between their own personal data and the company data. We deploy the  Mobile Application Manager for them so that we won't be able to interfere with their own personal data.

We are always working with Microsoft on improvements. Improvement is not something that is static, we are always looking for a dynamic way of working with Microsoft. We have a support and enterprise agreement with Microsoft. Every quarter, we review the performance of all our solutions and then we ask for further improvement.

In the next release, I would like a feature to be able to properly lock down the device. For example, if an attacker or somebody steals the phone, you can be sure that the pin cannot be broken.

I have been using Microsoft Intune for approximately four years.

I have found Microsoft Intune to be stable.

Microsoft Intune is scalable.

The installation is not complex.

I would advise others to ensure that the technical people are well versatile and trained, especially the technical people that will implement Microsoft Intune.

I rate Microsoft Intune a nine out of ten.