Microsoft Intune Reviews

Effectively, we are using Microsoft Endpoint Manager, which is a mix of Intune and CCM. I'm not sure if there's a specific category for that.

We are using it mainly for the office workers, for the regular laptops. On top of that, we got our fairly specialized devices on our factories, such as the tag down Zebra Scanners, the RealWear glasses - the augmented reality ones and the kiosks as well. Those are the main use cases.

The solution offers very good integration with broader enterprise systems.

The scaling seems to be okay.

It works well if you have a Microsoft environment.

The solution allows companies to capitalize on costs, especially if they are a Microsoft shop.

The product needs better management support, for sure, especially between non-Microsoft applications. It would be good, for example, to have some Chrome OS support.

The solution requires baselines within the web console. That's something that is missing. 

They need better delegation capabilities in the reporting.

The solution requires Mac support.

We've used the solution for about two years at this point. 

Recently, the scalability seems not to be very good. There are minor incidents appearing quite frequently. Besides that, from an overall standpoint, compared to Workspace ONE, it's much more stable.

The solution is scalable.

We have about 70,000 users on it.

We are using this solution extensively. We use it for daily routines. It's one of our core services. It's used by our end-users.

We are increasing it. We are willing to extend it in the near future.

We are not satisfied with technical support. Some improvements might be required.

We did previously use VMware. We tried mainly to reduce some costs. This product seems to come as a part of a bundle, which slightly reduces costs. Also, VMware had plenty of functionalities that were not necessarily fitting into our landscape. We were not able to capitalize on the cost of the process. They didn't have any great integrations with broader enterprise systems.

The initial setup was quite straightforward.

We do not need much staff for the maintenance of the solution. It's pretty low maintenance.

Our team handled the setup. Our internet team did it. We didn't need any integrators or consultants. 

We have a broader enterprise agreement which is set up as a four-year period.

In terms of extra costs, there may be some infrastructure costs, especially for the on-premise part of the solution.

I'm a service manager right now.  I'm a little bit within the scope of the consultant versus the advisor.

We're using the latest version of the solution.

Potential new users need to strongly assess their needs. If they are already on Microsoft stack, they shouldn't look for any other solution than that. If their daily usage or utilization or needs are varied and they have a variety of devices, not necessarily based on Windows or other standard platforms, they might consider a different solution, especially if they need Chromebook support.

I'd rate the solution at a seven out of ten.

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 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 use the solution for endpoint management, which includes security and compliance. 

We are a remote company, and the product helps us manage the global endpoints. It helps us natively manage the endpoints in the cloud from anywhere. 

Microsoft Intune's most valuable feature is Autopilot. 

We faced issues with macOS support. The product should have better inventory and asset management. 

I have been using the product for four to five years. 

Microsoft Intune is stable. 

My company has 200 users. 

Microsoft Intune's deployment is straightforward. 

We did the deployment in-house. 

I liked the tool's pricing until P2 came into effect. I am unsure about the current value versus the cost of the new licensing model. 

Microsoft Intune has improved access to devices for remote wipes. We can act quickly whenever someone leaves a company or a device gets stolen. It offers more visibility into our IT group. 

The tool's cloud-focused availability has improved the organizational security posture. It has helped to save time. We can do a lot more with a smaller team.

I rate the product a nine out of ten.  

We primarily use Microsoft Intune for device management and application management. It allows us to control and restrict user access, preventing data sharing and leakage. 

Additionally, we utilize it for endpoint management of Windows and Mac devices, ensuring their security and compliance.

The benefits include that it's very easy to deploy and integrate. Users actually feel satisfied and have a great experience with it.

The most valuable includes managing everything from a single console.

Integration with Mac devices requires some improvement.

I have been working with Microsoft Intune for eight years. I currently use the latest version.

It is a stable solution. I would rate the stability a nine out of ten. Sometimes we get some alerts from Microsoft Intune, but our team is responsible for managing that internally.

It is a scalable solution. Around 3,000 endpoints are being utilized in our organization. 

 Customer service and support are good.

Positive

We used VMware AirWatch. We switched because of the ease of use that we get from Intune. It's much simpler to work with.

The initial setup was very easy, not at all complex.

We have our own team that handles the deployment. Three to four people were included in the process. 

The deployment process was simple. We just enrolled devices and created the necessary policies, and that's it. It took approximately twenty to forty minutes, depending upon the use case.

Moreover, it is easy to create policies with Intune. It's not difficult at all to maintain. We have the same team taking care of the maintenance.

Just go with it. It's very simple to use. Overall, I would rate the solution a nine out of ten. 

We use Microsoft Intune for our internal security policy and team management. 

