Microsoft Intune Reviews

My main use case for Microsoft Intune is to manage all the endpoints and use the conditional access policies to manage all the applications for Microsoft.

In my organization, we are using M365 with Microsoft Intune, and we do not want users to access their email on any non-managed devices, so we manage devices with Microsoft Intune and the Exchange, meaning online exchange mail is only accessible on Microsoft Intune managed devices. This is the use case we are following.

For Microsoft Intune, we also use it for patching our devices because patching is very critical for us, and Microsoft Intune helps us to get all the patches centrally without going to any further third-party sites. It is helpful, and it also gives me options to see the vulnerabilities on all the Microsoft Intune-joined devices.

The best feature of Microsoft Intune is the zero-touch device provisioning, which is very helpful to reduce the manual imaging, as we do not want any dependencies on local engineers to install the OS manually, and it is easy to manage our devices from remote sites. It also increases the compliance which we follow and helps to reduce the time to deployment, allowing us to customize the OS with the software our company uses, making it ready to go.

Microsoft Intune impacts our organization positively by reducing the time for our engineers, allowing them to focus on other important tasks. It provides a complete overview of all the endpoints managed by Microsoft Intune, showing which systems are critical, not critical, healthy, and not healthy, and how many devices comply with our organization's policies. It also reduces the risk of data being shared outside of our devices.

Microsoft Intune reduces the time of our engineers, cuts down costs for the deployment of our endpoints managed by Microsoft Intune, and helps to improve compliance and the security policies we wanted to apply on endpoints, which was not happening earlier. Now it is working fine.

For improving Microsoft Intune, it sometimes feels laggy, taking some time to implement any policies on machines. I understand it's dependent on the network, but some other device management applications implement changes more quickly. This lag is the only gap I see.

There should be an easy guide to getting started with Microsoft Intune. As an admin, I feel we need clear steps to follow based on the licenses we have purchased. Best practices for Microsoft Intune would help us utilize all its features fully, giving us confidence and better value for our investment. Currently, we have to figure it out on our own.

I have been using Microsoft Intune for four years.

Previously, without Microsoft Intune, we were using a manual method by booting all laptops with USBs after procuring them to our office. We installed the OS and all the applications, provided antivirus, configured the Outlook Exchange, and other user profiles, then sent those laptops via delivery to any remote users located anywhere in India. This process reduced the time and cost of delivery, as we can now send laptops directly to users without going through our office, and it has significantly reduced the time for deployment of applications, images, and configurations which can now happen remotely.

Sometimes, the AI gives options that are not available, making it difficult, leading us to search repeatedly. While the AI understands we have purchased only basic licenses, it typically provides generic answers related to the complete feature set of Microsoft Intune, making it tricky. This occurs only sometimes, as most of the time, the AI's output is accurate.

Microsoft Intune AI is one of the most valuable AI-driven capabilities within Microsoft Intune, with its integration with Microsoft Security Copilot and AI-based analytics for endpoint management, detecting compliance issues, application failures, risky devices, and deployment problems proactively. It helps us analyze compliance issues, and if we ask the AI to improve compliance or reduce application failures and risky devices, it provides answers that make managing Microsoft Intune easy.

For remote management, we use Microsoft's default application, Quick Assist, which is helpful as we do not have to depend on any third-party applications, making it easy. We can also use the remote wipe if anything goes wrong.

The cloud provider we use for deploying Microsoft Intune is Microsoft.

In my experience, Microsoft Intune licensing and pricing mainly depend on the size of the organization, security requirements, and whether it is purchased standalone or as part of the Microsoft 365 subscription. We are using M365 and Microsoft Intune together, with my organization preferring Microsoft Intune through Microsoft 365 E3 or E5 because it includes endpoint manager capabilities along with security and identity services. The setup cost feels lower compared to other software in the market.

I would rate this product an eight out of ten.

My main use case for Microsoft Intune is device management and policy enforcement and securing remote corporate endpoints across Windows and mobile devices.

