Microsoft Intune Reviews

Microsoft Intune has been used in organizations ranging from US entities to Indian companies, with onboarding of systems in numbers ranging from 300 to over 7,000. We migrated from on-premise Active Directory to Microsoft Intune during COVID for remote work support.

As a user, I believe that Microsoft Intune is a superior tool that addresses many issues compared to previous methods, such as using a local Active Directory. As an administrator, I have a broader view of the system, allowing me to monitor whether users are online or offline, track their last activity, and manage various aspects effectively. This is a significant improvement over older methods, where we often had to inform users that certain activities were not approved due to insufficient access levels.

Microsoft Intune streamlines remote system access and management without a physical environment. I started my career in Active Directory configuration and Group Policy. In those roles, we provided systems to end users. When users went home and encountered issues such as password changes or other policy problems, troubleshooting those issues became quite challenging without physical access to the systems. However, using Azure and Intune has helped us resolve most of these issues. With these tools, we no longer need a physical infrastructure to manage systems, as we can push policies remotely and maintain control over the devices. This capability is a significant advantage of the cloud environment, as it allows us to streamline processes and provide remote access without reliance on physical setups.

Additionally, Microsoft Intune gives us a broader perspective, enabling us to manage policies for both users and systems through cloud portals. This approach allows us to deliver solutions much more quickly than the methods we previously used.

Reporting remains an issue, with challenges in providing comprehensive reports. For instance, while we can generate detailed reports for individual users—such as examining sign-up, sign-in, or audit logs—we struggle to produce aggregate reports for the organization. For example, if a user encounters issues logging into the system, we can monitor that specific case and provide detailed information. However, if the organization wants to know about multiple users experiencing problems with multi-factor authentication (MFA), we cannot compile a comprehensive report that highlights how many users faced this issue or identify the overall cause, such as a policy change. This limitation in Microsoft Intune is a significant drawback; we cannot produce overall reports on an organizational level. 

Another issue is that when configuring and deploying Microsoft Intune, some processes experience delays due to the cloud environment or other structural elements like the local area network and internet dependencies. I believe that if Microsoft Intune could operate through both agent-based and non-agent-based approaches, it would improve communication between cloud services and local systems. For example, the policies could first be downloaded to local systems, and once everything is ready, the deployment could occur. Currently, with Windows updates, we have control over when to deploy them, and we can see the status of the deployment, whether successful or failed. A more effective approach would be to allow for manual deployment initiation rather than automatic triggers. By implementing this, we could validate that the updates are properly downloaded and available on the local systems before proceeding with deployment. This streamlined process would enhance our ability to manage updates effectively.

Pricing can be challenging for startups or smaller companies. While larger companies have budgets for cybersecurity, smaller ones may struggle with recurring costs of cloud-based solutions like Microsoft Intune.

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

We haven't encountered any specific session outages or similar issues, but one drawback of this cloud environment is that we cannot accurately inform the end-user or management about when the exact policy will be applied and when the results will be visible. The nature of cloud deployment means that the rethinking process can take about 30 to 45 minutes, and in some cases, it can take a few days, as we've experienced.

Regarding scalability, there are no issues. We successfully scaled from 4,000 to over 10,000 employees without major changes. I don't foresee any significant issues in this regard.

While we encountered some initial problems during the early days of deployment, the frequency of these issues has decreased. Most troubleshooting can now be handled on our end. I would rate them an eight out of ten.

We previously managed 4,000 to 6,000 systems globally using Active Directory before migrating to Microsoft Intune during COVID.

The initial deployment and installation are quite comparable to other tools, but it offers more flexibility, especially since most systems operate on Windows. While the deployment or configuration might take a few days, once we finalize the planning phase, the onboarding process becomes much smoother. We can effectively onboard the system with or without user assistance. A significant advantage is that we can complete migrations remotely, minimizing user dependency. For context, we previously used Active Directory to manage 4,000 to 6,000 systems globally. We migrated to Microsoft Intune and other security solutions during the COVID-19 pandemic, when many organizations transitioned to remote work. During that time, we began the migration process, which included transferring user profiles. Typically, it took about 38 to 45 minutes to migrate a system from on-premises Active Directory to cloud-based Intune, assuming the user had minimal data in their profile. If the profile contained more data, the migration time could vary, but the average was still around 45 minutes for one system.

