Microsoft Intune Reviews

We use Microsoft Intune to automate the onboarding and maintenance of our customers.

Before using Microsoft Intune, we struggled with software deployment and remote device wipe capabilities.

Most of the Intune is for all the remote devices, so it's all on-prem. For cloud, it wouldn't make too much sense.

Microsoft Intune brings all our endpoint and security management tools into one place. We use both Mac and Windows devices. Having all our endpoints and management tools in one place is helpful. I have a single place to check for current status and add and remove assets.

Microsoft Intune provides full endpoint visibility and IT control across device platforms. Having full endpoint visibility and IT control across device platforms allows us to deploy and manage the systems more effectively.

Intune works well and is seamless for the users.

Intune has allowed us to standardize better.

Intune's use of Microsoft security signals has improved our security because we can now take remote action on these systems as well as have a more common deployment.

It has helped to reduce the risk of security breaches in our organization because of the standardization and single sign-on.

It has also helped us reduce the number of IT staff, saving us costs.

The Asset Management and Auto Pilot are valuable features.

One of the other features we leverage is the single sign-on that Intune facilitates.

The Mac integration has room for improvement.

I have been using Microsoft Intune for two years.

I have not had any stability issues with Microsoft Intune.

Microsoft Intune is highly scalable.

Although I have not used the technical support for Intune, I am not happy with Microsoft's technical support in general.

Negative

The initial deployment was complex until we understood the process. We went through a simple dev test and then prod methodology. 

Two to three people were required for the deployment.

We implement Intune for our customers.

For organizations that are a Microsoft shop, the pricing is compelling. To buy it outright, it's two dollars a seat, which is cheap. The price is worth it.

I would rate Microsoft Intune an eight out of ten.

We have 400 users across multiple regions internationally.

Given the evolving security landscape in the cloud, it's crucial that Intune Suite is integrated with Microsoft 365 and Microsoft Security for both cloud and co-managed devices.

Maintenance is required to keep the packages up to date for any software we deploy. We have four people that deal with the maintenance.

I recommend planning and understanding how Intune will be used before deploying it.

We use Microsoft Intune to manage our corporate devices such as mobile devices.

Microsoft Intune unifies all of our endpoints and security management tools.

Since Intune is part of Microsoft and managed under one umbrella, we don't need any third-party solutions and we can control everything from Intune which enhances our IT and security operations.

Microsoft Intune provides full endpoint visibility and IT control across device platforms ensuring our data is secure.

The user experience for Intune is good.

Microsoft's security signals within Intune improve our security posture.

Endpoint Privilege Management enables us to enforce least privilege access. We can assign different types of access based on each user.

Our attack surface is minimized because if there are any threats or suspicious activity, the affected device is automatically blocked and it becomes non-compliant. The application and company data become inaccessible until the issue has been resolved. These actions also trigger email notifications to inform us of the situation.

Implementing Microsoft Intune has significantly improved the efficiency of our IT team. Previously, managing our devices involved juggling Active Directory and SCCM, requiring multiple tools and a scattered approach. Now, with everything centralized in the cloud, we have a single portal, a single point of control, and a single subscription. This eliminates the need for dedicated servers and complex hardware setups, reducing the need for manual monitoring and update triggers. With Intune, everything is under one umbrella, offering a wide range of options with just a click. No more complicated settings or fragmented workflows. We simply choose the desired policy, perform a few clicks, and our machines are enrolled and updated seamlessly. This streamlined approach has not only boosted our IT team's productivity but also enhanced our overall security posture.

Intune has helped reduce the risk of security breaches by up to 70 percent.

Microsoft Intune has helped our organization save costs.

The many policies available in Microsoft Intune for managing our devices are valuable.

The policies we had in SCCM and AD offered features that are missing from Microsoft Intune.

I have been using Microsoft Intune for one year.

I would rate Microsoft Intune's stability a seven out of ten because it needs more granular policies.

The first level of support is not good but the higher levels are knowledgeable and they are available 24/7.

Neutral

We previously used Microsoft System Center Configuration Manager and switched to Microsoft Intune so we could better secure our personal and corporate devices.

The initial deployment was straightforward. We need a license to join the machines to Azure and then apply the policies we create.

One person is required for deployment.

The implementation was done in-house.

I am satisfied with the pricing.

I would rate Microsoft Intune a seven out of ten.

Intune has helped us consolidate vendors. The consolidation has saved us on licensing costs.

We have 100 plus customers and a team of 20 people using Microsoft Intune.

It's important that Intune's suite is integrated with Microsoft 365, and Microsoft Security for both cloud and co-managed devices.

Intune does not require maintenance but we do need to monitor the status of our devices.

I recommend trying Microsoft Intune.

