Microsoft Intune Reviews

The solution can be primarily used for mobile management. We're using the solution to enroll Windows 10 devices.

The policies on the solution are very good.

The process of enrolling devices is a useful aspect for us.

The features that allow us to control the devices are helpful.

The initial setup is not hard at all.

Technical support, in general, has been quite helpful.

We've found the configuration capabilities to be quite good.

So far, the solution is fast and has an intuitive interface.

The feature that allows us to import the business application from the configuration manager to Intune is not very good at this time. They should be getting better in the application input on that platforms. It's an aspect that could use some improvement.

Other than that, I can't recall the solution lacking any features. Overall, we've been happy with the offering.

I've used the solution in the last 12 months. We've been using it for one year, more or less. It hasn't been a very long time just yet.

The stability of the product is quite good. there are no bugs or glitches. It doesn't crash or freeze. The performance is reliable. 

We do plan to increase the use of the solution over the coming year. Our intention is to scale a bit. We don't plan on switching products anytime soon.

I've dealt with technical support in the past, and I'm quite satisfied with them. They are knowledgeable and responsive. I have no complaints.

We did not previously use a different solution. We've only ever used Microsoft Intune for these current use cases.

We found the initial setup to be quite easy and straightforward. It's not complex. If a company wants to set it up themselves, they shouldn't have an issue doing so.

The deployment didn't take very long. It was a pretty quick process overall. 

I can't speak to any aspect of the pricing. It's not something I handle. I don't deal with licensing and therefore don't know if it is expensive or reasonably priced.

I've been testing the solution. I'm a customer and an end-user. My company does not have a business relationship with Microsoft.

In general, I would rate the solution at an eight out of ten. We've been happy with the capabilities overall.

I work for Mastersystem Infotama who is a Microsoft partner. I am an engineer, and I deploy Microsoft Intune in several companies. Our customers use Intune for their mobile device management. We also use Intune to protect devices accessing the application's corporate data. First, you must be compliant with the same criteria. If users connect with the corporate IP address, they only connect with username and password. But if they connect from a coffee shop IP address or IP addresses that aren't corporate, they will have to engage in multi-factor authentication.

I like that we can implement conditional access. Microsoft has conditional access for mobile device management, and we can categorize it as a corporate application or a personal application. We can protect it so users cannot copy from the corporate application to the personal application, but users can copy from the personal application to the corporate application. 

We can also make one file with different permission for different people. The name of the feature is Microsoft Azure Information Protection. We can configure it to help the user work from home. They can download the file, and they can operate this file in another place, but the corporate organization still protects it. 

We can also protect user access from a mobile phone. They cannot save the file to internal storage for the mobile phone. They only can save the file to OneDrive or SharePoint drive.

It would be better if Microsoft can reduce the cost of the license. as we know the Intune device subscription is licensed per device at a cost of $2 a month. but for the best to enhanced security and feature we must added add-on license or buy/upgrade to bundling license such as M365E5.

Microsoft Intune is a core product, and it's very stable

Scalability is good. It can adopt Android and iOS and manage macOS. We couldn't support macOS two years ago, but now we can.

Technical support is good. We get help from Microsoft support. For Microsoft Intune, if we buy the license, we can get support for free. We can create tickets for the problems. We can also report the problem in the Microsoft portal.

Microsoft Intune is essentially software as a service for mobile device management. To configure Microsoft Intune, we only have to register the domain name and register the DNS. We can log in to enroll the device with Microsoft Intune. After we register the DNS and the domain name, we configure the policies. All policies like user access and permissions. After that, the admin can send the license to every user.

The configuration takes one to five days. But it takes a long time to educate the users on how they can use it. This is because some things change after we implement Intune. Users may complain that they can't do what they did before, but it's better from a security perspective.

Microsoft will maintain it. The customer only maintains the policy and the license.

The price could be better. Microsoft Intune pricing is based on the number of users. Every user license is for 15 devices. consists of 5 devices for PC (Windows or Mac), 5 tablets, and 5 mobile phones (Android and iOS). 

My customers already know and use Microsoft, so they adopted Intune. They use Office 365 for secure collaboration between organizations. Microsoft is the preferred choice and has user confidence to work together securely.

MobileIron has two types of licenses. One is a SaaS-based model, and they provide support, and the other is a license for the on-premise solution. Microsoft Intune offers only a cloud solution.

If a customer already uses a Microsoft solution like Microsoft Office, or an email solution like Microsoft Exchange, it's better to use Microsoft Intune. But if they want an on-premise solution, they can choose another solution like  Mobile Iron or Airwatch solution.