Regarding maintenance, while new deployments may not require a specialized person on-site, ongoing security improvements or updates to organizational policies need to be handled carefully. These adjustments are not something that a Level 1 engineer can manage alone. Proper planning and execution by specialized engineers are essential to implement these changes effectively.

On the pricing side, the cost for tools like Microsoft Intune can be challenging for early-stage companies that cannot afford such expenses. For smaller companies, the comparison often leads them to choose a local Active Directory, as it involves a one-time cost for purchasing and configuring servers. With Windows Server's built-in Active Directory feature, there are no additional costs for customizing policies. In contrast, Intune is a cloud-based solution that requires a recurring monthly payment. Moreover, the price increases with every additional endpoint, which wasn't the case before.

This cost structure could pose challenges for startups that are struggling financially. However, companies aiming for a fully secure environment and those with a dedicated cybersecurity budget can plan to implement Intune effectively. In summary, I would say that Microsoft Intune is the best product for established companies. It can be quite difficult for new companies without a cybersecurity budget to manage the associated costs.

I would rate Microsoft Intune a ten out of ten.

Microsoft Azure

The feature that we need occasionally but is really important is the ability to remotely wipe a device, control it, and perform similar functions. Being able to update devices is extremely important. Especially when people do not bring their devices in, we need to be able to reach out and update them over the internet.

Microsoft Intune does a great job of helping protect our environment. Particularly for mobile devices, it is great because our team is able to reach those devices and control the data that is on them.

I am not involved in the day-to-day with Intune, but we have gone with a different product for updating mobile device software. We do not integrate many of our mobile devices that are not Microsoft-based devices, such as Dell laptops, with Intune. We are using KACE from Quest to update our systems. We find that Intune is good with smaller mobile devices, the ones you put in your pocket. That is where I find Intune to be the best.

We had Microsoft Intune for a while, and we finally successfully deployed it.

Microsoft Intune scales effectively with growing needs.

We have not had to extend usage, but we are looking at Microsoft Intune for all kinds of new mobile devices that come out all the time. We will be expanding to cover those.

The support I get from Microsoft is very good. I have had a good experience with it. I would rate them a seven out of ten, which is pretty high in my book.

Neutral

Prior to adopting Microsoft Intune, we had KACE, but it could not handle mobile devices effectively. That is where Intune really shines.

I wasn't involved in the day-to-day deployment of it. I heard some pain points. The main thing is the learning curve.

It took time to implement. It was not the best product starting out of the gate. We were having difficulties getting our mobile devices integrated, but now we are doing much better. I was not in charge of the Intune deployment, but I am aware of some of the challenges they have been experiencing. It was really hard to integrate all the mobile devices. We integrated Surface devices properly, but our mobile workforce has many Apple iPhones, and those did not work quite as efficiently. We have got it all completed now. It is going smoothly.

Overall, the user experience with Microsoft Intune has a learning curve, but they are doing much better with it now. We had a really small help desk department, so they were stretched thin, but we have hired enough people now that we are able to get Intune deployed and working properly. We are in good shape.

We haven't moved a lot of our infrastructure to the cloud or Azure. We're still very much on-prem. We're a water district. We process water. A lot of our assets are physical, and they need to be secure. However, a lot of business applications are more Internet-connected. We have some cloud applications as software as a service.

We have seen a return on investment from Microsoft Intune. The main advantage is being able to manage the mobile devices at a good cost. Microsoft generally prices things pretty competitively, except for Azure, which is very expensive.

Microsoft Intune is pretty reasonable. We have difficulty with Azure, which is probably why we have not put many assets in Azure. Everything we put there is very expensive. Because we have so much on-premises equipment and assets, we put many items on-premises for that reason, and only if something absolutely has to live in the cloud, we put it there.

Before choosing Microsoft Intune, they did look at other options. I do not remember what was on the short list of what we were evaluating, but we have been using Intune for a while. Getting it deployed just took time.

I have played around a bit with Copilot for Microsoft Intune, but I use it more on O365. For Intune, I am not sure if we are using it. We do not use Advanced Endpoint Analytics as much because we have many other security tools. I find Microsoft to be good at the front end, especially for Exchange and similar applications. For inbound items, it is the first line of defense. We have many other layered defenses, with Microsoft being one of those layers.

I would recommend we stick with it. It has been great. I would rate Microsoft Intune a seven out of ten.

My use case with Microsoft Intune is for device management, app deployment, configuration profiles, and conditional access.

