What is your primary use case for Microsoft Endpoint Manager?

I work exclusively with Microsoft products, and we use the E3 license for Office, for the Microsoft portal, which includes some security solutions, SharePoint, and Office applications. Microsoft Intune is mandatory in our business. I work with Microsoft Intune as an integrator, user, and administrator. The major purpose for using Microsoft Intune is enforcing policies, controlling onboarding processes of computers, and enforcing privacy and data link prevention. I am using Microsoft Copilot in Microsoft Intune. I am using the Enterprise Application Management feature in Microsoft Intune Suite.

We are using Microsoft Intune to check device compliance issues, enrolling, patching policies, and deploying applications in end-user devices. We check device status in our Microsoft Intune portal. We are using managed policies through Microsoft Intune. We deploy applications through Microsoft Intune. We deploy Windows versions and patches through Microsoft Intune.

My use case for Microsoft Intune includes managing a fleet of about close to 800 laptops and another 500 mobile phone devices like iPhones. We migrated to Microsoft Intune to control and reduce the MSP cost, as our provider was very old-fashioned. As the solution architect, I create plans to ensure cost reduction and process efficiency, particularly regarding Windows patching. There wasn't any visibility regarding our devices. Most of the time, we couldn't tell which devices were turned on and which weren't. This lack of clarity resulted in delays with patches, as some devices were not powered on. Overall, it was a mess. To address this issue, we centralized everything into Intune, and we've been handling the patching process since last year. Additionally, we removed Bitdefender and whatever version we were using, and we implemented BitLocker. From Microsoft Intune, everything is automated. If you need to get the keys, it's super easy for users to obtain them, and someone from IT should also be able to access them. We use Intune because it supports a hybrid environment, allowing us to manage both on-premises devices and our cloud-based services. This means we can still utilize our Active Directory organizational units (OUs) through Microsoft Intune's policies. Eventually, we plan to migrate everything to Microsoft Intune. However, if we acquire another company that is behind in technology, we might still leverage the traditional Active Directory approach. This would involve integrating their domain into ours, while at the same time continuing to use Microsoft Intune. We work in the agricultural supply chain, but we prioritize technology. We have the world's fastest terminal for grain loading and unloading, located in Vancouver, Canada. We operate our own trains and are responsible for nearly 20% of Canadian grain exports.

We have an auto-enrollment process. There are many features in Microsoft Intune. Particularly, my expertise is with Autopilot enrollment and app deployment to workstations and mobile device management. Microsoft Intune is quite comprehensive in its capabilities. My main use cases revolve around supporting customers who have enrollment processes for laptops that come out of the warehouses. We support that and push packages, set up conditional access, and manage their devices from Microsoft Intune. We handle reset, reboot, deploying app software and deploying apps such as Microsoft 365, any kind of third-party software, Microsoft products, and removing them from an operations point of view. We are a managed service provider for many technologies, and Microsoft Intune is one of them.

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.

Microsoft Intune was used by the organization that hired me. Microsoft Intune allows organizations to manage all devices. It is a cloud-based service that helps organizations manage and secure their devices such as laptops, smartphones, and iOS devices. We primarily used it for managing applications through mobile application management (MAM) and mobile device management (MDM). Device enrollment is another purpose of Microsoft Intune which automatically configures devices within the organization with their work accounts. In the Microsoft Intune company portal, there is an option to develop and deploy applications that are trusted by the company. Additional use cases include compliance, conditional access, and endpoint security. To summarize, the main purposes are MDM for laptops, mobiles, and iOS devices; MAM; device enrollment; app deployment; compliance and conditional access; and endpoint security. I had access to compliance and conditional access, endpoint security, device enrollment, MDM, and MAM. App deployment was not part of my responsibilities.

It depends on the use case and what the client is looking for in terms of requirements. They will share the requirements with us, and we will check the feasibility of the solutions and then propose which MDM will be best suited for the client. If they only ask for managing their barcode devices or POS devices, we can go with SOTI. When managing smartphones or applications, Microsoft Intune is a good solution. We are combining Microsoft Intune with SOTI, Workspace ONE, and Microsoft Intune.

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 main use cases are that we are using Microsoft Intune in a co-management environment. We do have SCCM also in place, but currently we are managing limited workloads shifted to Microsoft Intune, such as configuration policies, and all devices are enrolled in Microsoft Intune. The patching is still going on from the SCCM end, but we are planning to migrate the patching workload to Microsoft Intune in the near future. Application deployment is currently under plan and I'm testing some use cases. There are many add-ons Microsoft has added in the Microsoft Intune suite so that we can have multiple third-party patches. We can package applications in a quicker time as part of the plan.

