Microsoft Intune Reviews

We primarily use Microsoft Intune for managing Windows devices, and we also work with Linux devices, though not with Mac. It's a significant help for Windows management, with excellent policies and report fetching systems compared to Jamf. 

Microsoft Intune brings all our endpoint and security management tools into one place. It acts as a comprehensive solution where we can manage numerous devices and configuration profiles, and block specific URLs, among many other capabilities. 

We use the Enterprise Application Management features. The automatic updating in Microsoft Intune is excellent. When a user comes up with an application package to update and deploy, we have to go through the UAT process, which can be hectic. However, the automatic updates are really helpful and decrease our workload.

Copilot is particularly useful as it helps analyze error logs and can even assist with writing emails, saving considerable time.

My favorite feature of Microsoft Intune is the device find and device applications options, where we can see which applications are installed on devices with accurate version information. This helps us troubleshoot systems effectively. 

I also appreciate the report system that allows us to fetch clear reports. Previously, we used Workspace ONE, but its reports weren't as reliable as Microsoft Intune's. 

The user interface of Microsoft Intune is good, though new members sometimes find it challenging to navigate due to the numerous options within categories such as devices, applications, Windows 365, enrollment, and configuration. 

Microsoft Intune could be improved by adding short video tutorials or direct links to Microsoft articles in the information button. Currently, the descriptions in the information button aren't always clear about what certain options do. Having these additional resources would be particularly helpful for new users, eliminating the need to search extensively for information.

I have been using Microsoft Intune for about two years. I have hands-on experience with Microsoft Intune. 

I started using Microsoft Intune in May 2023, and it took me two to three months to fully understand its capabilities. After this learning period, I gained a clear understanding of what Microsoft Intune does compared to Workspace ONE and Jamf. While every MDM tool has its own features, Microsoft Intune serves as a comprehensive solution.

We have contacted technical support for various issues. They demonstrate extensive knowledge and consistently resolve our problems.

We previously used Workspace ONE, but its reports were not as reliable as those from Microsoft Intune.

While I don't know much about securing hybrid work and protecting data on bring-your-own devices, it is secure. Microsoft Intune has endpoint security options and all the necessary features. However, organizations are using different options for security purposes. Some use Defender as well, so I haven't seen much about that. We use the Endpoint Privilege Management.

I would rate Microsoft Intune an eight out of ten. 

We use Microsoft Intune for managing devices. We deploy our devices to users using Microsoft Intune Autopilot, which enables us to set up the device for the user and then ship it to them. When they log in, everything is there for them, including all the applications they need. We push applications through Microsoft Intune; for example, we install Zoom through it. 

We do not allow users to install their own apps. We use AppLocker, which prevents users from installing their apps. We can use remediation scripts. One script uninstalls Google Chrome if someone installs it because it hasn't been set up in AppLocker yet. If it were, AppLocker would prevent the user from installing Google Chrome. We use Microsoft Edge because it's easier to manage using Microsoft Intune and Microsoft Endpoint Manager. We can prevent users from installing extensions, which is beneficial because password and session token theft often occurs through malicious extensions. We can have a whitelist of extensions that users can install or push an extension to be installed using Microsoft Endpoint Manager. I'm using Microsoft Endpoint Manager and Microsoft Intune interchangeably here because they're practically the same product.

The best feature in Microsoft Intune is the ability to wipe a device if it gets lost or stolen. Even if the device goes offline, if you send the command to wipe the device and it appears online, you can still wipe it. If the device breaks or ruins the storage, it doesn't matter because the goal is to ensure they don't have the data. You can also keep the device locked to your tenant if desired. If someone steals the device and tries to install Windows again, it will display 'Welcome to X company' and they cannot proceed past that point.

Another notable feature of Microsoft Intune is application supersedence. For example, if we were using Microsoft Paint and we don't want it on the device but want another paint program, we can specify that Microsoft Paint will be superseded by this new application. It finds the application on the device, uninstalls it, and then installs the new application, providing two actions for the price of one.