I use Microsoft Intune daily to push security policies, deploy apps remotely, and manage employee laptops without needing physical access.

The biggest advantage for us has been centralized management, especially with hybrid and remote teams where manual device handling isn't practical anymore.

The best features Microsoft Intune offers include centralized device management, seamless Microsoft 365 integration, remote app deployment, and strong compliance policy controls.

I rely the most on the policy and compliance management because it lets us secure and standardize devices across the organization with minimal manual effort.

The automation capabilities of Microsoft Intune have also saved a lot of admin time, especially for device provisioning and routine policy updates.

Microsoft Intune has positively impacted our organization by improving our security posture and making device management much more efficient, especially for remote users and distributed teams.

Microsoft Intune could improve its reporting and troubleshooting tools since diagnosing policy sync and deployment issues can still feel a bit complicated at times.

Better customization, reporting dashboards, and more detailed error messages would make administration and troubleshooting much easier for IT teams.

I have been working in my current field for one year.

Overall Microsoft Intune has been stable in my experience for day-to-day endpoint management, although occasional sync delays and policy deployment inconsistencies do happen in large environments.

Microsoft Intune scales really in my experience, especially for managing large numbers of remote and hybrid devices across multiple locations, although performance can slow down a bit with large policy deployments.

Customer support for Microsoft Intune has been decent overall, but response times and issue resolution can vary depending on the complexity of the problem and support tier.

I previously used traditional on-premises endpoint management tools but switched to Microsoft Intune for better cloud-based management, remote support capabilities, and tighter Microsoft 365 integration.

I have reduced device setup time from a few hours to under 30 minutes and significantly cut down the number of manual support tickets related to compliance and software deployment.

I saw ROI fairly quickly through reduced manual device management work, faster onboarding, and fewer support tickets, which saved my IT team several hours each week.

The licensing can feel a bit expensive initially, but since Microsoft Intune is bundled well with Microsoft 365 plans, the overall value has been reasonable for the features I use.

I am only a customer and do not have any partner or reseller relationship with Microsoft.

I also evaluated VMware Workspace ONE and Jamf Pro before choosing Microsoft Intune, mainly because it fit better with my Microsoft ecosystem.

If you are already invested in the Microsoft ecosystem, Microsoft Intune is definitely worth considering, but plan your policies and device groups carefully early on to avoid management complexity later. Microsoft Intune has been a solid platform for modern endpoint management, especially for organizations supporting remote or hybrid work environments. I would rate this product an 8 out of 10.

We primarily use Microsoft Intune for managing Windows devices, and we also work with Linux devices, though not with Mac. It's a significant help for Windows management, with excellent policies and report fetching systems compared to Jamf. 

Microsoft Intune brings all our endpoint and security management tools into one place. It acts as a comprehensive solution where we can manage numerous devices and configuration profiles, and block specific URLs, among many other capabilities. 

We use the Enterprise Application Management features. The automatic updating in Microsoft Intune is excellent. When a user comes up with an application package to update and deploy, we have to go through the UAT process, which can be hectic. However, the automatic updates are really helpful and decrease our workload.

Copilot is particularly useful as it helps analyze error logs and can even assist with writing emails, saving considerable time.

My favorite feature of Microsoft Intune is the device find and device applications options, where we can see which applications are installed on devices with accurate version information. This helps us troubleshoot systems effectively. 

I also appreciate the report system that allows us to fetch clear reports. Previously, we used Workspace ONE, but its reports weren't as reliable as Microsoft Intune's. 

The user interface of Microsoft Intune is good, though new members sometimes find it challenging to navigate due to the numerous options within categories such as devices, applications, Windows 365, enrollment, and configuration. 

Microsoft Intune could be improved by adding short video tutorials or direct links to Microsoft articles in the information button. Currently, the descriptions in the information button aren't always clear about what certain options do. Having these additional resources would be particularly helpful for new users, eliminating the need to search extensively for information.

I have been using Microsoft Intune for about two years. I have hands-on experience with Microsoft Intune. 