On a scale from one to ten, I would give Microsoft Intune a nine.

It works pretty well for us.

The configuration and pricing can be improved. It would also be better to meet with people in the country and teach us how to manage personal information because we will not look at or touch any personal information. They should teach us about managing personal information and make it really easy for us.

Pricing can be improved.

On a scale from one to ten, I would give Microsoft Intune a ten.

I use Microsoft Intune to manage iPhone devices that we currently deploy to the end-users, and I manage all that. Right now, we're running close to about 60 devices. 

But eventually, what we want to do is go ahead and enroll the Windows platform on that as well because there's only one license per user that can deploy up to five devices. That is going to be my next migration roadmap. We're going to be managing laptops through it as well. So it would be Windows 10 platform along with the iPhones.

I like how Microsoft Intune lets me lock down the email profile and make it accessible only on certain devices. I also like how one user license allows up to five devices.

I'm still playing around with it and haven't had any issues with the product yet, but support can definitely be improved.

I have been using Microsoft Intune for about eight months.

I would say that it's a stable solution.

It's definitely scalable because one single-user license can allow up to five devices to be added. We're going to be rolling some laptops out, and we can definitely work with either an Android or an iPhone. It doesn't matter which device. 

It's scalable to that point, and the fact that only one user license will allow up to five devices, I think that's something that we would be looking to do, and we're definitely happy with it.

I've dealt with Microsoft way too many times, and needless to say, I'm not too fond of Microsoft support most of the time. I've always had a better experience with Workspace ONE and VMware, and they're very good with their support. Microsoft support can definitely use a lot of improvement.

With Apple Business Management, we can pre-deploy everything, and we can manage everything on the phones with the lockdown. With Workspace ONE, I couldn't lock down the email profile and make it accessible only on certain devices. 

Especially with Office 365, this became the biggest issue because we couldn't lock down the profiles per device space. When I worked with VMware, I worked with Microsoft Office for a couple of weeks continuously to figure out a solution and couldn't find one. 

That's when we decided to go with Microsoft Intune management because we could lock it down to just those devices. Otherwise, it was locked, and our tenant is a government tenant, and we don't allow any external access to our tenant.

That was the issue I was having with Workspace ONE. Workspace One couldn't integrate Office 365 applications the way I wanted it to.

The initial setup was straightforward. I actually prefer Microsoft Intune over VMware Workplace ONE because it's a bit more complicated. The setup was also easy because I've worked with Intune before.

It's not a server license. It's an end-user license. Because it's an end-user subscription and it's on a monthly basis, and because we're a government tenant and have a lot more scalability and users, we use it monthly. 

We work with the subscription rather than a server license. I think it's economical this way because we don't have to have a server license for that, and I think that works in our favor.

I would definitely say that you need to work with Apple Business Manager first. If you don't set up that account first, you will run into some issues, especially if you're doing a managed profiles on it. 

Just make sure you do your homework before you get started because there are a lot of prerequisites. If you miss them and you don't do it, then you run into issues, and then you're literally recreating the same work you've already done.

On a scale from one to ten, I would give Microsoft Intune an eight.

I'm a senior information security analyst and a customer of Intune. 

Before having Intune, we didn't have the capability to have computers wiped. I couldn't manage the operating system from a central location and wasn't able to deploy policies and verify software updates. It's helped with software update needs, operating system version update needs, and security policy enforcement.

The support is excellent for this solution and the configurations are a good feature. 

There are some enrollment features that could be improved, possibly some other tools that do almost the same job with alternative ways to enroll the device. Intune doesn't have those features. Additionally, I think they could try to invest more on macOS devices making it more manageable, and making the management more accurate. A solution like Jamf, for example, gives you the greatest capability - more capability on management, on policy enforcement, wiping devices, locking devices, and many other things. This is the main reason I'm not using Intune for all the contractors now and the reason we're planning to have Jamf implemented at the beginning of 2021.

If they could improve the support on the macOS devices, it would be great. Then we wouldn't need to buy Jamf. I'm not sure it's possible because of the relationship the enterprise has with Apple, but if they could improve the macOS management, that would be great. 

I've been using this solution for about two years. 

The solution is very stable, we don't have any problems with the platform itself. We had a problem a few weeks ago with the whole Azure provider system which affected not only Intune, but most Microsoft services. This was the biggest problem I've had with Intune, no problems with the platform or instabilities.