Microsoft Intune is a very good product from Microsoft, and it has been used to manage endpoint devices and their security. You can do everything in Microsoft Intune except third-party app patching, which Ivanti gives you the liberty to do. Normal Windows updates and everything can be done by Microsoft Intune. On Microsoft Intune, you have very limited options, but it is very dynamic. When discussing the packaging part, for example, if you want to deploy Chrome in your environment with settings that prevent users from opening incognito mode, you can do it through Ivanti by writing a couple of scripts. You can also do it with Microsoft Intune, but you have to change the package from EXE or MSI to .intunewin. That is a crucial part. Without changing it, you cannot deploy it, so that's a limitation from the Microsoft Intune side. It also gives us an opportunity to learn something extra, making it a good product.

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.

Microsoft Intune has been used in organizations ranging from US entities to Indian companies, with onboarding of systems in numbers ranging from 300 to over 7,000. We migrated from on-premise Active Directory to Microsoft Intune during COVID for remote work support.

I enrolled devices with Microsoft Intune and applied policies and pushed applications. The main use cases for Microsoft Intune involve device management and policy implementation.

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

Mainly, the use cases I get are device migration and completely applying Microsoft Intune policies, security policies, Intune patches, deployments of applications, etc. I work as a consultant, and I guide companies. I consult companies on moving from one platform to another, specifically focusing on complete migration to Microsoft Intune. I have used the Microsoft Intune suite cloud PKI. I am using Microsoft Co-pilot for my use but have not used it for customers.

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

I use Microsoft Intune ( /products/microsoft-intune-reviews ) for mobile device management. My team is specifically responsible for managing mobile devices. Recently, we migrated all our devices to Intune ( /products/microsoft-intune-reviews ) from AirWatch. At my company, we are also utilizing Intune to manage desktops, laptops, and MVD devices.

I use Microsoft Intune ( /products/microsoft-intune-reviews ) on corporate devices as well as bring your own devices. It is always within an enterprise environment. I deal with industries such as manufacturing and health.

We use Microsoft Intune for our mobile devices, including tablets and mobiles, across both iOS and Android. Our intention is to eventually use Intune to manage our laptop estate as well.

We use Microsoft Intune ( /products/microsoft-intune-reviews ) for managing devices, deploying applications, and asset management.

I use Microsoft Intune to manage devices and Windows, including Linux and macOS. It provides a zero-touch experience for provisioning mobile devices like iOS, iPad, Android, and macOS. It offers security and serves as a management tool where multiple products can be managed.

I started using this solution in the summer of 2021. It was three years ago, and I remember it was to deploy new computers. I aimed to get a brand new laptop with the processing system entirely configured and ready to work with applications deployed.

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.

I use Microsoft Intune to enroll devices and monitor them. Sometimes, I need to wipe a device or reset it remotely. We use it in the retail industry for around a thousand enrolled devices.

I use Microsoft Intune to Autopilot our devices and manage various configuration policies mainly on Windows PCs. It helps in efficiently deploying company configurations remotely.

We use Intune for security or endpoint inside the company and especially for many customers we have.

We primarily use Microsoft Intune for managing laptops, cell phones, and mobile devices. We aim to have control over corporate data when it is on personal or company-owned devices. This control is crucial for ensuring data protection, especially when a device is lost or goes missing.

The primary use case is endpoint management.

We are using Intune for managing endpoint devices with zero-trust principles. The devices are not domain-connected because most people work from home. We do not trust these computers, so we use Intune to deploy and enforce policies related to updates, software installation, and management of admin users. When we are using Microsoft products on mobile devices, we are using Intune to enforce policies on them. Our usage is very simple. We are using Intune to manage devices that we do not trust. We are using Windows 365, and we install all applications only on these virtual PCs in the cloud. We do not have anything on endpoint devices. Not even a simple document can be downloaded there. We just have an access point to Windows 365 machines in the cloud. We are a financial company. There are not too many enterprise applications that we can use. We prefer to use zero trust. This means no there is no data on company devices at all. It is only on the cloud machines. It is easier to control one perimeter than 10,000 or 20,000 machines. We can reduce the attack surface in this way.

