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. 

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.

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.

Effectively, we are using Microsoft Endpoint Manager, which is a mix of Intune and CCM. I'm not sure if there's a specific category for that.

We are using it mainly for the office workers, for the regular laptops. On top of that, we got our fairly specialized devices on our factories, such as the tag down Zebra Scanners, the RealWear glasses - the augmented reality ones and the kiosks as well. Those are the main use cases.

The solution offers very good integration with broader enterprise systems.

The scaling seems to be okay.

It works well if you have a Microsoft environment.

The solution allows companies to capitalize on costs, especially if they are a Microsoft shop.

The product needs better management support, for sure, especially between non-Microsoft applications. It would be good, for example, to have some Chrome OS support.

The solution requires baselines within the web console. That's something that is missing. 

They need better delegation capabilities in the reporting.

The solution requires Mac support.

We've used the solution for about two years at this point. 

Recently, the scalability seems not to be very good. There are minor incidents appearing quite frequently. Besides that, from an overall standpoint, compared to Workspace ONE, it's much more stable.

The solution is scalable.

We have about 70,000 users on it.

We are using this solution extensively. We use it for daily routines. It's one of our core services. It's used by our end-users.

We are increasing it. We are willing to extend it in the near future.

We are not satisfied with technical support. Some improvements might be required.

We did previously use VMware. We tried mainly to reduce some costs. This product seems to come as a part of a bundle, which slightly reduces costs. Also, VMware had plenty of functionalities that were not necessarily fitting into our landscape. We were not able to capitalize on the cost of the process. They didn't have any great integrations with broader enterprise systems.

The initial setup was quite straightforward.

We do not need much staff for the maintenance of the solution. It's pretty low maintenance.

Our team handled the setup. Our internet team did it. We didn't need any integrators or consultants. 

We have a broader enterprise agreement which is set up as a four-year period.

In terms of extra costs, there may be some infrastructure costs, especially for the on-premise part of the solution.

I'm a service manager right now.  I'm a little bit within the scope of the consultant versus the advisor.

We're using the latest version of the solution.

Potential new users need to strongly assess their needs. If they are already on Microsoft stack, they shouldn't look for any other solution than that. If their daily usage or utilization or needs are varied and they have a variety of devices, not necessarily based on Windows or other standard platforms, they might consider a different solution, especially if they need Chromebook support.

I'd rate the solution at a seven out of ten.

Microsoft Intune is a comprehensive solution for mobile application management and mobile device management, securing various endpoints like Windows, Android, and Apple devices. It excels in managing BYOD scenarios, employing work profiles to segregate personal and company data, and ensuring device configuration and compliance with company policies.

Intune provides a centralized management solution, although its suitability depends on specific needs and comparisons with alternatives like Jamf, Kandji, or ManageEngine. Overall, Intune is a sufficient solution for general use cases requiring essential device management and data security.

The Intune Analytics section is quite useful, especially for Windows upgrades on remote devices. We frequently utilize it to assess compliance and gather analytics on upgradable devices, including TPM and Secure Boot support, and memory capacity. This allows us to identify devices that meet the requirements for Windows 11 and proceed with deployment accordingly. It's particularly valuable for managing Windows 10 to Windows 11 upgrade scenarios.

Copilot for Microsoft 365 is a valuable tool that I use daily for creating proposals, summarizing Teams meetings, and generating content in Word and PowerPoint. It's even helpful in Outlook on occasion. Additionally, both Bing Enterprise and the standard Copilot in Edge are particularly useful when integrated with Customer Data Protection. This integration allows Copilot to securely access company data, including emails, presentations, and documents, to provide relevant recommendations and answers to queries.

Intune secures Bring Your Own Devices through network access management and work profiles, separating personal and company data. Additionally, it utilizes Defender for Endpoint for device security and facilitates deployment. Features like cloud app security, Microsoft Purview, and data loss prevention further enhance security and compliance, depending on the Microsoft 365 package, protecting both devices and data.

Privilege Access Management sits mostly on Entra ID and is deployed through Intune.

The primary challenge lies in managing employee devices, particularly differentiating between personal and corporate devices. Personal devices often face pushback against deploying security measures, while corporate-owned devices can be managed more securely and effectively. For instance, if a corporate device is lost or stolen, Intune enables remote wiping to protect company data.

Intune has helped in integrating Windows Update for Business to ensure machines are compliant. It provides functionality for workflow management on devices and separating company data from personal data. It is also used for deploying security and compliance capabilities depending on the Office 365 package used.

I find Microsoft Intune valuable primarily for its Windows management capabilities, along with its Android Enterprise and Apple device management for mobile devices. The mobile application management features enable BYOD support and work profiles on personal phones, enhancing security and control. Additionally, Intune excels in configuration and compliance management for Windows 10, ensuring devices receive timely updates and adhere to organizational standards.

While Intune effectively handles basic functionalities such as device management, data separation, and updates, it may present challenges with update times and limited advanced features.

Intune is not the most user-friendly mobile device management platform available. Compared to Jamf, AirWatch, or VMware Workspace ONE, it is not as intuitive or easy to navigate. 

The primary challenge with Intune's enterprise application management feature is its focus on the Microsoft application stack. This limitation makes managing third-party applications difficult, as there is no centralized store or streamlined process for batch operations. Intune lacks the robust support for third-party applications.

Microsoft frequently changes its offerings, so features previously included in Intune might now require Intune Suite. For example, managing device certificates, once an Intune feature, now requires this separate package. Essentially, Microsoft releases new features but places them in Intune Suite, requiring an additional purchase for functionality we might expect in the standard Intune license. This ever-evolving strategy means staying current with Intune can become costly.

