Microsoft Intune Reviews

We use the solution for auto-enrollment with app EPP and application deployment with EPP.

We're currently testing the possibility of using the solution as a new MDM tool for mobile applications.

All regions and departments operate on the same model; we turn on the device, select if it's personal or corporate, and all the products and profiles are loaded onto it.

The solution hasn't improved our organization yet, as we're still in the testing phase and have yet to go into full production.

The ability to switch between Affinity and non-Affinity enrollment is great. 

The wiping features are very good. 

The capacity to create more profiles and switch between corporate and personal devices are beneficial features.

One of the main advantages of Intune is that it's a Microsoft product, so it integrates with the other MS products we use.

The solution needs to be better for managing laptops; many functions are still unavailable in this regard.

The scalability could be improved, and like most other MDM products, Intune is good but not 100% there yet.

We've been using the solution for a couple of years. 

The stability is good, and there has been a lot of progress since I last used the solution.

The solution is working well for the most part, but some improvements could be made to the scalability. 

I never had to contact technical support. 

I previously used MobileIron UEM and VMware Workspace ONE.

I wasn't involved in the initial deployment. Now that it's set up, deployment to devices requires turning the phone on, and the device will automatically pull up the profile if the client is linked to our Apple Business Manager tool. We currently have one staff member involved with the maintenance, but we're looking into distributing it to others on the same team.  

The pricing for Intune and the competitor products are all within the same range, there is no true advantage when it comes to cost. 

I evaluated MobileIron and VMware. 

I rate the solution seven out of ten. 

We have yet to reach a level where we can notice flaws or identify areas for improvement since we're still checking and have yet to run the solution through a capability list.

My advice to others evaluating Intune is that it's the best solution for mobile devices like Androids and iPhones. However, if you're rolling out physical laptops, I recommend using a second tool, as there are still many unavailable options on the Intune app for laptops.  

The solution is deployed on cloud. I'm part of the support team. There's another server team that works closely with Microsoft. They purchased an old 365 license, and Intune was one of the included features. We wanted to take advantage of the feature because it was part of the package. That's why our top management decided to save some costs by making use of Intune and not using AirWatch anymore.

We are enrolling through the Intune company portal, and then we are using the Outlook app to configure the email addresses of the company.

We are using the mobile feature, and we are also using MDM to lock the devices, to push restrictions, et cetera. Compared with AirWatch, I think it's easier to manage the devices and the profiles in AirWatch. Intune has a lot of options, but I've only been playing around with it for a few months.

In the past, I raised some tickets for the enhancement feature, which was missing in Intune. It can take a long time for these features to appear, or maybe they will just never happen.

There are certain things that I'm trying to replicate from AirWatch, and it's not possible.

In AirWatch, we have a launcher, which is like a container. You can choose single-app mode or multi-app mode. But in Intune, for example, you need to factory reset the device and then apply the MDM. If we choose multi-app mode, which is the kiosk multi-app mode in Intune, I cannot lock the application on the screen. For example, in the set mode, you have the option to set the leave Kiosk password. You can exit the kiosk. But if you choose Intune multi-app mode, you don't have this leave kiosk option. For us, it's very useful.

If you have this leave kiosk option in the multi-app, you should also have it in the single-app mode. We need this because we have an application that you run on a tablet in hotel rooms, and we want to lock the application in a single-app mode, but besides the application, we also need to have some background applications running, like we need to do some configurations in Knox from Samsung, and eFolder. 

We have three applications that we need to push, but the guests will only be able to see one. Because I don't have the option to leave the kiosk in the single-app mode, I cannot do any configuration in the background apps. We have one app we cannot migrate to Intune from AirWatch because of this issue. This applies to more than 2,000 devices.

I think we need the leave Kiosk option available for the Kiosk single-app mode, because we are stuck with at least 2,000 devices or more because we want to completely retire AirWatch, but we cannot until this feature is available. The applications that we are using in our hotel rooms are not compatible with Intune. My bosses are not really satisfied because we still have expenses with purchasing a license with AirWatch because Intune cannot really fulfill our requirements.

This option is already available in the multi-app mode. It should not be a new feature. This feature already exists. They just need to apply the single-app mode the same way they're applying the multi-app mode.

Compared with AirWatch, Intune is not very stable because I haven't had to deal with these issues. With AirWatch, I would try to fix something and I would need to fine tune the settings, et cetera. But once I fine-tune and push everything, it will run and be stable. With Intune, we are new with this product, but it took some time for me to create a profile and test the devices. It has been working for a few months, but then suddenly this weird issue happened. It affected all devices at once.

