Microsoft Intune Reviews

We have IT solutions in this organization, but it's different. It's AWS, majorly.

I am dealing with AWS S3 storage services myself, and apart from this, we have multiple services which we are using, the different instances of VM, virtual machines. Majorly the VMs and the storage part we are utilizing. We are planning to use Route 53 as well for the network.

I don't think we have been dealing with something Amazon Virtual Private Cloud. We are just launching the VMs, the instances, and utilizing it for the services. The storage services we have been using in it to store our data.

The user experience of Microsoft Intune is very friendly and the interface is very good. It's very easy. Although Microsoft keeps on changing the console, you log in today and you will find something, and then after two months you log in and you will see the options change. That's how it is, but then again, it's quite interesting. It's always nice to explore things in it, always nice to connect and do things. It's not very difficult for me; I don't find it very difficult. Somebody who has worked on SCCM or these products can easily use Microsoft Intune. If they understand the technology, they will be able to use it. It's very good. Microsoft Intune is very good in terms of support as well. We get very good support from Microsoft. Overall, my experience is awesome.

We have utilized Copilot in Microsoft Intune very well.

My experience with Copilot was good. There are always some chances to do some enhancement and improvement, and of course, there is a lot of competition in the market as well against the AI tools we have, the open AI tools we have, and the chatbots we have. Definitely, but it is very good. It is very nice.

I see room for improvement with Microsoft Intune because the only thing is that under the policies, there are certain policies which are very deep dive. Somebody has to understand it very particularly, then only they should implement it. That's the only thing. Some demo videos would be available on the portal, that would be helpful. If somebody has to do some implementation of any new policies, how would they do it? The person has to search somewhere how this policy works, and that will help. A small demo would be available in the portal itself. That would be helpful if Microsoft itself can launch some demos.

So far, I think the things are going smooth with Microsoft Intune. I do not see any conflicts with that, any additional features. In terms of comparing with the other cloud providers, the things are smooth. But when it comes to AWS, they have a bundled package of security and everything in one portal, including the billings part as well. Whereas in Microsoft, it is separate. A bundle package would be helpful. Although with AWS, we can get it through Marketplace, in Microsoft it is subscription-based. That is also good, but if I compare with both of them, then console-wise, of course, Microsoft Intune has very good features and everything in terms of endpoint devices. But in terms of the virtual machines connect and onboarding the virtual machines and syncing them, it is a bit tricky. One improvement that is needed if I compare with AWS where it's pretty easy.

I have been working with AWS for three months already, but this organization has been working on AWS for the past one and a half years or more.

During the onboarding of Microsoft Intune, we faced the problem that the policies were not getting synced. Sometimes, even after removing the devices from the domain and then re-onboarding the devices, joining the domain again, the sync was not happening. For example, there was one case where the devices were already synced, everything was synced, the user was logged in, and then suddenly when we handed it over, when somebody left the organization, we handed over the asset to another, assigned it to somebody else. In that case, that syncing was not working. It was taking a lot of time. It was very difficult. We removed it from the domain, we formatted the machine completely, then again installed the fresh image. Everything we did, it took time. Then ultimately, we had to take the help from Microsoft. It got resolved, but that was a difficult situation.

Microsoft Intune support is very good. We get very good support from Microsoft.

Ultimately, we had to take the help from Microsoft. It got resolved, but that was a difficult situation.

Before this, I was working with Microsoft in my previous company, where I was using Microsoft Intune and other services of Azure and Microsoft.

My experience with the deployment of Microsoft Intune was a bit tricky. It was tricky. But the overall experience was good because there was a lot of learning and enough support from Microsoft in terms of deployment as well.

I haven't used Microsoft Intune Suite Cloud PKI. We haven't used it. But we were having the Citrix environment, so we were launching the Microsoft Intune services in it, connecting our services, and connecting our virtual machines on Microsoft Intune, onboarding the VMs on Microsoft Intune. That's how we were using it, through Citrix.

I need to check that with the engineer regarding something Amazon DCV.

I would rate technical support at least a nine.

I would rate Microsoft Intune at least eight to nine overall.

I would rate it at least eight out of ten. My overall review rating for Microsoft Intune is eight.

My use case for Microsoft Intune involves remote access and mobile management. The purpose is to improve our operational efficiency.

The best features of Microsoft Intune that I appreciate most include its comprehensive management capabilities and user-friendly interface.

