Microsoft Intune Reviews

The solution is deployed on cloud.

Autopilot is a great feature. Most users are looking for zero-touch deployment. 

There are many things that could be improved in Microsoft. Reporting and troubleshooting for the application deployment could be better. It's very difficult to understand. 

It's also very difficult to monitor where exactly the error is and the kind of scripting we're trying to deploy. PowerShell scripting is even getting a delay compared to other applications or policies. Usually if we deploy the configuration profile, there is an immediate sync and it will be applied to the devices, but it's not happening on PowerShell. This is an apparent option for PowerShell that is not working properly, so that again needs to be rectified. The reporting is a major drawback in Microsoft in Intune. They're not properly reported on the console.

I have about seven years of experience with Microsoft. I have been working with Intune for the past four years.

The solution is stable, but the reporting steps could be improved. The product has been released for more than six years, but some complete information is required.

The solution is scalable.

Technical support is very active. We used to interact mostly with Microsoft, so we had a lot of issues from the Intune side, so we were often troubleshooting steps. The technical side is pretty good. Whenever it's required, they will immediately schedule a call. I would give them a 9 out of 10.

Initial setup is of average difficulty. It requires a lot of people. We need to have an Azure AD license, so some AD integration is required. A kind of firewall is included.

In Jamf, it's not like that, so we have a single console and we can implement it. But here, we have multiple because it can be integrated and co-managed. I can't say it is very easy to deploy. For very small-scale industries, then it's definitely easy if you have minimal user devices or user IDs. If you're looking to deploy the solution on a corporate-level, and if they have multiple tenants, in that case, it is definitely complex.

If you are looking for it to be co-managed, there'll be an SCCM and an AD team. Otherwise, one or two engineers is fine for Itune.

I would rate this solution 7 out of 10. 

If you are working as a SME, anybody can do the major part of troubleshooting and configuration. Even someone who isn't certified will be able to do the configuration and implementation part. Logs are required to troubleshoot.

Intune is the best tool going forward because everyone is moving to the cloud. If you have a cloud environment, it will be easy for a service provider to provide support. The solution can also be easily integrated to other tools.

There are so many additional features included in Intune that it's very easy for the users, corporate, and for companies to manage the devices. Even if the device is out of office, even if it is not domain-joined, it will be easy for us to manage for the client, or for the companies to manage it.

We use it to manage our mobile phone in the business, and we also use it to manage our Windows PCs.

It's managed through our IT company, so they have the latest version. I have admin access to it, but I haven't had time to be in the portal so much.

We have one person based abroad, and it was a lot easier to get him standardized than it would be if we had to get his computer shipped down and configured that way.

For our office workers who are not based in Norway, when we order the PC, we can do some of the settings for them. These are standardized settings. We can set them up exactly as they are in Norway so that they're the same. 

The reports that are generated aren't so great. They don't give a lot of meaning so far, but that could be down to user knowledge than the actual reporting side of things. I'm not a big user of it, but I was a bigger user of MaaS360, and we used to be able to run weekly and monthly reports. In the case of any deviations. we'd get a warning immediately. That's not so easy to do or to get in place for Intune. This could be just a user issue, but when I compare both, that's the only thing that's lacking for me.

I have probably been using it for eight months.

So far, we have had no issue. We only have an installer for one user abroad, and he hasn't had any issues. It is stable there, and the phones also work fine. 

It is scalable. We can add more users, and there are no extra costs.

We're probably not the best users of it. We have one person based abroad, and we are probably going to have more.

We go to our own IT support, and they contact them. I'm not familiar with the deal that they have. They're a big IT team over here. They probably have an agreement, and they're prioritized in the queue for Microsoft Intune. There has been no downtime, and we haven't had any issues so far.

We've switched over from MaaS360 to Intune. We took the decision that Intune is better for Windows and IBM products.