I use it for deploying software and managing devices.

My last job was cyber defense for clients in European countries like France, Belgium, Sweden, etc. We use Intune to manage definitions for Microsoft Defender and classic corporate reasons, such as limiting the access of Active Directory users. My current company supports clients using Office 365. We're one of the biggest service providers in Bosnia Herzegovina. We use it to deploy enterprise applications to specific users.

We use Intune for endpoint management to ensure they are updated with the latest patches. We also leverage Intune to oversee our applications and keep them current. Lastly, we employ Intune's remote tools for endpoint administration. We implemented Intune to ensure our endpoints were updated.

We use Microsoft Intune for both application management and deployment for new users. Applications are packaged within Intune and then deployed to the end user's machines or devices, specifically targeting designated user groups.

We use the solution for BYOD, MDM, and to access Microsoft applications like Teams. Microsoft Intune helps us access Microsoft applications on the road and mobile.

I used Microsoft Intune for compliance policies, configuration policies, and Intune enrollment. We implemented Microsoft Intune to manage mobile devices in bulk and enforce management policies. Intune was deployed in a hybrid environment. Devices were initially onboarded to Azure Active Directory and then enrolled in Intune. All devices originated from a local Active Directory.

We use Intune to manage more than 5,000 endpoints. It has many powerful tools that enable an organization to manage its devices and applications securely. The main capability is mobile device management (MDM), which allows you to manage hardware and mobile applications. I'm also working with application management. That lets you manage deployments, protections, renewals, identities, and device integration.

We use Intune to manage devices and configurations on all platforms, including Windows, iOS, iPad, and Android. It also provides conditional access from the Azure portal. We have also used Intune to bifurcate data and data transfers. We have an Intune entry list that shows the device count and bandwidth of each, so we can manage the data flow from every device based on whether it's corporate or personal.

You can use Intune to manage devices for any size project, from a small business to an enterprise-level project. You can manage hundreds of thousands of devices. Intune can manage on-prem and cloud services. We are working with large enterprises mostly.

I am using Microsoft Intune for a trading company, Where I need to establish a secure administrative role for this product. We utilize Intune to manage Android, iOS, and Windows devices. We use it primarily to secure devices, deploy applications, and enforce security policies. Additionally, when employees leave the company, we can remotely wipe devices or applications, especially if personal devices are used for business purposes.

We use Microsoft Intune to manage mobile devices across almost all platforms, including Android, Windows, and Linux, which was recently added just a few months ago. Previously, we relied on on-premises infrastructure using SCCM to manage mobile devices alongside other tools. Intune is a cloud-based solution that empowers administrators to manage cloud devices, implement policies, and deploy applications. While other MDM platforms exist, Intune is a top choice due to its feature set.

Around 90 percent of our platforms are in the cloud, and our company uses them to manage access to various platforms. In our company, what we used to do when we were on an on-premises setup was to use group policy to basically manage access and authorizations to various services, which can be quite challenging because not everything you want to do on GPO even though it is available in it. You can use or manage VBScript and PowerShell, but it was a bit challenging. With Microsoft Intune, you already have specific processes and platforms that have several things you can do with it in terms of security and in terms of making everything standardized, sort of a standard desktop, or even a customized one based on the user's job title, ranging from executive management to basic back-end staff. Microsoft Intune allows you to customize everything, like security, the availability of some features, and even updating particular systems or where and which system can access which service from a geographical location, which we couldn't do with GPO. Microsoft Intune allows us to be very flexible.

We use Microsoft Intune to manage our computers and users and enforce organizational policies on the computers. We wanted to remove our in-house service and move device management from on-premise to the tool. This helped us manage devices for staff who don't come to the office across locations. Before, when we had policy changes, they weren't always applied or enforced for remote staff in time. We needed a better solution, and Microsoft Intune worked well for our needs.

We use the solution for endpoint management for about 15,000 devices. It helps us ensure compliance and security for our devices according to standards. We also use it for application management, security and compliance, and centralized management from a single point. So, it covers endpoint management, app management, and compliance management and provides centralized control.

