Microsoft Intune Reviews

Mobile device management is the main thing for which we are using it. My role is to review the implementation.

Mobile device management is most valuable.

We only have major classifications for iOS and Android, but there are different brands that have different cycles of updates. If they can fine-tune it to make it more brand-specific, that would be even better.

I've been using this solution for three and a half years.

It's stable. I'd rate it an eight out of ten in terms of stability.

It's very scalable. I'd rate it a ten out of ten in terms of scalability.

It was deployed for an environment with multiple locations. There are about 500 end users. Our clients are mostly small-sized organizations.

I'd rate the previous vendor with which we had the contract a ten out of ten. We now have a new vendor. They haven't yet started.

We used BlackBerry. We switched because that was getting outdated, and it didn't have all the features that Intune has. Intune is continuously being improved because of the cloud service.

I reviewed its implementation. It was straightforward. There were some technical difficulties in getting it started, but after we resolved them, it was easy. There were some architectural issues we had to resolve because we had legacy architecture.

It was a consultancy service that was provided by us. There were about five people involved. One was a specialist; one was an architect. There were two different engineers having different specialties, and there was a project manager.

We have an engineer who works on the maintenance. There is a team of two engineers to manage Intune as well as Office 365.

There were quite a few, but this was the main solution that we looked at because Microsoft solutions integrate well with other Microsoft solutions.

I'd advise getting rid of legacy stuff. You need to go to the new architecture and new OS. The infrastructure should be matching for the Intune implementation. Otherwise, you will have a problem. That's what we faced. We had to upgrade all our operating systems.

Overall, I'd rate Intune an eight out of ten.

We use Intune for device management to ensure mobile devices such as laptops and tablets comply with our organization's regulations and requirements. We have some on-prem resources and operate a hybrid, primarily cloud-based environment.

We have seen many benefits from using Intune, especially in security. We have fewer company data leaked to the public as our security is tighter, and our company network is safer.

The ability to wipe data from and reset devices is one of the most important and valuable features. If a device is reported stolen, we can freeze it or wipe the data from it, preventing data leakage.

The solution offers excellent visibility into all devices connected to the network and whether they are safe or compromised.

There are some issues using the solution with macOS and iOS, and it offers limited granular control with them. Intune works better on Windows and Android. 

I've used the solution for two to three years as an end user and an IT admin.

Intune is very stable. 

The solution's scalability is excellent, though it could be improved regarding macOS and iOS.

We've reached out to Microsoft technical support many times, and they have always helped resolve our issues promptly and efficiently; I rate them ten out of ten.

Positive

We previously used Microsoft System Center Configuration Manager (SCCM) for group and on-prem policies, which we also pushed out to devices. We switched because Intune is more modern and cloud-based, so it fits our organization better.

As an IT admin, I was involved in the deployment of Intune as a consultant. The implementation was very straightforward as we're an experienced team of security professionals consisting of two IT admins and an IT manager. There was also a test environment for our benefit, and moving that over to a production environment was seamless.

We carried out the implementation internally. 

We definitely have an ROI with Intune, and the benefits are compounding. Security is a non-negotiable area; our business has to be secure, and our sensitive company data has to be protected from malicious actors. The security of company resources is always an ROI for the business, so it's essential.

The product is relatively pricey, but considering its benefits, I'd say it's fair. The benefits outweigh the expensive licensing fees, especially for large organizations, but medium-sized and smaller businesses may be unable to afford it.

We didn't consider other options; we wanted a Microsoft product, as it's great to add to our existing suite of business applications, and the integration is more seamless than it would be with third-party products.

I rate the solution ten out of ten. 

We implemented the solution to solve security concerns; users access our company resources from outside the network, and we must ensure the devices they connect from are safe. As an admin, I have complete visibility into devices connecting from outside and can ensure they are safe and secure.

My advice to those considering the solution is to be aware of its capabilities, limitations, and their business needs. These factors will allow you to determine if Intune is the best device management tool for you. Depending on the environment, you may have to combine Intune with an older technology to manage all company devices.