I do use the cloud PKI feature in Microsoft Intune, which enhances my management of the certificate infrastructure effectively. In cloud PKI, it helps me manage my certificate infrastructure by ensuring secure operations and streamlined processes.

I also use Microsoft Copilot as it offers significant value in enhancing my experience with Microsoft Intune. My experience using Copilot has been very positive as it integrates smoothly into my workflow. Copilot helps protect my environment by automating security processes and facilitating timely updates.

I am also using the enterprise application management feature in Microsoft Intune for better app discovery and deployment. I use the application management feature extensively within Microsoft Intune for automatic updating and deployment.

There are areas that have room for improvement in Microsoft Intune, particularly regarding integrations.

I have been using Microsoft Intune for about three years.

The stability of Microsoft Intune is relatively high, and I would rate it a 9 regarding downtime or bugs.

For scalability, I would also rate it a 9 as it adapts well to our growing needs.

From one to ten, I rate Microsoft Intune's technical support as 8, indicating it meets my needs satisfactorily.

Positive

I utilize a different solution for some aspects of endpoint management, which offers additional functionalities.

The deployment of Microsoft Intune was fairly easy, though it had its complexities as well.

It took me weeks to deploy Microsoft Intune fully, balancing the setup with existing systems.

I estimate I have seen a return on investment of about 20%, highlighting the value provided by Microsoft Intune.

Microsoft Intune has saved me about 30% of my time through streamlined processes and efficient resource management.

The pricing of Microsoft Intune, considering its features, is cost-efficient.

In terms of overall pricing, I find it to be fairly priced, reflecting its capabilities.

Considering the features, I recognize its pricing is competitive within the market.

I compare Microsoft Intune to other solutions based on its features and performance, indicating its advantages.

When comparing with other solutions I have used, I find Microsoft Intune to be quite effective.

To others looking to implement Microsoft Intune, I recommend them to evaluate through a proof of concept before finalizing their decision.

I would rate my overall experience with Microsoft Intune a 9.

I'm responsible for the end-user computing. I'm responsible for packaging the applications, deploying it to all the end-user devices in my organization via Intune, and also creating the monthly patching through update rings and deploying all the patches to the workstations across the entire organization. 

We have also created an Autopilot profile, deployment profile, and enrollment status page to ensure all the new devices are compliant with company policies and compliance policies as per our organization rules.

It significantly reduces the need for manual human efforts and is very cost-effective. This makes it particularly advantageous for large enterprises, especially in the financial sector, as it is secure and reliable. Microsoft Intune helps protect against vulnerabilities and third-party attacks by providing timely patches and update rings, ensuring compliance with security standards.

The best features of Microsoft Intune are creating the package in very simple terms using the Content Preparation Master tool, which I find easy. I'm able to pull reports and get device status very easily, which has been very helpful. 

Regarding the compliance policy settings and configuration profile, I can check on each device to see where it failed. However, I struggle to troubleshoot the exact root cause of these failures, which I want to highlight. 

I have observed that while I can generate reports, I am unable to address the log files from end-user devices effectively. For instance, when an application is deployed on a user device and it shows an error indicating failure, I can't pinpoint the exact reason for the failure. In Microsoft SCCM, we can access log files in the "C:\Windows\SCCM\Logs" directory. From there, we can check the "AppEnforce.log" and "AppIntentEval.log" files. Unfortunately, Intune’s management extension does not provide the same level of logging. When I try to review the "Windows IMEI" logs, I cannot determine where the application is failing.

Moreover, I lack the visibility in Intune that I had with SCCM. Looking ahead, with Windows 11 on the horizon and Windows 10 support ending on October 14th, I am currently involved in a Windows land migration project. I plan to image the new devices using Autopilot. Once the hardware hash is added to Intune, we are able to assign the group tag, which allows for the deployment profile to be assigned, enabling both device enrollment and user enrollment. This approach helps minimize the overall experience issues.

Maintaining Microsoft Intune is not very complex; we generally export the entire list of applications we've created once every three months, and we make sure to update or remove any old policies that are no longer required in our organization. However, this is a time-consuming and tedious process. I suggest that Microsoft include an option, similar to SCCM, for every three months or 90 days to automatically remove devices from the console. This suggestion could apply not just to device management but also to application management and compliance policies or configurations.

