Microsoft Intune Reviews

I use Microsoft Intune to configure policies and manage devices.

We implemented Intune to manage devices for specific users and departments, including device ownership and access control.

I would rate the Intune user experience eight out of ten. About two years ago, I was a team leader with an apprentice. Before the apprentice arrived, we hired another employee who, on his first day, asked what Intune was. I was surprised he didn't know but was comfortable with it within a few days. In the last few years, Intune has been user-friendly.

Intune Suite provides robust security at the operating system level.

The enterprise application management feature is functioning well in its current state.

By leveraging cloud infrastructure instead of private systems, Intune has offered increased remote security and greater ease of access. While I still appreciate SCCM's capabilities, I am satisfied with Intune's performance.

I would rate Intune's ability to secure hybrid work and data on company devices as nine out of ten.

Due to the infrastructure being used, Intune has helped save a minimum of 30 percent of our cost.

It is important that Intune is integrated with Microsoft 365 and Microsoft Security for cloud and co-managed devices because integrating user accounts is easy.

Intune consolidates endpoint and security management tools into a single platform, but its exclusive focus on Microsoft devices necessitates supplementary solutions for Android and iOS. While Intune simplifies numerous tasks, it doesn't provide a comprehensive, all-in-one solution, requiring access to platforms like Azure or AD for specific functions. Although valuable, Intune's primary challenge in a corporate environment is the complexity arising from overlapping rights and processes across departments due to its extensive management capabilities. As a global admin, I would implement changes to address these complexities and streamline the management process.

Intune's role structure is overly complex, with too many layers creating unnecessary access hierarchies. While users can mitigate this by limiting active roles, I suggest streamlining the menu structure to improve usability. For instance, combining device lists for Autopilot and Intune would be beneficial, as these functions are closely related but currently separated. Redefining categories and consolidating menu paths would enhance navigation and make finding features easier. Essentially, I propose simplifying Intune's interface by better organizing its components.

I would like to see more tooltips, such as those brief descriptions that appear when you hover your mouse over something. For example, when you move your mouse over the "delete" button, a small box could pop up explaining that the object will be deleted but can be restored. This is especially important for grayed-out options. Users should be informed why they cannot perform certain actions, such as requiring a different role, object unavailability, or access through a different part of the system. Tooltips would significantly reduce the time I spend explaining these limitations to others.

Intune Suite's remote command functions could be improved for security. Internet connectivity is required for remote resets, and other actions are limited. I propose a potential solution involving automatic device lock after a specific period without check-in, allowing access only upon reconnecting to the internet. This would enable remote management functions without a constant internet connection. Additionally, the current unreliability of remote command execution, often requiring multiple attempts or restarts, is frustrating and needs addressing.

While the ability to deploy applications at startup is reliable, the policy-based application deployment method has not reached the same level of consistency. This inconsistency between the two methods is a key area for improvement, as reliable startup deployment is a benchmark for the desired level of reliability in policy-based installations.

Though reluctantly, we are utilizing Advanced Endpoint Analytics as application installs and compliance policy issues plague it. Comm client policy errors frequently skew statistics, providing an inaccurate representation of our day-to-day operations. These misleading metrics are largely due to other Intune component problems. While we can access analytics, we often manipulate data to exclude irrelevant demographics and metrics, such as application install failures, to produce more accurate reports. Similarly, device compliance statistics are unreliable indicators of fleet performance. While Advanced Endpoint Analytics offers potential utility, it primarily highlights underlying issues requiring resolution rather than providing actionable insights.

We can rectify endpoint anomalies. However, we overlook many others unless issues are exceptionally critical and high-priority. While Intune Analytics is a system component we utilize, its performance metrics are underwhelming. Conversely, our other ITSM infrastructure metrics are quite positive. Intune Analytics requires significant troubleshooting.

Intune is not as streamlined as SCCM but offers greater accessibility. While Intune is more assured, SCCM ultimately proved more efficient in terms of time spent.

I have been using Microsoft Intune for six years.

I would rate the stability of Microsoft Intune nine out of ten.

I would rate the scalability of Microsoft Intune nine out of ten.