Microsoft Intune is used for Mobile Device Management. We enrolled our mobile devices as well as the mobile device solution for corporate devices. We have a lot of policies such as the compliance policy, and the conditional access-based policies for the corporate mobile user and we use the solution to assign their  Outlook Teams and other configurations for the organization. 

We use Intune to design compliance policies that apply to corporate devices and to wipe data from devices when users are terminated. Intune is also used for mobile-based solutions, but we have recently explored its capabilities by using the Autopilot feature. With Autopilot, Windows 10 devices can be reset and new versions of Windows 10 can be deployed from Intune.

Intune has many benefits from the Microsoft perspective. This solution can manage Windows 10 devices, app management, and provide security solutions. We don't need to worry about our network connection, and we'll be more secure with regular security patches and compliance. Since everything will be deployed through the internet and users will log in using the internet only, the risks have been mitigated. Security updates, security patching, and the application will be targeted from Intune. The location tracker will be available to track where the device is and the user's location. The user will be restricted from accessing certain applications using compliance policies. Conditional access policies will be based on the reason why the user needs access to the application.

Microsoft Intune is one of the best products in the industry for managing Windows devices. The solution has more feature restrictions. The conditional access policies also eliminate the dependency on the on-prem network for the devices. The solution also manages our security settings and a lot of other beneficial features such as Microsoft Purview which gives us the compliance portion. We can manage all aspects of our device from a single console, including M365 services. This allows us to configure data classification types, such as public, private, internal, confidential, and highly confidential.

The best feature is that we don't need to worry about downtime. We don't need to worry about the network connections of our office or the virtual private network. Everything is being done through the internet. Using Intune Autopilot, we can configure and deploy everything to the devices.

We need the capabilities of the Cloud Management Gateway (CMG) to be enhanced through Intune instead of Azure. I suggest that Microsoft consider this. If the user already has a subscription to Intune, they should not need to buy an additional subscription for Azure services.

The support needs improvement. When we need support, we don't get a response within the SLA because the support has been outsourced.

I have been using the solution for five years.

Microsoft Intune is a stable product. For the configuration, we could reach out to technical support, but other than that, we need not worry about anything. If we have configured the product correctly and we are not going to enhance any additional capabilities in Intune, then we need not worry about technical support.

The solution is extremely scalable. I give scalability ten out of ten.

Microsoft has outsourced its technical support so if we raise a ticket with severity, the technical support team may not be able to respond to us within the timeframe or the standard we expect. Sometimes we get the call within four hours. Sometimes we won't get that call for a day or more. The service side is pathetic now. To get support from Microsoft, we need to have our TAMs in place and then we need to submit the ticket. If we have already aligned a TAM for the tickets, we get support from Microsoft.

Neutral

Previously we were using Microsoft Configuration Manager. The Microsoft Configuration Manager is the dedicated server for managing devices on-prem. We need to make sure the device is on the same network through which the policy is getting replicated. The dependencies with that server as well as with the network are important, and the devices need to be online on the network. Using Intune as a backup solution, if the device is not on the network or if the device owner is not in the location but it has an internet connection, then we can deploy all our physical solutions onto the devices. We are using both, the Microsoft Endpoint Configuration Manager as well as Intune, since a couple of policies are still only being managed with the Configuration Manager.

The initial setup is straightforward. Once we have subscribed to the license, we will receive our tenant ID and organization ID. We can then access the portal and configure whatever we want. To save the configuration, we must enable it from the portal itself. The Azure Ready Connect GUI console makes it easy to join devices to Azure and to create and deploy conditional access policies.

We have four or five global administrator access levels in our organization. The most limited level is for the global administrator, who can be limited to one person. We need to involve them to enter the password while configuring the CMG, and then the Microsoft support in case we are missing any configuration during the installation or managing Microsoft Intune.

We deployed across more than 10 to 15 countries. The solution is used in India, the US, and England.

We have seen a return on investment using Microsoft Intune. We can save money by establishing our management point and cloud distribution point in Azure. Cloud support is an additional cost. We have to pay Microsoft for the VM, which doesn't act as a management point and the cloud distribution point for the endpoint. Endpoints are the on-prem devices.

Earlier, Microsoft used to give the license using the MSDN subscription, now the subscription part uses the M365 E3/E5. Existing E5 license holders for M365, Intune, and Azure, receive a free license.

If we're only upgrading to Windows 10 for the monthly security patches, Ivanti has Patch Now. Patch Now is a solution that gives us the same set of capabilities as IBM BigFix, but Intune has enhanced capabilities. Ivanti Patch Now is another product similar to the Microsoft Configuration Manager console and we have to make sure the device is on the on-prem network itself. Intune is a cloud-based solution that does not require the device to be on-prem. Everything is in the cloud, including device tracking, writing, and initiating remote connections.