Regarding the Enterprise Application Management feature for app discovery, deployment, and automatic updating, we utilize that functionality. We use advanced endpoint analytics with Microsoft Intune. Only one of the global admins needs the license, and the rest of the admins can manage without individual licenses.

I’m not sure if Microsoft can do anything to improve this situation. The most frustrating part for me is when we make changes to a device, particularly with our virtual machine setups and test users. These test users need an intern license, so we usually provide them with what the other users have, which is a business premium license—it's the best value for our needs. When we push an application, it’s usually manageable. However, when it comes to configuration changes, the waiting game can be tedious. Sometimes the change takes effect in just two minutes, but other times it can take up to two hours. It’s difficult to be patient while waiting to see if the change works. We could try restarting the Intune management service to prompt it to check for updates, but that’s hit or miss too. I really don’t know how the changes are pushed to devices—whether our changes go into a larger queue with others or not. What frustrates me the most is just waiting and tapping my fingers, uncertain about whether my changes will take effect. I honestly don’t know how they could improve this process, as I’m not familiar with the inner workings. But this delay is the most annoying part for me.

Sometimes, the menu system isn't very user-friendly. You'll find yourself digging through various sections, and the changes to the menu can be frustrating. For example, when you ask Copilot, "Where is this?" it might respond with a sequence of steps to follow, saying you need to go here, here, and then there. However, either Copilot is misunderstanding the situation, or the option has been moved, as it might no longer be where it used to be or it could have a different name. This is something that seems to change frequently. Microsoft tends to update things consistently; they do it with Windows and other products as well.

The most important thing is to stay patient while waiting for these changes to take effect. Additionally, not only do we need to wait for the changes, but we also need access to logs that detail what has changed. It's frustrating when you see the changes happening on the device, and maybe they fail, but then it takes twenty minutes to an hour for that information to be reflected in Intune. This delay hinders your ability to troubleshoot effectively. From Intune's perspective, while I can check the event logs to see why an application might not have installed, I'm more concerned about understanding why Intune itself failed. So, the two main issues are the time it takes for changes to be implemented and the time it takes to report on the effectiveness of those changes.

I have been using Microsoft Intune for approximately five years now.

There has only ever been one issue with Microsoft Intune, which they fixed quickly in less than a day. That issue concerned displaying incorrect access rights to users. It did not disrupt operations significantly; we simply couldn't test anything for a while.

It's a very scalable solution. You can have thousands of devices connected if you want. It allows you to manage numerous aspects effectively. This system has greatly benefited my company, as we were previously reliant on an inadequate VPN for connecting to our network infrastructure. Now, we have the flexibility to hire employees from places like Arizona and Washington, which wasn’t possible before due to the need for onsite presence. Using Intune has enabled our workforce to operate remotely. Since implementing this solution, our company has grown substantially, and our talent pool has significantly expanded. Although we only hire within the United States, we now have the ability to recruit from virtually anywhere in the country.

Our company has approximately 100 users working with Microsoft Intune, with a more complex setup due to our structure of five separate companies.

We contact our cloud service provider first, who escalates us to level two tech support if needed. Microsoft support can be very inconsistent, warranting a rating of seven out of ten.

Neutral

My last use of SCCM was about eight years ago. Microsoft Intune's interface is superior; SCCM appeared outdated at that time. While I cannot extensively comment on SCCM due to dated experience, Microsoft Intune remains a strong product despite its regularly changing interface.

Our deployment is entirely in the cloud. We used to operate on-premises, but I migrated everyone to use Entra ID instead of Active Directory on-site. I had to accomplish this while everyone was working remotely, which made the process more challenging since using Entra Connect or AD Connect was not feasible for many users. Currently, everyone is fully in the cloud. We do have an office, but people are rarely there. They only come in for meetings and such; most of the time, they are working remotely.

