Microsoft Intune Reviews

We've experimented with and deployed Autopilot for building and deploying software through Intune, utilizing Intune policies to modify Azure AD joined systems, now referred to as Entra joined. This covers the entire scope of Intune that we've explored and implemented.

We are a consulting company with extensive experience in deploying Intune. We utilize Intune for hybrid join Entra machines. For clients who have the necessary licenses, while Intune is not a full-fledged Remote Monitoring and Management solution, it can serve as an effective replacement for RMM if you are a Managed Service Provider.

While more mature tools exist for securing hybrid work and protecting data on BYOD and company devices, Intune is a viable option for clients who want to leverage MDM with their Premium or E3 license, especially if cost is a major concern. Despite some challenges with Samsung Knox and iOS devices, Intune has shown improvement, and these issues are less frequent. As Microsoft doesn't have a native phone, limitations are inevitable.

The Mobile Device Management in Intune is a valuable feature.

Microsoft recently separated Defender into Security. Intune does not centralize all endpoint and security management tools into one place. It used to be more centralized.

The Microsoft support has been subpar for some time now. Troubleshooting issues often require us to involve a partner, which isn't an ideal or easily manageable solution given the challenges with Microsoft support. We need a reliable partner, but that partnership might still require Microsoft's assistance.

We've faced significant pushback with Copilot as our clients aren't seeing a favorable cost-benefit analysis. Many are opting for ChatGPT Enterprise instead of integrating Copilot into their workflows. We initially expected significant value from Copilot, but Microsoft's pricing is excessive, and the product itself is not exceptional. It remains quite rudimentary in its current state.

Microsoft should not rely on partners to fix issues. While users can open tickets with Microsoft, they often cannot resolve the problems themselves and must engage a partner. This is not an à la carte solution. Perhaps when Copilot eventually becomes available, it will address this. It's not Intune's fault, as it is used frequently.

I have been using Microsoft Intune for ten years.

The technical support is not good.

Negative

We tried numerous solutions prior to Intune, but Microsoft's inclusion of it within their licensing model incentivized us to adopt it. Since we were already paying for the license, it made sense to leverage its full potential and maximize our investment.

If you're subscribing to Premium or E3, there are no additional costs for Intune, it's included. However, with lower-tier plans, you don't get the full suite of security features. Depending on your specific licenses, you might have some level of Advanced Threat Protection, Endpoint Detection Response, or other Defender tools, but not the complete package. Generally, for around 300 users, you get decent protection with Defender for desktop and server – it's a good value. But with E5 licenses, you're at the enterprise level, and you get what you pay for, so expect add-ons. I don't think Microsoft would position Intune as a primary security product anymore, given their recent cloud changes and the focus on Defender. Intune is useful for patching, but it's not a comprehensive security solution in itself. That's why Microsoft has rebranded their security offerings under security.microsoft.com.

I rate Intune six out of ten.

Many of our clients with premium or E3 or above licenses use Intune because it's included in their Microsoft solution. They prefer to leverage a Microsoft product over a third-party alternative. Additionally, Intune allows us to maximize the value of our clients' existing licenses. Therefore, if a client has a premium license, has under 300 users, or is on E3 or above, there's no reason to use another solution when Intune is readily available.

Microsoft recently transitioned from Intune to Endpoint, then back to Intune. Additionally, they moved certain security aspects of Purview into a separate deployment, as is the case with their ATP Defender Suite. This shift signifies a move away from a single, unified management interface to a more distributed model.

We use the enterprise application management feature to roll out apps. While there are better tools available for app discovery, deployment, and automatic updating, Intune's inclusion in the Microsoft bundle keeps costs down. Although Intune may not be the ideal solution for automated application deployment or MDM, its integration with Microsoft licenses makes it a worthwhile option, especially with the expectation of future improvements from Microsoft.

We use the Advanced Endpoint Analytics but it is no longer in Intune. It's been moved over to the security portal for Defender.

The endpoint analytics feature, which helps proactively detect and remediate anomalies and endpoints, is now part of Microsoft Defender formerly known as Advanced Threat Protection. Gartner rates it very highly. To perform threat hunting, we need the appropriate licensing, such as a P2 Defender license. This functionality is not available within Intune. We are transitioning from the older Advanced Threat Protection to the newer Microsoft Defender platform. Previously, configuration was done through Intune, but now we manage it through the Microsoft security site.