I give the solution a ten out of ten.

I manage the endpoints for the implementation strategy and use the desktops or Windows for migration. I'm not from the mobile device management team, but I can give presentations on how the devices will work in the Autopilot zone with Intune. I'm also familiar with conditional access policies and what needs to be in place for a successful migration.

We have 35,000 end-users.

Maintenance is minimal. There have been no reports of any outages from the cloud perspective, meaning that any downtime is from Microsoft itself. However, on-prem systems may experience challenges. We don't need to worry about downtime and all the systems will still be operational.

New customers are definitely going to reach out to Microsoft for purchasing all the products. Microsoft will have its own lab. They will give us the live demo from the lab, but that won't be a feasible solution. We should check and bring that solution to our environment. It would be good if we can create our own test environment and then ask Microsoft to perform all those configurations and just train our engineer about the Intune part. We will know all the legacy parts of our environment which could impact when we are moving our devices to Intune, either the legacy app, legacy hardware, whether those devices are supported, the TPM, the Tested Platform Module, the BitLocker configuration, everything we need to understand before we move our device to Intune.

I worked with Microsoft Intune.

Third party integrations are very convenient to use with Microsoft Intune.

Whatever is required is available in Microsoft Intune. Remote access functionality could be added in future updates.

Microsoft Intune is currently overpriced.

I have been working with Microsoft Intune for six years.

Microsoft Intune support needs improvement and they could work on enhancing their support services.

Microsoft Intune is the best among competitors, though I haven't worked with other similar tools.

I would rate it an eight out of ten. 

I use it for deploying software and managing devices.

Microsoft Intune brings all of our endpoint and security management tools into one place. I can log into only one console and jump from one system to the other system seamlessly.

It is easy. When I hand out a new device to new users, I ask them to enter their email address and password. They just need to give the device 15 to 20 minutes, and it is done. Users can then start working on their devices.

It just works. I do not have to run after the software to see if it is the latest update. It just runs. It is setup-and-forget.

Microsoft Intune makes it easy to secure hybrid work and protect data on company and BYO devices. Once you have set up all the rules, it just works. You cannot mix personal data with company-related data. Also, no data can be extracted from the business aspect to the personal one.

Microsoft Intune's Endpoint Privilege Management feature enables us to enforce the least privileged access. For me, it is a big advantage to only have the rights I need and not the ones I do not need. For every specific case, I just request the required role for it, and afterward, I deactivate the role. From the security aspect, it is at a very high level.

It helps reduce data loss. It helps with data loss prevention. We also use multifactor authentication and block unknown devices and unknown users. Any external attacks are blocked via a lot of mechanisms. We can use our privileged roles only inside a closed network and with PKI-based authentication.

Microsoft Intune has affected the IT productivity in our organization in a positive way.

It is very important for us that its capabilities are integrated with Microsoft 365 and Microsoft Security for both cloud and co-managed devices. This feature was one of the major things when we started digitalization.

The ability to work from all over the planet is valuable. You just need a functioning and working Internet connection. You can enroll devices by binding the hash values in Intune. You can enroll them from wherever the person is. It makes no difference if he is sitting at home or office or is on vacation.

They are always rolling out updates. You get more and more possibilities to enroll devices and configure their settings and security. I have confidence in the setup they have provided so far. I, as such, do not have any specific inputs or needs. However, there is always room for improvement when it comes to scalability.

I have been using Microsoft Intune for almost six years. I am always using the latest version. It is a cloud platform, and it is updated almost every month with new features.

I would rate it an eight out of ten for scalability. There is always room for improvement when it comes to scalability.

Their technical support is great. We always get an answer from Microsoft.

Positive

We were using Microsoft System Center Configuration Manager. We did not use any other vendor.

Using Microsoft Intune did not help us consolidate vendors. Our strategy is to not mix up too many different vendors and have just one. The best thing is that if you want to use Microsoft Azure and Intune, you can use the features out of the box. You do not need big modifications. You can take the default and build everything around your needs, and it will work.

This is the platform for every enterprise. It is easy to manage all devices such as Windows, iOS, and macOS in one place. You can also manage Android devices.

Overall, I would rate Microsoft Intune an eight out of ten because there is always room for more modifications and improvements.

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.

I am an Operations and Infrastructure manager. I do not use it directly. My team is the implementer, and I oversee it. I know the product, and I know what I can do and what it can do. I just do not push the buttons.

We are still launching it. We have about 85% of our PCs in Intune. We have only got two or three conditional access policies and compliance policies in place.

We are using it for endpoint management for basically getting control. Our next step will be to launch Autopilot. We will use Intune Autopilot and then also security policy management and group policy management. We will also use it for updates and patching compliance.