The synchronization of Intune with other Microsoft solutions is a valuable feature.

The reporting and cost have room for improvement.

I have been using the solution for two years.

Microsoft Intune is stable.

The technical support is good.

Positive

The initial setup is straightforward. We used our own certified people for the deployment.

The implementation was completed in-house and we implement it for our clients.

Microsoft Intune is a bit expensive compared to the competition.

I give the solution a seven out of ten.

Most of our clients prefer Microsoft Intune over other solutions because of the seamless integration with other Microsoft solutions which most organizations use.

The solution is easy to maintain. 

I suggest using the demo of Microsoft Intune before making a decision.

We use Microsoft Intune to deploy the software to Windows and iOS for the campus and to isolate any intrusion.

We can centrally control the software and the settings of the devices on the multi-platform using Microsoft Intune.

The most valuable feature of the solution is compliance. We have one MDM that works with Windows, iOS, and Android.

Microsoft Intune has a latency response time issue. The latency has room for improvement.

iOS devices have certain features that are not supported, which is not beneficial for end customers in terms of open deployment and device control.

I have been using Microsoft Intune for around three years.

Microsoft Intune remains stable if it is deployed correctly.

Microsoft Intune is scalable.

The initial setup is not complex. We started by setting up the environment on the cloud, then configured the devices and profiles. However, certain aspects of the deployment required the assistance of engineers.

The implementation was completed in-house.

I give the solution a seven out of ten.

We used Microsoft Intune because it is the only solution that can also support iOS.

In cases where a device encounters compatibility issues or technical problems preventing it from receiving the MDM profile, maintenance may be required. The maintenance is acceptable.

I recommend the solution to others.

It is used mainly for application deployment.

We are using it in our company and we also recommend it to our customers.

It has improved our organization a lot, especially because Intune is improving so much. It makes it a lot easier to deploy applications now, and there's less packaging work for us.

Among the most valuable features are the Company Portal that is built into Intune, and the update rings so that we can manage what types of future updates the devices get.

The solution could be improved by the opportunity to connect third-party application databases, such as Chocolatey or another setup store, to Intune.

I have been using Microsoft Intune for approximately four years. I have built approximately 100 tenants and I manage environments with roughly 20,000 workspaces.

The product is very stable.

It's also really scalable.

At my current job site, we have roughly 8,000 devices, which includes about 2,000 mobile devices, such as phones and tablets. They're used around the whole municipality. At that client, we are not looking to increase usage because they don't have many more workspaces, but our company is looking to get more customers and expand our usage of Intune that way.

The technical support is good, once you get somebody who knows what they're talking about. Reaching the right person is really difficult, but once you have the right person, it goes smoothly. It depends on the agent you get and which area you are connected to. If you're connected to a United States office straightaway, you will probably get better help than if you get connected to one of the locations in India.

Neutral

We also use Liquid. We are part of their development program and we helped them develop their software. We also have Liquid in the field, but that's mainly for use cases with social internet and launching applications from websites, which is a little bit more difficult using Intune.

In terms of deployment, what is difficult about Microsoft is that you need to have a broad knowledge of Azure and the other components because the endpoint manager is just a small part of your workspace. You need to have that experience and there's a lot of custom work for every single client. There isn't really an automated way, like a template base, within Microsoft, to fully deploy endpoint environments.

I help our customers with the design and deployment. Normally it includes making a list of all the applications they have within the company and seeing how much work it is for us to deploy an environment and how much application work is within it. In that way, we see which strategy fits them the best. Because there are a lot of on-premises applications that are really difficult to fit into a cloud environment, we will look to build more of a hybrid solution than a fully cloud-based solution.

We usually need three or four people for deployment.

Maintenance involves keeping up to date with the application. The only downside is that if you upload an application today, it doesn't download an update that comes out next week. That means you need to package and deploy it again.

We have most definitely seen return on investment in all of our projects. We still get a stable margin, but because of the price increases, it gets more difficult to sell it.

We don't get Intune as a separate module. Most of the time, we use it within an enterprise agreement like E3 or E5. Those licenses are at a good price, but what is annoying is that every single year they go higher. That makes it more difficult to get a company to take a full license. It will be really hard to manage, for us, if the prices keep going up every single year.

Currently, we pay €44 for an enterprise E3 license. There are no costs in addition to the standard licensing fees.

My advice would be to take your time and test what you deploy, due to the fact that sometimes a policy that you deploy with Intune can come into effect two or three days after a device is installed. Sometimes, testing for one hour is not really accurate. You need to test for a minimum of three days before you can actually see the results.

There are some improvements needed, but overall, it's a very solid product.