In the Outlook application, the scalability is good so far. But there are some differences between on-premises mailbox users and cloud users. For example, let's say I'm my boss's assistant and I'm able to view my boss's calendar on my Outlook desktop. Let's say I want to view a shared calendar on my Outlook app. For the cloud-use mailbox, I'm able to do this, but if I'm an on-premises mailbox user, this option is not available. Usually the cloud mailbox users have more options than on-premise users.

We have around 2,000 users enrolled in Intune so far, not counting the MDM device. That includes just email, the one that I have enrolled in the Outlook email app.

Our plan is to keep the solution because our primary solution for email mobile is now Intune because we are retiring AirWatch. We have already retired the email for AirWatch, and we are just using AirWatch for MDM devices. Of course, the plan is to keep increasing usage. If more users request email on their mobile, we are going to offer Intune.

Technical support is very responsive and helpful. There's another issue that I raised related to Adobe Acrobat. I'm not sure if it's a region issue, but I'm in Macau, and we also have some users in Manila, Hong Kong, and Cyprus. All of us are using the same profile. I make the Adobe Reader application available on the manage app store, but somehow the users in Macau, when they go to the manage play store, are not able to see Adobe Reader on the list. It's only happening in Macau.

I raised this issue. Support dragged the issue on for two months. Support said, "Because all the applications go through the Play store, maybe you need to reach out to Google." The issue was not really resolved because the issue might not be related to Microsoft but Google, et cetera. I just gave up.

Compared to AirWatch, I can upload APKs or I can just redirect the Play store link to push the apps. But in Intune for example, I'm forced to upload all the applications through the managed app store. To make it available is a different process, basically. There are some things that don't really stretch forward. 

If I upload a custom APK in the manage Play store and then I want to remove it, I cannot remove it myself. I need to send an email to Google and ask them to remove it. Then they will ask me to unpublish the app for 24 hours first. These are very simple things that I should be able to control myself, and it wastes a lot of time.

I think if you have the money and want something more stable, you should go for AirWatch. I don't think Microsoft is offering the same stability as VMware at this point. On other hand, I think the support from Microsoft is better, particularly the support in Asia. In VMware, all the support is from India, and sometimes I have a hard time with them.

Now that I'm starting to be familiar with the profiles, it's starting to get easier. A few weeks ago, there was a very odd issue that happened also related to MDM devices where we were using the manage home screen application to lock down the apps that we wanted to allow only the users to use, like the kiosk application.

We have configured the profile and have deployed to 200 or 300 devices. Some of our users called and said suddenly all the mobile devices were flashing. I don't know what happened, but it happened at the same time. The workaround that I had to do was to remove the manage home screen from the profile. Then all of the devices were kicked out and went back to the home screen of the devices. That was the only way they could resume the mobile devices. I don't know what happened, but something was wrong with the manage home screen app on that day because a few days after, I pushed back and everything resumed.

We have ROI because we are retiring AirWatch, so we're spending less and making the most of the free stuff.

The licensing is on a yearly basis.

I would rate this solution 7 out of 10.

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 use Intune for Windows computers, and we also have iOS phones.

Intune simplifies mobile application management. It is very good. Its console is perfect. I am satisfied with it.

Intune works well with Microsoft Defender. Intune brings all of our endpoint and security management tools into one place. It is very good. We can manage the firewall and other things. It is very good for the security of computers.

Intune provides full endpoint visibility and IT control across device platforms, but we need to have RBAC for the IT. We have to assign appropriate roles and manage the scope based on, for example, the country and division.

We can use Intune for computers on the cloud, and we can also use it for a hybrid setup with on-premises and cloud computers. We can use Microsoft Endpoint Configuration Manager to manage all the hybrid devices.

We have a lot of reports for data. There are reports related to Windows where we can see whether all the computers have required updates or not. We can also do an inventory of all applications on the computers. We can also do application installation across the company.

Intune works with Log Analytics for Azure. It is a tool for monitoring and analyzing log data.

We can configure Intune for compliance settings. It provides a method to know if a computer is compliant or not. We can use conditional access to allow or block connections. For example, we can set a condition where if a computer is not hybrid, we do not allow the connection to Azure or we block the Office access for that computer. We can configure a compliance setting to know if a computer is compliant or not. We can also block access if a computer, for example, is not encrypted. There are many settings that we can configure, and we can generate reports to see the compliance.