Because Microsoft Intune is cloud-based, we would like to gain a better technical understanding of how Microsoft develops the tool from the backend. For instance, with SCCM, we learned how it operates—creating distribution points, performing system discovery, and identifying machines present in Active Directory. We understood how to create boundaries and assign boundary groups for distribution points to access content. However, in Intune, we struggle to determine where content is stored. For example, when I create a .IntuneWin file or a package application, I want to know where it is stored and how to retrieve the raw files or the source media if needed. These are some of the challenges we face with Microsoft Intune. We lack a lot of visibility in Microsoft Intune.

I have been using Microsoft Intune for the past eight years.

I find that Microsoft Intune is stable, but it would be beneficial for support infrastructure engineers to receive presentations about new features and how earlier issues were overcome, as this information is not readily available to them, which affects the perceived stability. On a scale of one to ten, I would rate it a seven out of ten for stability.

For scalability, I would rate it a six out of ten.

Currently, I'm managing around 6,000 devices at Alter Domus, and once I deploy an application, profile, or policy, it takes around two weeks to achieve 92% to 94% compliance. We have around 13,000 users.

For technical support, I previously received direct calls from escalation engineers at Microsoft, and I found that very supportive. However, now Microsoft has changed their process, and L1 and L2 tickets are often assigned to third-party companies where the personnel may lack the necessary knowledge, resulting in lengthy resolution processes. In my organization, management suggests we handle issues ourselves until a solution is provided.

When an escalation support engineer at the L3 or L4 level assists me, I would give them a rating of 10 out of 10. However, for L1 or L2 engineers from third parties, I would rate them a four out of ten due to the lengthy resolution times. 

Overall, I would rate vendor support very poorly, at three or four out of ten. However, when I talk to engineers directly working for Microsoft, especially those familiar with SCCM and Intune, I would give them a 10 out of 10 due to their proper understanding of the tools.

Neutral

I have seen a return on investment with Microsoft Intune, as it has saved me resources. Previously, I managed my infrastructure with a team of around six to seven members, but after transitioning to the Microsoft Intune hybrid model, I am able to manage it with just one resource, allowing me to cut costs significantly, around 50-60 lakhs.

It's expensive.

When comparing Microsoft Intune with other solutions or vendors, I find that it is a very fast and safe procedure technology. While I believe it is good technology, there are minor issues that could be resolved by Microsoft. We want transparency for engineers to understand where issues arise so we can troubleshoot effectively.

I don’t want to constantly disturb the service support engineers by raising cases. As technical engineers, we want to solve problems on our own. We aim to become subject matter experts for Microsoft Intune within our organization.

In my organization, we use Copilot whenever we don't understand a particular feature, and it provides the answers we need. For example, when I need to create a BitLocker encryption policy, Copilot assists me and guides me through the steps and necessary settings required before creating that policy.

We have a certificate infrastructure, and we generally embed machine certificates and handle the PKI certificates via SCCM. 

The cloud distribution point that we have already configured in SCCM is particularly useful when an end-user device is not connected to the VPN (Virtual Private Network). During this time, the cloud distribution point allows content, such as application patches, to be distributed and successfully installed on end-user devices. This is why we have been able to achieve good compliance.

I would recommend Microsoft Intune to other users because it offers many benefits. Overall, I would rate Microsoft Intune an eight out of ten.

I work with Microsoft Intune on 365 Modern Workplace technologies. I have dealt with different Microsoft Intune-related projects because they fall within the security and compliance scope. I migrate customers to Microsoft Intune for endpoint management. I either onboard customers directly to Microsoft Intune or, as in my current employer experience, I detached their endpoints from SCCM and then fully managed those endpoints using Microsoft Intune.

The main purpose of Microsoft Intune is to fully manage corporate or enterprise devices, mainly Windows. From time to time, I make decisions and take action for macOS. I also commonly secure data for non-managed devices, very likely smartphones, using policies to secure data such as Outlook, emails, and Teams.

There is not much measurable improvement in fairness to Microsoft Intune because I typically try to set KPIs, but eventually I cannot. Customers are not focused on that part for KPIs because it would not be easy for them to define clear KPIs such as the number of incidents to be minimized across a semester, quarter, or yearly basis. Another example would be to define an SLA whereby endpoint disruption must be minimized in terms of recognition and response. I always try to establish KPIs, but customers often do not have that mindset.

