Its primary use case is mobile device and workstation management.
It is a platform, so there is not really a version per se.
Its primary use case is mobile device and workstation management.
It is a platform, so there is not really a version per se.
It allows our clients to have the confidence to centrally manage policies for security. It helps them in securing the organization from a technology aspect.
It is scalable, and it is fairly portable for customers, particularly for those who are already involved in the Microsoft stack.
Its configuration is fairly complicated. You have to do quite a bit of discovery to be able to deploy it for a customer. You have to ask them a lot of questions. So, its initial deployment is the biggest challenge. They should make it easier to deploy with the use of Wizards or something else. During the deployment stage, there could be profiles for the customers who are particularly wanting to use certain feature sets of Intune.
I have been using this solution over the past year and a half.
Its stability is pretty high. Once you get it deployed, it typically works pretty well. You might have the occasional snafu, but overall, it works pretty well.
There are no issues with scalability. It is cloud-based, and we've not seen any issues or limitations regarding scalability.
We have a handful of clients who use Intune. We're seeing more and more adoption. It's not widespread yet, but it's growing. We look for opportunities where this is a good fit for the customer.
We've had organizations as small as 20 to 25 users. We've had organizations with 200 to 300 users. It is used across the board.
We haven't had to use technical support, so it'd be hard to evaluate that.
There are some customers that have switched from other products, and typically, it's because they just couldn't get the other product to work. Miradore is one in particular that many of our customers had, and I like them
Its initial deployment is probably the biggest challenge. It is complex because Intune encompasses so many features and things that you can do with it, and it is so broad in scope. There are a lot of different things you can do with it, and there are a lot of different ways in which you can deploy it, which makes deploying it for a particular customer's environment complicated. It takes some time. I would rate it a three out of five in terms of the ease of setup.
We've had deployments that took weeks. We've had some simpler deployments that took days. So, it varies. The product is so big, and it encompasses so much. So, it depends on what the customer is implementing. One of our most recent customers wanted to use it for a lot of things. So, it was pretty complex. It took us time to get all the devices onboard and registered and so forth.
We might have multiple people working on a deployment, but that doesn't mean it takes that many. Overall, it doesn't take that many people to deploy it, but it typically takes a higher technical level person to deploy. You don't need a bunch of folks, but they have to really know what they're doing.
I don't have any statistics, but from a qualitative assessment, there is absolutely an ROI. Customers on Intune seem to keep it and be happy with it. It does offer significant security advantages for customers. We've seen customers really happy with the product once it is up and deployed.
Microsoft offers some licensing where it's included at no extra cost when customers are already using the licenses. In such a case, it's a really good value. If you have to buy the licensing for it, it's probably on par with other solutions. It isn't substantially more or less expensive. The great thing is that it is included in some of Microsoft's licensed packages. So, some customers don't have to spend additional money for it.
Typically, most providers that support Intune do charge a management fee of some sort or some fee. Certainly, we're no exception.
I would advise making sure that you look for vendors that have a lot of experience in deploying Intune. Make sure that you're working with an experienced vendor with a lot of experience. There is a fair amount of change and improvement in the application. It is constantly being changed and updated, so you really have to get somebody who is familiar with it.
Overall, I would rate it an eight out of 10. The challenges with deployment lower its rating a little bit.
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.
We propose Intune for information protection. We integrate Intune for application management and protection of company information on mobile devices.
It's normally able to meet 100% expectations of our customers.
Sometimes, customers compare it with AirWatch, but the concept of Intune is different from other solutions. It's an application management app. It gets a bit difficult to explain it to customers, but it's not a product limitation. It takes a presale document or presentation to explain it to customers.
I've been working with Microsoft Intune for more than five years.
It's stable.
It's scalable. Our client has 1,000 people.
I'd rate them a ten out of ten. All of the ticket questions are answered.
Normally, customers need a pilot. It takes around two or three weeks for the pilot. After that, we do the deployment. We start with a limited number of policies. Overall, it's done in three to four weeks.
We have five people in the company for implementation.
Its price is fair. It's a normal price. It isn't too expensive or too cheap.
Overall, I'd rate it an eight 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.
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.
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.
Mostly the pricing can be improved. If you are using the solution with EMS E3, then it's very expensive, but if you are using it in combination with a lot of products, then it can be cheap. Microsoft doesn't sell Intune separately. That's another consideration. The third thing would be how to view the use case because Microsoft doesn't release any documentation on how to view it when you adopt Microsoft EMS.
Their technical support could also be improved.
It is very stable.
It's scalable because this is a cloud solution only. They don't have it on-premises.
With Microsoft technical support, they only fix Teams and when they are open, they're mostly trying to close again at the quickest time. Sometimes, the solutions given are not very good.
It depends on the use case. If you only focus on Mobile Device Management, then it is very easy to setup. You just have to define the use case in the context you want to protect. If you are talking about how to integrate with the lock analytics and how to classify data in context, then this is another thing.
The main difference between Intune and Workspace ONE is the quality integration between Microsoft products and Office 365, which means that Intune is part of a solution; you are not only using Intune, but you have to think about its ecosystem. For example, with EMS, it will have at least three products. The first is Azure ID Premium, which is the IAM solution (Identity and Access Management), so there are use cases where you might need to use IAM. The one difference between EMS and Workspace ONE, since Workspace ONE doesn't focus on identity management, is that it only has the access part. It can leverage all identity management, like with the directory or any of the identity solutions.
The second difference is in the integration with Office 365 because in the Office 365 ecosystem, you have a lot of products, like Azure Information Protection, which is focused on the labeling and classifying of data. Microsoft also has Defender DLP and Defender for Endpoint. These make up a total solution. Based on that, if you have a long-term roadmap, you can actually integrate it with other Microsoft security solutions, like Sentinel, which is a SIEM solution. When choosing Intune, the main difference is the ecosystem and the roadmap.
I would rate this solution a nine out of ten.
For advice, it depends on the use case you are trying to solve here. If we have a look at the use case for security, how would you control the mobile? How would you deploy? How would you protect them based on that? The lesson depends on the answers to those questions.
It works pretty well for us.
The configuration and pricing can be improved. It would also be better to meet with people in the country and teach us how to manage personal information because we will not look at or touch any personal information. They should teach us about managing personal information and make it really easy for us.
Pricing can be improved.
On a scale from one to ten, I would give Microsoft Intune a ten.