For application deployment, there are a lot of methods that we can use. We can do it from the company portal from Microsoft. It is very easy for IT to configure. We can package, for example, an SAP application in three seconds. We have the possibility to use the automatic detection rules and package our internal application. We have a lot of possibilities. We can use the applications from the store, or we can package our internal applications. I find it very rich.

It is easy to use Intune. We do not have to work with agents. We do not have issues related to agents. With SCCM, we had to use an agent, and there were certain requirements. For example, we had to use a local administrator account, whereas, with Intune, we do not need to do all this. It is all cloud. It is very simple and easy to use.

It is very easy to configure deployment policies. For example, we can deploy something just for Windows 11 and not for Windows 10. It is very rich when it comes to deployment and configuration profiles. Intune is now much better than before.

Configuration profiles, remediation, scripts, and auto-pilot features are very good.

The user experience of Intune is very good for me. The user interface and navigation are very simple and clear. It is very easy to use for managing Windows, iOS, and other environments. People at IT level one and level two will find its console very simple to use. It is very useful.

There can be more logs. I do not have any other requirements. I am very satisfied with it.

I have been using Intune for six years.

It is stable.

It is very scalable. I would rate it a ten out of ten for scalability. 

Our clients have a lot of users. We have 16 or 17 people working with this solution.

I opened a lot of tickets. Their team is responsive, and they respond quickly to help users. I would rate them a ten out of ten.

Positive

For remote access, we are not using Intune, but in my previous company, we used Intune for that. It worked very well. We did not have any problems with it. For managing remote devices, we are using Bomgar.

We have a lot of departments. We are using Intune only for the production computers. For others, we use SCCM. We have a hybrid environment.

It is a cloud solution. Its deployment took about 40 minutes.

It does require maintenance.

It is not expensive.

We trust Microsoft. They are a big and good company. Microsoft is working very hard on security. We do not have any problems with Microsoft.

I would recommend Intune for all companies. It is a very centralized and good solution.

I would rate Intune a ten out of ten.

Our main use cases with Microsoft Intune are about how we automate the deployment. Auto-pilot is a feature that we normally recommend. Another piece is about the package deployment, where we recommend, or have helped, customers in deploying and converting their Win32 application. These are the two main areas in terms of automating the enrollment and Win32. Another use case in terms of the Apple, which is being used more by the customers, is where we recommend them to go for the zero touch process by using the AD.

Intune's feature that I have found most valuable is its auto-pilot feature. The main thing is that it keeps building it. Also Intune's capability in terms of Mac, which is slowly increasing, although the customers are moving towards vMOX and leaving the Intune just because of its limited capability with Mac, though it has already been enhanced. More features include the conditional access and the app production policies with respect to BYOR devices. These have been increased a lot in terms of security.

In terms of what can be improved, I am looking for better enhancements regarding Apple management, not only on the mobile device, but also on the laptop.

Other than that, it already has good capability with Windows, and it is already very good for the mobile device. The only area that is missing is for the Mac products.

I am using Microsoft Intune for the last two, three years.

In terms of maintenance, since it is a cloud product, it automatically gets updated by Microsoft. So there is no maintenance required for the upgrade part. But definitely the maintenance part that we track is the software asset management - that the devices are there and that the patches are deployed on a timely basis. We also do maintenance on the dashboard reporting feature in terms of whether the devices are compliant or not compliant.

In terms of performance, devices will be automatically enrolled and all the applications will be deployed. So it will be ready to use once they log in with their Azure-ready credentials. That is zero touch for them. In terms of having integrations in place with other tools, any issues they face will have proactive or automated actions to resolve their issues, instead of raising them and going through the long process of raising a ticket and the resolution.

Scalability is good.

In my experience, the customers who are mostly going for the Intune are small, medium and large companies. We have seen a mix. These days we have seen a large base of customers having more than one device. So it could be suitable for any size company.

Not too much to say on support. It is pretty fast. But in some of the instances we did not get much or a proper resolution where we had to troubleshoot a lot. But in most of the cases, support was good.

Initial setup is a simple process. It is a cloud solution. It is easy to deploy and easy to integrate with other tools as well. If we have to integrate with on-prem or Azure-ready through an AD connector, it is easy. Also, it is capable of integrating with other tools.

In terms of deployment, having things in the VM or physical VM or physical system in place and the ports enabled, as the main infrastructure is all in the cloud, is only part of connecting with the Azure already and the AD connectors, and does not take much time. With full testing, it takes one day if all things are in place.

