Microsoft Intune Reviews

Essentially, we use it to manage devices. We are looking at potentially moving away from VMware and bringing mobile devices and tablets into Intune along with desktops and laptops, which we currently manage, so that it serves as an all-in-one active asset list where we can look at the health of the entire technical estate. We can manage against threats. We can roll out apps, policies, et cetera. We can also manage logins, reset logins, et cetera, and it's an all-in-one, 24/7 solution.

Microsoft Intune has absolutely improved the way our organization functions. We're currently going through the AAD migration, so we are transitioning away from the old on-premise domain to Azure. The ability to take devices that were locally managed via AD but weren't managed via Intune is brilliant. We can see who last logged in, who it's managed by, which OS is there when it was last updated, etc. It gives us a micro overview of what's happening there.

Generally, we find it quite useful. We don't use it to the full extent. We've only got a P1 license, but generally, the application health and the ability to create and manage policies are valuable. We can split them very quickly into groups, multiple policies, etc. So, it's those core basics that we use, but they work very well.

It's very informative when there is an error. It allows us to backtrace where the error is and resolve that ourselves. It's a bit of a Swiss Army penknife. We find that it fixes most issues.

I'd like some more reporting so that I don't have to delve into PowerShell and I can pull more of the local device information such as memory, apps installed, etc. It would be nice to be able to see the apps that are present there but might not be managed. For example, if they installed 7Zip, it could report that back via an installed program or feature to see what was currently installed. Generally, it works, and nobody complains about it.

I've been using this solution for a couple of years.

Sometimes, they can take a little while to come back in showing that they are compliant. Typically, they may show us as not compliant even when we are. Typically, we find that it takes a couple of hours or a couple of days at worst for the machines to show as being compliant for them to settle down, but generally, it does what it says on the tin. We can set the policy, and we can put a machine or put a device into a group. That policy gets defined or pushed out, and it works. We can then move on to the next job. From my perspective, it works well, and that's why I'm just looking forward to using more Azure technologies moving forward.

It's deployed across multiple locations, departments, teams, and endpoints.

I haven't had any experience with them.

At the moment, we're using VMware AirWatch, which isn't my first choice purely because it's a super segmented platform. We are predominantly, about 95%, Microsoft. It feels a bit of an oversight not having a solution on a Microsoft platform where we've got full transparency and can make live changes. Currently, we have to go through our outsourced IT to make the changes and then we have to wait to see those changes rather than me or a colleague being able to make those changes in a live environment, so it would be my personal preference to get that moved over, which we're looking at. 

I wasn't a party to why they used AirWatch. I presume it was bundled in with the Microsoft service partner's offering originally. The IT team here is quite new. I've only been in the post for about a month, and my IT manager has only been in the post for about two months. We're just making sure that everything is easy to use and easy to manage, and it's cost-efficient for the charity moving forward.

Essentially, the way it was set up, it wasn't set up as a hybrid model. At the moment, we have got on-premises, and we have a cloud, but they're not joined. There is no passthrough, which is interesting. A lot of the on-premise has been copied over to the cloud. We are now taking the cloud to default, and the overall plan is to mothball the servers and reuse those as very high-powered desktops wherever possible. I just predominantly use the cloud.

I was not involved in its deployment, but in terms of maintenance, typically, our MSP makes the changes, but I've got GA rights to make anything that is critical. Generally, there are about 20 people at the Microsoft solution partner, and there are four of us on the IT team. There are less than 30 people in total.

I'm not sure. Certainly, it has been at least three years since the software has been rolled out, but it's not particularly well maintained by the solution partner. So, it's hard to measure the ROI. It does have merit, but in our particular sector, it's just overkill. We just need to make small and light changes whilst having effective security. We don't need corporate class, biometric/conditional access level security. Whilst we have multiple offices, they're very small. They're all under 20 users, and there's a lot of work from home. So, as long as we've got encryption, a form of AV, an anti-spam, and good account security, it certainly staves off a lot of the threats.

Personally, I feel that we haven't had the ROI purely because we're paying about £13,000 for under 300 users a year, which is a little bit top-sized. My personal feeling is to make a business case to switch to Microsoft Defender. Obviously, we've got P1 in our business premium licensing, so we've got a very basic protection at the moment that we don't use. We've got a large number of credits, and we could use those credits to switch over for a year to a higher project and see where we go from there.