The deployment of Microsoft Intune is relatively straightforward to set up. It's more straightforward than SCCM, though SCCM lacks certain features that Microsoft Intune has, and vice versa. For beginners, completing Microsoft SC-900 provides a foundation, which is more oriented towards Entra. However, MS-900 might be more suitable as it focuses on the admin center.

For new companies implementing Microsoft Intune, setup can be quick with experienced personnel. Transitioning from on-premises to a hybrid solution depends on the number of users. It's crucial to ensure proper ID transfer and appropriate Entra licenses, particularly for write-back functionality. Without write-back enabled, users changing passwords outside the office might end up with two different passwords.

One essential step is onboarding computers to Microsoft Autopilot. A script pushed through Microsoft Intune can accomplish this, though it becomes more complex without automatic enrollment settings. Autopilot facilitates device building and shipping, ensuring everything is set up when users log in. For organizations with small footprints using Microsoft Office and minimal apps such as Zoom and SharePoint, the process is streamlined. When moving to the cloud, consideration must be given to migrating SharePoint from on-premises, for which Microsoft provides migration tools.

Maintenance involves running reports and managing stale devices. Setting up automatic removal of inactive devices helps maintain a healthy Microsoft Defender secure score. When reassigning devices, running an offboarding script ensures proper device management in Microsoft Defender.

Regarding return on investment, Microsoft Intune's value becomes apparent when comparing it to licensing costs of other management tools. Since it comes bundled with Microsoft Business Premium, it serves as a powerful tool that proved more valuable than initially anticipated. The overall ROI is positive, and the solution effectively meets our needs. Additionally, we can now deploy Global Secure Access, a VPN solution that protects remote workers and filters internet traffic, adding further value.

The pricing of Microsoft Intune rates around four or five out of ten. The cost structure varies based on requirements. We utilize licensing bundles such as Microsoft 365 Business Premium, which includes the Microsoft Intune license and provides good value. Microsoft Intune alone costs approximately $6 monthly, but considering its device management capabilities, application installation features, and Microsoft Autopilot deployment functionality, the price is reasonable.

The user experience has been good. There is some crossover with Microsoft Entra ID. You can access groups and users from Microsoft Endpoint Manager when onboarding a device. This can be set up using Microsoft Endpoint Manager. If someone receives a new device, they can sign in for work purposes, and if you are familiar with Microsoft Windows, they will have the option to choose whether the device is for home or work use. Once we see the device in Microsoft Endpoint Manager, we can begin assigning profiles and encrypting the drive, making it easier for us to remain compliant. We utilize the CIS framework for compliance, which provides guidelines on tasks such as drive encryption and ensuring all settings are appropriately configured.

Additionally, we implement conditional access policies. For instance, if someone is outside the United States, we can require them to re-authenticate using Microsoft Authenticator for security verification. This measure ensures that if an unauthorized person managed to steal someone’s MFA token and attempted to sign in from outside the country, they would be prompted to complete another MFA session, which adds an extra layer of protection. Furthermore, we can restrict actions on mobile devices. For example, we can prevent users from copying and pasting content from Word documents into applications like Apple Notes. This feature is particularly useful for maintaining security.

If you are a Microsoft shop, these processes streamline operations significantly. However, for larger enterprises, costs may escalate. In such cases, it would be necessary to contact Microsoft to establish a suitable arrangement, similar to agreements made with Microsoft Azure for their resources. For small to medium-sized businesses, getting set up with these systems is straightforward and can assist in achieving compliance. It's important to note that this information pertains to Microsoft Purview and is distinct from Intune, which I will not discuss further.