Their price is really good. That is the reason customers move here, because as part of the Office 365 package, they always get the E365 as well, which makes it easy for them to manage their devices without having additional licenses for Intune.

That is the best part.

The main differences between Intune and other products are, like I mentioned, in terms of the Mac. If the customers are majorly moving and adopting Mac laptops while they are using the Intune, they are leaving for other platforms, like Workspace ONE and vMOX. That is the reason for moving and the major difference I have seen these last couple of months. But at the same time, if there is not much dependency on Mac devices, they are moving from other platforms to Intune, also.

My advice to anyone considering Intune would be to definitely test it and have devices enrolled at least in a pilot phase. They will get feature compatibility, the policies, and the auto-pilot feature. So, I would recommend to do at least a POC, and then decide.

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

We are rolling out the product to manage cloud-based devices. We heavily use it for iOS and Windows devices.

Microsoft Intune improves our organization’s response time. We are supporting an older population of users. It is a key advantage to be able to support users who lock devices quite frequently.

The product’s biggest advantage is its ability to unlock a large number of devices remotely. It supports end-users who tend to lock their devices quite frequently. Its conditional access policy helps us keep the users logged in to their devices.

Microsoft Intune fails a lot when it comes to device compliance. The devices fall out of compliance a little too easily. If the users don't check in within a certain amount of time, they become non-compliant, even after having up-to-date standard settings.

I have been using Microsoft Intune for three years, personally. Our organization was using it for one or two years before I joined.

I haven’t encountered any stability issues for the product.

Microsoft Intune supports over 10,000 devices for our customers, primarily using iOS and Windows. We have a large number of managed apps in the aerospace industry. We were able to transfer apps to our devices managing app licensing through Intune.  I rate the product’s scalability a nine out of ten.

The technical support services are pretty decent.

Positive

I can see a good return on investment in terms of the areas it can automate to summarize day-to-day tasks, making them less time-intensive.

Intune has helped us greatly by rolling out conditional access policies with the RBAC settings. It helps us create a security posture for devices.

The product is critical for our organization to keep devices safe. We have a large number of around 300-400 IT executives. It is crucial to be able to limit any one user or group of users within the IT field from a zero-trust standpoint.

In the time aspect, the product helps users get the right tools whenever required. It saves a couple of work hours per month by letting the right IT executives know how to access the devices.

We heavily use iOS space with iPads. I advise others to decide to buy the product depending on the operating systems their environment supports. They should make sure it is the right product for their devices. 

I rate Microsoft Intune an eight out of ten.

We primarily use the solution for device management. 

There are a lot of use cases, however, the base is the mobile security for our corporate devices and deployment of applications. We are a worldwide organization and in many countries. There are also country-based use cases, or areas that incorporate these use cases for some specific business units such as healthcare and similar SAP solutions. We have a lot of small areas where we use this, however, the main driver is improving the security of the devices and providing some automation configuration for the users including VPN solutions and corporate WiFi connections, applications, et cetera.

If I compared this product to XenMobile, except the conditional access, which was also partially possible to integrate with Citrix XenMobile, then there is not much difference between the two. The functionality s very good. However, the main way this has improved our organization is that there is support for conditional access and native integration with Office 365 services which we migrated to. 

The integration with conditional access is great. That's maybe the most important aspect of the solution.

The pricing is very good.

We already use a lot of Microsoft products in our company, and therefore, it made sense to also use this product.

For the most part, the solution is stable.

As a cloud solution, the scalability on offer is great.

There are a lot of small use cases where we realized that some technical solution was missing in Microsoft in comparison to other products. For example, it lacks something similar to sensing or location-based rules and configurations.

We would like, for example, integrated remote control or a remote session tool or something like this. You must have TeamViewer and the integration with this is limited and it's extra money. Nothing is built-in. Some functionalities are really limited to fully managed devices and so on. It took a long time for them to integrate the big ECS infrastructure into the corporate devices. This is now done, however, it took a longer time than expected.

Technical support could be h=better.

We've used the solution for the last three years, starting with the integration. 

The solution is pretty stable. As it is in the cloud, there are not many issues in terms of a service outage or things like this. Maybe when there are new patches integrated every month, which sometimes happens, some functionality may be influenced or affected. It's more or less a small issue, however, issues are possible. I don't recall a situation where downtime happened or users were really affected, however. It's just an occasional issue we may have with a patch that we would need to address.

The solution is quite scalable. As a cloud product, there are no issues surrounding expanding if you need to. 