I started using Microsoft Intune in May 2023, and it took me two to three months to fully understand its capabilities. After this learning period, I gained a clear understanding of what Microsoft Intune does compared to Workspace ONE and Jamf. While every MDM tool has its own features, Microsoft Intune serves as a comprehensive solution.

We have contacted technical support for various issues. They demonstrate extensive knowledge and consistently resolve our problems.

Positive

We previously used Workspace ONE, but its reports were not as reliable as those from Microsoft Intune.

While I don't know much about securing hybrid work and protecting data on bring-your-own devices, it is secure. Microsoft Intune has endpoint security options and all the necessary features. However, organizations are using different options for security purposes. Some use Defender as well, so I haven't seen much about that. We use the Endpoint Privilege Management.

I would rate Microsoft Intune an eight out of ten. 

I use Microsoft Intune for all kinds of operating systems, including Mac, Windows, and Android. For these operating systems, I use compliance policies and deploy apps.

What I appreciate about Microsoft Intune is that it is easy for me to deploy software to an environment with 600 laptops. I can deploy the software and it installs directly on all 600 laptop devices. This is why I use Microsoft Intune, and I also use many Conditional Access policies. With these Conditional Access policies, I can determine if a device is compliant or not.

The portal of Microsoft Intune is slow for me, but otherwise I think it is an acceptable product.

What I would like to see improved in Microsoft Intune is that the portal runs slowly for me. If I have deployed software, I can only see it after 20 minutes, so the reporting is quite slow. Additionally, some of the portals take a considerable amount of time to load. For example, it is difficult to see the assignment overview because I have different configuration profiles and different policies, and I cannot see directly to which groups the profile is assigned. I have to click open manually and then I can see it is assigned to this group, but I cannot have a wide overview of policies that are assigned to the group.

I have been working with Microsoft Intune for about three to four years.

I have not experienced any downtime or performance issues with Microsoft Intune. There is no downtime.

Microsoft Intune is effective for small organizations and also great for large organizations, so it scales well.

We have not expanded our usage.

My experience with the customer service and technical support teams of Microsoft depends on the situation. Sometimes the service is good, and sometimes it is really bad.

Prior to adopting Microsoft Intune, I was not using another solution to address similar needs. We started directly with Microsoft Intune. I used Microsoft Deployment Toolkit before that, and before that all work was done manually. Then we transitioned to Microsoft Intune.

Regarding my experience with the deployment aspect of Microsoft Intune, I find it quite easy. I use Autopilot to deploy the devices. In the beginning, I had many issues with it, but now it seems much more stable, so I do not encounter issues with deploying new devices to Microsoft Intune.

I work with the Autopilot V1 model, not the V2 version, for Microsoft Intune.

I did not consider any other options or solutions available in the market before selecting Microsoft Intune. I chose it because it was included in the licensing. I tried Jamf before for macOS, but now it is also included in Microsoft Intune, so I only use Microsoft Intune.

I do not use Microsoft Intune Suite's Cloud PKI yet.

I am using Copilot for Microsoft 365, but not Copilot Studio or Copilot for Microsoft Intune.

Given my extensive experience with Microsoft Intune, my advice for other organizations considering it is to use the new filters in Microsoft Intune. Instead of dynamic groups, it is better to use these filters because they are faster. I would rate this product 9 out of 10.

I mostly use Microsoft Intune for device management and application deployment.

From my perspective, I appreciate the scalability in Microsoft Intune and the portal management, which is extremely intuitive and very simple to use.

Regarding the user experience of Microsoft Intune, I do not have any negative feedback. Users take the solution very well.

If you ask me about improvements, I would like to see some additional features in Microsoft Intune in the future.

Nothing is perfect, so there is room for improvement in every product. I would like to see more customization in Microsoft Intune or some features such as more connectors.

Apart from the full management agreement, I do not think there are any other aspects that can be improved in Microsoft Intune.

I have been using Microsoft Intune for about two years.

I assess the stability and reliability of Microsoft Intune positively.