Generally, it's not too bad. Obviously, a cheaper price would be great. Typically, we are in touch with the partner to provide non-profit discounts wherever possible. Generally, we get favorable discounts, so it's not too bad. Obviously, we're looking at decreasing those wherever we can to bring value back to the public purse because it's all charity based. It's all publicly funded.

Create a test group and create test policies, and then just test, test, and test before anything is rolled. It's the usual IT gambit. Test everything, and then just test it again before you roll it out.

I worked for a couple of MSPs before. I've seen it in very remote areas. I'm very impressed with it. Whilst it seems almost fashionable to criticize Microsoft, Intune is pretty much a well-laid-out product. It does what it says it's going to do. There is a lot of dependence on Microsoft products being pushed to it, and that's probably my only criticism. It would be good if Intune was a bit more open-source, but that would lead to more complications. It's a bit of a complicated beast, but generally, I like it.

I'd rate Microsoft Intune a nine out of ten. I'm happy with it.

We use it to a small extent for approximately 1,100 devices. The biggest portion of it is used in the Aviation department, which is one of our departments. They have invested heavily in some customized software that they've developed in-house. It is put on the devices, and the devices are primarily used by field staff. It's basically a mixture of work order assignment and work order management, as well as record keeping. For example, I could have a technician who is assigned to go and do a preventive maintenance inspection on an HVAC component in one of the terminals. That request or work order is submitted to his device. When he gets there, he scans barcodes for the room he is in and for the piece of equipment that he is working on. So, they track their actual work order, work order status, workloads, and equipment life cycle, and that's all done through Intune.

It helps us in securing devices. It has eliminated a lot of paperwork. It has simplified record-keeping and maintenance of equipment, life cycle management, staff workload, work hours, et cetera. That's the biggest impact on us, and that's also where most of the devices are used.

Its security is most valuable. It gives us a way to secure devices, not only those that are steady. We do have a few tablets and other devices, and it is a way for us to secure these devices and manage them. We know they're out there and what's their status. We can manage their life cycle and verify that they're updated properly.

It doesn't economize when you scale up. We have over 14,000 employees, and we have between 7,500 and 8,000 city-owned or personal devices being used to conduct city business. Its price can be improved. It is not a cheap solution.

It has been years since it was implemented.

Its stability has been fine. We've had no issues at all.

I don't see any issues with it. We currently have only about 1,100 users and licenses for the Intune product. The largest portion or over 50% of usage is by our Aviation department for tracking and managing their work order, workload,  equipment life cycle, etc. Other users are scattered in small numbers throughout a number of departments. 

Our Parts department also uses it. One thing that's a little bit unique is that they also have these assigned to temporary workers. So, we provide the licenses for a number of temporary workers for the summer or for the winter, and then we take them back and reassign them to somebody else. 

The other departments mostly use it for educational or small use cases where they think this will be a good fit, and it is the product that is available to them. I've heard nothing bad about it, and I have no problem at all with Intune.

In terms of future growth, we're currently looking at another product, but that doesn't mean we're going to go with that other product. We're working with a vendor on another solution, and that vendor also has a mobile device management product, but we're not yet ready to go there.

I've no direct input on it. Right now, we're on unified support, but we've always had their premier support. If we ever have a problem with any of our Microsoft products, including Intune, we do have a way to reach out and get additional assistance.

I'm not aware of any other solution being used. I know there were one or possibly two failed mobile device management project implementations. I was not a member of the department then, so I don't know the details. I only know that both of the deployments failed. In other words, either the vendor promises were not met, or we found a function that was supposed to exist but did not exist. 

It was pretty straightforward. It was not a very long, complex, and involved process. It was fairly easy to set up.

It was done in-house. For its maintenance, we have no one dedicated to it. Our client computing side takes care of that.

I've never tried to quantify an ROI for the program. We have just a small number of devices. At some point, we will look at implementing large-scale mobile device management, and that'll be a different case where we may look at Intune, Workspace ONE, or another product.

It is not a cheap solution. The price for a device when you start using it at a large scale can be improved.

It is covered under our enterprise agreement. We pay once a year. I am not aware of any additional costs.