The nice, clear interface when managing devices in Microsoft Intune is what I appreciate about the solution. It is quite intuitive and easy to navigate around.

The app deployment is another feature I value.

Microsoft Intune does help bring all of my endpoint and security management tools into one single place or into one single solution. I can clearly see if the device is compliant or not in there as well.

Microsoft Intune is extremely important from a security perspective to ensure devices are compliant and gives us the efficiency to deploy apps automatically to a large number of users without the need for interaction from a client side, which is always helpful.

Microsoft Intune works well for securing hybrid work. I have a variety of customers who do BYOD as well, so giving that flexibility of how much control we have over data is helpful.

App deployment in Microsoft Intune definitely helps when it comes to managing app discovery, deployment, and automatic updating.

Being able to deploy apps to multiple devices at once in Microsoft Intune is very helpful. I do not have to manually install, require admin rights, or anything else. Behind the scenes, silent deployment is very helpful from a disruptive point of view.

Microsoft Intune does provide seamless integration with third-party solutions.

Microsoft Intune is very helpful in terms of integration with the rest of the Microsoft ecosystem because it is already in the Microsoft ecosystem. Typically, all of my clients are under that Microsoft ecosystem, so that is always helpful. The UI is very clear and precise.

Microsoft Intune is easy to maintain.

In my opinion, Microsoft Intune has room for improvement.

The pricing could be a little better, and the reporting could be a little better as well.

More granular reporting and aesthetically a little better improvement would be beneficial.

I have been using Microsoft Intune personally for probably six or seven years.

I would give stability in Microsoft Intune a nine. It is up quite a lot.

I would give scalability an eight.

I would give technical support a seven for Microsoft Intune.

Response times at Microsoft are sometimes not the best, which is why I rate it a seven.

Neutral

I do use Jamf for Mac equipment. Jamf Connect is the product from Jamf I am using.

I am satisfied with my partner.

The purchase would have been through a partner, not through the AWS Marketplace.

I would say Microsoft Intune falls around a six from one to ten, where one is cheap and ten is expensive.

Potentially, I might use the advanced Endpoint Analytics in Microsoft Intune. It is not something I have been exposed to, but I might.

I think I use third-party solutions for detecting and remediating anomalies in my endpoints, so potentially.

Microsoft Intune allows me to grant the permissions as of when they need it for that particular role. On-demand access is quite helpful. I can also have it time-limited as well, so if a particular task has to be actioned just in a specific time, I can grant the level of access and then obviously revoke that as well. The monitoring and auditing on that is good as well.

Using Microsoft Intune reduces the attack surface for my organization. I can revoke access if needed, so there is less risk.

I do use Copilot in Microsoft Intune. I am not sure how it protects, but I know I enroll it for more client use with Microsoft Intune. Having it tie into Microsoft apps already is helpful, and from a security perspective, it is probably more intuitive if it is using AI and the Copilot model. Copilot in Microsoft Intune helps simplify my security operations by about fifty percent.

Microsoft Intune saves me probably a couple of hours a week in terms of app deployment and other tasks.

My user base is global. My clients are small to medium businesses. Fintech is the specific industry I take clients from.

I would definitely consider Microsoft Intune if someone is already using Microsoft products. If someone is already in the Office 365 environment, that is my advice.

Our current use cases for the solution involve consulting and implementing for many customers. Primarily, the majority of our customers are India-based, but we have a few customers in the US. We essentially help them with all their device management, end-to-end, including mobile device management.

We are mainly using CoPilot in Microsoft Intune for configuration and from a productivity point of view. Additionally, we want to standardize many of these processes so we do not have to reinvent the wheel when we go to different customers. This is the context in which we are using CoPilot to help us speed up in terms of reusable objects that we can generate and then deploy across customers.

It is an ideal solution for customers who are a Microsoft-shop. The ecosystem plays a big role, and there is support for a variety of devices. I do not see any problem because Microsoft Intune supports all sorts of devices and platforms, but if their ecosystem is much more Microsoft, it is even easier for us from a configuration and implementation point of view.

We are using the enterprise application management feature in Microsoft Intune. We support end-to-end, and we have customers ranging from small to mid-size and large enterprises. Depending on the customer's needs, it may change, but we do use it. Enterprise application management in Microsoft Intune primarily helps in terms of throughput and productivity.