Regarding the scalability part, Microsoft Intune is very scalable.

The process of scaling up and scaling out was smooth and easy.

I have some knowledge about the customer service and technical support teams.

Regarding my experience apart from Microsoft Intune, I have worked with other mobility management solutions, but I did not consider any other options in the market before selecting Microsoft Intune.

The experience with the deployment of Microsoft Intune is very easy for me because I have worked with Microsoft solutions for five years. The portal management is very intuitive and not difficult.

I use only Microsoft Intune and do not use Copilot at the moment.

I purchased Microsoft Intune through a local partner.

Enterprise Application Management has changed my abilities significantly when it comes to app discovery, deployment, and automatic updating.

I do not know much about the pricing, setup cost, or licensing part of Microsoft Intune. I am using the Enterprise Application Management features of Microsoft Intune.

I would advise organizations considering Microsoft Intune to ensure they understand their needs. Other companies should consider their specific requirements before choosing Microsoft Intune.

I have one remark about the application management for the Android version. Often, the Play Store opens and leaves the possibility to download to the user, which is not good. It is not the policy to create inside the configuration, and there is a problem with synchronization often for the Android version.

I gave this review a rating of 9.

From my previous experience and my current experience, I deploy Microsoft Intune for all the devices in the company. In my current company, Copilot is being used by all the users to do their work. I can also use automation tasks for Microsoft Intune. I combine the use of Microsoft Intune with Microsoft Purview, Sentinel, and Defender to maximize cybersecurity protection.

For the PKI, most of the products are now using the cloud. My daily task is managing and monitoring things on the Microsoft web page. We have not fully stopped using Sophos because some other office licenses will expire at the end of this year.

The most valuable features for Microsoft Intune are direct control over devices. I can set the policy for USB and data transferring for all company devices. This makes device management easier. It is user-friendly because most companies use Microsoft products, making the interface and features quite good, although the price is higher than other products.

It is much easier to deploy software updates and Windows updates globally because of the cloud base. Thus, I can manage from anywhere, making it quite convenient for me.

The areas that Microsoft Intune can upgrade include BYOD devices. I am currently facing issues with BYOD devices, receiving many alerts about software updates and corrupt files, although I have already whitelisted them. Microsoft Intune should update or upgrade their interface or system to reduce false positive alarms.

I have been working with Microsoft Intune for three to four years.

Initially, almost every day I would chat with technical support for the initial deployment to find solutions for problems, such as false positive alarms.

I give Microsoft Intune a seventy percent rating for scalability because it is much easier for me to manage the 500 or more devices in the company, deploying updates for software and Windows.

Almost every day during the initial deployment, I would chat with technical support for solutions.

They did not give me a suitable solution to solve the false positive alarms.

Negative

I used Sophos previously. We are still using both Sophos and Microsoft Intune since some other office licenses will expire at the end of this year. There are pros and cons between Sophos and Microsoft Intune, but my company chose Microsoft Intune because many users are familiar with Microsoft products.

The initial setup for Microsoft Intune is not so complicated, but the hardest part is creating and assigning policies and rules. We kept receiving false positive alarms during the deployment, requiring adjustments to create new rules for Microsoft Intune.

Both an internal team and vendor are involved because my company has offices in several other countries such as Cyprus, Jordan, and Dubai.

We considered using Microsoft Azure but chose AWS instead because of the price difference.

I already mentioned using Microsoft Purview, Entra ID, Sentinel, and Defender for maximizing cybersecurity with Microsoft Intune. My overall review rating for Microsoft Intune is seven out of ten.

We do use Microsoft Intune internally in our company. We handle the distribution software, collect metrics for app usage, and create policies to make the device compliant for Microsoft Intune.

The features that we use very frequently include collecting information about the software installed and determining which software is allowed from our company or not. This is our main feature for now.

We have different departments in our company, and the configuration and distribution of Copilot is another team's responsibility. We use it, but we do not have any part of that process.