We do use Copilot, but we have it turned off for email due to a current exploit. There are hidden Copilot commands that can pull data from sources a user might have access to and then email it to someone else, which is why it's disabled for mail. We only have a handful of licenses, and they are primarily for people who have limited time during the day and receive a lot of emails. It's a time-saving feature for them. Sometimes, they use it to write scripts quickly, like in PowerShell, which I then review to understand what it does. You can trust it, but you should always verify its output. Copilot is also helpful for creating a basic outline for documents, such as policies, where you can simply fill in the blanks. However, the pricing is not great. Additionally, you are locked into a one-year subscription with no month-to-month option. The cost is around $360 a year per person, which adds up quickly, so you have to be sure the person really wants it. Consider purchasing one license first to let someone try it out. If they find it beneficial, they can keep it, and we can buy additional licenses for others who express interest. Currently, we have very limited licenses due to the high cost. If they were half the price, I believe everyone would have access to it.

For those implementing Microsoft Intune, if you plan to have remote workers, consider whether you want to provide them with actual physical devices or if you can offer cloud PCs instead. Cloud PCs can be managed through Intune, and anyone with access to a Chrome-based web browser can use a desktop from anywhere with an internet connection. This approach also helps you avoid issues with retrieving physical devices from users, as they are not legally obligated to return them, potentially leading to a loss of significant investment.

Additionally, there are compliance issues to consider when providing devices. For instance, if you give a physical device to a contractor, they may be legally considered your employee under laws in certain states, such as California. Therefore, think carefully about your deployment strategy. Decide whether you'll be using physical devices, which may require more effort to manage, or cloud PCs, which might save you headaches in the long run. You also need to be proficient in PowerShell, as you may have to write remediation scripts. If you're not comfortable with PowerShell and prefer a simpler solution, be aware that there may not be many alternatives. This also aligns well with Microsoft Windows.

If you prefer to use Apple products, keep in mind that you can't just purchase a MacBook from a store. You'll need an Apple business account to obtain a certificate required for managing the device through Microsoft Intune. This rule applies to iPhones and iPads as well. In contrast, with Android devices, you don’t have these management restrictions. So, before making any decisions, consider your deployment strategy and the existing device ecosystem you have in place. I'm not familiar with using SCCM or other management tools, but be sure that with Microsoft Intune, simply buying a MacBook will not allow you to manage it without following the necessary procedures.

I would rate Microsoft Intune overall as an eight out of ten.

We separate users on mobile phones from users on other spaces. 

I really appreciate the features in Microsoft Intune, including the Intune Suite Cloud PKI. 

The main benefits that Microsoft Intune provides for me include data safety.

My main pain point for Microsoft Intune is the contact part. Not all Android or iOS applications have access to integration, for example, contacts. 

Another area I would want to improve in Microsoft Intune is the pricing. 

I have been working with Microsoft Intune for four to five months as a new user.

I would rate the stability of Microsoft Intune as fairly stable.

I have no issues with the scalability and ability to expand Microsoft Intune.

I have never contacted technical support from Microsoft.

Positive

We solely work within the Microsoft environment. 

The setup of Intune is easy; however, getting used to it is not.

We purchased the solution directly from Microsoft. I find the price for Microsoft Intune too high, which represents an area for improvement in Microsoft's pricing model.

We did not compare the solution to any other vendor.

We are using SharePoint as object storage, and for file storage, we are using Azure for verification and authentication services. I would not be able to tell you more about what we are using on the back side, however, Microsoft Intune is being used.

I personally am not working with the integration of Copilot with Microsoft Intune.

I can recommend Microsoft Intune for everyone, whether they are small, mid-size, or enterprise-level companies.

On a scale of one to ten, I would rate Microsoft Intune an eight.

Intune is suitable for everyone. It's good for companies of all sizes. I'd recommend Intune to other users.

We use Microsoft Intune to manage all devices, including Windows devices, Android, and iOS. We have fully managed Android devices or dedicated Android devices, and RealWear glasses. 