We can cater to more customers with the limited capacity that we have. We do not have to hire many more engineers, especially with CoPilot and other tools. Also, standardizing some of these deployment options across customers helps us to scale easily.

The most valuable feature of Microsoft Intune is that it is more of a one-stop shop, providing an easier experience. The seamless experience and remote management for customers from our office with our engineers are the most convenient aspects. It increases productivity and helps us to scale and expand.

The user experience of Microsoft Intune is very good. For the last eight years, we have been using it effectively. It is probably one of the best experiences. I do not have any complaints or problems. My team quickly gets through it, and they understand it easily. Training becomes easier, especially when people move out and then get new people onboarded. It is a seamless experience.

So far, I have not heard any complaints because it is a pretty mature product. From my level of analysis, the feature I would prefer to see added to Microsoft Intune is extensive support. Anything that helps to diagnose the problem and solve it would be useful. Helping the engineers, especially with CoPilot, with ready or out-of-the-box solutions would make life a lot easier because that helps us reduce tickets and respond faster. They can support engineers to do their job better and in a much more proactive way. They can also suggest solutions so that we do not have to waste time. Being more proactive is essential.

I have been using Microsoft Intune for more than eight years.

Microsoft Intune is very stable. I have not experienced any downtime, crashes, or performance issues with Microsoft Intune at all.

Microsoft Intune scales with our growing needs. We are mostly catering to our customers, and scaling is never a problem. We have worked with customers with over 100,000 employees, so it performs exceptionally.

We support the entire M365 end-to-end, and Microsoft Intune is a part of that. We support all features and capabilities around Microsoft Intune. My team is technical. We give L1, L2, and L3 support, and we only escalate to L4, L5 when needed, which is a very limited situation. This happens only when new features and products are released, such as CoPilot, which we have not experienced before. Generally, my team is self-sufficient.

Positive

Its deployment is seamless. We have on-premises and cloud deployments. The cloud provider is Azure.

We have seen a return on investment. There are more revenue generation opportunities for us and productivity. Those are the two key aspects, along with customer satisfaction.

We have data points and metrics to calculate our return on investment, as we continuously track our internal stats, especially on the support side. We have to report back from the reports point of view, so we have many internal stats around it.

My experience with the pricing, setup costs, and licensing of Microsoft Intune has been good. As a partner, we always look for how we can generate more revenue from a consulting point of view, but I do not see any complaints from the customer side regarding pricing, so they are satisfied with it.

We have been using Microsoft Intune for a long time. We are a Microsoft partner, so we will stick with them.

I would rate Microsoft Intune an eight out of ten.

We use Microsoft Intune for mobile device management, which includes both endpoint and mobile devices.

The feature I find most valuable in Microsoft Intune is being able to configure policies and push them directly to mobile phones.

Being able to remotely wipe mobile phones in case they are stolen or misplaced is very important for us.

We're hoping we'll be able to deploy patches quickly once fully deployed. 

It's a cloud solution and you can easily scale. 

Currently, I have not seen any areas I want to improve in Microsoft Intune. We haven't gone far into using it. We still rely mostly on SCCM. We are trying to transition mobile device management and endpoint management from SCCM to Microsoft Intune, so we are still in the process of doing that. I haven't actually explored all the functionality of Microsoft Intune. Probably when we do that, I will have more to say about it.

A feature I would want to see added in Microsoft Intune is the ability to manage other non-Microsoft devices.

I have been using Microsoft Intune for probably three years.

Microsoft Intune has been stable and reliable.

It is a cloud solution, and you can easily scale as your needs grow.

Whenever we have had challenges, we were able to get Microsoft support on time. Not all technicians are knowledgeable of the Microsoft solution, so they have to work on that as well. Some technicians are good and give you the best support you can get, but some of them are not there yet.

Neutral

It has always been Microsoft solutions prior to adopting Microsoft Intune.

Microsoft Intune is deployed on the Azure cloud. I wasn't part of the deployment as it was already in use when I came to the company. 

The question about return on investment with Microsoft Intune would probably be for the Solutions Manager, as they manage all the solutions and would understand if there has been a return on investment. I don't have any access to numbers around that. Once we're done fully migrating, I'll have a better sense of ROI in terms of time savings.

We're not using CoPilot and INtune. The Copilot we use currently is just for Office 365.

I am also not currently using Enterprise Application Management in Microsoft Intune.

Advanced endpoint analytics is tied to Defender for Endpoint.