We use Microsoft Intune for device and identity management, providing end-user support, determining device hardware placement, collecting diagnostic logs, deploying patches, distributing software and feature updates, and managing quality rings. This platform enables us to manage over 20,000 devices across our organization effectively.

Our organization utilizes Microsoft Intune to safeguard company data on employee laptops and cell phones that might be used for remote work. We use Microsoft Intune to ensure compliance on devices, both on and off-site. Intune enforces settings like requiring a screen lock and allows us to remotely wipe lost devices to protect sensitive company information.

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.

We are using it for the endpoint deployment piece. By implementing Intune, we are trying to get everything off on-prem.

We control the endpoints and push the software. We also manage the patch schedule, quality updates, and feature updates. We use pretty much everything that is offered within Intune.

Our primary use of Microsoft Intune is for device management and improve security. Initially, it focused on management for Windows devices. However, over time, its capabilities have expanded to encompass mobile device management in general, as well as management for other platforms like iPO, Android and Mac OS devices. To ensure our devices are manageable regardless of location, we transitioned from an on-premises device management solution to Microsoft Intune. This cloud-based approach allows us to manage devices from anywhere, eliminating the need for them to be on our company network or VPN. Intune empowers us to remotely take actions on devices, including software installation, user identification, performance checks, and even triggering a remote lock if a device is compromised.

I use Microsoft Intune to manage mobile devices and enforce security policies.

We are using Microsoft Intune for personal devices, specifically for mobile devices with Android, iOS, and Windows. We have applied the policies over there for device restriction and compliance. We also have a few policies related to Microsoft Defender.

I worked with Microsoft Intune in my level two support role. My tasks included license assignment and assisting users with configuration issues, especially in mobile device management for iOS and Android devices.

We use Intune to manage endpoints as a centralized enterprise solution. Instead of relying on Active Directory or an on-premise system, we directly manage employee devices using Microsoft Intune. Intune, a cloud-based SaaS product, simplifies endpoint management. From a user perspective, it's an improvement. Users no longer need to be on the office network. They can set up their devices anywhere with an internet connection, whether at home or another location. Security is also enhanced. By using Intune as a mobile device management solution, we can implement security controls and restrictions on endpoints. Intune helps us achieve a balance between user experience and security.

We use Intune for Windows computers, and we also have iOS phones.

Microsoft Intune serves as our central platform for device management, ensuring timely patching and secure access through conditional controls. We leverage Intune to automate device onboarding, ensure patch deployment and device compliance, and generate compliance reports. We prioritize patching devices identified as non-compliant through these reports.

We use Microsoft Intune to secure and control our notebooks and mobile devices. Intune is deployed as SaaS.

Currently, we are using Intune to manage our iOS devices. We are planning to extend its use to our Windows computers. Initially, the immediate need was for a Mobile Device Management to support the iOS platform, and Intune fulfilled that requirement.

We use it for device compliance and posture, application control, and we use it for integration with our corporate devices.

We use Microsoft Intune to manage our corporate devices such as mobile devices.

I use Microsoft Intune for my Active Directory and my end-point and zero-day protection.

We propose Intune for information protection. We integrate Intune for application management and protection of company information on mobile devices.

We use the solution for endpoint management, which includes security and compliance.

We are replacing AirWatch MDM with the product so that we can manage our devices. Eventually, we plan to migrate from SCCM, Windows, and Mac to the Microsoft Intune environment. It will help different departments to manage devices from one place.

When we develop, it's used for multiple different solutions. It could be anything, such as a portal, field services, web development, web apps, and lots of other different things.

We primarily use Microsoft Intune for device management and application management. It allows us to control and restrict user access, preventing data sharing and leakage. Additionally, we utilize it for endpoint management of Windows and Mac devices, ensuring their security and compliance.

We use the solution for information and protection. The solution identifies anything that can be exploited.

We use Microsoft Intune to manage desktop, mobile, Apple, and Windows devices.

I'm using all the services that Intune provides, including managing Windows 10 devices and mobile devices, with both the mobile application management and without enrolling the devices. I use it for deploying configuration profiles, compliance and app protection policies, as well as onboarding Windows 10 devices to the Defender portal.

The primary use case is to safeguard the company's data. My management wanted to categorize the applications and ensure privacy and security in terms of corporate applications versus personal applications on corporate devices. We began to prioritize B objectives in 2013 and 2014, which is why it is essential for the organization to prioritize its categorization. To accomplish all of these objectives, we embarked on a successful journey.