At this stage, we have not fully utilized its capability for securing hybrid work and protecting data on company and BYO devices. We are still growing. We have been managing our security manually through the security portal and through Azure Security. Intune can provide an additional level of management capability by bringing all of the external services into one management console. It is going to make managing our security posture a little bit easier.

Intune has not yet affected IT productivity in our organization, but it will. Once we start bringing on the remote support capabilities and we are fully compliant in terms of touch management and minimum touch levels, it is going to ease up a lot more. There will be more time and resources for us to look at the other features and capabilities.

Intune has helped to reduce the risk of security breaches in our organization, and that is purely due to its patch management at this stage.

Intune has saved us costs. As it is bundled with our enterprise agreement or enterprise subscription, we have not had to look at additional products. I am still hoping to convince our business that maybe Absolute is not needed if we can manage things with Intune. As we are still relatively young and immature in that area, we might need to look at alternate products to bolt onto it, so we have not yet had any direct savings. We have possibly had indirect savings.

Based on the bit of work or research that I have done, it seems to fit our needs. When you are looking at some of its tracking and management capabilities versus Absolute, it just does not go that one step further where Absolute would go with the recovery service for Precision laptops. My users or asset management are asking for the recovery capability on laptops. If they were not asking for that, I would just settle for Intune and provide the lost location and submit those details to enforcement, but they want the recovery service.

Intune has not helped us consolidate vendors because we are pretty much a single vendor. We have only got the Microsoft ecosystem. We are busy decommissioning our on-prem System Center setup, and we are moving to Intune on the cloud. It is integrated fully with AAD. We do not want to run infrastructure in South Africa. Because of the load shedding and electricity problems that we have here, we would rather use the cloud.

In the context of our journey to the cloud, it is important for us that the capabilities of the Intune Suite are integrated with Microsoft 365 and Microsoft Security for both cloud and co-managed devices. It would not have been attractive if it was not.

It is quite easy to manage. From what I have seen, it is very easy to check through. It is very basic. I do not need to be a rocket scientist to manage it. It takes a little bit of experience to set it up if you have never done it before. From a manageability point of view and ease of use, I would give it an eight out of ten rating.

It is quite policy-enabled, so you can build pretty much any policy to manage remote endpoints.

There could be more wizard-driven policy development or creation. Some of the policies can get quite complex. If they have a wizard that assists the administrators in creating the policy, that will be a great job.

Microsoft South Africa should improve their support for Intune in terms of turnaround time.

We started using it in about October 2022. It has been about a year and four months.

Microsoft South Africa could certainly improve on their support of it in terms of the implementation experience and completion of the project. This project has been going on for a year and four months already, but it should have been completed in six months. There are just too many clients looking at it, and there are not enough Microsoft support engineers for Intune.

We have one assigned Microsoft resource. We have got a unified support contract. They have only one support person to deal with multiple clients within our area, and if he is not available, we just wait.

If we had confident and good support from Microsoft, we probably could have cut the project time by 50%. We probably would already be finished and have 100% PCs fully compliant with Intune. 

I would rate their support a four out of ten.

Neutral

We are busy migrating from Microsoft System Center Configuration Manager and Endpoint Manager because of the infrastructure requirements. We want to be on the cloud.

We are a key government department that looks after and advises 13 other departments. They are rolling up Intune to those 13 departments.

It comes as a bundle, so you do not really know what the prices are. Microsoft does not break it down to the user cost for us. It is just bundled with our E5 license.

We did not evaluate other solutions because Intune was a part of our subscription.

My advice would be to make certain that you have the relevant in-house capability so that if you are working with Microsoft, you are able to cross-skill with Microsoft. If you do not have that and you are going to fully rely on Microsoft to assist you with deploying it, then make certain that you go into your project with your eyes wide open in terms of timing. The product is good. The scoping of the project is good, but the turnaround time is an issue. There is a lot of improvement required at Microsoft's end. The easier they make the policy creation within Intune with the wizard-driven process, the easier it will be for the internal administrators to implement it. If you remove your reliance on Microsoft, you can run a good product.

We do not use the feature called Tunnel for MAM to provide remote access to corporate resources on mobile devices. We do use Teams as a support or email support tool. We have a very small department, so that is sufficient. We would not migrate it to Intune.

We are not using Intune's Endpoint Privilege Management feature. At this stage, we are using Azure privileged management as the primary means of control. If it makes sense, we will get to it. It is not the first one on the list of things that we have got to do at the moment. We are on a zero-trust journey. If it is going to be one of the tick boxes, we will get to that.

Based on what I have seen of the product and its capabilities, I would rate Intune a seven out of ten. There are some issues that need to be dealt with, especially with the integration with Microsoft Defender Endpoint. Most definitely, the level of support and Microsoft resource capability is where I would mark it down.