I have been using Microsoft Intune for almost five years.

Microsoft's product support can be inadequate, with slow response times and unsatisfactory resolutions impacting the overall user experience. This contrasts with Jamf's support, which is generally perceived as superior due to its responsiveness and effectiveness.

Neutral

Microsoft Intune's costliness stems from licensing fees and the overhead associated with its management, user experience, and device remediation. While its licensing costs are high, the platform's limitations in manageability and user experience customization further contribute to the overall expense. Unlike Jamf, which offers greater flexibility and remedial capabilities, Intune's intrusive, yes or no approach limits user customization and potentially increases support needs. Therefore, determining Intune's true cost of ownership is subjective and depends on how these factors are measured.

I have evaluated Jamf, Kandji, ManageEngine, and VMWare Workspace ONE.

I would rate Microsoft Intune a six out of ten. Its management is not user-friendly, and device additions can take up to 24 hours to synchronize, unlike Jamf, which updates within 15 minutes. This delay is problematic for immediate remediation actions, such as removing harmful content or addressing device exposure, where a 24-hour wait is unacceptable.

It is advisable to prepare for the complexities of Intune and consider Jamf for better support and manageability if working alone. If you plan to use Microsoft Intune, be prepared for manageability and potential delays in changes and support responses.

The solution has a holistic approach. The device management, application management, identity management, and cybersecurity features are valuable. It brings all of the endpoint and security management tools into one place. It provides complete integration with Microsoft products. It provides full endpoint visibility and IT controls across device platforms.

It makes the security measurements easier to maintain. The user experience is sufficiently good. It helps secure hybrid work and protect data. The tool provides an add-on that integrates artificial intelligence and Microsoft Graph. It is a good development. The product has affected IT productivity in our organization.

It's a good platform for management and security for all kinds of devices. There is less trouble for the users so they can do more. For the IT team, the product provides a guarantee of security. The solution has reduced the risk of security breaches by 30%. It has helped us save on direct and indirect costs. We are a global organization. We need fewer resources and are more secure due to the solution. There are much less incidents based on security.

The tool helps consolidate vendors. There is much more functionality that we can leverage. It has positively affected the security posture of the organization and licensing costs. The capabilities of Intune that are integrated with Microsoft 365 and Microsoft Security are very important. I work in environments that are completely Microsoft-dominated. The more we use Microsoft, the better the integration. It is easier to connect the different parts. I am satisfied with the product’s performance.

The add-ons must be integrated into the solution. They should not be separate add-ons. The add-ons have artificial intelligence and must be part of the base product.

I have been using the solution for very long.

I am satisfied with the product’s scalability.

The technical support is quite reasonable.

Neutral

The pricing is competitive, but it is not cheap. All the licenses are not cheap nowadays.

I have used AirWatch in my previous organization. The integration provided by Microsoft Intune is its biggest advantage over its competitors. Most of the integration with third-party tools is good.

I'm familiar with Microsoft Intune from the beginning. I have heard that the solution’s Tunnel for MAM feature enables users to use their private phones to make a secure connection to the company's network to access company resources. I haven’t used it yet. We are partners and customers. Overall, I rate the solution a nine 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. 

When using Microsoft Intune our main focus was on Office 365. Our Azure Active Directory was only held up for users. When we had implemented the endpoint user management in our workstations in a cloud environment, then we started to use Microsoft Intune on an everyday basis, such as remote connection, deploying workstations, Autopilot, and deploying applications. It is a great tool.

Microsoft Intune is a cloud solution. For an on-premise solution, you have SCCM from Microsoft. However, it is old and it will be an obsolete tool soon. There are other solutions such as ManageEngine. Microsoft Intune tool is in the cloud and we can manage everything. You can manage Azure AD, Intune, and not only mobile hand devices, such as iOS or Android, the main focus is on workstations. This is what makes the solution powerful.

I expect Microsoft Intune to have more features in the cloud because there are two major functionalities that we need to be added. This is software metering and license management. These functionalities, for now, must be on-premise. For this purpose, we have set up a SQL Server and I hope that in near future this option will be in the cloud in Microsoft Intune.

I have been using Microsoft Intune for approximately two years.

The stability of Microsoft Intune is great.

Microsoft Intune is highly scalable. When you configure your network connection, there are a lot of firewalls and you can optimize your internet speed. Everything works great. You can tune up some repository sizes with Microsoft because if you have large applications, such as AutoCAD, when you upload the images to the cloud it takes some time and it needs more space.

We had four people in my company that used Microsoft Intune on approximately 100 systems.

The technical support of Microsoft Intune is good.

I previously used BEAM for client management from an American company and SCCM from Microsoft. Additionally, I used ManageEngine and Lansweeper. Lansweeper was a light tool with similar functionality. We use it in combination with TeamViewer.

We have projects all over the world. It took us four months to implement Intune Microsoft Intune for approximately 100 clients in three countries. We implemented it in many locations, such as Germany in three cities, Croatia, and Bosnia, there is a total of 50 locations. Microsoft Intune is easy to work with.

The initial setup is not simple, you need a specialist to be involved that has the appropriate experience. This is not a solution where out of the box you run the executable file on your system and hit next, next, to finish the installation.

Microsoft Intune requires specialists to implement the solution. We used an external team of two engineer specialists that was dedicated to the project. I helped too because I have experience in plant management.

There is a license required to use the solution. If you're core users in Office 365, for example, you have Outlook email and E3 license, this is only email. You have to buy an EMS license to have Microsoft Intune. It is expensive.

I would recommend the solution to others.

I rate Microsoft Intune a nine out of ten.