Once we are done fully migrating to Microsoft Intune, I will compare that with what we currently do with SCCM. Currently, with our Microsoft Intune, it is limited in the sense that it focuses more on mobile device management and less on other endpoint management. Once we have fully transitioned into endpoint management, I can compare and see how it helps in terms of patch management and deployment.

On a scale of one to ten, I rate Microsoft Intune an eight out of ten.

Public Cloud

Microsoft Azure

I use Microsoft Intune for mobile device management. My team is specifically responsible for managing mobile devices. Recently, we migrated all our devices to Intune from AirWatch. At my company, we are also utilizing Intune to manage desktops, laptops, and MVD devices.

One valuable feature of Microsoft Intune is the enrollment process, which is user-based, making it easier to manage compared to AirWatch. Additionally, the integration with Azure and other Office 365 apps is seamless. Another beneficial aspect is that Intune brings all endpoint and security management tools into one place, allowing us to streamline management and have a single point of view. Mobile users have found the enrollment process seamless, and the Company Portal displays required apps effectively.

There is room for improvement in the reporting capabilities, specifically app reporting. It is challenging to report which apps are installed on which device. Also, there needs to be more granularity in pulling up stale records. I cannot control mobile devices separately or create separate policies, which Microsoft mentioned they are working on.

I have been using Microsoft Intune for a little more than two years now.

The migration to Intune took some time to show benefits, as we started about two years ago and are finishing the migration now. Initially, there were challenges due to differences between Workspace ONE and Intune, requiring adjustments to internal policies.

From an end-user perspective, mobile users have had a good experience, with enrollment being seamless. However, there are concerns with inconsistent device syncing, as there are times when synchronization with Intune takes longer than expected.

My experience with customer service is that once I reach higher-level support, the service is good. However, intermediate levels of support haven't been very successful, so I often escalate to get higher-level engineers involved.

Neutral

I used AirWatch, which is now called Workspace ONE from VMware, before switching to Microsoft Intune due to better pricing with Intune, as it is included with an E5 license.

The initial setup of Microsoft Intune was made easier as I had previously been using it on the desktop side. However, there were challenges due to differences with Workspace ONE, but after addressing those, everything went smoothly.

My entire team was involved in the implementation, with at least three people working on it.

The pricing was much better with Microsoft Intune, as it is included with an E5 license, requiring no additional hardware purchases, which was a deciding factor for us to switch.

Overall, I would rate the solution a seven on a scale of one to 10. The more mature features of Workspace ONE mean it offers better functionality in some cases, but Microsoft Intune’s pricing and integration with our existing licenses make it more appealing financially.

Other

We primarily use Microsoft Intune for deploying Windows patches, security patches, and various software applications such as Office and Zoom. It serves as a deployment tool to manage updates and application installations on user machines.

One of the most valuable features of Microsoft Intune is the detection and remediation script capability. This allows us to detect issues on user machines and run remediation scripts based on these detections. This functionality has greatly helped us resolve issues more efficiently. Having all endpoint and security management tools in one place through Intune has streamlined operations and improved compliance, almost reaching 99%.

There is room for improvement in the remediation and detection modules, which are currently about eighty percent fully functional. There could be enhancements to address issues faced due to cloud or internet connectivity problems. These improvements would enhance precision and reliability.

I have been using Microsoft Intune for approximately one year.

I was part of the deployment discussion, and the process was complex and challenging. It required a lot of coordination across teams, such as security and stakeholders, for whitelisting and setup. However, once everything was configured, the tool performed effectively.

Microsoft Intune is very stable, although there is always room for improvement. I would rate its stability nine out of ten.

Being a Microsoft product, scalability is not an issue. Microsoft Intune can be scaled up or down as per requirements, making it highly scalable. I would rate its scalability ten out of ten.

The customer service and support from Microsoft is prompt and effective. If there are issues, we can raise requests, and they respond quickly. I would rate their service nine out of ten.

Positive

Previously, we used SCCM. However, Microsoft Intune offers better features, such as automatic remediation and improved deployment efficiencies, which is why we transitioned from SCCM to Intune.

The initial setup was complex and required considerable collaboration with security and other teams to complete necessary configurations.

The administration and implementation of Microsoft Intune were handled by a separate team. I initially joined the team to learn about its use and how to resolve issues.

In the long term, Microsoft Intune is cost-effective as it helps in monitoring software licenses and usage, allowing the uninstallation of unused applications to save license costs. It's about twenty percent more effective than SCCM.