My advice for any organization that is already paying for a Premium or above Microsoft license is to deploy Intune because it makes financial sense. Intune is not a bad tool but if they run into any issues, the Microsoft support is no good so they need to rely on a good partner to help resolve the issue.

Microsoft cannot fully replicate the functionality of a Remote Monitoring and Management tool. However, it could incorporate certain RMM features into its existing products or develop new tools that complement RMM solutions.

By implementing Intune, we are exposing aspects of our infrastructure to the cloud that traditionally would remain on-premises. This means relying heavily on Microsoft's infrastructure and security. As we saw a few years ago with the Department of Justice's issues, which were clearly Microsoft-related, placing all our trust in one provider can lead to potential problems. However, despite these concerns, we have not encountered any security issues with Intune to date. But at the end of the day, we are maximizing our license.

Intune deployment is straightforward if you're well-prepared, whether for a hybrid setup or a purely Azure-based one. Packaging new apps is generally well-documented, but troubleshooting can be trickier. There are helpful PowerShell scripts available, though they might not be easy to find.

We are a Microsoft vendor, not an Intune user. I have deployed Intune for several customers who use this product for business. Our clients use Intune for device management and data security, which gives them control over end-user devices.

Previously, we used a device manager and had a local Active Directory. However, most of our SME customers do not have a local Active Directory set up in their organization that allows them to control their devices. Intune does not require any local AD. It's a cloud application. We can directly join the user devices to the cloud, and the organization manages them. We have enterprise customers and also SMBs, but most of our clients have less than 100 users. 

One of my Indian clients previously had all their devices at the workplace. None of the devices were joined to an Active Directory, so they had to install applications on each device individually. With the help of Intune, we could push the applications to all the portal users simultaneously. 

We have to create a group, assign an application to it, and automatically install it on the user's devices. We also apply the company logo and desktop wallpaper via Intune, which a tech user can change. We can also find the exact location of the devices where the user is sitting.

We also have the option to enroll hybrid devices with Intune. We can enroll users'  devices and separate work and personal data. The devices on the local Active Directory can be joined to Intune. 

Privilege identity management helps. Let's say someone is a company administrator for five to ten days. We can create a dual administrator role for that user for seven days. I can create a PIM role and assign it to the user for seven days, after which the role will be deleted automatically. 

Intune provides routine management of user devices. Once the device is not enrolled in any domain or Active Directory, the IT person must delete every user device to change anything. Intune can work on all those things. That device can be updated and marked as non-compliant. If someone is using Windows 7 or a version of Windows that has been deprecated, we can restrict Windows 7's user ability to log in to the work environment. We can control all this over the admin panel.

If we scale 10 to 50 percent, where new customers manage all their devices. After enrolling all the devices, this work can be done with only one or two people, saving the organization money.

The best part of Intune is device control. If we need to block a user from opening something in their organization's system, we can do it from Intune. If we want to restrict the movement of an organization's data to prevent users from copying the data into Outlook, WhatsApp, or their personal Gmail, we can limit that via Intune. It secures all corporate data.

If they share the data with someone outside the organization, that external person cannot see it until an analyst provides them with access or creates a policy. 

The user experience is good. Users are happy that Intune is managing their work devices. In addition to Windows devices, we can control iOS and other mobile devices. There are good features for managing mobile devices. Work data is stored in different containers, making it easier for users to find their work data. 

In the case of application deployment, we have more services like application updates and patches that can be implemented from the Intune portal. We do not need to outsource these tasks to the device user.

We are currently unable to control aspects of group policy from Teams like we can for GPO. They are still not part of Intune. Microsoft is adding this, but it's currently in preview, and few GPO features have been added to the product. 

I have worked on Intune for the last two years. 

Intune is a stable solution with a lot of capabilities. Most customers who are moving to Intune are also exploring the capabilities of the cloud. 

I rate Intune seven out of 10 for scalability.

I rate Microsoft support eight out of 10. Microsoft is good, but Intune support is delayed compared to other products. If I make a support ticket on the Intune portal, I get a reply after one or two days. For Exchange or SharePoint, I get a response after an hour, but Intune takes a minimum of a day. 

Positive

One product we can compare Intune with is Jamf Pro. Intune has limitations when managing Mac devices. You can enforce fewer policies because Apple has its own hardware and software. There are lots of limitations of control. Most of my clients use Intune for Windows and Android devices, but Jamf Pro if they have Mac devices.