We handle the distribution software, collect metrics for app usage, and create policies to make the device compliant for Microsoft Intune.

The features that we use very frequently include collecting information about the software installed and determining which software is allowed from our company or not. This is our main feature for now.

The interface is easy, but it is not user-friendly when evaluating the overall user experience of Microsoft Intune.

The settings are confusing, and it is not always clear where I apply the configuration because we have to open various pages to see where we are applying the settings that we have configured.

We are using Microsoft Intune for about two years.

Microsoft Intune is acceptable and adapts well. I give it an eight regarding scalability.

The technical support of Microsoft Intune rates as an eight when rated from one to ten, where ten would be the best support.

We have addressed other questions and other possible customization, and it is satisfactory because our company also has support from Microsoft directly in our company. This makes it easy for us to ask questions and request features that can be useful in our company.

Positive

Before choosing Microsoft Intune, we did not evaluate other options other than BigFix.

The initial setup and deployment of Microsoft Intune is easy to participate in.

We actually used service technicians from Microsoft to deploy Microsoft Intune. We hired Microsoft technicians to do that.

The technical team from Microsoft are good technicians, and we can see that they are comfortable with the process.

Before choosing Microsoft Intune, we did not evaluate other options other than BigFix.

I am involved in solutions, and we have Microsoft Intune and BigFix in our company.

We are administrators and end users of this solution. However, it is not the priority application because our priority is BigFix.

We are separated into different areas in Microsoft Intune. We have many solutions in Microsoft Intune, but for now, we are only creating policies, managing devices, and installing software because other teams handle other configurations.

We are using Microsoft Copilot in Microsoft Intune. I cannot make any comments about whether Copilot in Microsoft Intune helped protect our environment because Copilot is another department's responsibility.

We had the BigFix platform before Microsoft Intune. We chose Microsoft Intune in the first place because most of our components and services are moving to Microsoft. Microsoft Intune is adding to all the services that we now have from Microsoft.

My overall review rating for Microsoft Intune is eight.

Our use case for Microsoft Intune is managing end-user endpoints, specifically Windows desktops. It is not limited to Windows desktops as it can also manage Mac OS desktops, laptops, and mobile devices for both Android and Apple iOS. 

In terms of needing Microsoft Intune to manage devices, first, there is a requirement that devices must be joined to an Azure domain, either hybrid joined or purely joined. 

From my perspective, purely joined is really the only viable way of setting up an environment. Once devices are joined to Azure, access to Microsoft group policy is no longer available. Because group policy is not accessible in Azure, another way to manage and control devices is necessary. This alternative method uses Microsoft Intune Windows profiles. 

When setting up devices using Microsoft Intune, Windows profiles can be established which perform most of the same functions that Microsoft Group Policy did in a local Windows Active Directory environment. Microsoft Intune can manage and control machines and install software. It allows for Windows provisioning on machines and enables autopilot deployment with pre-packaged installations. When a user receives the machine, sets it up, and turns it on, it connects to the domain and begins installing software, becoming ready within approximately half an hour, which represents a significant time savings for IT departments.

Companies using Microsoft Intune are much better at managing their endpoints with far more visibility. The endpoint inventory is far more accurate and up to date. The Windows versioning for the endpoints is much better, and Windows stays current. Companies not using Microsoft Intune still rely on manual or prior methods of updating and inventorying, which are subject to gaps and inaccurate information.

The Microsoft Intune management console provides visibility into the current status of machines and deployed software. It can automatically update components within its capability, primarily Microsoft products. Third-party software updates, such as VLC media player, are not within Microsoft Intune's update capabilities. Some companies, such as Adobe, have packaged their software to be updatable in Microsoft Intune, though this is more the exception than the rule. Installing software in Microsoft Intune can be challenging if it is not already prepackaged.

The stability and reliability of Microsoft Intune is good. Microsoft takes everything in, and if users stay with Microsoft, everything works together effectively.

Microsoft support for Microsoft Intune is good. In my own use of Microsoft Intune, I did not spend significant time with support because the Microsoft documentation was adequate for our needs.