Intune provides a platform for managing all our devices, including mobile iOS devices and PC workstations. It can also control some aspects of servers.

We can automatically enroll our devices with Intune. It helps us implement company-wide policies and ensure regulatory compliance because we can restrict how company devices are used. Intune improves security by enabling us to set conditional access policies for each device. 

Intune can wipe devices. For example, if a disgruntled employee wants to leak the data on their company phone, Intune can terminate their access and wipe the entire device with a click. Conditional access is another essential feature. 

You can set up two profiles on every device to keep personal data separate from company data, and the employee cannot copy data between them. This is a critical requirement for most companies to avoid the loss of sensitive data.  

Intune doesn't provide much control over Windows servers. It's something we struggle with.

I have worked with Intune for six years.

Intune is mostly stable. Microsoft guarantees 97 percent availability throughout the year, so it's pretty stable. 

Intune is scalable. 

I have used multiple endpoint management solutions in the past nine years. I also work with Jamf, a solution that focuses on iOS devices. Compared to Jamf, Intune also has some limitations when working with iOS. For example, Jamf can create specific policies for each iOS device, whereas Intune can't go that far. It also has role-based and device-based features. You can do more customization on iOS devices with Jamf. 

The initial installation isn't too difficult, but it can be complex if you have a large number of devices and need to do lots of customization. It is more complicated to onboard Windows PCs versus mobile devices, which are pretty easy.

The number of staff members required also varies according to the job and the timeline for deployment. For example, I would probably need additional resources if I'm enrolling 20,000 devices in under a month. However, we don't need too many resources if we have enough time

Intune is a cloud-based solution, so Microsoft is responsible for maintaining the infrastructure. We only need to handle the administrative and configuration adjustments on our side. 

Most clients get the ROI they expect, with the exception of those organizations that primarily use Mac and iOS. Jamf is more appropriate for iOS users. You may need to buy two solutions if you have a mixture.

Intune is reasonably priced. When we design a solution, we always compare costs for the client, but I don't know the price of Intune off the top of my head right now. It varies depending on the size of your organization, the market, and the reseller. You can buy a stand-alone license for Intune, or it may be included in a 365 license. 

I rate Microsoft Intune nine out of 10. 

Before implementing Intune or any endpoint management solution, I recommend looking at your internal requirements. Are most of your devices iOS or Android? Do you need automated enrollment? Go for Intune if you're using mostly Android mobile devices and Windows PCs.

I use Intune to manage all the organization's PCs.

We use a local Active Directory, but we weren't able to manage all our on-site systems without a solution like Intune, and we needed to deploy software like VPNs and other things. It's seamless now to do this through Intune.

The reporting is subpar. That's the only issue we have with Intune. We use another solution for that purpose. 

I have used Intune for about two years.

Intune is stable. 

Intune is scalable.

We purchased our licenses locally. We contact the reseller when we have support issues, and they contact Microsoft support. We've only needed to contact them once or twice. 

Deploying Intune isn't easy, but it isn't too complicated. Someone with two or three years of experience can do it. I completed the initial installation quickly, but migration took a long time because it's a manual process. We deployed Intune in-house with only two people. 

After deployment, Intune doesn't require any maintenance. It's a cloud solution, so Microsoft is responsible for maintaining it. However, we need to handle any tenant-level configuration.

Intune has somewhat of a monopoly. There aren't many alternatives for this kind of solution, so we have to pay what they're asking. Still, I think it's reasonable. 

We are primarily using Microsoft products, so our options were Google Cloud or Intune. We decided that it was better to go with Intune because the learning curve would be steeper with Google. 

I rate Microsoft Intune eight out of 10. We have never faced any serious issues with Intune. My advice to future users is to plan before you deploy or migrate. 

It's usually used for managing mobile devices, such as Android and iOS, for application deployment, for securing the device landscape, and for making sure all devices are compliant.