The technical support is good.

Positive

I would rate Microsoft Intune seven out of ten.

We are working to expand Copilot's utility beyond its current primary use case of text-based summarization, which offers limited business value. While it aids productivity in meeting contexts, it does not significantly contribute to tasks that generate value. Consequently, we are investing resources in improving Copilot's capabilities without seeing commensurate returns.

Intune is an accessible system and one of the industry standards, so there's not a lot that you'll be left wanting.

We use Microsoft Intune to manage our endpoint.

Microsoft Intune simplifies endpoint and security management by unifying app deployment, device administration, and security features under one cloud-based platform. This lets us easily generate reports, and even remotely wipe missing devices through the Azure portal, enhancing overall endpoint protection.

Intune's user experience has been fantastic! The flexibility, especially with the company portal, allows users to independently install applications. This eliminates the need to constantly request installations from IT, saving everyone time.

Initially, some resistance and a learning curve slowed our adoption of Intune, but its benefits became clear during the shift to a remote workforce because of COVID-19. After initial deployment in 2020-2021, Intune simplified onboarding for new hires with remote access, allowing them to sign in to their laptops and gain immediate access to company resources.

Microsoft Intune helps with hybrid work models to secure company data by allowing employees to access work resources with BYOD while enforcing security measures on those devices.

Intune has positively affected our IT team's productivity. Everything is automated so their workloads have been reduced by 50 percent.

Intune has allowed us to consolidate other vendors. 

Microsoft Intune simplifies device management by replacing the traditional method of installing OS, joining a domain, and configuring everything manually. With a central management portal, we can easily group and manage all devices, eliminating the need to physically join them to a domain. This allows for seamless enrollment from anywhere, making Intune a user-friendly and flexible solution.

Manually syncing devices to enforce policies is cumbersome. Automating this process in Intune would significantly improve efficiency.

The licensing cost has room for improvement.

I have been using Microsoft Intune for three years.

We experience occasional delays with Intune, especially during updates, software deployments, and device syncs. While changes on the Intune portal should ideally reflect immediately on all devices, restarts or repeated syncing might sometimes be necessary for policy updates to reach endpoints. However, Intune functions well once everything is up-to-date.

Microsoft Intune is scalable as long as we have the licenses.

While SCCM offers a lower upfront cost with a single license, Intune's cloud-based subscription model provides greater flexibility and more features. Although continuous subscription fees make Intune more expensive over time, its functionality outweighs the cost factor for many users, especially those who don't require constant network connectivity for updates.

The initial deployment process was straightforward. We followed the on-screen instructions, downloaded the necessary software from the cloud, and our device was ready to use.

The time it takes to deploy Intune depends on our internet speed and location. On a fast network, deployment can be completed in ten to 20 minutes. Slower connections with high latency can take 30 to 45 minutes, and remote offices with limited bandwidth may require up to an hour or two.

Two people were required for the deployment.

The implementation was completed in-house.

Using the Cloud is expensive. Perhaps in five to ten years, we will see some cost savings.

The Intune license model is costly. We need to have an enterprise mobility license to use Intune. 

I would rate Microsoft Intune eight out of ten.

Our organization is currently piloting Microsoft Intune Copilot, which includes its AI functionalities. We're evaluating its features and functionality to determine its suitability for broader deployment across the entire organization.

Microsoft Intune simplifies mobile device management with BYOD for businesses, reducing the total cost of ownership. Intune's user-friendly interface eliminates the need for extensive IT expertise, making it a strong recommendation for most organizations.

We use Microsoft Intune to automate the onboarding and maintenance of our customers.

Before using Microsoft Intune, we struggled with software deployment and remote device wipe capabilities.

Most of the Intune is for all the remote devices, so it's all on-prem. For cloud, it wouldn't make too much sense.

Microsoft Intune brings all our endpoint and security management tools into one place. We use both Mac and Windows devices. Having all our endpoints and management tools in one place is helpful. I have a single place to check for current status and add and remove assets.

Microsoft Intune provides full endpoint visibility and IT control across device platforms. Having full endpoint visibility and IT control across device platforms allows us to deploy and manage the systems more effectively.