Deploying Intune is a little complex but not too complicated. At the time of deployment, there is much work to do to join a device to Intune. We have to create a new Windows profile and make users log into the enabled Windows profile. We need to configure all the Office applications and copy users from one to another. It takes 30 to 40 minutes on a single device. 

Intune requires some maintenance, but the customer performs the maintenance once we implement it. We support the customers with issues while they are enrolling the device.

I rate Intune five out of 10 for pricing. It's expensive. 

I rate Intune 10 out of 10. I recommend Intune to every organization that wants to secure user data and control endpoint devices. It can manage other platforms on the market. Google has device management software, but it doesn't have the same scope as Intune. 

It's cost-efficient and cheaper than the other device management and third-party applications available. Intune can control most things, especially Windows devices. Intune has the best compatibility with Microsoft Windows.

We use it for pretty much everything related to endpoint management. We use it for bring-your-own-devices and corporate-related devices such as laptops and tablets. We have various operating systems such as Windows, iOS, and Android.

Microsoft Intune is helping to streamline operations and minimize administrative overhead.

We are using the Enterprise Application Management features of Intune Suite. It is very well designed and very well suited for Microsoft-related applications. Third-party applications can require some workaround. They do not always organically fit into the solution, but, overall, it is a great option to have visibility into what the users are using and be able to set up some policies based on that. We can allow applications or deny applications. We can manage what users can onboard. Overall, it is a great solution. We can definitely simplify and streamline some security operations.

Microsoft Intune is great for securing hybrid work and protecting data on company and BYO devices. What is more important is that it is not a static product. It is not that the product is very well established and not moving anywhere. It is constantly evolving. Microsoft seems to be spending lots of resources trying to improve and bring new features. That is great.

We are starting with Intune's Endpoint Privilege Management feature. It definitely impacts productivity. It is great and definitely helps a lot. It helps minimize the attack surface because you do not have elevated privileges accounts available all the time. It helps mitigate or shrink the potential impact or potential entry points into the network.

Microsoft Intune has helped us to manage the accounts with elevated privileges. We are a managed service provider. We sometimes have big turnarounds on the help desk. By their job definition, many of them are supposed to have access to different clients and different sensitive areas. It helps us to mitigate and manage these accounts, and, as a result, to be more secure. We can make sure that those accounts are not being distributed very freely. We have control over their actions. We have control over what they are doing. We have full visibility and accountability.

Microsoft Intune is easy to use, and it is able to enforce policies towards multiple devices. It is able to bring multiple classes of devices into the same security posture. I found that very useful.

The interoperability or communication with a different platform can be better. It is a two-way street. It is not only about Microsoft. The other platforms also have to be willing to share some information, but that absolutely can be improved.

I have been using Microsoft Intune for five to six years.

It depends on the level of access you have. We are a managed service provider, so we do have access to Microsoft. Generally, it is okay if you are able to find the right parties to talk to. It can definitely be improved.

Neutral

We did not use any other solution previously.

First of all, we do not have to deploy any third-party privileged account management solution. That is one tangible benefit. An indirect benefit is that by protecting your environment and making it more secure, you are potentially avoiding any downtime. It is hard to quantify what that downtime cost could be.

If an account with elevated privileges is compromised, you need to perform a lot of work. You need to change the password, disable the account, and recreate another account, so 10% to 15% of the downtime definitely could have been avoided.

We use Defender ATP and E5 licenses.

Intune was an organic choice because we are a Microsoft shop. We use everything that Microsoft can offer.

Microsoft Intune is a great solution. If you have a Microsoft environment, it is definitely the way to go. It can help you to streamline operations and simplify a lot of things. If you go into a multi-cloud environment where you have AWS, GCP, or any other cloud workloads, it may be a little bit more complicated. If you are a Microsoft shop, it is the way to go.

In terms of user experience, for the end users, it is pretty much seamless. It is more on the administrative side. If you properly configure it, it is a relatively seamless experience.

We have just started working with Microsoft Copilot in Intune. It is a very fresh solution. It has just been released, so we are setting up use cases and working with Copilot. We have a Copilot for Teams. We have a Copilot for Microsoft Office that we are utilizing. We have started playing with Copilot for some security operations. It is yet to be determined how much value it can bring. Generally, it can help you analyze and optimize some workloads and events more efficiently, effectively, and quickly. There is great potential, but we will see how it is in real life.