Everything that we used to do with Microsoft System Center as an on-premise solution, we migrated to a cloud solution with Microsoft Intune. We are using Autopilot for device management, and for iOS, we use the ABM to include our devices in Microsoft Intune. We are using Microsoft Intune as our standard solution for managing devices.

We utilize Microsoft Copilot in Microsoft Intune and use autopilot to provide user flexibility in device provisioning without requiring IT team involvement. Users can install needed applications from the Company Portal independently. Our machine distributors perform pre-provisioning at the factory, which expedites the process for users.

Microsoft Intune effectively secures hybrid work environments. For data protection, we implement BitLocker.

Microsoft Intune has impacted IT productivity in our organization. The physical team has mixed feelings because they traditionally handled device provisioning, and now fewer people are needed for this task. However, enabling users to perform tasks independently without IT team intervention has improved overall productivity.

Microsoft Intune saves us time, though I cannot provide exact metrics since I don't track this specifically. It is more efficient to have one solution rather than having security parts spread across three, four, or five solutions. 

The user experience with Microsoft Intune is excellent because we can manage users and maintain security and policies anywhere they are. If users have a problem, they can factory reset and start the provisioning again without needing to return to the office. This provides flexibility and improves the experience for users.

The reporting functionality of Microsoft Intune is limited compared to Microsoft System Center, which offers many more reporting options. We also encounter some information inaccuracies that require verification using PowerShell scripts and other tools. We maintain close communication with Microsoft through our support contract and consistently provide feedback to improve the solution.

I have used Microsoft Intune since the beginning of the pandemic in 2020. It has been five years.

We would rate Microsoft's support an eight out of ten.

Positive

While I don't have access to high-level financial information, I believe we have achieved lower costs with this implementation.

We migrated some devices from Soti MobiControl to Microsoft Intune. My manager has requested a comparison between these two tools. We currently use Microsoft Intune and plan to discontinue Soti Mobicontrol use, but we are conducting a final comparative analysis before making this transition.

Overall, I would rate Microsoft Intune as eight out of ten. While I greatly appreciate the solution, some information inconsistencies and issues still need to be addressed by Microsoft.

My main use cases for Microsoft Intune are to manage devices, remotely wipe lost devices, and enforce device security.

Microsoft Intune has definitely reduced management burdens. It has helped us significantly. 

Microsoft Intune has changed my customers' abilities regarding app discovery, deployment, and automatic updating. They use it extensively.

The feature of remotely wiping devices in Microsoft Intune is what I prefer the most. When employees come and go, we can remotely wipe devices. This is what we primarily use it for.

In terms of the admin experience, it is straightforward, but the Windows enrollment experience could be improved. Sometimes, for enrollment, we have to reset devices and re-enroll them. Just configuring Windows, Azure, or Active Directory doesn't enroll the devices. We need easy enrollment for Windows.

Microsoft Intune can be improved by integrating Lighthouse and making it easier for partners to manage customer devices. They have remote help in Microsoft Intune, but they charge a license for it. For partners who manage thousands of devices, they should not charge, as it could be integrated with Lighthouse to provide remote support and better help customers.

It is at times slow. It takes time in the backend whenever we push out enterprise apps or reset devices.

I have been using Microsoft Intune for approximately five years.

Microsoft Intune meets my needs for scaling and is scalable.

It's good. We pay for premium support, so we receive good support.

Positive

We also experimented with Google's solution before choosing Microsoft Intune. The main difference was that Google only supports Chromebook and doesn't handle Windows, so we use Microsoft Intune for Windows.

The return on investment when using Microsoft Intune is good. It has been helpful for us and our customers. 

It's bundled with Business Premium and an E3 license, which is beneficial. If you have to pay extra, it's pricey, but with the bundled package, it's acceptable. They recently increased the Business Premium pricing, which we don't appreciate. The price increase and yearly commitment are causing some problems for us.

We considered TeamViewer. We went for Intune because it is included with our Business Premium licensing, so we don't have to pay extra for it.