Help Desk engineers don't need to spend a lot of time enrolling new devices. In the past, you had to do that by using a complete infrastructure on-premise, or if you wanted to do it by hand, you had to go through every device. You had to install Windows, configure it to set security, etc. Intune does that automatically for you. It saves a lot of time.

There are so many features, but Windows Autopilot is one of the features that are very valuable for most customers. Personally, I like most of the aspects of Intune. I've been working with it for about 10 years. I'm a Microsoft MPP for the Modern Workplace. I like a lot of features. There's no one particular part of Intune that is the best for me. It has developed into a very mature product. About 10 years ago, it wasn't a very good product, but now, Intune is a very good mobile device management platform.

There should be more support for macOS. Even though macOS is supported by Intune and Microsoft is working very hard to get more features into Intune to manage macOS, that's one thing they can give a lot more attention to.

I've been using Microsoft Intune for about 10 years.

It's stable. There are issues once in a while, but they are not worth mentioning.

It's very scalable. It's deployed across multiple endpoints. My customers vary, but there are between 50 and 15,000 endpoints.

I do have experience with Microsoft technical support, and I'm happy with it. I'd rate their support an eight out of ten.

Positive

I've migrated from other platforms to Microsoft Intune, but I've not used any other similar solution.

It's a cloud solution. The cloud depends on the customer, but Microsoft Intune is a cloud solution serviced by Microsoft. My customers have various cloud environments. It could be a hybrid, public cloud, or private cloud. It depends on the customer.

It's quite straightforward to deploy it, but configuring it and doing it right is something else. The deployment duration varies. Some customers have 100 devices and others have 10,000. It depends on the landscape of a customer. Even though nothing changes technically, it's more difficult to move large enterprise organizations to a mobile device management platform.

The number of people required depends on the qualifications of the person who is deploying Intune. Intune can be deployed by one person. 

Its maintenance depends on the company. If you have a very big landscape with tens of thousands of devices, you want to have more engineers monitoring Intune and configuring. If it's a smaller environment, you can manage it with one or two people.

The ROI has been in terms of time savings.

It's affordable. In comparison to the competitors, the price depends on what features you need from Intune, but it's affordable. There are no hidden costs, but there are some features that go for a premium price. Those are the add-ons for which you have to pay extra.

I did have a look at other options, but I'm a Microsoft specialist, so it's a Microsoft-first sort of policy. If Microsoft can do it, I'll do it with a Microsoft product.

Get yourself well-informed. Talk to a specialist who can help you out with deploying Microsoft Intune.

I'd rate Microsoft Intune an eight out of ten.

We are going to use Intune for registration and then we're going to use some kind of condition policies for resource access for unmanaged devices. With on-prem AD-based access, when the users are working from home or somewhere else, they need to connect to the VPN or something to access the corporate network, whereas, with Azure and Intune, we are going to provide the resources for application access. We can directly provide them access by using conditional policies.

It has been only three months since we took the Azure subscription and migrated all the users to it. We are running it in the production environment. We are not running it in the testing environment. We are not implementing everything in one go because if any issues happen, it's not easy to roll everything back in minutes. For this reason, we're implementing them one by one.

With on-premises Active Directory, the main challenge was that we had no control when a user was working from home. We didn't know what exactly a user was doing and whether the AV was up to date or not. Intune provides better control of their machines.

A few of the options are a bit hard to understand. As compared to on-prem services such as AD, it's a bit different. For example, group policy objects have different names. It takes some time to find out where various options are available.

I wanted to check if there is any provision at the Intune level to restrict certain things, such as a website, but unfortunately, that feature is available only in Microsoft Defender. Intune has web filtering capabilities, but they are only useful for protection from malicious websites, whereas we would like to be able to restrict a website. For example, YouTube is a clean website. No one would identify it as a malicious website, but if we want to stop the end-users from going to that website, we have to go for another product, such as Microsoft Defender or another third-party proxy solution. It would be great if this capability is included in Intune.