I'm not able to scale because of the issues with macOS management. We really have some needs here that Jamf Pro covers more efficiently than Intune does. We are trying to work it to have Intune on Mac systems, but we need to install something extra to make that work. We were looking for a more transparent tool in order to get this enrollment done by a central console, and not have to install other tools on the computers. Jamf does that, so we essentially don't need to install any kind of tool. You just need to enroll your device using a URL and it's done. Scalability in relation to the entire Windows or Android or iPhone environments can be done without a problem. We have around 2000 computers. In my previous job we had 55,000 PCs, and they were all Windows.

We had four analysts working on implementation and we now have two people dealing with day-to-day maintenance. For now, we won't continue installing Intune on macOS. We'll just keep them on Windows, Android, and iPhone and we'll go through the macOS with Jamf Pro.

With Microsoft, everything is on the community and easily accessible. Jamf Pro also provides a very, very, good support team. They have engineers, and depending on the support you buy or the support agreement you make with them, you can have a personal engineer working with you 24/7. Both tools have very good support teams.

It's really simple to implement Intune. Everything is already deployed on the cloud and you get everything you need. If you have a Windows 10, you can perform this connection from the Windows control panel and it's quite easy. We are now working to get the Android and iOS cell phones enrolled as well. We are on a pilot right now for macOS. Computers running macOS are already in a pilot period. We're just verifying that everything works well. We're also proceeding with the implementation for the macOS computers as well. Deployment took one or two weeks and I did it myself. 

In Brazil, we need a partner to get a license. The partner communicates with Microsoft and provides us with the license. We have a monthly contract which is paid annually and we have a three-year contract with Intune. 

If you have a complete Windows workstation environment, Intune is fine. But if you have a mixed environment like I do, running Windows and Mac, Jamf Pro is the best tool to manage an Apple environment. The reason we chose Jamf is because it integrates to Intune. In a single panel you can have all the inventory you need, either from Mac computers or Windows computers, because they send the information to the Intune platform. This was the main reason we chose Jamf.

I would rate this solution a nine out of 10. 

Typically, for customers that tend to come from a transportation logistics background, it's essentially free or the TCO is literally non-existent. It's a good fit for our resume offerings. Anywhere between 50 to 200 users is a typical use case that we see, where they're leveraging the product for low subscription costs.

Its overall integration into Microsoft 365 is great. 

I would say the biggest benefit is the single-pane view. There's no jumping around multiple UI's to do your overall management. Linkage to a single pane is probably the best benefit.

I'm looking at it in comparison to other EMMs and there are better EMMs out there. It's still for me at an MBM stage, as it's addressing other areas that make up EMM, however, if you put it in comparison to others, for instance, the overall experience is better. We get OL and DM and we get in the mobile threat detection. We get in a lot of other things into that EMM. 

Intune, in their port description, for me is still pretty infantile. I will say in the next 18 months to two years, they'll start becoming a bit more major, I hope.

It's pretty straightforward to implement as long as you've got a Microsoft subscription. However, it's kind-of convoluted how they explain it and what you are paying for. Obviously, we know that the more money you pay, the more features you get. I think that they can lay it out a little bit better, sometimes it's pretty hard to follow what their offering actually is.

There's quite a lot of development that they can do within their Intune dashboard. I think there are too many lines hyperlinked to move you around. Others, in contrast, give you a simple dashboard and an intuitive administrative walkthrough.

The solution looks too technical. Even though it is a technical feature, it comes across as too technical to navigate through. They can certainly work on the overall dashboad and the layout, to simplify everything.

They can do a lot more with Enterprise Firmware over here to give it full support.

Coming from a Samsung perspective, they need to comprehensively support the Android provisioning methods.

I’ve been using the solution for three years now.

From a stability perspective yes, it's very stable. The SLA that Microsoft gives around their network, the cloud service offering, makes it very stable.

It's highly scalable. Anything that's in the cloud should come with scale, and in this case definitely a highly scalable option.

I'm not sure, in total, how many people are actually on the solution. With Samsung, there's no preferred EMM solution in place. Most of it tends to come down to local/regional preference. Each region's location has its own mobile provider or EMM provider. We don't manage Intune for ourselves or for customers. Therefore, within the business, I would say it's less than 5%. As I say, we have our own solution. Nobody's going to use Intune within Samsung and we have our own EMM. Therefore, I don't forsee us increasing usage.

As we're consultants, we never rely upon a specific Microsoft consultancy to resolve anything and we clear our own testbed issues. We've very rarely been in contact with Microsoft's technical support. We're more engaged with Microsoft from a strategic partner level or in partnership as regards to our EMM offering. We have all the expertise we need in-house.