It meets the basic security needs and management needs for most organizations. It allows you to monitor the security of devices and manage those devices if they're organization-owned. It is fairly easy and straightforward to manage. It is not difficult. Some of the other solutions are a little bit more difficult.

I would rate it an eight out of 10. It meets all the basic needs that most organizations will have for device management and device security. I am not sure if it can provide the required level of security for different business scenarios that require additional security, which means you'd have to run two systems in tandem.

Nowadays, we've seen more evolution towards Autopilot for Windows 10 and then in a hybrid or cloud-only setup. After the Windows devices, we use it with Android, the most frequent mobile, and then iOS. I have five or six projects regarding Microsoft.

It helps deal with conflicting policies. We do a lot of graph API calls toward Microsoft for reporting, et cetera. 

It simplifies the work of the IT admins in a company if you set it up right. The setup will take some time, obviously. However, if you set it up right, it will simplify the management of your endpoints. The enterprise app management is great. With Intune, you can shorten the time needed for handling the necessary updates so that there are no vulnerabilities on the applications or on the operating system side of things.

The Intune suite offers a lot of features. 

The AutoPilot feature is helpful.

Endpoint privilege management is very good. You can bring your own device setup. You can use it in combination with conditional access policies for encryption.

Migration from on-prem to cloud is good.

The settings catalog and configuration profiles are also very, very useful.

Intunes brings all of our endpoint and security management tools into one place. This is a good thing. We now have one portal to check instead of dozens. I'm really happy with that.

The overall user experience is quite nice. I have no complaints from end users regarding their devices enrolled in Intune.

We've used Copilot. We have nothing to complain about, however, it is very expensive. With Copilot, we summarized a few of our policies and devices, which were great. We check the properties of the devices, hardware, of the devices, and so on. Mostly, we played around with the summaries of the policies, however, we switched it off since it was running for a couple of days, and it was a few hundred euros for those few days. 

Witnessing the benefits of Intune happen quickly. Clients usually begin to see benefits after the kickoff meeting. Intune is an ongoing development product. It helps both greenfield and existing setups. It's not static. We'll work with policies and versioning, and after every quarter, we'll review our policies and update where necessary. If clients used Intune managed services, they get policy updates included in the managed service. 

Intune is good for securing hybrid work and protecting data of the company while bringing our own devices. We use device framework policies from Microsoft themselves with some minor adjustments. They have level one, level two, and level three policies. You can just fix the settings of their site, and that's also what we use. Then we just tweak and bring in our own experiences. 

The endpoint privileged management enables users to enforce privileged access and can positively affect user productivity. In in small environments, the end users are, in 99% of the cases, also local admins on their devices, which is obviously not good. In bigger environments, we get into that less often as it's more of an organized thing. That said, in small environments, everybody is a local admin and that brings certain risks with it. So users can install and download everything they want. With endpoint privilege management, we can set rules for specific applications, and then, a user can ask for approval to run a certain application, which is very good. 

Intune positively affects overall IT productivity in organizations. If users need to install it on a device that they need in their workday or day-to-day business, they can just grab it themselves from the company portal app. They do not have to wait. They do not have to enter a support ticket that goes to the help desk to request a certain type of software. They can do it themselves, so they save a lot of time.

Intune, when applied on the cloud, can save on costs. With the cloud, there's no on-prem infrastructure that needs service, electricity, space, or cooling, for example. 

There are a lot of features that need to be released. There is no copy-paste or fie transfer. There's more work to do. They don't live up to my expectations anymore. Microsoft has a history of releasing features that are not completely finished. 

Remote help needs to be better.

Reporting needs improvement. It's still lacking. The built-in reporting is pretty basic. In managed services, we have a lot more reporting. However, we had to develop it ourselves.

I've used the solution since the product launched, about 15 years ago. 

The solution is fairly stable. I cannot recall the last time that there was a health issue reported on the Microsoft side regarding Intune.

The scalability is perfect. I've had no issues with scaling. 

The communication between us and Microsft is good. They do come back with insights on what's to come. When it coms to support, if you are lucky, you will get a good tech that can help. The knowledge of some techs are insufficient. They may ask basic questions that are not relevant to the issue. You spend a lot of time re-answering questions you may have already addressed in the original ticket.

Neutral