I would rate Microsoft Intune an eight out of ten.

I'm part of a break/fix team using Intune to support our clients. We support Android, iOS, Mac, and Windows devices and help customers with enrollment issues, Apple configuration problems, app deployment, and other issues. My clients are small-to-medium-sized.

Intune brings all endpoints and security management into one place. Through the same portal, we can manage policies and deploy apps. If we push apps through the portal, they can be deployed to all users. 

Intune makes it easier to manage devices, saving us time. It solves many challenges we face in deploying and configuring devices. When something breaks, we need to investigate, starting with the configuration. For example, the kiosks are Android-based devices. When we have issues, we need to check to ensure everything is configured correctly on the portal. 

Intune's security features for Apple iOS and Mac OS are helpful. We can check enrollment, manage public and private settings, and manage the organization's data using security key features. Like the MCM interface, the Intune portal is flexible and easy to understand.

The Cloud PKI feature helps us manage our complex certificate infrastructure across our cloud and on-prem Active Directories. We are using Copilot. The settings are controlled by Intune and SCCM, so Copilot works the same regardless of the product we use. It simplifies IT operations and helps us manage both. We can use AD Connect to integrate our on-prem Active Directory, connect with hybrid devices, and manage every device in the organization.

Intune could add more Linux security features and more integration with on-prem devices. The application deployments can also be improved. 

I have used Intune for around two years.

I rate Intune nine out of 10 for stability. 

I rate Intune nine out of 10 for scalability. 

I rate Microsoft support nine out of 10. 

Positive

We use SCCM to manage users and patches. We can push all the patches using Microsoft releases patches where we can push in a one we're using a one group and meeting one group, and then we are pushing it through this patch management.

Deploying Intune can take one to three days, depending on the configuration required. 

I rate Intune seven out of 10 for pricing.

I rate Microsoft Intune nine out of 10. I recommend Intune because it's more flexible, user-friendly, and has more security features. I work with Microsoft technologies like SCCM, Windows Server, and Intune. 

I enrolled devices with Microsoft Intune and applied policies and pushed applications. The main use cases for Microsoft Intune involve device management and policy implementation.

It excels at endpoint management and security. When managing a large number of devices in an organization, it becomes easy to handle them on one platform using Microsoft Intune. For security purposes, we can push many applications through Microsoft Intune to numerous devices in our organization, making it the best solution.

For organizations with numerous devices, Microsoft Intune's application management is beneficial because IT administrators don't need to push applications to devices individually. This makes the process easier, more time-efficient, and cost-effective.

Microsoft Intune is best for Windows devices and security in Office 365 and Microsoft-related enterprise environments. It's a nice platform for endpoint management.

Microsoft Intune lacks live location tracking capabilities. Improvements should be made in terms of MDM platforms for other devices. Microsoft Intune could be enhanced for better implementation across various device types.

I have been working with Microsoft Intune for two years.

I don't have detailed information about specific downtime or performance issues, but these issues can be there on any platform.

Microsoft Intune is a good platform for scalability. There were many challenges, but with experience, the scalability improved.

Microsoft support is good. However, compared to SOTI MobiControl, Microsoft Intune needs more efficient technical support. SOTI MobiControl's technical support is superior to Microsoft Intune's support.

Neutral

I have worked with SOTI MobiControl. The choice depends on customer requirements. If the customer's needs align with the capabilities of Intune, we choose that option. Conversely, if the requirements fit better with SOTI MobiControl, we go in that direction. Ultimately, it all depends on the customer's input. Intune is best suited for enterprises using a Microsoft environment, especially for Windows devices. However,  SOTI MobiControl is more appropriate for Android devices. While Intune can also support Android and iOS, it is particularly optimized for Windows. For iOS devices, both platforms offer similar capabilities due to platform-level restrictions that limit endpoint management solutions. Therefore, we evaluate each option based on the specific needs of the customer and their device ecosystem.

I primarily work with device enrollment and am not certain about the complete initial setup process of Microsoft Intune. Device enrollment is easy. I've worked with iOS, Android, and Windows as well.

With one user base license, we can use Intune for up to five devices. However, with SOTI MobiControl, each license is tied to a single device, meaning one license is dedicated to one device only.