I would rate Microsoft Intune an eight out of ten. To make Microsoft Intune a perfect ten, they could provide remote help for partners with Lighthouse, make it easier to enroll all devices, and make it faster.

Our primary use case for Intune has been securing our desktops. We now also use it to secure our servers, which started about a year ago.

Before, we used to reactively track down issues and fix security holes. Now, we're more proactive, stopping threats before they occur rather than reactively removing them afterward. This change helps stop the spreading of security issues.

Intune's integration with Defender and other security solutions is valuable because it offers a view into different security vulnerabilities and enables us to secure them more effectively. It's easy to use. There isn't a huge learning curve. It doesn't take long to get in and figure out where everything is. 

The application management feature's automatic updates help a lot, especially when we need to push updated scripts and apps to our desktops. We can update quickly instead of getting everybody to download and install it. 

Intune's server management could be better. If it could incorporate more features from System Center into Intune's Configuration Manager, it would be beneficial.

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

There are no problems with Intune's stability. 

Scalability is great. We've had no issues scaling it across different environments, managing multiple Office 365 tenants and servers with no problems.

We used System Center Configuration Manager before moving to Intune. It's essentially an upgrade that allows us to manage both desktops and servers.

The initial setup had some issues, primarily with understanding scattered documentation, but it was resolved without much difficulty.

We deployed Intune in-house with our internal IT staff.

We are saving at least two or three hours a day since implementing Intune.

I don't have any information on pricing, setup costs, or licensing.

We did not evaluate other options before choosing Intune.

I rate Intune 10 out of 10.

Our company has consistently used Microsoft products. As the mobile device administrator, I oversaw the transition from Workspace ONE to Microsoft Intune. This decision stemmed from a desire to reduce licensing costs by leveraging existing Microsoft licenses held by all employees, ultimately leading to significant financial savings.

Intune consolidates endpoint and security management tools into a single platform. This centralized approach allows for specialized roles while maintaining a shared understanding of the complete security solution.

Intune's overall user experience is good.

Intune's most valuable feature is its centralized management capability.

The enterprise application management system for mobile devices is effective for app discovery, deployment, and automatic updates. The automatic update feature functions well, eliminating the need for manual updates and individual prompts, which is convenient for both administrators and users.

Intune has made things easier for us because we are using Autopilot to build our laptops.

We've saved a lot of money by moving from Workspace ONE to Microsoft Intune for mobiles.

I've recently started using Microsoft Intune, specifically its mobile device management features. While both Intune and Workspace ONE offer similar functionality, I've noticed that Workspace ONE operates in real-time, whereas Intune has a noticeable delay when deploying policies or apps. The time we have to wait to deploy policies has room for improvement.

People using Intune for Windows deployment, etcetera, can get annoyed because of the Windows updates.

I have been using Microsoft Intune for three months because we've just moved over.

From a mobile perspective, Microsoft Intune has been stable.

From a mobile perspective, Microsoft Intune is easily scalable.

I have contacted technical support only once, and it was very helpful.

Positive

We used VMware Workspace ONE previously. The decision to switch and save on costs was made by the higher-ups.

I would rate Microsoft Intune nine out of ten.

I would definitely recommend Intune to a colleague. It provides a centralized platform for managing various devices, including laptops, desktops, and mobile devices, and seamlessly integrates with other Microsoft solutions like Azure and Active Directory.

We have a team that continuously works on solutions to make workflows smooth, like building laptops and ensuring deployments work smoothly.

Microsoft Intune is deployed across various departments and locations within our local government council. We have different physical sites and departments, and Intune is managed and implemented at the departmental level.

Our team is continuously developing solutions to streamline the laptop production workflow, including assembly, traffic management, and deployment. We also have a separate team dedicated to ensuring the process runs smoothly.

Our use case for Microsoft Intune is managing end-user endpoints, specifically Windows desktops. It is not limited to Windows desktops as it can also manage Mac OS desktops, laptops, and mobile devices for both Android and Apple iOS. 