I did not use a different solution previously. 

I've been in touch with MobileIron and AirWatch, however, that's very, very basic.

I work with both on-cloud and on-prem versions of the solution. 

The initial deployment is very simple and straightforward. I've been doing it for 15 years, so I understand the process. When people are new to Intune, there may be some complexity. There are many things that need to be considered. The learning curve can be steep. 

There is support from Intune for maintenance, like when an application fails to install. 

I tend to implement the solution myself. 

Some people have Microsoft 365 with a security add-on, and Intune is integrated. 

Copilot is expensive as an add-on.

It's a rather expensive solution, especially if you want to use all the bells and whistles. 

I've been involved with the solution as a customer, integrator, reseller and consultant. I'm a freelancer as well and use it myself. I'm selling licenses and doing greenfield setups for different customers. 

We've not yet used all aspects of Intune suite, which is a new collection of advanced endpoint management and security tools. We have demoed it, and we are showing it in workshops. However, we do not have it in a live environment. A lot of customers are hesitating to buy the Intune suite due to the price. Some users may be paying fifty euros per user per month and then would need to add another 10 euros for the Intune suite, and that's a big step since that would be a fifth of the license that they're already paying. 

It's helpful that Intune is integrated with 365. It's important that everything is integrated together so that the Microsoft ecosystem becomes seamless. 

I'd rate the solution 8 out of 10 overall. 

It's a fund product. The possibilities are almost endless. It will make your life easier. 

We manage all our client devices, including Windows laptops, MacBooks, iPhones, iPads, and Android devices, using Microsoft Intune.

We regularly survey our users to gather feedback on their experience with device enrollment and app installation. The feedback we have received so far has been positive.

Intune is good at securing hybrid work and BYOD. There are a few gaps but we can manage those with other tools.

Microsoft Security Signals within Intune is an effective tool. It allows us to restrict access to specific systems or resources for certain devices based on their risk score. We can also prevent access for other devices that don't meet a specific risk threshold until their score improves.

It has enabled our IT team to use their tools more effectively.

Intune streamlines our endpoint management by consolidating multiple vendors into a single platform. With Intune, we can now manage features like the Windows Defender firewall and disk encryption directly, eliminating the need for separate third-party products. This simplifies our management process and potentially reduces costs.

The vendor consolidation has helped to reduce our licensing costs.

It is extremely important to us that the Microsoft Intune suite is integrated with Microsoft 365 and Microsoft Security. We're looking at consolidating more systems and solutions into our Microsoft licensing because of how easily it integrates. 

While Microsoft Intune boasts a wide range of features, its user-friendliness and bundled licensing cost are key considerations for me.

The licensing has room for improvement.

It would be great if Intune offered better data protection controls for BYOD Windows PCs.

I have been using Microsoft Intune for four years.

While Microsoft Intune is generally stable, there are recurring issues with deploying Microsoft 365 apps through Intune. These outages occur around the same time each month.

I would rate the scalability of Intune a nine out of ten.

While the technical support team is generally good, there have been instances where feedback sent to the product group has resulted in delayed or absent responses. This can be frustrating, especially when requesting new features or clarifying existing ones. It would be beneficial to establish a clearer communication channel with the product group to ensure timely responses and address customer concerns efficiently.

Neutral

Previously, we used Workspace ONE. While I find Intune to be generally better, there are still some specific areas where Workspace ONE offers functionalities that Intune currently lacks. Additionally, Workspace ONE was significantly faster for generating reports. However, I acknowledge that Intune has undergone significant improvements over the past year and a half, and it's steadily approaching the level it needs to be. Nevertheless, there's still room for further improvement.

The implementation was completed in-house.

The current licensing model separates essential features into higher-tier subscriptions, requiring additional purchases. Ideally, all functionalities should be included in a single bundled license.

I would rate Microsoft Intune eight out of ten.

We rely on Intune for device management and leverage other tools for security.

Additional maintenance is required to deal with the monthly outages.

I recommend using Intune for endpoint management. It's important to familiarize yourself with the product beforehand. Researching endpoint management via Intune and reviewing Microsoft's online recommendations is crucial for successful implementation within your organization.

We use Intune to manage mobile devices and applications. I'm not solely using Intune for the agents installed on each machine. I use the Microsoft Endpoint Manager solution primarily for device configuration, device compliance, and mobile application management.