Intune works well and is seamless for the users.

Intune has allowed us to standardize better.

Intune's use of Microsoft security signals has improved our security because we can now take remote action on these systems as well as have a more common deployment.

It has helped to reduce the risk of security breaches in our organization because of the standardization and single sign-on.

It has also helped us reduce the number of IT staff, saving us costs.

The Asset Management and Auto Pilot are valuable features.

One of the other features we leverage is the single sign-on that Intune facilitates.

The Mac integration has room for improvement.

I have been using Microsoft Intune for two years.

I have not had any stability issues with Microsoft Intune.

Microsoft Intune is highly scalable.

Although I have not used the technical support for Intune, I am not happy with Microsoft's technical support in general.

Negative

The initial deployment was complex until we understood the process. We went through a simple dev test and then prod methodology. 

Two to three people were required for the deployment.

We implement Intune for our customers.

For organizations that are a Microsoft shop, the pricing is compelling. To buy it outright, it's two dollars a seat, which is cheap. The price is worth it.

I would rate Microsoft Intune an eight out of ten.

We have 400 users across multiple regions internationally.

Given the evolving security landscape in the cloud, it's crucial that Intune Suite is integrated with Microsoft 365 and Microsoft Security for both cloud and co-managed devices.

Maintenance is required to keep the packages up to date for any software we deploy. We have four people that deal with the maintenance.

I recommend planning and understanding how Intune will be used before deploying it.

We use Microsoft Intune to manage our corporate devices such as mobile devices.

Microsoft Intune unifies all of our endpoints and security management tools.

Since Intune is part of Microsoft and managed under one umbrella, we don't need any third-party solutions and we can control everything from Intune which enhances our IT and security operations.

Microsoft Intune provides full endpoint visibility and IT control across device platforms ensuring our data is secure.

The user experience for Intune is good.

Microsoft's security signals within Intune improve our security posture.

Endpoint Privilege Management enables us to enforce least privilege access. We can assign different types of access based on each user.

Our attack surface is minimized because if there are any threats or suspicious activity, the affected device is automatically blocked and it becomes non-compliant. The application and company data become inaccessible until the issue has been resolved. These actions also trigger email notifications to inform us of the situation.

Implementing Microsoft Intune has significantly improved the efficiency of our IT team. Previously, managing our devices involved juggling Active Directory and SCCM, requiring multiple tools and a scattered approach. Now, with everything centralized in the cloud, we have a single portal, a single point of control, and a single subscription. This eliminates the need for dedicated servers and complex hardware setups, reducing the need for manual monitoring and update triggers. With Intune, everything is under one umbrella, offering a wide range of options with just a click. No more complicated settings or fragmented workflows. We simply choose the desired policy, perform a few clicks, and our machines are enrolled and updated seamlessly. This streamlined approach has not only boosted our IT team's productivity but also enhanced our overall security posture.

Intune has helped reduce the risk of security breaches by up to 70 percent.

Microsoft Intune has helped our organization save costs.

The many policies available in Microsoft Intune for managing our devices are valuable.

The policies we had in SCCM and AD offered features that are missing from Microsoft Intune.

I have been using Microsoft Intune for one year.

I would rate Microsoft Intune's stability a seven out of ten because it needs more granular policies.

The first level of support is not good but the higher levels are knowledgeable and they are available 24/7.

Neutral

We previously used Microsoft System Center Configuration Manager and switched to Microsoft Intune so we could better secure our personal and corporate devices.

The initial deployment was straightforward. We need a license to join the machines to Azure and then apply the policies we create.

One person is required for deployment.

The implementation was done in-house.

I am satisfied with the pricing.

I would rate Microsoft Intune a seven out of ten.

Intune has helped us consolidate vendors. The consolidation has saved us on licensing costs.

We have 100 plus customers and a team of 20 people using Microsoft Intune.

It's important that Intune's suite is integrated with Microsoft 365, and Microsoft Security for both cloud and co-managed devices.

Intune does not require maintenance but we do need to monitor the status of our devices.

I recommend trying Microsoft Intune.