In terms of needing Microsoft Intune to manage devices, first, there is a requirement that devices must be joined to an Azure domain, either hybrid joined or purely joined. 

From my perspective, purely joined is really the only viable way of setting up an environment. Once devices are joined to Azure, access to Microsoft group policy is no longer available. Because group policy is not accessible in Azure, another way to manage and control devices is necessary. This alternative method uses Microsoft Intune Windows profiles. 

When setting up devices using Microsoft Intune, Windows profiles can be established which perform most of the same functions that Microsoft Group Policy did in a local Windows Active Directory environment. Microsoft Intune can manage and control machines and install software. It allows for Windows provisioning on machines and enables autopilot deployment with pre-packaged installations. When a user receives the machine, sets it up, and turns it on, it connects to the domain and begins installing software, becoming ready within approximately half an hour, which represents a significant time savings for IT departments.

Companies using Microsoft Intune are much better at managing their endpoints with far more visibility. The endpoint inventory is far more accurate and up to date. The Windows versioning for the endpoints is much better, and Windows stays current. Companies not using Microsoft Intune still rely on manual or prior methods of updating and inventorying, which are subject to gaps and inaccurate information.

The Microsoft Intune management console provides visibility into the current status of machines and deployed software. It can automatically update components within its capability, primarily Microsoft products. Third-party software updates, such as VLC media player, are not within Microsoft Intune's update capabilities. Some companies, such as Adobe, have packaged their software to be updatable in Microsoft Intune, though this is more the exception than the rule. Installing software in Microsoft Intune can be challenging if it is not already prepackaged.

The stability and reliability of Microsoft Intune is good. Microsoft takes everything in, and if users stay with Microsoft, everything works together effectively.

Microsoft support for Microsoft Intune is good. In my own use of Microsoft Intune, I did not spend significant time with support because the Microsoft documentation was adequate for our needs.

In a prior environment, when setting up Microsoft Intune, we utilized a third party for assistance. They contacted Microsoft on several occasions, and their needs were answered sufficiently.

We have a couple of companies using other options besides Microsoft Intune. One company is using Avanti Neurons.

I rate the documentation for Microsoft Intune very highly, approximately nine or ten out of ten. One of our companies is beginning to provision and establish a Cloud PK to replace their legacy on-prem ADCS server. 

I used Microsoft Intune extensively in setting up, running, and managing it for several years. In my current role, I don't have hands-on management responsibility for Microsoft Intune as much as responsibility for ensuring it secures the environment from a cybersecurity perspective. 

From an IT infrastructure team perspective, the experience with Microsoft Intune is good, although somewhat complex to navigate initially. From an end-user perspective, the experience is good as long as the infrastructure team has done their due diligence in setting it up to remove any obstacles from the user's setup of their own machine. 

I rate Microsoft Intune a ten out of ten.

In our organization, we use Microsoft Intune for enrolling our end user devices. We handle enrollment and de-enrollment and BitLocker recovery. We manage conditional access policies, configuration profiles, MDM, MAM, and managed endpoint devices such as Android phones, iOS devices, and tablet devices. 

We use Copilot in Microsoft Intune as it is premium-based with licensing. In our organization, we have over 1000 licenses for our end users. If there is any requirement from our end users, we check their approval from their manager and provide Microsoft Copilot licenses. 

We also manage and protect our apps through Microsoft Intune and have protection tools such as DLP, Netscope, and Zscaler. We utilize monitoring features in Microsoft Intune through conditional access policy.

The best features in Microsoft Intune that I appreciate most are its centralized features. There is no concern about managing end user devices. We enroll the user devices through Microsoft Intune and can manage them from anywhere. For instance, if I am in India, I can manage a user device that is available in the USA, Dubai, or any other country. 