I would rate Microsoft Intune a seven out of ten. I find SOTI MobiControl to be the best, which I would rate a ten out of ten.

It is being used for device management. We have a couple of clients using it at the moment. They have Windows, Android, and iPhone devices that are managed by it. We have another client with only three devices, but they are Windows SE devices with the cut-down version of Windows.

They are using the latest version because it is always kept up to date online.

Microsoft Intune pretty much brings all of our endpoint and security management tools into one place. I cannot think of the ones where it does not do what we need. Apple Mac management could be better. It makes IT and security operations much easier and much more convenient.

We use the Enterprise Application Management features of Intune Suite. That is what the data manager is set to. These features are good. So far, we have had no problems with that.

Implementing applications is easier than MaaS360. There are definitely time savings. It is a lot smoother and a lot more well-integrated with Azure AD, etc.

The integration with Microsoft 365 and Microsoft Security for both cloud and co-managed devices is very important. That is the key thing for us. Almost all of the clients have Microsoft Office 365. We have only two clients who use Google G Suite, so this whole integration is very important.

It has helped us consolidate vendors.

Its benefits can be realized within a couple of weeks. It is very good because it works. Conditional access and compliance work from anywhere, so it is very good.

For our clients, the conditional access feature along with different compliance policies that they can set is valuable.

All the remote tools you can use on the mobile are also valuable. Features such as passcode reset for the device lock are helpful, so you can set a code and get people back into the device.

The Apple Mac management is a bit basic. The mobile management is good for iPhone and iPad, but the Apple Mac management needs improvement. That is probably because Microsoft does not have low-level access to Apple Mac hardware. If you are doing basic things, it is okay, but if you want to image Apple Macs and do things like that, then Jamf is much better.

Their support needs to be improved.

I have been using this solution for about eight years.

It is stable.

It is definitely scalable.

Their support is absolutely useless. They used to be good, but now, there are separate departments. We had an issue with conditional access where the client did not like the fact that single sign-on was working and automatically logging them into everything. They found it to be a security issue. It was not a good thing. We were trying to disable that, but then conditional access would not work. Their support could not figure it out. They would say that it is Entra and then they would say that it is Intune. I found out what it was. It was a token that was coming from a single sign-on.

Negative

We use Jamf. We are still using IBM MaaS360 for some of the clients, but it is getting phased out for Intune.

MaaS360 does not integrate with all Microsoft products as well as Intune for obvious reasons. A lot of our clients want Intune for data protection, conditional access, etc. It is more about protecting their data and making sure that the devices are compliant and meeting certain policies. 

The user experience of Intune is good. It is a lot less clunkier than MaaS360. We do most of the setup, so the users are not really affected by it.

Jamf is mainly for Apple Mac management. Intune is mainly for Windows management and mobile management. Intune does not have the same level of integration with Apple Mac, so you cannot image them properly. It supports very basic imaging. Jamf is a much better tool for managing Apple Mac.

You have to use Azure because it is a part of the Microsoft environment.

I am the lead engineer involved in setting it up and configuring all the policies. It is straightforward.

From a maintenance point of view, there is no maintenance you have to do because Microsoft does it all in the cloud. You might need to tweak a few things on an app after you send it out, but those are general tweaks to make things run better. You do not have to put updates on or do things like that.

We do not use any external help. We just use Microsoft documentation.

We work in the charity sector, so a lot of our clients get Microsoft Premium licenses or Business Premium for free. They get ten licenses free, and a lot of our clients do not have more than ten staff members. They are getting the tool for free, so its cost is not an issue.

We did not evaluate other solutions.

It is good. If your clients want to protect their data and they are using Microsoft tools, then Microsoft Intune is definitely the one that they should be using.

We are not using it to its fullest. There is a lot more we could do. I work for an MSP, so we are bound by what the client wants to do. If the client does not want to advance anything, we will not advance it.

In terms of IT productivity, it does not benefit us directly because we are an MSP, but it is a lot easier to use than MaaS360 and other ones we have tried. Similarly, it does not save us costs because we are an MSP. We charge people to implement a solution, and that is it. If we are paid to manage it, we obviously try to manage it, but it does not save us any money.

It does not affect our security because we do not use it ourselves. We just install it for other people.

Overall, I would rate Microsoft Intune an eight out of ten.

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.