We started using it three months ago. 

Over the past three months, I haven't seen any instability from the Intune point of view.

We have approximately 220 users. We don't have any immediate plans to increase its usage, but by the middle of next year, we might increase the usage of the product to another 70 or 80 people. We would be able to scale it based on our needs.

I haven't raised any case with Microsoft support, but I believe Microsoft has different types of service agreements based upon which they provide support for different applications. 

I have gone through multiple Microsoft articles, and they have sufficient to-the-point information there. 

We were using on-premises Active Directory, and we were restricting certain things through GPO, but there were a lot of challenges when the users started to work from home. 

Its initial setup is fine. I haven't seen any issues. I have worked as a technical lead at the architect level on different products. For that reason, I haven't had many challenges.

Its implementation was a bit longer because we took our time in testing on multiple machines and multiple users. We wanted to ensure that we are able to achieve what we wanted. We completed all the use case scenarios and what we were expecting from the security point of view.

We implemented it in-house. We had two people for the setup, which included a junior person and me. 

We also take care of its maintenance. We are managing approximately 220 people. I take care of all the cybersecurity and software-related work at the corporate level. Most of the people are now coming to the office. So, we have prepared a simple document for them to follow. 

We don't have just the Intune license. We have the Enterprise Mobility + Security E3 license, but I don't have the exact figures. Someone else was involved in the initial discussions and purchase, and the entire environment was handed over to me.

Any bundle package, such as Security E3, covers multiple things, such as AAP, BitLocker, etc. If you go for them individually, they would be more expensive. Bundling makes the price more attractive and competitive.

It is suitable for small, medium, and large companies, but it also depends on your requirements, budget, and the things you want to restrict. 

I would rate it a nine out of ten.

Microsoft Endpoint Manager is simply a desktop, a laptop, a smartphone, or a tablet. An endpoint is exactly what it sounds like. Microsoft, on the other hand, makes use of that tool.

Endpoint allows you to deploy the operating system level. It enables the packaging and deployment of applications. It enables you to secure systems with BitLocker and incorporate things with Active Directory.

We are a consulting firm.

Our clients use it to simplify desktop builds and to maintain the patch management on their servers and desktops, as well as to have an easy mechanism for both rolling out BitLocker, which is a Microsoft tool and publishing new updates for their various software packages.

Microsoft is investing significantly more in the cloud. For our use and our clients' use, and again, our clients who use Endpoint number over 500, with an increase of 1,000 users. It is effective. It significantly reduces the overhead associated with providing support. It actually works quite well.

The installation could be improved to be simplified.

I have been working with Microsoft Endpoint Manager for the last 12 months.

We are Microsoft partners. 

We have been working for well over a decade with SCCM, and now with Microsoft Endpoint Manager.

They are deployed both on the cloud, and on-premises.

Microsoft Endpoint Manager is quite stable.

Microsoft's cloud has a capacity of 100,000 users. Depending on what you are dealing with, it's highly scalable, depending on how and where you deploy it.

It's from Microsoft. However, we are a Microsoft Premier partner. As a result, we are quite familiar with the product. Again, there isn't much of a need for it. However, our clients call us if they run into problems, which happens very rarely.

You do not have to maintain the Microsoft Endpoint that is built into their cloud, it's a cloud-based service. Locally, there is now maintenance every 16 months if you are deploying the local endpoint or creating a hybrid to Microsoft's cloud. You have to upgrade if you are deploying the local deployment. The current build changes every 16 months, but the upgrade is a very low skill set, you don't need anyone to upgrade it.

SCCM is no longer known as SCCM. It's known as Endpoint. Microsoft no longer recognizes that product. Endpoint refers to both the local and cloud-based installations. And, prior to their acquisition by Dell, we were a long-term partner with Quest. We've had clients use Quest products, but we haven't.

