We are using it for the endpoint deployment piece.
By implementing Intune, we are trying to get everything off on-prem.
We are using it for the endpoint deployment piece.
By implementing Intune, we are trying to get everything off on-prem.
Because of the FedRAMP space and some of the pieces we are doing, such as the new policies for CMMC 2.0, we have more worries when we have anything physical. It just made sense to go for a cloud solution. Because we were already using Microsoft products and we were previously partially using Intune, it just made sense to use Intune.
Once you start getting things hosted in the cloud, rather than having to host the domain pieces yourself, they can be generally managed by Intune. One of the issues that we had when we had the hybrid or on-prem deployment set was that users would have to use a VPN to be able to change their user email or their password sets. Having to manage on-prem exchange was an issue as well. There were other things like that. As we are moving the pieces over, we are noticing a lot more availability and easier configuration of pieces for users.
Intune has helped us with compliance. We are using it for CMMC 2.0 compliance.
Intune provides full endpoint visibility and IT control across device platforms. You can individualize it for your company with the Intune Company Portal app. You can make applications and other things and have them deployed via scripts.
The user experience of Intune has been nice for other individuals from what I have seen.
A lot of security is achieved via Intune policy deployment cases. There is a baseline security set, and then a part of it was configured with some of the other things that we needed for CMMC 2.0 compliance. It is containerizing for cell phones in particular and not allowing specific connection sets. We have more cells than anything else. A lot of the users do not even need to touch a lot of the system sets that we use. We have not had any issues with user availability.
One of the things that you can do with Intune is that you can have approved app sets. As a corporation, you know that a user needs to use an application, so you can have it added to Intune Company Portal apps. You can have it pre-downloaded for the users without the need for an admin's intervention. For the apps that users could need or do need, you can either force installation or set it up for the user if they need it.
Intune certainly affects our organization's attack surface. We are utilizing DLP, domain policies, and things like that via Intune. It is nice to be able to make sure that the users can have their laptops, and there is also no need to have a VPN service for a lot of those. It makes it easier for each user's things to be isolated.
We started utilizing the app proxy service. If you have local applications that use a web URL, you can use the app proxy and have Microsoft handle the VPN connection set rather than needing a VPN yourself.
Intune has helped to reduce the risk of security breaches in our organization. Intune has saved us costs. It has helped us reduce our workloads. When doing the hybrid deployment, we have to manage our on-prem environment and have additional security for it. By moving into the cloud, we have reduced the electrical cost of the office. There is also a price difference. Hosting our own VM sets versus having them host in Azure are two different things. Doing cloud integrations with pieces is easier in Intune than on-prem. It has been a nice thing that we have been dealing with recently.
We are using it for its DM Hosting, user hosting, and end-to-end deployment as well. It is all very nice.
I would like them to stop making changes and not tell people they have already made the changes.
I know that their AI pieces are at the infancy stage, but allowing users to do more tagging for information would be an interesting thing because Intune also directly integrates with Azure. Because a lot of the devices are hosted with that, you also get a lot of tagging of user data and other things like that. Tagging is still at more of an infancy set. You get a lot of false flags.
There can also be a more simplified use case for app deployment. They leverage MSIs and WIN32. I am having a more washed-out EXE process. Rather than having to build the script sets yourself, having them autogenerated script based on you uploading in a default location would be nice.
We are still in phases. It is not simple to just do a hard cutover for a lot of it.
Even though it is a Microsoft product, Microsoft does not sell or support the product directly, so you have to talk to a third-party set that is considered their partner to be able to access support. Our partner is JourneyTEAM. After utilizing billable hours with them and other pieces like that, we have been getting a lot of nice support via them. I would rate JourneyTEAM a 10 out of 10. I really enjoy working with those individuals.
We were using Symantec, and we ended up using Intune. Symantec is a nice security piece, and it does some device management. There is a domain-joined service for laptops. Intune has a similar service set. You do what is called the hardware hash join into the Microsoft Intune to have the laptop cleaned by an organization rather than turning on a VPN and connecting to a domain service for a domain controller that an organization has. A lot of that is cloudly or natively handled by Intune. Especially if you go further with the Intune hardware hash joining process, there are some script sets that were put out. You can even do hardware hash harvesting from where you are purchasing, so you can have the OEMs give you the hardware hashes to be able to input that into your cloud environment. You then know that anyone cannot just walk away with the laptop because it is still joined to your Intune base.
In terms of differences between these two solutions, there is the domain service set. Intune manages the whole domain set, and then it also integrates into the other application sets. Intune is more of a product suite set. It also does the policy and detection pieces for devices, whereas Symantec is more strictly the policy sets and security.
Intune can bring all of your endpoint and security management tools into one place. For the use case that we are doing, we are leveraging additional security software as well, so there is a little bit of everything.
We are not using it for corporate assets. We are utilizing the M365 VM license set, which is a semi-part of Intune. That is how the users are reaching some of the remote corporate resources.
I would rate Intune a 9 out of 10. It is definitely a nice product, but there are nuances to it. Especially with them coming out with and changing name schemes for a lot of the features, you have to do digging to find the whole use case, but with all the options and different use cases, there is a lot to be gained.
I worked with Microsoft Intune in my level two support role. My tasks included license assignment and assisting users with configuration issues, especially in mobile device management for iOS and Android devices.
The features I found most valuable in Intune are its user visibility and troubleshooting options. With Intune, I can easily search for a user and see details about their devices and real-time activity. The advanced audit log is especially helpful for diagnosing login and communication issues. Another standout feature is Autopilot, which simplifies machine integration by automatically adding devices to the domain when they are logged in.
Areas for improvement in Intune include expanding support beyond Samsung devices to accommodate other Android manufacturers like Redmi and Motorola. Additionally, there is a need for better support for Linux operating systems, as patch management for Linux is currently not managed by Intune, unlike for Windows devices.
I have worked with Microsoft Intune for three years.
In terms of stability, Intune generally performs well, but there may be occasional bugs like the issue with Redmi devices. While bugs are addressed, the resolution process can be time-consuming.
Intune is a scalable tool with long-term viability. I think it is likely to remain stable and relevant in the market for at least the next decade, even as competition evolves.
I would rate the technical support team for Intune as a five out of ten. It could be improved a bit.
Neutral
The implementation of Intune follows a structured process, starting with a change activity managed by a dedicated team. This involves creating a ServiceNow ticket detailing the implementation plan, rollback options, and involvement of various teams. After approval, testing is conducted, followed by deployment in a phased manner, typically at the beginning of the month to avoid interfering with critical month-end activities.
In comparison to other vendors, Intune is reasonably priced because it offers a comprehensive package that includes email access, Outlook, Office, and OneDrive storage, with storage increasing based on the license. Other service providers may have limitations and additional storage charges, whereas Intune provides services within a single cost, making it attractive to many companies for its flexibility and included features.
We used Microsoft Intune to solve problems, such as ensuring device security and compliance. For instance, some Redmi devices weren't meeting encryption requirements. We addressed this by enabling developer options on those devices, specifically, Redmi models 5 and above. We documented this solution for reference and future troubleshooting.
The most effective feature for managing and securing our mobile workforce is multifactor authentication. It adds an extra layer of security by requiring additional authentication steps when logging into devices. Additionally, conditional access policies allow us to set specific rules, such as blocking downloads or file transfers from personal devices to company resources, ensuring compliance with security policies.
It took about six months to start seeing the benefits of Intune deployment, especially regarding application deployment and user machine management.
Intune integration with other Microsoft products has strengthened our device management strategy by incorporating in-house applications like Outlook, Wi-Fi, and others. Additionally, it provides a mechanism similar to the Google Play Store for adding required applications internally, including Microsoft products like Dropbox, Google Chrome, and others.
Intune is deployed across various locations and departments within our organization. Licenses are allocated based on department and employee roles by our Office 365 team. Users are added to Active Directory groups, and ServiceNow automates configuration and support requests.
Intune requires regular maintenance, typically provided by the IT team or architects. Microsoft releases service updates approximately every three to four months, during which maintenance downtime may occur.
I would recommend Microsoft Intune to others, especially those working in the field of technology. Staying updated with new technologies is crucial, and Intune offers valuable features for device management and security. However, the decision to use Intune depends on individual needs and preferences, as well as company requirements.
Overall, I would give Microsoft Intune a seven out of ten. While it is a solid tool, there are other competitors in the market like AirWatch and BlackBerry UEM that offer similar functionalities.
We manage all our client devices, including Windows laptops, MacBooks, iPhones, iPads, and Android devices, using Microsoft Intune.
We regularly survey our users to gather feedback on their experience with device enrollment and app installation. The feedback we have received so far has been positive.
Intune is good at securing hybrid work and BYOD. There are a few gaps but we can manage those with other tools.
Microsoft Security Signals within Intune is an effective tool. It allows us to restrict access to specific systems or resources for certain devices based on their risk score. We can also prevent access for other devices that don't meet a specific risk threshold until their score improves.
It has enabled our IT team to use their tools more effectively.
Intune streamlines our endpoint management by consolidating multiple vendors into a single platform. With Intune, we can now manage features like the Windows Defender firewall and disk encryption directly, eliminating the need for separate third-party products. This simplifies our management process and potentially reduces costs.
The vendor consolidation has helped to reduce our licensing costs.
It is extremely important to us that the Microsoft Intune suite is integrated with Microsoft 365 and Microsoft Security. We're looking at consolidating more systems and solutions into our Microsoft licensing because of how easily it integrates.
While Microsoft Intune boasts a wide range of features, its user-friendliness and bundled licensing cost are key considerations for me.
The licensing has room for improvement.
It would be great if Intune offered better data protection controls for BYOD Windows PCs.
I have been using Microsoft Intune for four years.
While Microsoft Intune is generally stable, there are recurring issues with deploying Microsoft 365 apps through Intune. These outages occur around the same time each month.
I would rate the scalability of Intune a nine out of ten.
While the technical support team is generally good, there have been instances where feedback sent to the product group has resulted in delayed or absent responses. This can be frustrating, especially when requesting new features or clarifying existing ones. It would be beneficial to establish a clearer communication channel with the product group to ensure timely responses and address customer concerns efficiently.
Neutral
Previously, we used Workspace ONE. While I find Intune to be generally better, there are still some specific areas where Workspace ONE offers functionalities that Intune currently lacks. Additionally, Workspace ONE was significantly faster for generating reports. However, I acknowledge that Intune has undergone significant improvements over the past year and a half, and it's steadily approaching the level it needs to be. Nevertheless, there's still room for further improvement.
The implementation was completed in-house.
The current licensing model separates essential features into higher-tier subscriptions, requiring additional purchases. Ideally, all functionalities should be included in a single bundled license.
I would rate Microsoft Intune eight out of ten.
We rely on Intune for device management and leverage other tools for security.
Additional maintenance is required to deal with the monthly outages.
I recommend using Intune for endpoint management. It's important to familiarize yourself with the product beforehand. Researching endpoint management via Intune and reviewing Microsoft's online recommendations is crucial for successful implementation within your organization.
We opted for Microsoft Intune for endpoint management within our Microsoft solution bundle.
Intune unifies our endpoint and security management tools.
Managing our devices in a single solution helps our IT security operations.
The user experience is good, especially for SIS Administration.
Intune provides 90 percent visibility and IT control across device platforms.
Intune helps us secure our hybrid work.
Our information security team has been quite satisfied with our organization's security posture since deploying Intune.
Microsoft's E3 and S3 subscriptions keep us within their ecosystem and enhance our IT productivity, eliminating the need for third-party solutions.
With the implementation of Intune the risk of security breaches has been decreased.
Intune's unified platform has saved our organization money by eliminating redundant costs, like extra licenses and the need for multiple solutions for the same tasks.
Intune helped us consolidate vendors. This consolidation has improved our security posture.
It is important for us that Intune integrates with Microsoft 365 and Microsoft Security for both cloud and commonly managed devices.
Intune's unified endpoint management platform is invaluable.
Microsoft Intune is not user-friendly to manage and has room for improvement.
The detection and prevention of end-user data leaks from mobile devices can be improved.
I have been using Microsoft Intune for nine months.
The first level of remote support is inadequate. While the E5 license grants access to advanced support, I've encountered instances where the technical support team deflects responsibility. For example, a recent issue with Microsoft not syncing properly with the cloud was attributed to Windows and redirected to another team. Due to Microsoft's overall responsibility for their products, I believe since it all falls under the umbrella of Microsoft, they should deal with it.
Positive
Once we create our tenants, the migration and synchronization of the users to the cloud services is straightforward.
We deployed the solution in phases and it took around three months to complete. Three people from our end were involved in the deployment.
Our Microsoft partner helped with the deployment.
We evaluated IBM, Ivanti, and Workspace ONE but our management decided to move away from third-party platforms to simplify and save costs.
I would rate Microsoft Intune a nine out of ten. Intune is missing a single-pane-of-glass, requiring us to jump through multiple portals to manage all our devices.
We have 3,000 users.
Microsoft Intune is a top-notch solution and I recommend it.
We use Intune for endpoint management to ensure they are updated with the latest patches. We also leverage Intune to oversee our applications and keep them current. Lastly, we employ Intune's remote tools for endpoint administration.
We implemented Intune to ensure our endpoints were updated.
Intune brings all our endpoints and security management tools into one place.
Intune is integrated with Defender to manage our security policies.
The user experience is good. Intune is easy to use and deploy.
Intune has significantly improved our IT productivity by automating the updates for Windows and third-party applications. This automation reduces costs and improves efficiency, allowing us to adopt a set-and-forget approach to software maintenance.
The automatic patching is the most valuable feature of Intune.
Intune needs to incorporate more tools to reduce the number of third-party applications we rely on. For instance, I currently use PatchMyPC to package new applications for Intune and then deploy them to endpoints. If Intune offered this functionality natively, we wouldn't need to rely so heavily on third-party applications.
I have been using Microsoft Intune for almost four years.
The technical support by Microsoft is terrible.
Negative
The initial deployment was complex, requiring an expert for setup. It took one week to complete and involved one system administrator and me.
The implementation was completed in-house.
We have seen a return on investment from Intune through time saved, which correlates to around $20,000 per year.
I would rate Microsoft Intune seven out of ten. Intune is a valuable tool, but following the screen prompts can sometimes be challenging.
Two of us are responsible for the maintenance of Intune.
I'm working with InTune on the user side. It's used for device enrollment and mobile device management. It's used for remote desktops and remote control for compliance.
The solution helped us resolve user enrollment issues. Sometimes, users want to reset, for example, file server systems and Intune ensures a user can't just enroll any new systems.
The mobile device management is very useful. With mobile device management, we can monitor everything and control devices. We can monitor devices and fix things on remote desktops.
Intune brings all endpoints and security management tools into one place. This helps us monitor everything from one portal. We can exclude any PowerShell command. It helps us not only monitor for but also fix any problems. We can add and remove items remotely from any device from a single place.
The solution has a helpful feature called Co-Pilot. We can access it via the portal and configure it as we need. However, I have not used it myself.
We use Intune with a hybrid model. We can connect it easily to other services.
With the ability to monitor everything from one place, our security is quite good. The level of security is better. I'd rate the level of security we've been able to achieve ten out of ten.
It's positively affected IT productivity in our organization. Having Intune has made our IT engineers more effective. They can use the cloud portal from anywhere and at any time to easily adjust or deploy whatever users need.
We've been able to save money compared to using SCCM. Intune has helped from a cost-savings perspective, although I can't speak to exact costs.
There are a lot of updates happening on Microsoft.
I've used the solution for about six months.
I haven't had any challenges with stability.
I haven't come across any limitations in terms of scalability.
I've never had to reach out to technical support.
I also use VMware.
The initial setup was straightforward. We simply needed to create an account don't he Microsoft side and then we can go and get licenses.
I administrate and maintain Intune for the company.
I don't have any visibility in regards to Intune pricing.
I'd recommend Intune to others. I'd rate Intune ten out of ten.
Nowadays, we've seen more evolution towards Autopilot for Windows 10 and then in a hybrid or cloud-only setup. After the Windows devices, we use it with Android, the most frequent mobile, and then iOS. I have five or six projects regarding Microsoft.
It helps deal with conflicting policies. We do a lot of graph API calls toward Microsoft for reporting, et cetera.
It simplifies the work of the IT admins in a company if you set it up right. The setup will take some time, obviously. However, if you set it up right, it will simplify the management of your endpoints. The enterprise app management is great. With Intune, you can shorten the time needed for handling the necessary updates so that there are no vulnerabilities on the applications or on the operating system side of things.
The Intune suite offers a lot of features.
The AutoPilot feature is helpful.
Endpoint privilege management is very good. You can bring your own device setup. You can use it in combination with conditional access policies for encryption.
Migration from on-prem to cloud is good.
The settings catalog and configuration profiles are also very, very useful.
Intunes brings all of our endpoint and security management tools into one place. This is a good thing. We now have one portal to check instead of dozens. I'm really happy with that.
The overall user experience is quite nice. I have no complaints from end users regarding their devices enrolled in Intune.
We've used Copilot. We have nothing to complain about, however, it is very expensive. With Copilot, we summarized a few of our policies and devices, which were great. We check the properties of the devices, hardware, of the devices, and so on. Mostly, we played around with the summaries of the policies, however, we switched it off since it was running for a couple of days, and it was a few hundred euros for those few days.
Witnessing the benefits of Intune happen quickly. Clients usually begin to see benefits after the kickoff meeting. Intune is an ongoing development product. It helps both greenfield and existing setups. It's not static. We'll work with policies and versioning, and after every quarter, we'll review our policies and update where necessary. If clients used Intune managed services, they get policy updates included in the managed service.
Intune is good for securing hybrid work and protecting data of the company while bringing our own devices. We use device framework policies from Microsoft themselves with some minor adjustments. They have level one, level two, and level three policies. You can just fix the settings of their site, and that's also what we use. Then we just tweak and bring in our own experiences.
The endpoint privileged management enables users to enforce privileged access and can positively affect user productivity. In in small environments, the end users are, in 99% of the cases, also local admins on their devices, which is obviously not good. In bigger environments, we get into that less often as it's more of an organized thing. That said, in small environments, everybody is a local admin and that brings certain risks with it. So users can install and download everything they want. With endpoint privilege management, we can set rules for specific applications, and then, a user can ask for approval to run a certain application, which is very good.
Intune positively affects overall IT productivity in organizations. If users need to install it on a device that they need in their workday or day-to-day business, they can just grab it themselves from the company portal app. They do not have to wait. They do not have to enter a support ticket that goes to the help desk to request a certain type of software. They can do it themselves, so they save a lot of time.
Intune, when applied on the cloud, can save on costs. With the cloud, there's no on-prem infrastructure that needs service, electricity, space, or cooling, for example.
There are a lot of features that need to be released. There is no copy-paste or fie transfer. There's more work to do. They don't live up to my expectations anymore. Microsoft has a history of releasing features that are not completely finished.
Remote help needs to be better.
Reporting needs improvement. It's still lacking. The built-in reporting is pretty basic. In managed services, we have a lot more reporting. However, we had to develop it ourselves.
I've used the solution since the product launched, about 15 years ago.
The solution is fairly stable. I cannot recall the last time that there was a health issue reported on the Microsoft side regarding Intune.
The scalability is perfect. I've had no issues with scaling.
The communication between us and Microsft is good. They do come back with insights on what's to come. When it coms to support, if you are lucky, you will get a good tech that can help. The knowledge of some techs are insufficient. They may ask basic questions that are not relevant to the issue. You spend a lot of time re-answering questions you may have already addressed in the original ticket.
Neutral
I did not use a different solution previously.
I've been in touch with MobileIron and AirWatch, however, that's very, very basic.
I work with both on-cloud and on-prem versions of the solution.
The initial deployment is very simple and straightforward. I've been doing it for 15 years, so I understand the process. When people are new to Intune, there may be some complexity. There are many things that need to be considered. The learning curve can be steep.
There is support from Intune for maintenance, like when an application fails to install.
I tend to implement the solution myself.
Some people have Microsoft 365 with a security add-on, and Intune is integrated.
Copilot is expensive as an add-on.
It's a rather expensive solution, especially if you want to use all the bells and whistles.
I've been involved with the solution as a customer, integrator, reseller and consultant. I'm a freelancer as well and use it myself. I'm selling licenses and doing greenfield setups for different customers.
We've not yet used all aspects of Intune suite, which is a new collection of advanced endpoint management and security tools. We have demoed it, and we are showing it in workshops. However, we do not have it in a live environment. A lot of customers are hesitating to buy the Intune suite due to the price. Some users may be paying fifty euros per user per month and then would need to add another 10 euros for the Intune suite, and that's a big step since that would be a fifth of the license that they're already paying.
It's helpful that Intune is integrated with 365. It's important that everything is integrated together so that the Microsoft ecosystem becomes seamless.
I'd rate the solution 8 out of 10 overall.
It's a fund product. The possibilities are almost endless. It will make your life easier.
I was using Intune with a customer. I had a long-term contract with a mining company, and then I moved to another organization. I am now in a different company. They all are large organizations. They are moving to the cloud, and Intune is one of the tools they are going to utilize.
In my previous job, Intune was being used for the cloud environment. We migrated fully from on-premises SCCM to cloud-only managed. We were utilizing all the benefits of Intune for cloud management, such as Windows updates, encryption, configuration, replacement of GPOs, etc. Moving away from the SCCM to Intune was a part of my previous job.
It is a modern tool. It is a cloud-based or software-as-a-service tool that gives you centralized management at one location. You have good dashboards. You have pretty much everything at a single location. You can manage different settings in one place. It is about manageability. It also gives you access from any place. It is a cloud solution, so as long as you have connectivity, you can do pretty much everything.
Intune brings all of the endpoint and security management tools into one place, but it is a lengthy process because I have been working for large organizations. They have been heavily dependent on on-premise services for years or decades, so the transition always takes time, but it is pretty successful. It is a good tool, but in security, there are dependencies, so it takes time for the transition to be successful. We have been using different security baselines and CIS or NAS methodology. It is a difficult process. Especially when you do GPO migration, not all settings are yet directly supported in Intune. Sometimes, you have to do a bit of workaround, power shell settings, and registry settings. It is tricky, but it is a key area for a successful transition.
Intune does not yet provide full endpoint visibility and IT control across device platforms. There is still a significant gap between all the systems we used on-premise and Intune. It is probably going to take time for Microsoft to fill the gap. Sometimes, you have to use third-party products, and sometimes, you have to use workarounds. It is a tricky one, but Microsoft is moving in the right direction, slowly but surely.
In terms of user experience, users do not use Intune. From the user perspective, it is about the performance and the impact, and there are some analytical tools to measure performance, reliability, etc. The built-in reporting is pretty good.
Intune affects IT productivity. From the IT operations perspective, things are much more simplified. The transition also enforces some cleanups, optimization, etc. It is definitely a great improvement for the IT organization.
Intune itself has probably not reduced the risk of security breaches, but there are many add-ons. There are many security products from Microsoft that integrate with Intune and Azure. Its reporting is great. By having the right knowledge and the right understanding, you can utilize this. There are some security baselines that you can utilize in Intune, which are coming out of the box. Microsoft is providing its own products for security, and this is probably an area we should explore.
Intune helps to save costs. As a part of the transition from on-premises to Intune, you can decommission your legacy infrastructure such as SCCM and domain controllers.
Intune has helped to consolidate vendors. It is one product, and Microsoft is trying to fill all the gaps with the add-ons. Microsoft is constantly adding functionality pretty much on a monthly basis. Utilizing a single vendor or single tool set is always good. This consolidation affects the licensing costs. When you have a single vendor, you have more options for contract negotiation, license discounts, etc.
It is very important that the capabilities of the Intune Suite are integrated with Microsoft 365 and Microsoft Security for both cloud and co-managed devices. You have a single pane and the same toolset. It is always good to utilize a single product.
It is a modern desktop management tool. It is a replacement for SCCM and GPOs. When organizations are moving away from the AD to Azure AD, especially for devices, it is very useful. It is helpful for managing devices anytime and any place without requiring dependency on the local networks.
There is still a gap between SCCM and Intune, especially in the reporting, inventory, and software deployment areas. For people using SCCM, Intune seems to be very simple. It is a good thing, but sometimes, it is a bad thing. There is a significant gap, especially for large organizations in terms of functionality. Microsoft still has a lot to do.
I have been working with Intune for about 5 years. I am an endpoint management specialist. I am using it pretty much daily.
I would rate it an 8 out of 10 for stability. It is still under development, so there are issues. Sometimes, settings are not consistently applied everywhere, so they give unexpected results. It is probably because of the learning curve and also the ongoing development. Sometimes, there are bugs or some mistakes. It is a cloud environment, and sometimes, some settings are not applied. It is a matter of time. It will get fixed.
It is very scalable. It is practically unlimited.
I have been working with companies with different numbers of users and devices. In one company, there were 40,000 devices, and in another one, there were 300,000. The number of users is more than the number of devices because the companies I have been working with have different shifts, so they are sharing devices. That is why there are more users than devices. The average is 35,000.
The first and the second lines of support are quite poor. They redirect end users to publicly available documentation, which is not very useful because usually, the first thing you do is to check what is available publicly before you raise the ticket. Their support is not very good. I would rate their support a 6 out of 10.
Neutral
I have been mostly using SCCM. The move to Intune was a part of the cloud transition. Most companies are moving not only the MDM solution but all kinds of services to the cloud. Intune is just one of them. It covers one of the areas.
Its deployment and maintenance are easy. I would rate it a 9 out of 10 for both. It is generally deployed on a public cloud.
The number of people required for maintenance depends on the size of the organization. One person is never good enough because you need to consider various time zones, people going on leave, etc.
Intune comes with the licensing that is common for large organizations. However, Microsoft has recently released many add-ons that are very expensive, especially for large organizations or corporations. They are not very happy. They are not willing to buy them. That is the problem. Microsoft should probably work on the strategy for pricing for the add-ons.
They probably did not evaluate other options. A lot of organizations are trying to use one vendor, and they have been using Microsoft for a long time. Intune seems to be the most complete as compared to others. I have been doing some research recently for a company, and I have been going through some Gartner reports. Intune is clearly number one in this area.
To those evaluating this solution, I would advise to be aware of the fact that this is a product that is still being developed. There are many features that are not available yet, especially as compared to a product like SCCM which has been on the market for many years. Do not expect everything to be available straight away.
I have not used Intune much for BYO devices. The companies I have been working with do not allow that. They either provide their own hardware, such as laptops or desktops, or virtual desktops such as cloud PCs. They either have Azure virtual desktop or Windows 365, so I do not have much experience with BYO devices.
I have also not used Intune's Endpoint Privilege Management feature. It is probably a new functionality that is not free. For large organizations, it is a significant cost, so they are reluctant to go in this direction. They might use it in the future.
Because of its scalability and future-proofing, I would rate Intune a nine out of ten.