In a prior environment, when setting up Microsoft Intune, we utilized a third party for assistance. They contacted Microsoft on several occasions, and their needs were answered sufficiently.

We have a couple of companies using other options besides Microsoft Intune. One company is using Avanti Neurons.

I rate the documentation for Microsoft Intune very highly, approximately nine or ten out of ten. One of our companies is beginning to provision and establish a Cloud PK to replace their legacy on-prem ADCS server. 

I used Microsoft Intune extensively in setting up, running, and managing it for several years. In my current role, I don't have hands-on management responsibility for Microsoft Intune as much as responsibility for ensuring it secures the environment from a cybersecurity perspective. 

From an IT infrastructure team perspective, the experience with Microsoft Intune is good, although somewhat complex to navigate initially. From an end-user perspective, the experience is good as long as the infrastructure team has done their due diligence in setting it up to remove any obstacles from the user's setup of their own machine. 

I rate Microsoft Intune a ten out of ten.

Currently, we use Intune for endpoint security and deployments. We're migrating from SCCM to Intune cloud-first technology. We use it to deploy applications, CSPs, and conditional access.

Previously, we used on-prem SCCM to deploy applications we built manually. After migrating to Intune, we automated and streamlined the process of deploying applications with Autopilot. I can do more with my day. I can manage more applications and ensure that they're updated without monitoring and manually starting that process all over again.

My director used to say that we need to have cattle, not pets. You need to care for and manage pets, but you only need to feed cattle and put them out to pasture. Once you deploy it, you just let them out to pasture, and they update themselves. It's streamlined and so easy.

I've been exploring the Intune Suite, which includes Security Copilot and enterprise application management. EAM is a godsend. I can manage my third-party applications without having to worry about it. I

I set up a proof of concept for the advanced analytics. It was very streamlined. I like the information I got from it. For example, when we were troubleshooting an application, it told me possible scenarios and commonalities between group one and group two and what could be the issue. It is great in that aspect, but we decided ultimately we didn't want to go with it.

We're still learning how Copilot fits into our environment and setting up a POC for Security Copilot. We're trialing Copilot for a subset of users to get a baseline of how we're gonna be using it. I use it to manage my day, meetings, teams, and chats. It keeps me organized.

There are challenges with Intune, specifically in reporting. Many third-party companies offer single-pane-of-glass reporting that shows you what your update environment looks like, how your patch is doing, application status, etc., but Intune's reporting is not intuitive. You can connect to Azure, monitoring, and the workbooks, but it's not streamlined. 

The user experience is still a little difficult. In the first version of Intune, everything is all over the place. It wasn't organized, and things weren't categorized. They changed the name in six months, and we had to relearn everything. 

I have used Microsoft solutions for about 15 years.

I am very impressed with the stability of Microsoft Intune. There hasn't been an instance where things just weren't working. While there may be service alerts or outages, it doesn't significantly impact our operations.

I rate Microsoft support five out of 10. Customer service is inconsistent. Sometimes, the support provided is excellent, and the representative is knowledgeable, while other times, the service needs improvement.

Neutral

We looked at Tanium and Recast for servers and management but ultimately chose to stay with Intune.

The initial setup was made easier with online resources. After setting up some basic components and connections, everything was interconnected seamlessly.

We used a consultant for further development after it was configured. CDW was used to help refine the setup.

There is a return on investment, particularly with the Enterprise Application Management and the efficient deployment features of Intune. It has given me more time in my workday.

Experience with pricing and licensing was challenging. Understanding Microsoft's licensing costs can require certification, making it difficult to know exactly what is needed versus what is available.

I would rate Intune seven out of 10. As much as I sing Intune's praises, I would like more improvements, especially in the reporting. We need to standardize how we use the solution. For example, just in October, we had the update rings completely fleshed out. Then, I went on vacation, and when I came back in October, it had completely changed with new names and new scenes. There are lots of strategic hoops to jump through, but it's a solid solution.