According to Microsoft, SCCM is no longer in use. Microsoft Endpoint is the new name for the current build. You can now deploy an Endpoint structure locally or pull Endpoint from Azure.

SCCM is no longer active.

I have worked with both Microsoft Endpoint Manager as well as Quest in the last 12 months. We have clients running the Quest Software.

The most recent Quest software we've seen is the Exchange PTS, or mail migration tool. That is probably the tool that we've had clients deal with twice. However, that is apples to oranges in comparison to SCCM.

It is the mail migration utility. According to my understanding, Quest recently sold that to a different company. So it's an old Quest product.

The initial setup is complex.

You have to appreciate two points with Microsoft Endpoint Manager. Microsoft Endpoint is based in Microsoft's cloud, 365 Azure. And Microsoft has simplified it quite a bit. They also work well with Intune. Many of their services are complementary to the solution. Autopilot is being sent out. You can have a machine auto-built from a remote location, or you can order an Autopilot deployment from your HP, Dell, or Lenovo. They've simplified it considerably since the old days, but there is still a technical element. For those with a technical nature, it is quite simple. Anything is simple if you understand the product.

You should probably consider cloud deployment before local deployment because Microsoft has made significant investments in the cloud. The local deployment is still in place. Microsoft's cloud comes with a lot of extra features that are free of charge. Furthermore, if you deploy it locally, you must own SQL, whereas, in the cloud, SQL is not required.

I would rate Microsoft Endpoint Manager a nine out of ten.

We use it for the rollout of Windows and Apple devices to our users.

Its direct integration with all the other products that we have from Microsoft is valuable. We're using the E5 license, and we have a whole wealth of different products available. It just makes it easier to have everything from one provider. 

One big problem with Microsoft is that they're changing the names of the products quite often, or they're quite consistently doing so. Intune is now Endpoint administration. Constantly switching the user interface or the administrative interface makes it quite hard to keep pace. If you are on a two-week holiday and you come back and look at the same screen you have looked at for the last couple of months, it looks different, which is annoying. Changing things around all the time doesn't make it easy.

There are some elements where the integration isn't finalized. So, for some of the things, you use the user interface, meaning the administrative website, and for some of the things, you have to use PowerShell to make changes, and it's not quite clear why you have to do things at one point this way and at the other point that way. If they could improve that a little bit more, it would be a good thing.

Other than that, functionality-wise, it, more or less, serves our purpose. I'm not really sure what I would wish more at the moment.

I have been using this solution for over a year.

It is stable 99% of the time. There are some problems with Microsoft in terms of outages, but overall, the solution is very stable.

It is very easy to scale. It is basically adding additional licenses. It requires adding additional domain names and things like that and maybe adjusting a couple of security groups, but other than that, it's really easy to scale up or down.

We have only 120 users in 44 companies. A few of them have financial, accounting, or legal backgrounds. We are not an engineering company; we are a service company. We are a shared service center catering to the needs of more than 44 other companies. That's our business. We are a managed service provider to all these companies.

Its documentation is quite okay, and if not, if you Google things, you would find almost everything. 

We had four, five issues over the last year, and we had to contact them. They were actually quite swift at solving problems. So, overall, we are happy.

It was easier than expected. We did the full deployment for 44 companies and about 120 users in about three months.

ROI is very high at the end. We were using a full data center before with three racks built up with about 30 host systems and 220 virtual servers that we operate in, and by just switching to Microsoft 365, we could get rid of all of them. It made our life easier in terms of support and maintenance. We have saved the costs for all the hardware that we had and all the hassle that we had when parts were broken.

If you ask the accountant or the finance department, they'll tell you that it is way too expensive, but when I look at the cost and compare it with the value you actually get, it's more than fair.

We looked at the Sophos solution as well. We are a Sophos partner, but it was easier to deal directly with the Microsoft solution primarily because of the rules management and the Microsoft groups and the security groups that we use. We use rule-based access, and we have access packages so that users can elevate their rights with an approval process in the back.

I would rate it an eight out of 10.