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 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.
I work for a company as an administrator for Office 365, and I use Microsoft Intune in this capacity.
We implement this solution in conjunction with Microsoft IIS.
It is an enterprise mobility tool that is used for mobile application management and mobile device management.
This product allows us to restrict users who have access to the system, or to Office 365. We have to enroll the devices and give the users rights as directed by our management or security department.
The interface is friendly and well organized.
The security features should be improved.
I have been working with Microsoft Intune for two years.
We have more than 1,000 employees in the company, and there are about 500 users for this solution. Typically, it is used by managers and higher-ups.
We have not yet had to open a support case with Microsoft. To this point, we have solved any problems ourselves. As such, technical support has not been a concern.
We did not use another similar solution prior to Intune.
The initial setup is not complex.
The length of time required for deployment depends on the number of people in the environment. It also depends on how adopted people are with this type of technology. Six months is enough to complete a full deployment.
Some of our deployments are on-premises, whereas others are on the cloud.
Our in-house team was responsible for deployment. Based on our license, we have the option to engage with a partner but we haven't used them.
When it comes to security solutions, it is difficult to calculate the return on investment. This is because it is somewhat like car insurance, where car buyers are protected if something happens. If there are no incidents then you don't see it but you're still protected.
This cost is approximately $30 USD per user per month.
This product is included with our Microsoft 365 E3 subscription.
My advice for anybody who is looking into this product is to try it before they buy it. Microsoft offers a program that allows them to do this.
I would rate this solution a nine out of ten.
The most important part is that they're fast in implementing and integrating with the Windows operating system, as well as how it integrates with other Office 365 products.
There is no option to do end-to-end macOS management. The second thing is that the actions or policies don't get applied immediately, so there should be much faster way of implementing the policies. If you wanted to implement some actions on the device, it doesn't happen very quickly.
I'd also add more flexibility with the mobile device management part of it. At the moment, it's very limited compared to other MDM providers, so there should be more options.
I've been using it for four or five years.
Intune is quite stable.
Microsoft's technical support isn't very good. They're very slow in responding. You get a response, but the problem is if you have an issue with a feature or a critical bug, the response is very slow.
It is very easy to set up compared to other MDM products.
I would rate this solution an eight out of ten.
It is used for mobile device management. We use it for mobile phones and even PCs. We have its latest version.
Its protection policies are most valuable. It protects mobile devices as well as individual apps.
It is pretty scalable, and its documentation is also pretty good. It is also pretty straightforward to deploy.
They need to add more group policies. I know that they are already working on it, but this is something that I would like them to do quicker. Intune currently does not have many group policies that you can deploy. It is quite limited in terms of group policies. For example, if I want to disable the password manager on my browser, I can get support in Google Chrome, Internet Explorer, and Edge, but not with Firefox. It would be ideal if they can add some of these things.
Its reporting, which is very limited at the moment, also needs improvement. I can see basic information, such as how many devices are enrolled, but I can't get customized information. It will be great if they can add report customization.
Its stability needs to be improved. Sometimes, when you register a device in Intune, it doesn't show up instantly on the engine portal on the admin side. There are sync issues between the admin side and the user side.
They need to provide better support for complicated issues. They also have a long turnaround time for resolution in regards to overall escalation.
I have been using this solution for three years.
It needs improvement in terms of stability. Sometimes, when you register a device in Intune, it doesn't show up instantly on the engine portal on the admin side. There are sync issues between the admin side and the user side. It is not very stable. Sometimes, it works instantly, and sometimes, something goes wrong, and you get stuck there. It is not consistent.
It is pretty scalable because you can also integrate on-premises stuff. You can also integrate it with SCCM.
When I contact technical support, I normally find the junior engineers to be not that good. They're just good with the basic issues. If there is something complex, you have to escalate the case, but they take a lot of time to escalate it. After the escalation, they are able to fix the issue, but the overall time they take to solve an issue is too much. Sometimes, the solution is very simple, but the process of escalation takes too long.
I find it pretty straightforward, which could be because I have been working on this solution for three years. It mostly involves clicking the Next button. It will also depend on your requirements and policies, but it is generally straightforward.
Microsoft documentation is a very good place to start. They have done a great job for beginners who want to deploy Intune in their organization. They have done a good job in describing different scenarios in the documentation. I would advise starting with the documentation and doing some certification as well.
I would rate Microsoft Intune a seven out of ten.
It has a useful device management feature.
I guess they have been working a lot on the current features, but the active directory core features like group policy management are still missing. It would be better if I could integrate it with my core group policy.
I would like to have a group policy in my current environment, which has strict control, but those things are still missing. Although it has maximum compliance and security, it's not available on-premise.
Integration with other products could also be better. If I want to integrate with AirWatch, I have to do a lot of manual stuff and a lot of middleware changes. Technical support could also be better.
I have been using Microsoft Intune for the last three years.
The support is not very good. It's very poor. At least at implementation time, Microsoft should support or should have a team who can support instantly or rapidly. But the process remains the same for the support, and I have to call, and I have to wait for four to eight hours, especially if I'm migrating from AirWatch, Mobility, or some other applications.
AirWatch is a bit complicated, especially during a disaster or when something happens. Their technical support is very poor, and Intune is far better.
The initial setup is easy. We can complete the Intune implementation in one hour, but for the base configuration, we require Microsoft support. Because at the end of the day, it's a cloud product, and we don't have many resources on it.
The price is reasonable, but they should lower it a bit to make it more competitive. It's cheaper than AirWatch and other products, but I still feel like Microsoft can make a base version or with Exchange online or a la carte only Intune version which will be useful. A customer who doesn't want to go full-fledged E3 or E5 can take out or consume an Intune solution only for their purpose, and we want to target that customer.
On a scale from one to ten, I would give Microsoft Intune a nine.
Much easier installation than previous MDM solutions at 3M, including Good For Enterprise and SAP Afaria.
Conditional access has helped 3M tailor and enforce our security policies in the mobile space.
Microsoft Intune lags market leaders, such as Apperian, in its MAM capabilities.
Intune lags all of its competitors in terms of report generation.
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.
I use Intune for endpoint management. We manage our workstations via Intune because we have remote users on and off the corporate network. It's deployed across over 500 Windows workstations. We're also trying to incorporate cell phones, but we haven't reached that point as yet.
Intune reduces the load on our on-prem Active Directory by having everything go to one Intune panel. That way, we can configure group policies, deploy applications, and manage devices. It has really improved our operations. In the past, the device had to be on our corporate network, but now we can provision a device remotely.
I like the group policy management feature, which performs application monitoring and device enrollment.
It would be nice to have a location tracker for the mobile device management tool. I'm not sure if it exists but hasn't been configured or if it's missing, but we've been unable to utilize the location features.
I have been using Intune for about two months.
Intune is pretty stable. It's also great for helping us maintain compliance in our environment. If it's a hybrid deployment, you should be fine as long as the sync is running.
Intune is easy to scale because it's in the cloud. There are no limits on what you can manage.
Microsoft support isn't too bad, but it depends on the department you called. Intune support is better than support for Defender for Endpoint. I would rate it about a six out of 10.
Neutral
I was previously using on-premise Active Directory with group policy management. Intune puts your dashboard and panels in the cloud, but they sync with the on-prem Active Directory. Most of the management is done from in the cloud. All we need is internet access to manage the devices.
Setting up Intune was straightforward. Microsoft provided all the materials we needed, and we had support from their team. We had about five guys working on the solution. It can be from one to five guys, depending on the scale of the solution.
We went through the reseller.
The price isn't too bad
Yes, we've tried ManageEngine and SolarWinds.
I rate Intune 8.5 out of 10. My advice to future users is to perform a proper inventory before enrollment. This is essential cost-wise. You need a good idea of how much it will cost per month so you don't overrun your budget.