Our primary use case of Microsoft Intune was initially to provide a more cohesive update platform. Our organization was trying to move away from SCCM as far as updating our device platforms across Windows devices. We chose Intune because it had a simplified way to configure Windows Update, view reports, and manage devices for updates. We expanded its use for configurations, moving from a hybrid join scenario to CloudJoin, which offers advantages for hybrid work and on-premise settings.

Everything has worked better since we started using Intune. Our devices use Intune for their authentication SSO process, which is also something that Intune integrates with, so we get fewer SSO prompts for our devices. There's more consistency in the configuration. 

Our configuration profiles used to be all over the place. For example, there's a lot of legacy in Active Directory. Going through Intune has helped us enforce settings, which has improved device security and functionality. When you apply something through Intune, you know it works. You don't have to worry about a legacy setting from Active Directory that was uploaded by somebody seven years ago. With Intune, you can see that a device has a setting, and you can be confident that the device is configured how you want.

The most valuable feature of Microsoft Intune is the extensive reporting that is available. The platform's transparency allows us to see when a device has been configured correctly and what it is receiving. 

We haven't implemented it yet, but Intune provides a cohesive platform for passwordless authentication. The single pane of glass is also huge. We were using SCCM with a third-party management platform. We took down five servers and consolidated everything into Intune. The ability to migrate everything into one platform greatly reduced our server footprint. It was effortless. We onboarded all 12,000 of our devices to Intune in a week.

Our users don't notice it, which is probably a good thing. If you don't notice something interacting with your computer, that's good from a user perspective. When we deploy stuff through Intune, it's silent. We recently deployed a bunch of potentially impactful settings to our users and tried to align devices with Microsoft's best practices. Nobody noticed.

Sometimes the syncing is inconsistent. I'm confident that the devices are checking in every eight hours, but sometimes the devices aren't picking up the settings as quickly as I would expect. Some features haven't been updated in a while, and Microsoft doesn't seem interested in developing them. Unless you talk to an engineer, you don't know whether there will be an update.

There are communication issues, so you might start working with a feature without knowing if it will be deprecated six months from now. Some reporting areas still need development. For example, I noticed that the reporting for driver updates is still confusing. 

We have been using Microsoft Teams since the middle of 2022 when we started rolling it out to our Windows devices.

Microsoft Intune has been very stable. There has been only one incident with an outage on the Microsoft side, but it is rare to have significant outages.

Microsoft Intune is a scalable platform with room for growth. Over the past year, it has significantly developed, with onboarding Mac OS devices now an option. Microsoft has put effort into making Intune manage macOS effectively, surpassing some other providers.

I rate Microsoft support eight out of 10. Microsoft Intune's customer service is generally efficient. When a support ticket is submitted, it directly reaches someone with Intune support expertise, unlike other Microsoft products where assistance may be delayed. Elevation to the right person is swift, though I haven't needed to submit many tickets because Intune functions well.

Positive

We previously used SCCM and a device management platform called Remedy in tandem. We switched to unify our mobile device management under one platform and eliminate internal servers. Intune functioned as that single pane of glass for us. Additionally, Intune is more functional and user-friendly than SCCM or Remedy, making it an obvious choice.

The ease of setup depends on your scenario because there are many ways to deploy Intune. Our setup was straightforward because our devices were already in Active Directory, so we could add them using a GPO. After that, we had to do some fine-tuning. We first onboarded our mobile devices and moved our Windows devices to it once the Windows management side matured a little. It took about a week to deploy the solution.

We did not engage a reseller or consultant for our migration. The migration was handled internally without external help.

I can't speak to specific ROI numbers, but there is a noticeable reduction in man-hours spent on support and troubleshooting. Applications are deployed through Intune, and we see fewer tickets for common issues because we can resolve them through the solution.

We did not incur additional setup costs for Intune, as it was already included in our E5 license.

We didn't evaluate other solutions; choosing Intune was obvious as the next step.

I rate Microsoft Intune eight out of 10.