Microsoft Intune Reviews

We switched to Office 365 applications and we already had an Office 365 license that covers Microsoft Intune. We decided to use Intune for our Mobile Application Management solution.

I only use Microsoft Intune for Mobile Application Management for the management of Office 365 apps. Additionally, we have Microsoft Intune integrated with Workspace ONE.

We have used conditional access policies to prevent users from copying internal resources or internal data to external devices. This has helped protect our organizations from being compromised.

The conditional access policies that we set up are very useful.

Microsoft Intune could improve by being more user-friendly and having it geared toward device management. The graphic interface is not very good.

The VPN option within Intune is not as intuitive as the one available in Workspace ONE. We're trying to implement a VPN tunnel for SharePoint sites. This will allow users trying to access internal resources, such as SharePoint, and other Office 365 data, but it doesn't work as well as Workspace ONE. 

We are in the POC stage of the VPN tunnel. We only have a development tenant for the tunnel. We plan is to implement that in production and get rid of Workspace ONE, if it meets our needs.

I have used Microsoft Intune within the past 12 months.

The solution is stable.

I have found Microsoft Intune to be scalable.

We have over 5,500 users using this solution.

The technical support from Microsoft could improve, it is not as good as the Workspace ONE support. It is difficult to contact Microsoft support.

I have used Workspace ONE, and I would highly recommend it over Microsoft Intune.

The initial setup was complex, and the full deployment took us one year.

We did the deployment ourselves. There is little maintenance required, we have to only update policies. We have a mobility architect that set up most of the backend and we did work with a Microsoft resource for this process.

I have received a return on investment, the solution is inexpensive.

There is a license required to use this solution. However, it was part of a bundle package. 

Microsoft Intune is far less expensive than other solutions, such as Workspace ONE.

We are only using Microsoft Intune because it came with our Office 365 license.

I rate Microsoft Intune a five out of ten.

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.

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.

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.

The solution has a holistic approach. The device management, application management, identity management, and cybersecurity features are valuable. It brings all of the endpoint and security management tools into one place. It provides complete integration with Microsoft products. It provides full endpoint visibility and IT controls across device platforms.

It makes the security measurements easier to maintain. The user experience is sufficiently good. It helps secure hybrid work and protect data. The tool provides an add-on that integrates artificial intelligence and Microsoft Graph. It is a good development. The product has affected IT productivity in our organization.

It's a good platform for management and security for all kinds of devices. There is less trouble for the users so they can do more. For the IT team, the product provides a guarantee of security. The solution has reduced the risk of security breaches by 30%. It has helped us save on direct and indirect costs. We are a global organization. We need fewer resources and are more secure due to the solution. There are much less incidents based on security.

The tool helps consolidate vendors. There is much more functionality that we can leverage. It has positively affected the security posture of the organization and licensing costs. The capabilities of Intune that are integrated with Microsoft 365 and Microsoft Security are very important. I work in environments that are completely Microsoft-dominated. The more we use Microsoft, the better the integration. It is easier to connect the different parts. I am satisfied with the product’s performance.

The add-ons must be integrated into the solution. They should not be separate add-ons. The add-ons have artificial intelligence and must be part of the base product.

I have been using the solution for very long.

I am satisfied with the product’s scalability.

The technical support is quite reasonable.

Neutral

The pricing is competitive, but it is not cheap. All the licenses are not cheap nowadays.

I have used AirWatch in my previous organization. The integration provided by Microsoft Intune is its biggest advantage over its competitors. Most of the integration with third-party tools is good.

I'm familiar with Microsoft Intune from the beginning. I have heard that the solution’s Tunnel for MAM feature enables users to use their private phones to make a secure connection to the company's network to access company resources. I haven’t used it yet. We are partners and customers. Overall, I rate the solution a nine out of ten.

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. 

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.

When using Microsoft Intune our main focus was on Office 365. Our Azure Active Directory was only held up for users. When we had implemented the endpoint user management in our workstations in a cloud environment, then we started to use Microsoft Intune on an everyday basis, such as remote connection, deploying workstations, Autopilot, and deploying applications. It is a great tool.

Microsoft Intune is a cloud solution. For an on-premise solution, you have SCCM from Microsoft. However, it is old and it will be an obsolete tool soon. There are other solutions such as ManageEngine. Microsoft Intune tool is in the cloud and we can manage everything. You can manage Azure AD, Intune, and not only mobile hand devices, such as iOS or Android, the main focus is on workstations. This is what makes the solution powerful.

I expect Microsoft Intune to have more features in the cloud because there are two major functionalities that we need to be added. This is software metering and license management. These functionalities, for now, must be on-premise. For this purpose, we have set up a SQL Server and I hope that in near future this option will be in the cloud in Microsoft Intune.

I have been using Microsoft Intune for approximately two years.

The stability of Microsoft Intune is great.

Microsoft Intune is highly scalable. When you configure your network connection, there are a lot of firewalls and you can optimize your internet speed. Everything works great. You can tune up some repository sizes with Microsoft because if you have large applications, such as AutoCAD, when you upload the images to the cloud it takes some time and it needs more space.

We had four people in my company that used Microsoft Intune on approximately 100 systems.

The technical support of Microsoft Intune is good.

I previously used BEAM for client management from an American company and SCCM from Microsoft. Additionally, I used ManageEngine and Lansweeper. Lansweeper was a light tool with similar functionality. We use it in combination with TeamViewer.

We have projects all over the world. It took us four months to implement Intune Microsoft Intune for approximately 100 clients in three countries. We implemented it in many locations, such as Germany in three cities, Croatia, and Bosnia, there is a total of 50 locations. Microsoft Intune is easy to work with.

The initial setup is not simple, you need a specialist to be involved that has the appropriate experience. This is not a solution where out of the box you run the executable file on your system and hit next, next, to finish the installation.

Microsoft Intune requires specialists to implement the solution. We used an external team of two engineer specialists that was dedicated to the project. I helped too because I have experience in plant management.

There is a license required to use the solution. If you're core users in Office 365, for example, you have Outlook email and E3 license, this is only email. You have to buy an EMS license to have Microsoft Intune. It is expensive.

I would recommend the solution to others.

I rate Microsoft Intune a nine out of ten.