I assess the user experience of Microsoft Intune as a very positive experience from our user end because it is user-friendly and manageable, resulting in great reviews from our users.

We use advanced endpoint analytics, which is very useful and protective. That is the benefit of advanced analytics. We use Microsoft Enterprise features. The Enterprise Application Management feature is very useful because we simply configure through policy and do not need to worry about any disturbance or further monitoring. We check the monitor or report sheet, and everything works perfectly and smoothly.

We could benefit from some AI features in Microsoft Intune, and it would be helpful to have some automation features available.

For macOS devices, we use the Jamf portal. I understand that the Jamf portal and server are more secure than Microsoft Intune for macOS. It would be beneficial if there were ways to improve and make it more user-friendly for managing macOS devices.

I have approximately 1.5 years of experience managing and supporting Microsoft Intune.

I would rate it a ten out of ten for stability.

For scalability, I would rate it a nine out of ten.

We are using it at multiple locations. In India, we have about seven offices, and we have multiple offices in UAE and the USA.

Approximately, we have 10,000 users, but at my location, I manage and support about 1,000 users.

Their technical support deserves a rating of ten out of ten.

Positive

It's not complex. It's very user-friendly. It generally takes 24 to 48 hours.

It's a hybrid environment. We use the cloud and on-prem environments.

It doesn't require any maintenance from our side.

It's cheap. It's not expensive. 

As compared to other products, Microsoft Intune is more secure, reliable, and user-friendly. 

I would rate Microsoft Intune a ten out of ten.

My use case for Microsoft Intune is to deploy applications and enroll devices, pushing the apps to the devices.

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

The integration of Microsoft Intune with Microsoft 365 and Microsoft security for cloud and co-managed devices is flawless.

Microsoft Intune works smoothly for discovery, deployment, and automatic updates.

Microsoft Intune helps simplify our IT and security operations as it takes less time, and it's easier to use than SCCM.

Microsoft Intune is flawless for securing hybrid work and protecting data on company and BYO devices.

We are using Microsoft Intune's endpoint privilege management feature. For enforcing least privilege access with Microsoft Intune, we use Entra ID. It restricts unauthorized access, requiring roles to be activated to proceed with necessary tasks, enhancing security.

Microsoft Intune has positively affected my IT productivity, as the decisions made at the enterprise level show it to be a more efficient way than SCCM.

In Microsoft Intune, everything is great. The interface is user-friendly, and the reporting tool works in real-time. Uploading the content is fine as well.

There is room for improvement in server patch management and allowing direct uploads of EXE applications instead of needing to convert them to Intune format, which would save time.

I have been using Microsoft Intune for more than one and a half years.

We have not experienced any issues. I would rate the stability of Microsoft Intune a nine out of ten. 

We have approximately 90,000 devices in our organization. We have multiple locations across various regions of the world. In our IT team, there are about ten people working with Intune, with plans to add more.

I would rate the technical support for Microsoft Intune an eight out of ten.

Positive

Previously, we were using MECM. The reason for the switch to Microsoft Intune is that the organization I work for has migrated to Intune. Microsoft Intune is far more efficient and faster than MECM. The deployment would take a lot of time in MECM; Intune is quite faster.

We are still using SCCM for cloud PKI as it hasn't been migrated.

Deploying Microsoft Intune in the cloud was complex as the previous work needed to be deleted and recreated, which wasted time.

Microsoft Intune saves about 10% to 15% of time. For example, deploying a 2 to 3 GB application at an enterprise level typically takes around one hour to one and a half hours, but with Microsoft Intune deployment, it gets completed in 30 to 40 minutes.

Microsoft Intune saves us around 10% to 15% in resources.

We are using Microsoft Copilot in Intune as an AI tool; it doesn't protect much, but it is handy for our users.

I would recommend Microsoft Intune to other users, especially those using MECM or SCCM, because Microsoft is ending support for older solutions.

Overall, I would rate Microsoft Intune an eight out of ten.