The solution is cloud-oriented. As long as you have a valid Microsoft Enterprise Subscription, it's all subscription-driven. From an installation or deployment perspective, it's pretty quick and pretty straightforward. It's not complex. As long as you paid for at least a standard enterprise subscription.

Where I am with Samsung, we're pre-sales. This is the customer's OMS. We're engaging with customers that have these environments in place, to then obviously bolt in our Samsung cloud solutions port. Obviously, we become consultancy on our cloud solutions. However, more so you have the engineering aspects of that.

For my area of business, we have a yearly subscription, which provides us with Intune capabilities within our test labs. It is negligible. It's pennies compared to our growth target. It's very affordable.

I'm typically an Azure consultant. Therefore, anything on the Azure platform now obviously includes Intune from an EMM perspective.

We use a multitude of versions. I can't tell the specific numbers. We use many as we have to constantly compare against different customer environments. We have test labs that have multi-versions as well.

Predominantly, our deployment models are on the cloud. There's literally no call for on-premise at all, apart from network connectors.

I would advise users to consider the solution on a use case by use case. I personally work in a Samsung Android environment and there's a lot more feature support in other EMMs. Therefore, I wouldn't necessarily recommend it. In the next 18 to 24 months, I hope that severe changes are made as Microsoft establishes itself more.

Overall, I would rate it at a seven out of ten. There's still a lot of room for improvement in how they deliver. Their products and features are pretty good, and they serve the need. They probably just need to work on their explanation and probably the layout and UI quite a bit more. 

We are VMware and Microsoft partners, so we offer services around their products.  

We are using Intune internally but we are leveraging it for our customers as well. That is a different story. One part of Intune is within our company, but we are also providing services around Intune and Workspace One for our customers.  

For us, Intune is on the public cloud. For our clients, it depends on the requirements and it varies from customer to customer. Some clients' requirements are deployed in private cloud mode or the hybrid setup. It depends. Requirements differ from industry to industry. If a company is BFSI (Banking, Financial Services, and Insurance), then they will be looking for a private cloud solution. If it is something which is not BFSI or maybe some industrial interest, they might go with the public cloud.  

In the end, most of our instances are in the public cloud unless there is some compliance requirement. Otherwise, the accounts are mostly in the public cloud to conform to regulations.  

Intune is used essentially to facilitate the ability of enterprise organizations to manage their endpoints. It is for end-user computing or UEM (Unified Endpoint Management) solutions.  

One of the major advantages of using Intune is for our ISO (International Organization for Standardization) certification. We have to meet requirements for ISO 27001 and 27002 and part of that is that we need to have a proper control mechanism for endpoints and the users who are using those endpoints. The other requirement is that we need to manage the workforce. We have to manage their time to understand how long they have been working, how long their device was on, when they were working, et cetera. So we use some other products that compliment Intune to gather the data on that.  

For example, we have something called Time Doctor. We use it to monitor how long people have been working. We get reports that detail how long their devices have been on. Then there are different ways we can leverage these results and statistics. For example, we can compare the uptime of the device and uptime of Time Doctor. With that, we can understand how long an employee was working on something, but how much more time the machine was up in addition to the work period. That shows the period of time that he or she was not using Time Doctor.  

The other thing is we can remotely access a device. For example, say we have to do some troubleshooting because a user is having an issue. We can remotely log in via Intune to troubleshoot the issue, as long as the device is accessible. Obviously, that can only happen if there is no issue with the internet and connectivity and services. But we can remotely access the device and troubleshoot the issue securely.  

Those are some of the different use cases.  

I guess in our company we are using most of the features in Intune. What we use it for is to control the endpoints. We publish some selected applications and the end-users are only able to download and install those applications. They are not allowed to install or use any other applications other than what we provide. We do compliance checking. We run assessments periodically on the endpoints using Intune, and Intune generates reports. Sometimes we need those reports to qualify for our ISO certifications.  

It is a similar thing for customers as well. There is a different requirement but it is a similar idea. For example, if we are engaged with an oil and gas company, they have back-office stations and point-of-sale solutions. In this case, those are Windows systems. What they used to do is they had to manage those solutions manually. They had a contract with some third party. The third-party would go on the sites if there was an issue or something, and maintenance and delivery were all manual. They did not have any EMS (Endpoint Management Solution) at all. The only thing they had was something called a radiant configuration management server. That was only used for configuration purposes, not for maintenance or other troubleshooting.  