The integration with different kinds of endpoints is the most valuable feature in Microsoft Intune: Windows, Mac, iPhone, Android, and anything else. The most reliable feature is the integration with Microsoft XDR, which grants administrators and solution architects like me the ability to bring value to a business. Microsoft Intune integrates deeply with Windows and with Microsoft Defender for Endpoint, which is the antivirus. This integration grants comprehensive security from an endpoint perspective.

I am part of the private preview with Microsoft, which is a program for very few customers working with Microsoft to improve features in the future. I am currently working with Microsoft to improve Microsoft Intune RBAC, which is role-based access control because I came across a limitation. I worked with Microsoft for approximately four months, and I and other few customers participated in that program to give our inputs to improve that feature. They have made improvements, and I think later this year Microsoft will release the new RBAC feature in general availability, either in two or three months.

The other area needing improvement is Autopilot because there are currently other limitations. Microsoft opened another private preview for Autopilot and we have been working on that as of middle of February. Those are the two features that did not impress me much, and currently with other customers I am improving them with Microsoft directly.

I have used the solution since 2020.

Regarding the overall stability of Microsoft Intune, I would rate it a seven. Generally speaking regarding scalability, it works quite well. The problems I came across were the ones I already mentioned and led me to join the Microsoft preview program. Generally speaking, I am quite happy with the product, and I would have said even eight, but generally speaking it works quite well.

The problems I came across were the ones I already mentioned and led me to join the Microsoft preview program. Generally speaking, it works quite well.

Regarding customer service and technical support, I would rate it a seven on a scale from one to ten. I would say it is fair enough.

Prior to adopting Microsoft Intune, I was focused on Microsoft solutions, so I try to be consistent with Microsoft Intune. I saw a demo from another vendor, but I have not really worked with other solutions or other vendors.

In relation to the deployment regarding Microsoft Intune, the first difficulty I had to cope with was the decision to make between continuing with co-management or stopping and going to a full Microsoft Intune management. The difficulty there was co-management because there are some decisions to make and also some technical constraints to address. When I decided to go with full Microsoft Intune management, it meant I had to unlink those devices from SCCM and then uninstall the SCCM agent on endpoints and also fix some gaps. There were some difficulties in fully onboarding and unlinking those devices from SCCM and then fully onboarding those devices to Microsoft Intune. Those are the most difficulties I came across in my current Microsoft Intune project experience.

Regarding where I bought Microsoft Intune, that is a difficult question to answer because it depends. When talking about Azure, you are talking about a tenant. When you open a tenant, you open it by yourself. When you need licenses, you may either have a direct relationship with Microsoft, as is the case where I am currently working, or if I used to work as a consultant, I provided help for customers to open a tenant or to buy licenses.

Regarding ROI with Microsoft Intune, Microsoft Intune provides value for customers and they are happy. There is definitely a return on investment for customers when they adopt Microsoft Intune. For larger companies that can manage a large fleet of endpoints, there is definitely a return of investment.

Regarding the quotation for customers, which is something I did in the past, generally speaking from a sysadmin perspective, the pricing for what they offer is in line.

I will answer this question broadly because I work with 365 modern workplace projects and also Azure. I will not answer this question just from a Microsoft Intune perspective. Generally speaking, I try to leverage and maximize the value of a customer's license baseline. For instance, a customer has purchased E5 licenses, which grants the customer very different parts of the 365 ecosystem. There is a lot for a customer to improve. Every time I try to ask questions in relation to what they have now regarding awareness and understand what might be the gap from what they currently have. I am not talking about just in relation to licenses but their awareness for data protection, endpoint management, endpoint protection, identity protection, VM protection, and some workloads protections in the cloud.

There are constraints due to the technology of Microsoft Intune, but this applies to almost any technology. I have not had the chance to integrate with any third-party software. I was able to comply fully with Microsoft Intune solely.

The integration with different kinds of endpoints is the most valuable feature in Microsoft Intune: Windows, Mac, iPhone, Android, and anything else. The most reliable feature is the integration with Microsoft XDR, which grants administrators and solution architects like me the ability to bring value to a business. Microsoft Intune integrates deeply with Windows and with Microsoft Defender for Endpoint, which is the antivirus. This integration grants comprehensive security from an endpoint perspective.