The pricing of Microsoft Intune is costlier than SCCM in the short term, but it becomes less expensive in the long run due to features that allow better management of software licenses.

Before choosing Microsoft Intune, we did not evaluate any other alternatives. I consider Intune to have little competition in its category.

Microsoft Intune is a mandatory tool for companies due to its role as a deployment and security management backbone. It is evolving rapidly and will surpass other automation tools. I would rate Microsoft Intune nine out of ten.

Hybrid Cloud

Other

As an enterprise, I work with Microsoft Intune with clients. I am a project engineer in the IT field working with Microsoft Intune. The usual use cases for Microsoft Intune that I work with mostly involve setting it up from scratch, creating the profiles, and creating the out-of-box experience for clients. When they sign in to their device, all applications are loaded and all security policies are applied to it. I also handle deploying Microsoft Intune to the environment.

I participated in the initial setup and deployment of Microsoft Intune. For clients, I have done it from the ground up, setting up and creating the profiles, doing the device wipeout, adding the applications, adding the security, and adding the Entra ID identifiers so it can be assigned to every device.

I have been dealing with a lot of on-cloud and on-premises Microsoft Intune solutions, so more of a hybrid solution.

The features of Microsoft Intune that I have found the most valuable and useful include adding applications, doing single sign-on for applications to integrate into Microsoft Intune. I have worked with profiles, security, firewalls, BitLockers, creating conditional access, creating policies in Microsoft Intune, and deploying it to mobile devices such as Android and iOS devices.

What I have found most useful in Microsoft Intune is creating an environment where customers or clients need someone to work immediately with an out-of-box experience. When they sign in with their username, their device is already set up and completed, their profiles are all there, and the applications are all there. They are able to sign into all the required applications. Previously, that used to take time to set up a laptop. The security policies we can apply to every device and the automation of Microsoft Intune represent the most useful parts.

The user experience with Microsoft Intune has been quite successful because when onboarding and off-boarding customers, it is a seamless interaction between the user and the IT team.

In terms of Microsoft Intune, it would be nice to have everything on one single page instead of links for every option that I need to access, such as Defender, Microsoft Intune, Entra ID, and Exchange. It would be beneficial to have it on one dashboard so I can view everything from one dashboard.

The only issues I have had with Microsoft Intune were with applications where if they are not an MSI file, I cannot really upload it as an application. I will have to first convert it, and that has given us some problems where the application does not actually deploy to the device. In some cases, I will have to do a manual deployment to the device.

I have been working with Microsoft Intune in depth for four years.

I assess the stability and reliability of Microsoft Intune as very reliable and very user-friendly, and it is easy to deploy and work on.

Microsoft Intune works quite well with scalability because if the environment is small at one moment, it might grow. It is quite seamless in scaling up to more users, more licenses, more security, and different locations and regions without any complications.

I do communicate with the technical support of Microsoft Intune in general. I would rate it a seven out of ten. In some cases with Microsoft support, it takes long to reach back to me. If they do reach back to me, I get transferred from engineer to engineer until I escalate it, and then they respond with clear instructions of what the problem is.

Positive

I found the deployment process of Microsoft Intune quite straightforward. Initially, there is some pushback. However, with doing it from the ground up, I learned quite easily what the issues are and I was able to deploy it the next time without any other problems.

I do use Microsoft Intune's cloud PKI.

I have not dealt with cloud PKI in Microsoft Intune so much, but the complexity involves providing and making sure that the virtual AVD is set up, the databases are there, networks are all connected, hosting applications, managing the infrastructure, and scaling the IT solution.

I use Microsoft Copilot in Microsoft Intune on a daily basis because it is much safer because it is contained into the environment. If I put any customer information into it, it is secured and protected.

I usually use Microsoft Copilot in Microsoft Intune for emails and also with troubleshooting. If I have troubleshot anything, I do a process of elimination where I can see exactly where the issue is. If I cannot resolve it, I use Microsoft Copilot to assist with the issue and provide me with some fixes.

Because Microsoft Copilot in Microsoft Intune is a built-in system and with all the open-source AI models now available, it is much safer to add information or clients' information into Microsoft Copilot because it is much more protected than ChatGPT and other AI devices.

I would rate my overall experience with Microsoft Intune a nine out of ten.

Hybrid Cloud

Microsoft Azure