Microsoft Intune Reviews

We use the solution to manage the Microsoft apps on company-owned devices. 

The product has eased the deployment of Microsoft apps to the devices. We can manage it properly. We can control it and push the updates. Another company helped us with the deployment. However, we can do it internally. 

Microsoft Intune's most valuable feature is easy management. It also keeps our devices secure. 

Microsoft Intune needs to improve the initial login process.

I have been working with the product for two years. 

Microsoft Intune's stability is good.

We have seen ROI with the tool's use. 

We don't have to worry about security after deploying Microsoft Intune. We can manage the security of our data and apps on the devices by using a single authentication mode. I will use it again if I have to make a choice. I rate the product an eight out of ten. You need to consider user experience when making the choice. 

Mobile device management is the main thing for which we are using it. My role is to review the implementation.

Mobile device management is most valuable.

We only have major classifications for iOS and Android, but there are different brands that have different cycles of updates. If they can fine-tune it to make it more brand-specific, that would be even better.

I've been using this solution for three and a half years.

It's stable. I'd rate it an eight out of ten in terms of stability.

It's very scalable. I'd rate it a ten out of ten in terms of scalability.

It was deployed for an environment with multiple locations. There are about 500 end users. Our clients are mostly small-sized organizations.

I'd rate the previous vendor with which we had the contract a ten out of ten. We now have a new vendor. They haven't yet started.

We used BlackBerry. We switched because that was getting outdated, and it didn't have all the features that Intune has. Intune is continuously being improved because of the cloud service.

I reviewed its implementation. It was straightforward. There were some technical difficulties in getting it started, but after we resolved them, it was easy. There were some architectural issues we had to resolve because we had legacy architecture.

It was a consultancy service that was provided by us. There were about five people involved. One was a specialist; one was an architect. There were two different engineers having different specialties, and there was a project manager.

We have an engineer who works on the maintenance. There is a team of two engineers to manage Intune as well as Office 365.

There were quite a few, but this was the main solution that we looked at because Microsoft solutions integrate well with other Microsoft solutions.

I'd advise getting rid of legacy stuff. You need to go to the new architecture and new OS. The infrastructure should be matching for the Intune implementation. Otherwise, you will have a problem. That's what we faced. We had to upgrade all our operating systems.

Overall, I'd rate Intune an eight out of ten.

I use Intune to manage all the organization's PCs.

We use a local Active Directory, but we weren't able to manage all our on-site systems without a solution like Intune, and we needed to deploy software like VPNs and other things. It's seamless now to do this through Intune.

The reporting is subpar. That's the only issue we have with Intune. We use another solution for that purpose. 

I have used Intune for about two years.

Intune is stable. 

Intune is scalable.

We purchased our licenses locally. We contact the reseller when we have support issues, and they contact Microsoft support. We've only needed to contact them once or twice. 

Deploying Intune isn't easy, but it isn't too complicated. Someone with two or three years of experience can do it. I completed the initial installation quickly, but migration took a long time because it's a manual process. We deployed Intune in-house with only two people. 

After deployment, Intune doesn't require any maintenance. It's a cloud solution, so Microsoft is responsible for maintaining it. However, we need to handle any tenant-level configuration.

Intune has somewhat of a monopoly. There aren't many alternatives for this kind of solution, so we have to pay what they're asking. Still, I think it's reasonable. 

We are primarily using Microsoft products, so our options were Google Cloud or Intune. We decided that it was better to go with Intune because the learning curve would be steeper with Google. 

I rate Microsoft Intune eight out of 10. We have never faced any serious issues with Intune. My advice to future users is to plan before you deploy or migrate. 

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'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.

We switched to Office 365 applications and we already had an Office 365 license that covers Microsoft Intune. We decided to use Intune for our Mobile Application Management solution.

I only use Microsoft Intune for Mobile Application Management for the management of Office 365 apps. Additionally, we have Microsoft Intune integrated with Workspace ONE.

We have used conditional access policies to prevent users from copying internal resources or internal data to external devices. This has helped protect our organizations from being compromised.

The conditional access policies that we set up are very useful.

Microsoft Intune could improve by being more user-friendly and having it geared toward device management. The graphic interface is not very good.

The VPN option within Intune is not as intuitive as the one available in Workspace ONE. We're trying to implement a VPN tunnel for SharePoint sites. This will allow users trying to access internal resources, such as SharePoint, and other Office 365 data, but it doesn't work as well as Workspace ONE. 

We are in the POC stage of the VPN tunnel. We only have a development tenant for the tunnel. We plan is to implement that in production and get rid of Workspace ONE, if it meets our needs.

I have used Microsoft Intune within the past 12 months.

The solution is stable.

I have found Microsoft Intune to be scalable.

We have over 5,500 users using this solution.

The technical support from Microsoft could improve, it is not as good as the Workspace ONE support. It is difficult to contact Microsoft support.

I have used Workspace ONE, and I would highly recommend it over Microsoft Intune.

The initial setup was complex, and the full deployment took us one year.

We did the deployment ourselves. There is little maintenance required, we have to only update policies. We have a mobility architect that set up most of the backend and we did work with a Microsoft resource for this process.

I have received a return on investment, the solution is inexpensive.

There is a license required to use this solution. However, it was part of a bundle package. 

Microsoft Intune is far less expensive than other solutions, such as Workspace ONE.