I have 80 different clients, and their environments vary. We have people that work in offices across multiple foreign countries and domestically. Most have a strictly cloud-based deployment, but a few have a private cloud that we host ourselves. Some have their own data centers. I've got a couple of clients with hybrid environments. None of them are entirely on-prem. Everybody is using a hybrid cloud or completely on the cloud.

Intune helps us from a compliance standpoint by making it easier for system admins to configure devices and ensure they conform to business policies. It gives us more visibility into where the devices are and their postures.

I try to use conditional access policies for every client I can. It's essential for a zero-trust security posture. Conditional access policies make it possible. This dramatically reduces the risk of unpatched devices connecting to our corporate network.

The conditional access policies, compliance, and updates affect employees positively. Once the value is explained to them, they don't complain much about MFA.

You can use Endpoint Manager to see whether or not a device is compliant and apply conditional access policies in Entra to only allow connections to your environment from compliant devices. That significantly reduces your risk from unpatched software because that device cannot connect to your machine or environment. Using those two features together definitely helps protect us.

It saves some time. Either way, you will have to manage an Active Directory environment, but Intune allows you to manage devices over the internet. You don't need to worry if the machines are connected to a VPN or on-site.

The most valuable feature is probably mobile device management. Small businesses are coming under greater scrutiny and requirements for compliance as time goes on. We don't have to worry about a VPN because we can manage these devices, control company data, and lock users out. If needed, we can remotely wipe devices and switch them. 

It's a big deal to be able to assure an insurance company or auditor that our endpoint devices are effectively managed. Intune is a solid solution if you use Microsoft and Microsoft 365 products.

Intune's third-party patch management could be better. It should be easier for an average system admin to keep non-Microsoft applications updated. 

I have used Intune for about six years now.

Intune is highly stable. 

Intune is highly scalable. Thus far, I haven't had to expand it to a thousand users, but the scalability appears to be readily available.

I rate Microsoft support a nine out of ten. I enjoy working with them, and I'm often surprised at how good they are. 

Positive

I've used Rocky MDM and Google MDM. Microsoft is the primary platform on which we do business. Intune works better with the Windows operating system, desktop applications, and SharePoint. It also reduces vendor complexity. I don't require multiple vendors, which reduces my costs because many features are baked into it. 

I log into fewer systems daily. Microsoft's virtual monopoly on productivity applications in your average small business makes them the right choice in most situations.

Deploying Intune is pretty straightforward. It doesn't matter whether you use autopilot or manual deployment. Each machine is enrolled in Intune automatically if it's connected to Azure AD with the correct user licensing. It's a relatively painless enrollment process.

Intune involves some maintenance, like any solution. You must ensure it's still working correctly and helping you achieve your business goals for compliance and configuration of your endpoints.

Meraki and Google are relatively common in small businesses. Many small businesses use Meraki for wireless and networking solutions, so that is one MDM option. Also, small businesses often start with Google and transfer to Microsoft 365 once they mature. Google is already in the environment. I don't sell anything as an IT guy, so I don't care what solution my clients use. I choose what's best for them in that particular instance.

I have tried Okta, but I haven't used it seriously as an MDM solution. I've only used Okta as an SSO provider. I didn't realize they did MDM solutions. I don't understand the point of Okta. If you have Azure AD and Entra, I can't fathom why you would bother with Okta. It seems redundant to me.

I rate Microsoft Intune a nine out of ten. Don't underestimate the solution, and spend time learning about it. Intune has some powerful capabilities. Often, small businesses acquire systems but never fully utilize them because nobody has the time to dive deeply into them. It's a big solution with a lot of features. 

We use Intune to deploy and manage applications to devices based on our client requirements and needs. We handle a lot of use cases, especially with regard to Microsoft Edge. Recently, we have deployed BitLocker and Docker encryption using Intune. We utilize Intune to patch and onboard Defender and Core Endpoint. We apply Intune to laptops, mobiles, and tablets, including iOS and Android.

Intune has automated the deployment of patches and applications, which is more efficient and easier. It allows us to deploy applications, packages, Windows updates, and security updates like BitLocker encryption more efficiently and easily.