We're an MSP, and our primary use case is for fleet management; our entire fleet is handled through Intune, so all our mobile devices are logged in through the Azure portal, and we can manage our apps that way. We've been able to lock down our devices and control our field of frontline workers.

The primary use case of Microsoft Intune is for patch management and app deployment. Microsoft Intune is deployed in a hybrid environment and we use Atel cloud.

We are currently using Intune, and we are also deploying it for customers. We use Intune to manage our mobile devices. We manage our Android and iOS devices with it, and at the same time, we also use Intune to manage our macOS and Windows devices. During the pandemic, there were devices that we couldn't control. For example, we wanted to manage BYOD and make sure that they are secured so that when they access our corporate resources, our data, computers, users, and mobile devices are protected. We use Intune to publish some of our company applications and at the same time push down our restriction policy and configuration profiles, such as VPN.

It is used mainly for application deployment. We are using it in our company and we also recommend it to our customers.

Microsoft Intune is used for Mobile Device Management. We enrolled our mobile devices as well as the mobile device solution for corporate devices. We have a lot of policies such as the compliance policy, and the conditional access-based policies for the corporate mobile user and we use the solution to assign their Outlook Teams and other configurations for the organization. We use Intune to design compliance policies that apply to corporate devices and to wipe data from devices when users are terminated. Intune is also used for mobile-based solutions, but we have recently explored its capabilities by using the Autopilot feature. With Autopilot, Windows 10 devices can be reset and new versions of Windows 10 can be deployed from Intune.

We are going to use Intune for registration and then we're going to use some kind of condition policies for resource access for unmanaged devices. With on-prem AD-based access, when the users are working from home or somewhere else, they need to connect to the VPN or something to access the corporate network, whereas, with Azure and Intune, we are going to provide the resources for application access. We can directly provide them access by using conditional policies. It has been only three months since we took the Azure subscription and migrated all the users to it. We are running it in the production environment. We are not running it in the testing environment. We are not implementing everything in one go because if any issues happen, it's not easy to roll everything back in minutes. For this reason, we're implementing them one by one.

I'm an IT manager contracting with a European company. We had to onboard Windows machines to the Azure AD, but they did not have an on-prem AD. I prepped the Azure AD on the cloud, and I started to migrate the laptops to Azure AD. Once that is done, we need to apply policies, but group policies will not run from Azure AD because there's no on-prem AD to derive the policy from. Intune comes in handy there. It has multiple capabilities. You can create your configuration profiles in Intune that apply to Windows and Mac. You can create security profiles and configuration profiles, and you can apply browser settings to some extent. It isn't a small tool in terms of size or breadth of capabilities. It's very capable. Anybody who has used SCCM will see a lot of similarities.

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.

Generally, the top three uses are operating system deployments, software updates and patching, and software deployments to endpoints.

Microsoft Endpoint Manager is simply a desktop, a laptop, a smartphone, or a tablet. An endpoint is exactly what it sounds like. Microsoft, on the other hand, makes use of that tool. Endpoint allows you to deploy the operating system level. It enables the packaging and deployment of applications. It enables you to secure systems with BitLocker and incorporate things with Active Directory. We are a consulting firm. Our clients use it to simplify desktop builds and to maintain the patch management on their servers and desktops, as well as to have an easy mechanism for both rolling out BitLocker, which is a Microsoft tool and publishing new updates for their various software packages.

We primarily use the solution for both deployment and operating system deployment, and also as security for patching.

We are deploying and rolling all kinds of devices - our laptops, our tablets, our smartphones. We are using it locally here in Holland, in the Netherlands, and we are expanding the use to all business units abroad.

Effectively, we are using Microsoft Endpoint Manager, which is a mix of Intune and CCM. I'm not sure if there's a specific category for that. We are using it mainly for the office workers, for the regular laptops. On top of that, we got our fairly specialized devices on our factories, such as the tag down Zebra Scanners, the RealWear glasses - the augmented reality ones and the kiosks as well. Those are the main use cases.

We use Microsoft Endpoint Manager for patch management and software and application deployment. We also use it to engage with the user to be flexible and encourage them to use our organizational tool in their home or country, along with Microsoft 365 features and VDI.