I personally preferred IBM. I always outsourced the IT, but I preferred IBM. I liked the interface with IBM. I like being able to push out and seeing which updates were not available and which ones had to be pushed out. It was a lot easier to use. So, I preferred IBM, but I'm not really using Intune. It's outsourced to our IT.

It was quite extensive, and it took a few days for them to set it up.

We have outsourced IT for it. They did it themselves.

It's monthly for us, but it's built into the license cost that we pay our IT each month. It's maybe 129 Kroner per head, which translates to £10.

There are some additional costs. Our IT had to set up and configure their own server, so there is an extra cost for that, but I'm not sure what that costs.

I would advise setting aside the relevant time because it is time-consuming. It probably needs to map to all your devices so that you have a proper overview of all different applications that are needed on PC and mobile. I wasn't really involved in the migration. So, I only know what they needed, and from their side of things, I had to gather the information based on our MaaS360 database.

I would rate it a seven out of 10.

Basically, the Intune solution is to provide services for MDM and mobile application management. In addition, support or ticket to control Windows 10 devices is provided.

We provide this solution to our clients.

More integration with monitoring tools is needed.

I have worked as a solution architect for Microsoft Intune, for the past six or seven years, and when you consider my overall experience, it is more than two decades.

On-premises is not absolute. You can integrate co-management, but you must first integrate with, ACCM. We are currently providing both solutions.

This is a stable solution. The performance of Microsoft Intune is good.

Microsoft Intune can be scalable.

As a solution architect, I have more than 50 customers.

I have not reached out to Microsoft's technical support. So far, we have not had to.

I am also familiar with CyberArk.

Intune is essentially a SaaS solution. Although Intune is a SaaS solution, it can be integrated with the ACCM. You can integrate a co-management solution in two modes, or you can integrate only the cloud. As a result, the cloud is mostly used by small and medium-sized businesses. However, for enterprise customers, we must use co-management, the team, the ACCM, and Intune.

Maintenance isn't that based on the volume. For example, if you want to go with 500 devices, you need to size the people accordingly. If you want to implement 5,000, 10,000, one lakh, or one million people, you must size the people accordingly. As a starting baseline, we need to assign one person to manage every 5,000 devices.

Every customer used to purchase licenses based on their needs. 

They used to buy a license as part of a package, possibly on a yearly basis, but they never went for pay-as-you-go, but they used to buy for a year, three years, or something like that.

Intune is the best, in my opinion. CyberArk is primarily used for identity purposes. For example, if you want to protect your password, enable local administration, or enable the lapse solution, CyberArk was the best tool at the time. However, if you want to manage your mobile devices as well as your Windows 10 devices, Intune is the best option.

Both goals are completely different. If you want to manage and control your devices, Intune is the best option.

I work with Microsoft technology. I always strongly recommend Intune.

I would rate Microsoft Intune a ten out of ten.

We use Microsoft Intune for match management for the more than 1,000 computers we have in our organization.

Before using Microsoft Intune we were having trouble when people were not coming to the office and they were working from remote locations. We did not have any control over their devices. Since the introduction of Microsoft Intune, we have had the problem completely taken care of. 

Right after we started using Microsoft Intune we were stuck with this pandemic of COVID-19, and 100% of the users were working from home. It was a good thing we started using it at that time, we were able to do the patch management even though 100% of the workforce were sitting at home.

We have a lot of on-premise server policies which we were struggling with because users get authenticated on the company network, but some elements would not take effect. However, with the implementation of Microsoft Intune, we do not have that problem anymore because the user only needs to be connected to the internet. They will get all the policies that we configure on a global scale.

These are the main areas that have changed the way we do administration tasks on the devices. Additionally, we have control over the applications, such as Mobile Application Management (MAM), we can control how the user can share the company data which we did not before. They could previously install a certain email application on their phone and then they could share it with anyone, but now we have the control; we can restrict it and we can even restrict the applications that they can use. We can stop them from sharing things on WhatsApp. We can only apply limits to the Microsoft platforms, such as Teams and Outlook.