Regarding missing features in Microsoft Intune, I was part of the private preview with Microsoft, which is a program for very few customers working with Microsoft to improve features in the future. I am currently working with Microsoft to improve Microsoft Intune RBAC, which is role-based access control because I came across a limitation. I worked with Microsoft for approximately four months, and I and other few customers participated in that program to give our inputs to improve that feature. They have made improvements, and I think later this year Microsoft will release the new RBAC feature in general availability, either in two or three months. The other area needing improvement is Autopilot because there are currently other limitations. Microsoft opened another private preview for Autopilot and we have been working on that as of middle of February. Those are the two features that did not impress me much, and currently with other customers I am improving them with Microsoft directly.

I would rate this product an eight overall.

I can describe the use case as working from scratch with the deployment profile, device restrictions, and application deployment since the company is totally on cloud, making it easy to use Microsoft Intune and apply everything needed effectively.

The best feature in Microsoft Intune is zero touch deployment, which allows me to automate many tasks compared to manually installing Windows and applications one by one, making it easier to enroll devices with Autopilot and pre-deploy applications. There are also self-assessments based on location and risk that improve conditional access and endpoint security. Moreover, I can utilize compliance policies and configuration profiles effectively by clearly defining what I need, testing them on a few devices, and then implementing them across the board, contributing to a smooth experience.

I assess the overall user experience as a mix. Specifically, for the Windows platform, it is totally fine and very easy to handle using features such as Autopilot, zero touch deployment, and IT management, allowing users to onboard smoothly in Microsoft Intune with pre-applications installed through Autopilot. However, for non-Windows platforms, there are many areas that still need improvement, such as on macOS. For Windows, it works well with compliance policies, conditional policies, and integration with multiple platforms such as Azure AD and Windows Defender.

Areas with room for improvement in Microsoft Intune include the policy sync process; reducing the time it takes for changes to be applied would help facilitate testing. Faster feedback on whether policies fail or pass would minimize wasted time while also improving the handling of Windows 32 application failures, which often depend on manual intervention to diagnose and initiate processes again.

I have been using Microsoft Intune for the last four to five years.

Prior to using Microsoft Intune, I experienced a hybrid model, and the switch to a cloud-only solution enhances manageability due to ease of backing up processes. Using Microsoft Intune or similar cloud-based tools simplifies management significantly compared to hybrid methods.

My thoughts on the pricing for Microsoft Intune are that while it might seem costly for a single service, if an organization operates completely on the cloud without a hybrid model, it is quite reasonable. The integration with other Microsoft services such as Entra ID and Defender adds substantial value and features, making the cost manageable.

On a scale of one to ten, with one being cheap and ten being expensive, I would place Microsoft Intune at a 7.5.

Comparing Microsoft Intune with other solutions, I find it excels for Windows management, but for non-Windows systems such as macOS or Linux, there is substantial room for improvement. Other tools, such as Addigy and Kandji, have made strides in enhancing macOS management; they apply policies immediately upon clicking, something Microsoft Intune struggles with.

I have not initiated the use of Copilot in Microsoft Intune yet, but I am testing it; it has not been deployed to everyone. My experience has been that manually performing tasks may take more time, but having an AI tool to prompt actions can save time, and so far, testing Copilot has been good.

The deployment process in Microsoft Intune is a mix; for normal applications that do not require custom versions, it can be complex. Issues such as Windows 32 app failures occur frequently, and detailed manual detection rules are often necessary. I find that deployment failures require extensive troubleshooting, as I must dig through Microsoft Intune logs, refresh and sometimes start over with the same devices.

The deployment in our environment is primarily cloud and on-premises; however, we are not using a hybrid model. I am using about four hundred physical laptops in total, and while some devices are purchased directly from OEMs with hardware already deployed and onboarded smoothly, I am still working on onboarding other devices which are not yet on Autopilot individually.

Our organization currently has more than four hundred fifty users working with Microsoft Intune. The scenario is predominantly a mix of devices, with ninety percent being Windows, while the remaining are macOS. I have previously mentioned that our work with macOS is limited as I continue to test its capabilities; the policy syncing and application management are not as smooth as one would expect compared to third-party systems.

The solution does require maintenance; I use update rings with Windows for feature and normal updates, which are relatively easy. I create policies for updates that I test on a limited number of devices in IT; once I confirm that the policies have been successfully applied, I then roll them out to broader groups. There are instances where some systems fail to update, which requires troubleshooting and running a resync to resolve.