The concern and the requirement over delivery was raised because of COVID. No one was able to go to the sites to do the troubleshooting, maintenance, and delivery. The only solution that they had was to engage with us to deploy these solutions on their endpoints. They did not all go with Intune, some went with Workspace One, which is also a UEM solution. So they wanted us to deploy UEM on AWS public cloud, then connect it, wire their MPLS (Multi-Protocol Label Switching) network to the end-point spots and box devices in order to manage them.  

The generic answer to what can be improved is that I hope that the reporting needs to be a bit more interactive.  

In our company, we have been using Intune for the past three years.  

I think Intune has been in the market for a long time now. That maturity makes it pretty much stable because it has been through so many iterations.  

Until now, we did not have any concern with respect to scalability within whatever we have done either for our organization or for our clients. We have done installations for bigger companies, for smaller workforces within bigger companies, but not for the larger endpoints. We do not know how well it scales in every direction and if scaling will cause any problems. We have not come across those things.  

In our organization, we probably have 250 to 300 people who are using the product. We will probably increase that usage in the future, but it depends. We were planning to introduce Microsoft ATP with Intune for advanced threat protection, which compliments the security part. Because Intune does not have advanced threat protection capabilities on its own this resolves that issue. There may be other considerations in the future that influence the importance of Intune to what we need it for and how we proceed.  

We are Microsoft partners and we have a different support model with Microsoft than a typical client will. We have not had any issues with our support team and they have worked well with us up to this point. We have a different channel than the partners who need to communicate with Microsoft another way.  

It is a tricky thing to answer exactly what I have used that either was prior to or a substitution for Intune. That depends on different things and factors. First of all, Workspace One is definitely highly scalable, that I know. Workspace One also has a lot of integration options wherein we can have a lot of peripheral tools. Workspace One actually started with only UEM, but it is now not limited to UEM only.  

Intune, is only a UEM. So Workspace One has one integration as UEM, but it has many other things. Apart from that, it has Workspace One Intelligence, it has Workspace One Assist, et cetera. There are four different parts that can be integrated with Workspace One and they can work together for a highly scalable, highly secure, and highly analytical solution.  

Microsoft also has solutions. It is just that they are different solutions implemented in a different way. For example, ATP (Advanced Threat Protection) Microsoft is for advanced threat protection. WAD is for virtual desktops. They do not have the same type of tight integrations as Workspace One. All of these Microsoft products work separately. In Workspace One, all the products compliment each other and all the products can be combined more like modules under Workspace One. They can push their findings to Workspace One Intelligence where all data intelligence can be done. Auto remediation can be done. We can get findings from VMware because now Workspace One security is there to make sure that this is secure under the umbrella. VMware Carbon Black is also the same in that it can send its findings to Workspace One Intelligence. So the integration is the part that is handled differently. Workspace One has many features. Microsoft also has those features. It is just that it is a different way to orchestrate. In Microsoft, it is not under one umbrella. In VMware, that is under one umbrella, which is Workspace One.  

The pros and cons are different because both approaches have their own advantages and disadvantages. Both have solutions for each of the functions. For example, each has advanced threat protection and all those capabilities. If you stay working with that family of solutions, you do not have a problem.  

Now say, for example, a company went with Workspace One because they wanted to leverage UEM. They adopted some other modules as well with it to create solutions for problems or needs that they want to solve. They have to have Workspace One for this solution and they can not work with it separately. That might be a cost factor because they can not work with one tool only, they have to make the license for two products because they do not work separately.  

For Microsoft, since the products are completely separate, customers can choose which one to go with and only use that. They can go with only one product, or they can add any of the others. They do not need to have the central component to bring them together.  

So that might be an advantage or disadvantage in using one product or the other depending on the use case.  

We did not experience any complexity in the initial deployment and there was no problem with the installation, I do not think. The complexity definitely depends on what you are trying to accomplish. I do not remember exactly because I do not directly deal with deployment anymore. I am actually leading it. We have a team that deploys the product. I do not look over their shoulder to know how much time it takes exactly and what factors it requires for successful deployment.  

We did the deployment by ourselves without the help of consultants or vendors, that I know. We are system integrators. We have the capabilities to do things for customers. We did it ourselves. The only thing is, we have a separate team for the Microsoft product installations. Especially for something like Microsoft Intune, we need to have a special expertise. Something called Microsoft Windows, virtual desktops, all of that needs someone to install it who is intimate with the application. Microsoft Azure is something that can be used for different Microsoft technologies and solutions. We have a different team that we will put on the implementation of these products depending on the requirements.  