We have maybe 27,000 people using the solution at this time. There is a plan to have all mobile users in this solution, so we are talking about 70,000 users at some point. However, it's a question also of the licenses, as you have to have a license for that product.

Technical support is hit and miss. Sometimes it's really good and other times it's not so great.

We used Citrix Endpoint Management in the past. We used it about two years ago. It was a good product. They are comparable, really, Citrix and Microsoft. 

I was not involved from the beginning of the project. However, from what I remember, we did the implementation directly with the help of a support engineer from Microsoft. Their involvement ensured the setup was not such a big deal.

Deployment took maybe one year in our environment, however, this was because we had a lot of time to tune it up and to test it, to have a pilot for a few months and then add more people to the pilot before we started migrations for mobile, for example. We took our time to really prepare the product as best as possible and then deployed it to the users and migrated them over.

We have two levels of people at a global level that handle deployment and maintenance. They mostly focus on improving the environment, not troubleshooting WiFi issues. 

We had direct assistance from Microsoft. Their assistance made the process seamless and it was a positive experience.

The solution offers reasonable pricing.

It's my understanding that we have the licensing set up for monthly payments, however, it's not an aspect of the solution I'm directly involved with. I don't know enough about it.

That said, I am aware that, in order to have mobile involved, you need the EMS solution or EMS license, and that's an extra cost to the standard Office license.

We're just a customer and an end-user.

As we are on the cloud version of the solution, we are more or less on the latest version of the solution.

The product was chosen for political reasons, as the company is mostly using Microsoft products and also the prices were maybe better than other options. 

I'd recommend the solution to others. If they are already using Microsoft or 365, it's a good product for companies sot have. 

I'd rate the solution at an eight out of ten.

We are using Microsoft Intune for personal devices, specifically for mobile devices with Android, iOS, and Windows. We have applied the policies over there for device restriction and compliance. We also have a few policies related to Microsoft Defender.

At the security level, it has done wonders. We can easily differentiate between applications. For example, there are a few applications that are only related to the organization's work. We can deploy those applications.

It is very effective. Since the pandemic, we have been in the remote work scenario. We are managing people working from the office and home. Microsoft Intune has been helping us with most tasks we are doing, such as deploying applications and resetting passwords. We are also enrolling the devices. It has saved lots of time and money.

It did not take us long to realize its benefits. We just put our scenarios, and it took us a month or two months.

Microsoft Intune integrates well with other Microsoft solutions. It collaborates well with Defender and Cloud PC. We will see a few more collaborations in the future. It will work with other features of Microsoft as well.

The reporting of Microsoft Intune is very good. They have been introducing new things as per the requirements of customers. It is quite granular compared to other MDM solutions.

The feature I like the most is that we can perform remote tasks. If we want to retire or wipe out personal data or corporate data from a device, we can use Microsoft Intune remotely, and with the click of a button, data is removed automatically. Nothing needs to be done from the end-user side.

The App Protection policies are very effective. With these policies, we can separate the corporate data and personal data. We can block the sharing of information from personal data to corporate data and vice versa.

There are lots of areas. The backend of Microsoft Intune needs to be improved. We have seen a little bit of delay as compared to other MDM solutions. That needs to be improved. A little bit more granularity should also be added.

I have been using Microsoft Intune for 3 years.

Its stability is great. I would rate it a ten out of ten for stability.

It has great features. It has a good amount of scalability.

They have been great. They have a team that works granularly on the issues. They also have unified support for this. They also have 24/7 support. We get good support from Microsoft. I would rate them a nine out of ten.

Positive

I have only used SCCM which was provided by Microsoft and was totally on-premises. I have not used any MDM solutions from them.

In my organization, it is a hybrid deployment. I was not involved in its initial deployment, but I know that it is a little bit complex for people who are using it from scratch. You need at least an experience with SCCM.

It is deployed at a single location. In terms of maintenance, it does not require any maintenance from our side. Everything is handled by Microsoft.

We have seen an ROI.

I am not that aware of the pricing, but as compared to other MDM solutions, Microsoft is providing a lot of things at the organizational level. So, it is quite reasonable as compared to other MDM solutions.

I would recommend Microsoft Intune to others. If you have any plans for having remote work in your organization, Microsoft Intune has the capability. In the future, you will also see Microsoft handling everything related to Active Directory, which is the backbone of an organization, from Microsoft Intune itself. 

I would advise learning Microsoft Intune as soon as possible because this is the future.

I would rate Microsoft Intune a nine out of ten.