We are only using Microsoft Intune because it came with our Office 365 license.

I rate Microsoft Intune a five out of ten.

I work for Mastersystem Infotama who is a Microsoft partner. I am an engineer, and I deploy Microsoft Intune in several companies. Our customers use Intune for their mobile device management. We also use Intune to protect devices accessing the application's corporate data. First, you must be compliant with the same criteria. If users connect with the corporate IP address, they only connect with username and password. But if they connect from a coffee shop IP address or IP addresses that aren't corporate, they will have to engage in multi-factor authentication.

I like that we can implement conditional access. Microsoft has conditional access for mobile device management, and we can categorize it as a corporate application or a personal application. We can protect it so users cannot copy from the corporate application to the personal application, but users can copy from the personal application to the corporate application. 

We can also make one file with different permission for different people. The name of the feature is Microsoft Azure Information Protection. We can configure it to help the user work from home. They can download the file, and they can operate this file in another place, but the corporate organization still protects it. 

We can also protect user access from a mobile phone. They cannot save the file to internal storage for the mobile phone. They only can save the file to OneDrive or SharePoint drive.

It would be better if Microsoft can reduce the cost of the license. as we know the Intune device subscription is licensed per device at a cost of $2 a month. but for the best to enhanced security and feature we must added add-on license or buy/upgrade to bundling license such as M365E5.

Microsoft Intune is a core product, and it's very stable

Scalability is good. It can adopt Android and iOS and manage macOS. We couldn't support macOS two years ago, but now we can.

Technical support is good. We get help from Microsoft support. For Microsoft Intune, if we buy the license, we can get support for free. We can create tickets for the problems. We can also report the problem in the Microsoft portal.

Microsoft Intune is essentially software as a service for mobile device management. To configure Microsoft Intune, we only have to register the domain name and register the DNS. We can log in to enroll the device with Microsoft Intune. After we register the DNS and the domain name, we configure the policies. All policies like user access and permissions. After that, the admin can send the license to every user.

The configuration takes one to five days. But it takes a long time to educate the users on how they can use it. This is because some things change after we implement Intune. Users may complain that they can't do what they did before, but it's better from a security perspective.

Microsoft will maintain it. The customer only maintains the policy and the license.

The price could be better. Microsoft Intune pricing is based on the number of users. Every user license is for 15 devices. consists of 5 devices for PC (Windows or Mac), 5 tablets, and 5 mobile phones (Android and iOS). 

My customers already know and use Microsoft, so they adopted Intune. They use Office 365 for secure collaboration between organizations. Microsoft is the preferred choice and has user confidence to work together securely.

MobileIron has two types of licenses. One is a SaaS-based model, and they provide support, and the other is a license for the on-premise solution. Microsoft Intune offers only a cloud solution.

If a customer already uses a Microsoft solution like Microsoft Office, or an email solution like Microsoft Exchange, it's better to use Microsoft Intune. But if they want an on-premise solution, they can choose another solution like  Mobile Iron or Airwatch solution.

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

Intune provides a platform for managing all our devices, including mobile iOS devices and PC workstations. It can also control some aspects of servers.

We can automatically enroll our devices with Intune. It helps us implement company-wide policies and ensure regulatory compliance because we can restrict how company devices are used. Intune improves security by enabling us to set conditional access policies for each device. 

Intune can wipe devices. For example, if a disgruntled employee wants to leak the data on their company phone, Intune can terminate their access and wipe the entire device with a click. Conditional access is another essential feature. 

You can set up two profiles on every device to keep personal data separate from company data, and the employee cannot copy data between them. This is a critical requirement for most companies to avoid the loss of sensitive data.  

Intune doesn't provide much control over Windows servers. It's something we struggle with.

I have worked with Intune for six years.

Intune is mostly stable. Microsoft guarantees 97 percent availability throughout the year, so it's pretty stable. 

Intune is scalable. 

I have used multiple endpoint management solutions in the past nine years. I also work with Jamf, a solution that focuses on iOS devices. Compared to Jamf, Intune also has some limitations when working with iOS. For example, Jamf can create specific policies for each iOS device, whereas Intune can't go that far. It also has role-based and device-based features. You can do more customization on iOS devices with Jamf. 

The initial installation isn't too difficult, but it can be complex if you have a large number of devices and need to do lots of customization. It is more complicated to onboard Windows PCs versus mobile devices, which are pretty easy.

The number of staff members required also varies according to the job and the timeline for deployment. For example, I would probably need additional resources if I'm enrolling 20,000 devices in under a month. However, we don't need too many resources if we have enough time

Intune is a cloud-based solution, so Microsoft is responsible for maintaining the infrastructure. We only need to handle the administrative and configuration adjustments on our side. 

Most clients get the ROI they expect, with the exception of those organizations that primarily use Mac and iOS. Jamf is more appropriate for iOS users. You may need to buy two solutions if you have a mixture.

Intune is reasonably priced. When we design a solution, we always compare costs for the client, but I don't know the price of Intune off the top of my head right now. It varies depending on the size of your organization, the market, and the reseller. You can buy a stand-alone license for Intune, or it may be included in a 365 license. 

I rate Microsoft Intune nine out of 10. 

Before implementing Intune or any endpoint management solution, I recommend looking at your internal requirements. Are most of your devices iOS or Android? Do you need automated enrollment? Go for Intune if you're using mostly Android mobile devices and Windows PCs.