The solution is easy to use.

The solution could improve its flexibility.

I have been using Microsoft Intune for one year.

Microsoft Intune is stable.

The solution is scalable.

We have approximately 1,200 users using the solution and for the operators or managers using the solution, we have approximately 15.

The support is satisfactory.

I have used ManageEngine Desktop Central and SCCM. When comparing SCCM to Microsoft Intune, when we used SCCM we had more control and visibility on what we deployed. There are certain cases where you do not want to deploy something. For example, there are security updates or quality updates that could have bugs or glitches that you see around the world. Another example is, every second Tuesday Microsoft patches will be released and you hear that some of them can have bugs or glitches, we can take them off the list and not proceed with that particular patch. This was possible in SCCM because you can select whatever patch you want before deployment. However, in Microsoft Intune that is not possible because Microsoft releases it across the world as one data piece. You do not have control over whether to select it or not, we have to accept it.

ManageEngine Desktop Central is very similar to SCCM, you can select what updates or patches you want. If you do not want one patch you do not have to select it. 

We migrated all the services to Microsoft platform cloud architecture. We went with Intune for the patch management, but we do have ManageEngine Desktop Central, which is capable of doing patch management.

The installation of Microsoft Intune was not difficult, it was smooth. Once it was set up it was up and running, we only had to configure the policies. Integrating was easy with Active Directory.

I did the implementation of the solution myself. We have a team of four to five that do the deployment of the solution.

There is a license needed to use the solution and we are on an annual license.

I would recommend this solution to others.

I rate Microsoft Intune an eight out of ten.

We use Microsoft Intune to manage mobile devices or tablets, or Windows devices from anywhere. Intune is the best solution through which we can completely manage mobile devices and Windows devices. There are two options for that. We can manage or directly control the whole mobile device and provide security at the application level—for example, MDM and MAM.

I like that it's very good and very simple. I found that we just needed to have a proper subscription for an Intune tenant, and from the subscription, if we have the right role assigned, like the global admin role or the owner role, we can use Microsoft cloud resources. With the help of that, we can do many things like setting up Microsoft Intune in the cloud to create our virtual machines. All these can be done, and the steps are very simple. I really liked it.

I like features like Windows Auto-Enrollment. I like it very much because whenever you supply it to the end-user, it will be ready to use immediately. The end-user only needs to provide the user credentials, and then they are good to go. I also really like Cloud PC, which was recently launched on Azure.

The documentation about the custom image setup could be better. Although Microsoft provides the steps to configure Intune or set up or deploy Intune, it doesn't have much information related to custom images. 

If you ask, "how can we deploy the custom image?" There is no information. The steps they mention ask you to connect to your on-premises environment or create your own image on the cloud itself once there is connectivity. But I needed to go to multiple websites to get all this information. I had to figure out how to upload the custom image if you want to use the on-premise custom image for Cloud PC. If you have the proper subscription, you must have the right access, like global admin or owner. Then you can add your custom image to that. There are no steps mentioned over there.

Microsoft Intune doesn't have Chrome browser support. I would like to have that support because they will want it if we pitch the product to clients.

I have been working with Microsoft Intune for over four years.

It's definitely a reliable solution. They are also providing real-time security, and that's very good.

It's easy to scale up, and that's one of the major highlights of this particular product.

The initial setup is straightforward. To set it all up, we need to connect to the OEM and then provide all the hash information and more. Everything should be pre-configured on the laptop, and then the user is good to go.

We implemented this solution. Maintenance completely depends on us. It depends on what service we want. We have to decide if we want to manage it on our own or whether Microsoft should manage everything. We can decide that. We can deploy applications through the management console. If you don't want to take care of its backend, everything can be managed through Microsoft. That's very good, and I think it's very simple.