I would rate this review an eight out of ten.

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 main use case for Microsoft Intune is to secure, manage, and monitor all the endpoint devices from a central platform. I use Microsoft Intune to secure and manage endpoint devices by enrolling a new laptop automatically when a user signs in with corporate credentials, providing security settings and applications without any manual intervention for the IT team.

Microsoft Intune has positively impacted my organization in many ways, enabling us to perform remote actions and have device lifecycle control, such as remote wipe, reset device, and lock the device, along with role-based access control.

These positive impacts translate into real results for my team by saving a good amount of time. With Microsoft Intune, we set up the device within 20 to 30 minutes, reducing the provisioning time by 70 to 80%, and it has also reduced the IT workload by 40 to 60%.

The best features Microsoft Intune offers include centralized device management and automating provisioning, which is really helpful with this device.

Out of centralized device management and automated provisioning, I find centralized device management most valuable because it gives us good visibility from a single place, allowing me to see all the devices, whether their compliance is okay or not, and their security posture from a single console for real-time control and response.

I have not seen any kind of challenge with Microsoft Intune; it is working well and providing deep, built-in visibility that improves troubleshooting steps, though I believe detailed customized reporting can be improved.

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

Microsoft Intune is stable.

Scalability with Microsoft Intune is good, handling the growth of the organization over time.

The customer support for Microsoft Intune is good in their technical aspects and provides great support to our IT teams.

From the start, we have been using Microsoft Intune and did not switch from a different solution.

Microsoft Intune is deployed in my organization through the public cloud.

We have seen a return on investment with Microsoft Intune, including time-saving and money-saving outcomes.

We have not gone for evaluation of other options before choosing Microsoft Intune.

My advice for others considering Microsoft Intune is to deploy it as it will really help build a foundation for their identity first, aligning Microsoft Intune with their identity setup by starting with a pilot phase and keeping policies simple during the initial design. Microsoft Intune is deployed in my organization through the public cloud, and we do use Azure as our cloud provider. I would rate this solution an 8 out of 10.

The primary use case for using Microsoft Intune is to secure the endpoint and device management, along with a strong focus on enforcing compliance and enabling secure access within our corporate resources. When a new user joins, we use Windows Autopilot via Microsoft Intune to provision their laptop. As soon as the device connects to the internet, it automatically joins Microsoft Entra ID. Security policies are applied, and the required applications are also installed automatically. This is our real-time example of how we use Microsoft Intune.

The best feature of Microsoft Intune is its unified endpoint management. The second thing is the conditional access integration, as we can deeply integrate with Microsoft Entra ID. This is also one of the best features, along with its automated policy and device provisioning.

We rely on the automated provisioning feature the most, as it is really great for onboarding that we use frequently.

Microsoft Intune has positively impacted our organization by covering processes, improving security, and saving time. The centralized endpoint management is really helping us to reduce the administrative overhead, and it has made it easier to maintain consistency in the configuration part. We are able to onboard and deploy faster with the help of Autopilot and automated policy deployment, so it is really saving us time and money.

We have seen almost 40 to 60% faster deployment during onboarding, and time saving is a really big matter. It has saved us almost 50 to 60%.

Microsoft Intune is working well, and all the features are very useful and smoothly working without any significant frustrations or wishes for change. I think nine is a very good rating for this solution, and I kept one point out because I think in the future it requires improvement based on future scalability in the IT infrastructure.

I have been working in my current field for more than five years.

Microsoft Intune is very good and stable.

Microsoft Intune is really handling our organization's growth in terms of scalability.

The experience with customer support has been positive, and they are really technically rich.

We have not switched from a different solution before Microsoft Intune.

We have seen great time saving and also money saving as employees don't waste their time in deployment because of automation. It automatically onboards.

We have seen almost 40 to 60% faster deployment during onboarding, and time saving is a really big matter. It has saved us almost 50 to 60%.

My experience with pricing, setup cost, and licensing for Microsoft Intune was straightforward, and it is a very good experience.

We have not evaluated any other options before choosing Microsoft Intune.

If anyone is planning to implement Microsoft Intune, they should start with the identity and access design, plan their device enrollment properly, and start small before scaling up. This advice will be really helpful. I gave this solution a rating of nine out of ten.