The most valuable feature currently is the BitLocker encryption. Most clients in the Philippines are moving to BitLocker encryption via Intune, transitioning from any existing third-party encryption tools they may have.

The most significant challenge is reporting and monitoring. The reporting accuracy for deploying applications and all aspects of Intune needs to be improved. Intune is less admin-friendly than SCCM and WSUS systems. In WSUS and SCCM, you can classify the updates you want to deploy to the endpoints, whereas Intune only has quality updates, definition updates, etc. I rate the admin experience seven out of 10. It's not terrible, but there is room for improvement. 

We've used Microsoft Intune for nearly 10 years now.

I rate Intune eight out of 10 for scalability.

I rate Microsoft support eight out of 10. Microsoft's engineers provide varied approaches and knowledge about the product.

Positive

We are resellers, consultants, and they often refer to us as implementers. We handle the solution and technical support.

I can rate Microsoft Intune eight out of 10.

Intune is a cloud-based platform for mobile application management and mobile device management. We can deploy applications on user devices and enroll user devices. We can enroll devices as per the organization's security policies. The devices comply with all the policies of the organization. We can also change the policies at the backend via Intune.

Intune helps with enrollments and securities. We can control the access to devices and users. We can specify what users can do. We can give role-based access. For example, a person working as a normal user does not require the same access as a manager. We can give access to users based on their roles. For example, a manager can add users to a particular group, but users cannot do that. We can restrict a user from doing certain activities. For example, we can restrict the user from using a camera or microphone. We can do such a configuration at the backend and deploy it to the user device.

Intune is very helpful for IT and security operations. If Intune is not there, we have to manually connect to user devices and deploy the changes. If we have thousands of devices, doing this manually on each and every device is very difficult. With Intune, we just configure the required settings and deploy them to a thousand devices in a single group. In a single step, we can add devices to a group. We can apply configuration easily. It is very helpful. It saves time. Adding or configuring devices manually takes a few months, whereas the same thing can be done with Intune within minutes.

We have had a very good experience. It is a Microsoft product. Everything related to a user is available. We have user names, user devices' names, and user licenses. We can also check the device compliance. We can see whether the device complies with the company policies or not.

Application updates and patching are available through Intune. We can also change group policy settings and registry settings of a device via Intune. We can change these settings without connecting the device. We can do that by deploying the PowerShell script or configuration profiles. For example, a kiosk device should stay up for hours and hours. It should not go to sleep. You can configure such devices to not go to sleep until 999 minutes. It is a very long time. If we enable such settings and add a particular user device group in the configuration, after the device starts syncing with the policy, no device will go to sleep.

With the Advanced Endpoint Analytics, we can see the application installation status. If we deploy a script to the user, we can see the status. We can see if it is a success or if there is a conflict. We can monitor the changes in user devices and check the compliance status. We can see if any app such as CrowdStrike is not updated.

With the help of Advanced Endpoint Analytics, we can proactively detect and remediate anomalies in endpoints. We can then reach out to users.

Intune saves us a lot of time. If we package an application using virtual packaging or physical packaging, it will take nearly two to three hours to package a single application. If we do this in Intune, it takes just minutes to add applications and deploy users. We can also monitor the particular application status in Intune.

The devices that are linked with Azure Active Directory are automatically linked with Intune. That makes the enrollment and management of BYO devices easy.

Intune has affected IT productivity in our organization. By saving time, it has automatically improved productivity.

Intune certainly saves costs. Without a cloud-based solution like Intune, we would require more IT staff.

Microsoft releases updates every second Tuesday. We can deploy those updates from Intune. We can also do patching through Intune. We can do quality updates and feature updates from Intune. We can also monitor the application status in Intune. We can see which applications are installed, pending, or available to install. We can see these things in Intune.

It is user-friendly. We can also troubleshoot any issues.

Intune saves time, and it is very easy to use. It allows us to manage applications completely.

If we could remote into a device, it would be great. Currently, we cannot directly connect to the user device. We have to use other tools such as VMware for connecting to devices.

If there are any issues, we should be able to connect through the Intune portal. The administrator should not have to go anywhere from the portal. He should be able to do everything from the portal.

Intune does not show whether a device is online or offline. It just shows the last login. It would be useful to know whether a device is online or offline.