The pricing for Microsoft Intune is reasonable. Our clients are satisfied.  

If someone is looking to have a more integrated result, they are looking for many other things like EDR (Enhanced Data Detection and Response). It is probably better to go with Workspace One because they have that under one banner. Obviously, if there is something under one banner, the integrations are simple, they are seamless, and they complement each other.  

I do not think I will have a good answer for what advice to give because technically I have not used Intune myself for some time now. I have a team that works under me for this. I am at an architect-level position now. My perspective reflects that.   

On a scale from one to ten (where one is the worst and ten is the best), I would rate Intune as an eight at least if you are only talking about a UEM solution. Personally, I am not very concerned about the reporting part, so I will consider it at eight. But if someone is looking for extensive reporting detail that is easy to understand. Interactive reporting that will give them better-tuned results, then obviously the rating might go down.  

The only thing which I see that can be done to raise this product from an eight is to package Intune as a product under one umbrella. If that were to happen, it covers the whole of end-user computing and security solutions.  

At the moment, these are two separate things when using Intune. There may be another way to accomplish this under the one umbrella if you go with Intune. For example, if there is an add-on within Intune to leverage containerized security, auto containment, and all those things. This would be a more flexible solution if that were the case. At the moment, Intune is not required to be installed as a client. As a client in the system, it can communicate with servers and do some auto containments, endpoint detection, and response. If there was a separate solution that could be added as a paid solution to create the umbrella, you have created both solutions simultaneously.  

The main reason this problem came into the picture was because of this COVID pandemic. IT teams and security teams do not go well together normally. There has to be one solution which can offer both. It can be for both IT architects, IT technical support, and security support. That is the solution that can be leveraged for both security and end-user computing. It is simple.  

We primarily use the solution for remote workforce systems that are not connected to the VPN, to flexibility deploy software, and operate system upgrades and policies, as well as pushing scripts to the devices. Pretty much just about anything that we can do in Intune, we're going to be doing. If we're not doing it already, we will be doing it.

Right now, pushing out software and policies is the solution's most valuable aspect.

The pricing and support are great. 

The dashboards, the security, and the customization capabilities work very well for us.

Everything is so tightly integrated with the on-premise solution. 

In terms of what is missing on the solution, I can't really think of anything right off the top of my head. It's doing everything we need it to do.

It would be helpful if there was proactive remediation.

In terms of some of the reporting, I find that it takes too long for some of the reports to display actual data.

We started in February using Intune on an actual production project. We had used it on a very limited basis as a testing bed several years ago, however, it wasn't a mature product back then.

The stability is great. We haven't had any issues in that regard. We don't have bugs or glitches. It doesn't freeze. It's reliable.

The scalability is very good. If you need to expand the solution, you can.

It's a management system, so every single endpoint across the enterprise has Intune connectivity. I would say 100% of our users are basically on it. We're managing all of our internal resources through Intune and the on-premise solution configuration manager. We've got upwards of 8,000 employees currently.

The support has been excellent. We're quite satisfied with the level of service provided.

The initial setup is not complex. It's relatively straightforward.

Deployment was basically a three-day engagement.

We had some assistance from Microsoft. A Microsoft engineer came on-site to assist us over the course of the deployment.

We're not paying for Intune due to the integration with Configuration Manager. If you own Configuration Manager, you own Intune and vice versa. If you own Intune, you own Configuration Manager or the on-premise solution. As far as how much Configuration Manager costs, I'm not exactly sure. We set that up a long time ago and I just do not recall the cost on that.

Our company does not have a business relationship with the vendor. We're simply customers.

We're using the very latest version of the solution. We're using it with Microsoft Endpoint Configuration Manager, and we're running a 2006 build. With Intune, since it's the SaaS model, it's whatever version is available in the cloud.

My advice to other organizations considering the solution would be to be patient. Some of the reporting, for example, takes up to 24 hours before it is actually displayed in the console, depending on a number of endpoints you're trying to manage. 

The other recommendation would be is be prepared to switch your way of thinking around deploying policies through Intune. The policies in Intune are similar to GPOs, but there is a difference. There is a very, very distinct difference between those policies and the equivalent of the policy and the configuration as a baseline. They're similar in nature, but they're very different. You have to kind-of switch your method of thinking.

I would say I'm very, very pleased with the solution. Even with the delayed reporting, I would give it probably a solid nine out of ten.