Microsoft Intune is used for Mobile Device Management. We enrolled our mobile devices as well as the mobile device solution for corporate devices. We have a lot of policies such as the compliance policy, and the conditional access-based policies for the corporate mobile user and we use the solution to assign their  Outlook Teams and other configurations for the organization. 

We use Intune to design compliance policies that apply to corporate devices and to wipe data from devices when users are terminated. Intune is also used for mobile-based solutions, but we have recently explored its capabilities by using the Autopilot feature. With Autopilot, Windows 10 devices can be reset and new versions of Windows 10 can be deployed from Intune.

Intune has many benefits from the Microsoft perspective. This solution can manage Windows 10 devices, app management, and provide security solutions. We don't need to worry about our network connection, and we'll be more secure with regular security patches and compliance. Since everything will be deployed through the internet and users will log in using the internet only, the risks have been mitigated. Security updates, security patching, and the application will be targeted from Intune. The location tracker will be available to track where the device is and the user's location. The user will be restricted from accessing certain applications using compliance policies. Conditional access policies will be based on the reason why the user needs access to the application.

Microsoft Intune is one of the best products in the industry for managing Windows devices. The solution has more feature restrictions. The conditional access policies also eliminate the dependency on the on-prem network for the devices. The solution also manages our security settings and a lot of other beneficial features such as Microsoft Purview which gives us the compliance portion. We can manage all aspects of our device from a single console, including M365 services. This allows us to configure data classification types, such as public, private, internal, confidential, and highly confidential.

The best feature is that we don't need to worry about downtime. We don't need to worry about the network connections of our office or the virtual private network. Everything is being done through the internet. Using Intune Autopilot, we can configure and deploy everything to the devices.

We need the capabilities of the Cloud Management Gateway (CMG) to be enhanced through Intune instead of Azure. I suggest that Microsoft consider this. If the user already has a subscription to Intune, they should not need to buy an additional subscription for Azure services.

The support needs improvement. When we need support, we don't get a response within the SLA because the support has been outsourced.

I have been using the solution for five years.

Microsoft Intune is a stable product. For the configuration, we could reach out to technical support, but other than that, we need not worry about anything. If we have configured the product correctly and we are not going to enhance any additional capabilities in Intune, then we need not worry about technical support.

The solution is extremely scalable. I give scalability ten out of ten.

Microsoft has outsourced its technical support so if we raise a ticket with severity, the technical support team may not be able to respond to us within the timeframe or the standard we expect. Sometimes we get the call within four hours. Sometimes we won't get that call for a day or more. The service side is pathetic now. To get support from Microsoft, we need to have our TAMs in place and then we need to submit the ticket. If we have already aligned a TAM for the tickets, we get support from Microsoft.

Neutral

Previously we were using Microsoft Configuration Manager. The Microsoft Configuration Manager is the dedicated server for managing devices on-prem. We need to make sure the device is on the same network through which the policy is getting replicated. The dependencies with that server as well as with the network are important, and the devices need to be online on the network. Using Intune as a backup solution, if the device is not on the network or if the device owner is not in the location but it has an internet connection, then we can deploy all our physical solutions onto the devices. We are using both, the Microsoft Endpoint Configuration Manager as well as Intune, since a couple of policies are still only being managed with the Configuration Manager.

The initial setup is straightforward. Once we have subscribed to the license, we will receive our tenant ID and organization ID. We can then access the portal and configure whatever we want. To save the configuration, we must enable it from the portal itself. The Azure Ready Connect GUI console makes it easy to join devices to Azure and to create and deploy conditional access policies.

We have four or five global administrator access levels in our organization. The most limited level is for the global administrator, who can be limited to one person. We need to involve them to enter the password while configuring the CMG, and then the Microsoft support in case we are missing any configuration during the installation or managing Microsoft Intune.

We deployed across more than 10 to 15 countries. The solution is used in India, the US, and England.

We have seen a return on investment using Microsoft Intune. We can save money by establishing our management point and cloud distribution point in Azure. Cloud support is an additional cost. We have to pay Microsoft for the VM, which doesn't act as a management point and the cloud distribution point for the endpoint. Endpoints are the on-prem devices.