We can see the issue related to updates in the Intune portal, but we cannot do anything from the Intune end. We have to connect to the user's device manually. We also need a better understanding of why the update is not happening on a particular device. It will decrease the time to troubleshoot the issues.

At times, there have been slowness issues with the company portal. It takes time to load and does not show the application status.

It would be great if there is a way to generate a PowerShell script to do certain things. Learning the PowerShell script is not easy, so such a feature would be helpful. Based on what we want, if it can automatically generate a script, it would be helpful.

It is not necessary, but it would be great if they added a messaging system in Intune. For example, when it is a shared device, a number of users log in to the device. In the case of any issue, it would be great to be able to directly message a user from Intune. Currently, there is no option for that, but if it could be done, it would be a very good thing.

I have been working with this solution for the last 18 months.

It is 100% stable.

It is very scalable.

We have about 12,000 devices and 20,000 users.

So far, I have not raised any questions with them.

I have worked with Microsoft SCCM. It is similar to Intune but not as user-friendly as Intune. Intune is very easy to understand. Its framework is very good. Microsoft SCCM is very old.

I have not worked with any other vendor. 

I am involved in the deployments, enrollments, troubleshooting errors, and monitoring in Intune. I take care of adding devices, users, and licenses, deploying policies, and configuring policies and scripts.

Its deployment does not require much. We just need a license to operate it. Our management takes care of that. There are a few licenses that are active only for nine hours. After nine hours, the roles are deactivated.

It does not require any maintenance from our end.

Intune is linked with Microsoft. We can deploy the Microsoft E365 license to users by Intune. There are different types of licenses, such as device administrator licenses, E5 licenses for device enrollment manually, and P1 and p2 licenses for device enrollment automatically. These are the licenses required for the administration.

I did not evaluate any other option. This was my first project, and I started as an Intune administrator.

It is a very good tool. It is easy to learn. You can expect quick assistance from Intune.

Before using Intune, I would recommend learning about Windows. Learn about the registry, configurations, and group policies. If you know these, it is easy to learn Intune.

You can face enrollment errors if the prerequisites are not met. For example, to upgrade from Windows 10 to Windows 11, you need to have some amount of free space or RAM. If you do not care about the prerequisites and just enroll the device, it causes issues. It will affect the device, and you need to enroll the device again.

I would rate Intune a nine out of ten.

We use Microsoft Intune to secure and control our notebooks and mobile devices.

Intune is deployed as SaaS.

Microsoft Intune has been instrumental in helping facilitate remote work.

Microsoft Intune brings our endpoint and security management tools into one place.

Microsoft Intune provides full visibility and IT control across our device platforms.

The Microsoft Intune user experience is seamless. The users are not affected by the control we have over the devices.

Enforcing privilege access using the privilege management feature allows us to quickly address the user's service requests.

Microsoft Intune has helped reduce the risk of security breaches. This control over our devices reduces the attack surface and makes them more secure.

Microsoft Intune has helped consolidate our vendors making it easier to administer control.

Intune suite's ability to integrate with Microsoft 365 and Microsoft Security for all managed devices is important and makes managing them easier.  

The policies restricting non-corporate devices on our network and the installation of unauthorized apps are the most effective for managing and securing devices.

The ability to block and erase remote devices is valuable to us, especially when those devices are lost.

I would like the ability to install the agent on devices from suppliers, which would enable us to implement a zero-trust strategy for guest devices.

I have been using Microsoft Intune for almost two years.

Microsoft Intune is stable. I have not encountered any issues.

Microsoft Intune is scalable. We are planning to increase the size of our company within the next 12 months.

I have contacted Microsoft support once because we primarily use one of their local partners for support.

Positive

One infrastructure analyst completed the deployment.

We used a Microsoft partner to help with the initial deployment.

On a scale of one to ten with one being the cheapest, the cost of Microsoft Intune is a five.

We evaluated a solution from Blackberry but did not like it because it was not as intuitive and the configuration was antiquated. Microsoft Intune was also less expensive.

I would rate Microsoft Intune nine out of ten.

We have only 100 users. It is easy for us to administrate this number of devices.

A junior-level infrastructure analyst manages the solution.

Before implementing Microsoft Intune make sure to have a good plan and become familiar with all the solution's features.