They have categorized the licenses according to the size of the business. So, if it's a smaller organization, we can choose the license accordingly. If it's a big organization, then we can choose accordingly. Everything is clearly mentioned, and we can decide. It's suitable for all kinds of infrastructure, and that's very good.

I would tell potential users that Intune is a very good product and everything is cloud-based. If you want, you can use it as a pay-as-a-service. That is also very good, and it provides a very simple unified platform to manage everything from the single management console. It also provides a report for many things like how many end-users are using it and what applications they are using. We get a very good report, and we can manage it very well. 

Along with mobile device management, you can also use it for Windows management. Microsoft has combined Microsoft Endpoint Manager, Microsoft Configuration Manager, and Microsoft Intune into a single console. 

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

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.  

The primary use case is managing mobile devices and applications. It really answers the question of managing BYOD end-point devices.

The benefit is the way it integrates with the entire Microsoft ecosystem. If you're a company that has a bit of this, a bit of that, and a bit of everything else, then Intune probably doesn't hold up so well. But if you say, "We're going down the path of Microsoft's strategy, we believe in what Microsoft is doing as a cloud provider," then Intune, as far as security and managing end-point devices and managing everything, brings in the story quite nicely.

When a customer asks me about the most valuable features, one is that Intune itself integrates with that entire Microsoft ecosystem. As an individual product, it's okay. It holds up. But when you start saying "I've bought this as part of a wider solution, as a company we are going Microsoft throughout," then it makes more sense to have Microsoft Intune, because it plugs into Azure AD Premium, it plugs into Information Rights Management, it plugs into Windows Defender, so you have that single dashboard. It also has an integration with System Center which means again, from a single pane of glass, I can manage everything.

I believe they've just released a Mac OS support so that's great. And it has its own sandboxing.

I would like to see micro VPN. I like the way that some of the other providers have done something similar where, as you open that app on an end-point device, it creates a micro VPN straight into your device, which is quite a nice little feature. 

Also, Microsoft Intune relies heavily on its fellow products in the suite. It would be nice if Microsoft Intune could stand on its own two feet.

The stability is better than it was. It's brilliant. It's a lot better than it was about three or four years ago. Four years ago, you wouldn't even have considered it as an MDM solution. Now, it's in the top-right quadrant.

The scalability is there. Microsoft has always said it's for SMB, public sector, and enterprise users. It needs to be there because, if you look at some of the bigger organizations using Office 365 and Microsoft 365, it's got the scalability.

My advice would hinge on what your strategy is. It comes down to: If you're using Citrix then Citrix ZenMobile makes more sense. But if you've got a Microsoft strategy and you're looking at Microsoft security and you're looking at buying into the Microsoft cloud strategy, then Windows Intune is a very viable solution.

For me, the most important criteria when selecting a vendor depend on what is it I'm trying to achieve. I always want to check:

• where it ranks in industry reviews
• for the features that I'm looking for
• pricing.

For example, I may have a product that's brilliant and is amazing and does 120 things, but costs $10 per month; if I only need two of those features and I've got another product that has only those two features and it only costs $2 per month, I'd rather go for that.

I would rate Intune at about a nine out of 10 because it has come a long way, it is continuing to be developed, and I can see it as part of Microsoft's wider vision. It's not 100 percent there but it's getting there. The fact that you can now plug Intune into third-party products is fantastic.

We are moving from our parent company's tenants to our own, using the product to manage devices. 

I like the tool's integration with Apple. Anyone who creates an ID in Intune will get an Apple ID. 

The product needs to upgrade itself when the server is overloaded.

I have been using the product for a month. 

The product is very scalable. 

We have weekly calls with the Microsoft team, who are very attentive. 

Our parent company makes the deployment process very complex by using non-Microsoft tools. 

We rely on a vendor team to complete the deployment. 

The product is easier to manage and integrates with our ecosystem. It has made our organizational security posture simple. We can leverage the security policies in Azure and create our policies in MDM. I rate it a ten out of ten.