Earlier, Microsoft used to give the license using the MSDN subscription, now the subscription part uses the M365 E3/E5. Existing E5 license holders for M365, Intune, and Azure, receive a free license.

If we're only upgrading to Windows 10 for the monthly security patches, Ivanti has Patch Now. Patch Now is a solution that gives us the same set of capabilities as IBM BigFix, but Intune has enhanced capabilities. Ivanti Patch Now is another product similar to the Microsoft Configuration Manager console and we have to make sure the device is on the on-prem network itself. Intune is a cloud-based solution that does not require the device to be on-prem. Everything is in the cloud, including device tracking, writing, and initiating remote connections.

I give the solution a ten out of ten.

I manage the endpoints for the implementation strategy and use the desktops or Windows for migration. I'm not from the mobile device management team, but I can give presentations on how the devices will work in the Autopilot zone with Intune. I'm also familiar with conditional access policies and what needs to be in place for a successful migration.

We have 35,000 end-users.

Maintenance is minimal. There have been no reports of any outages from the cloud perspective, meaning that any downtime is from Microsoft itself. However, on-prem systems may experience challenges. We don't need to worry about downtime and all the systems will still be operational.

New customers are definitely going to reach out to Microsoft for purchasing all the products. Microsoft will have its own lab. They will give us the live demo from the lab, but that won't be a feasible solution. We should check and bring that solution to our environment. It would be good if we can create our own test environment and then ask Microsoft to perform all those configurations and just train our engineer about the Intune part. We will know all the legacy parts of our environment which could impact when we are moving our devices to Intune, either the legacy app, legacy hardware, whether those devices are supported, the TPM, the Tested Platform Module, the BitLocker configuration, everything we need to understand before we move our device to Intune.

I worked with Microsoft Intune.

Third party integrations are very convenient to use with Microsoft Intune.

Whatever is required is available in Microsoft Intune. Remote access functionality could be added in future updates.

Microsoft Intune is currently overpriced.

I have been working with Microsoft Intune for six years.

Microsoft Intune support needs improvement and they could work on enhancing their support services.

Microsoft Intune is the best among competitors, though I haven't worked with other similar tools.

I would rate it an eight out of ten. 

Our primary use case is managing our devices and policies and having a consistent way to manage devices on the Windows side.

Implementing Microsoft Intune has provided a more streamlined and consistent method for device management across our multiple domains, effectively consolidating our administrative efforts.

The Microsoft Intune user experience is good. I would rate it eight out of ten.

Within Intune, managing policies and having a consistent way to manage devices is valuable.

Intune is a constantly evolving product, with Microsoft prioritizing its development over on-premise tools. While no specific feature requires immediate improvement, the ongoing expansion of reporting and inventory capabilities promises to enhance its utility.

I have been using Microsoft Intune for at least seven years.

The Microsoft Intune stability is getting better, and I would rate it eight out of ten. A couple of years ago, the performance was not as good as it is now, but there are noticeable backend improvements.

Microsoft Intune's scalability has improved over the years.

Positive

We used Configuration Manager and are continuing to use it. The addition of Intune was due to Microsoft's direction.

I would rate Microsoft Intune eight out of ten. Nothing is perfect, but it's good.

We began using Copilot, but it is currently restricted to a select few. Due to its potential for increased productivity and improved user experience, we are advocating for its wider adoption.

I support mobile technology for the Department of Homeland Security first responders nationwide, particularly in the weapons of mass destruction area. This diverse group includes first responders, firefighters, and police, explicitly located in high-risk urban areas like New York, including Northern New Jersey and Southern Connecticut, Chicago, San Francisco, and Washington D.C. Additionally, a mobile deployment group travels to major events like New Year's Eve in Times Square, Pro Bowls, Super Bowls, and World Series games, carrying chemical and biological detection devices with Microsoft Intune integrated into their mobile technologies.

Intune consolidates our endpoint and security management tools, providing a centralized solution for controlling security and ensuring compliance with the federal government, NIST, and ISO standards. This centralized control is crucial for maintaining a secure and compliant environment.

Endpoint analytics help proactively detect and remediate anomalies on endpoints. We receive alerts from various detection devices, including biological, radiological, and mobile platforms. A common challenge with Bluetooth or similar technologies is maintaining connectivity, whether it's Bluetooth or Wi-Fi. Additionally, we need to protect the Wi-Fi network itself. To address these security concerns, we often use proprietary connectivity protocols to ensure data integrity and prevent hacking, fraud, or unauthorized access.

Intune's Cloud PKI helps us manage our current and historical actions. We can easily access recurring tasks and look for common problems, which is an important attribute of using the cloud service.

For our benefit, Intune is very useful. However, the challenge is keeping it up to date and dealing with shift workers across different time zones. When deploying to the New York region, multiple fire and police departments use these devices. We maintain a database to track deployment status and device updates to ensure effective management. Devices unused for 90 days are suspended with the carrier to avoid higher fees for inactive devices. Although maintaining these devices can be challenging, we closely monitor them and collaborate with regional directors to ensure they are turned on at least every 90 days for automatic updates.

We use the privilege management feature exclusively for points of contact or location managers. Due to the group's diversity and the inclusion of shift workers, these individuals require specific access from an identity management perspective. We only permit access in these designated areas.

Intune saves costs for the federal government.

One reason my employer switched to Intune was the integration of Intune with Microsoft 365 and Microsoft Security.

We deploy applications and manage infrastructure based on specific needs, including lockdown services to prevent unauthorized app downloads. We utilize management controls for this purpose. Currently, it's a small environment consisting of approximately 20 major locations nationwide, with plans for future expansion. The management control feature is the most valuable.

Intune endpoint analytics can be challenging. However, factors like usage patterns, timeliness, and time of day can provide valuable insights. We must also consider help desk tiers, change management processes, and other relevant factors. We must prioritize user-friendly reporting over complex, jargon-filled explanations to present these analytics effectively to the federal mobility group and leaders countering weapons of mass destruction, who may need to be more technical experts.

I have been using Microsoft Intune for 18 months.

The technical support has been good. We have priority, given that we work with first responders.

Positive

Before I joined as a contractor consultant, the government used VMware. They changed vendors, and the new vendor convinced management that Microsoft Intune was superior to VMware. I disagreed, having done a lot of business with VMware over the years. I believe any VMware issues could be resolved with the proper account management and connections in production and development.

They believed Intune offered superior controls compared to VMware, but a thorough evaluation wasn't conducted. Instead of adhering to federal government regulations that mandate due diligence when switching technologies, they bypassed the process. They directly consulted the individual heading CWMD at the time, whose recommendation led to their employment and subsequent contract. Their justification for the switch to Microsoft Intune was based on their assertion that it would enable them to perform better. Typically, an in-depth evaluation is conducted before any transition, highlighting the differences to the federal government and justifying the necessity of the change. Cost-benefit analysis might be a factor, but not always the deciding one. Improved engineering, deployment models, and infrastructure management could all contribute to the rationale behind such a decision.

I would rate Microsoft Intune nine out of ten.

The user experience is a learning process, and it's improving. We primarily deal with shift workers who share devices, making identity management difficult and necessitating tighter security. For first responders, feedback and chemical and biological device management for alerts aren't the top priority. They focus on murders, robberies, thefts, fires, etc. Getting them to update their devices is challenging. We try to set it up so they only need to reconnect their devices every 90 days, but depending on the vulnerability, it might have to be done sooner.

Intune is a necessary tool, and we're currently undergoing a transformation with one vendor leaving and another coming in. This involves going through documentation, projects, upgrade requirements, and processes. MDM is only necessary due to the number of tools we have, including Sonim rugged mobile devices and Panasonic rugged desktops used in police cars, fire trucks, and other mobile settings. Dealing with Sonim is challenging because our contract is with the carriers, AT&T, Verizon, etc., not the federal government. Attestations and an executive order 14.28 about managing technology on these devices exist. Sonim is developed and manufactured in China, raising concerns about mobile technologies and managing them through third-party suppliers from non-friendly countries. All these factors contribute to the challenges in MDM.