Microsoft 365 / Intune: enroll Windows devices, configure security, and deploy apps

Microsoft Intune is a cloud service that registers and manages organization PCs and mobile devices, including settings, security status, and work apps. If you are managing Windows devices for the first time, check the license and registration scope, and then proceed in the order: register test devices → deploy security settings → check compliance status → deploy apps. This guide describes a pilot scenario using a Windows 11 PC and explains what to select at each step and where to check the results.

Admin Center and Practice Preparation

Manage devices through the Microsoft Intune admin center, previously called the Microsoft Endpoint Manager admin center. These procedures use English interface labels; follow the named settings if your tenant layout differs.

  • User and licensing: Confirm that managed users have Intune licenses. Automatic mobile device management (MDM) enrollment also requires Microsoft Entra ID P1 or P2; check the relevant licensing separately for Conditional Access. Office apps require appropriate activation licenses as well.
  • Administrator Permissions: Verify whether the Intune roles and scopes can manage the relevant devices, policies, and groups. Just because a menu is visible does not mean all operation permissions are granted.
  • Test Scope: Prepare one test PC and test users/groups approved by the organization. First, check existing MDM management, Windows version and edition, and the backup and recovery methods for important files.
  • Record: Record the device name, serial number, registered users, modified policies and groups, and values before application. Do not assign immediately to all users or all devices.

General support for Windows 10 ended on October 14, 2025. The fact that Intune enrollment is possible is separate from whether the operating system is still receiving security support. For new exercises, use a supported Windows 11 environment, and check the update and support plans separately for existing Windows 10 devices. You can check enrollment methods and requirements in the Windows Enrollment Guide.

Choosing a Device Enrollment Method

Enrollment is the process by which a device becomes connected as a managed object in Intune. Do not assume that enrollment in Intune is complete just because the device appears in Microsoft Entra ID. You need to check the management method, user, and last check-in in Intune's Devices → All Devices.

Method Suitable Situations and Checkpoints
Company Portal This applies when a user proceeds with work-related connection and enrollment. For personal devices, managed information and organizational policies are provided to the user first.
Automatic MDM Enrollment This is when a designated user wants to join or register a device to Entra ID and also connect it to management. The user scope and licenses are important.
Windows Autopilot This is when deploying the initial setup of a new company PC according to organizational standards. Device registration, profiles, groups, and initial setup steps must be prepared.

Register a test device with the Company Portal

The administrator first checks Windows enrollment restrictions, per-user enrollment limits, and the specific user's Intune permissions. Do not arbitrarily disconnect a PC that is already managed by another organization; handle it with the existing management administrator. Simply installing the Company Portal app and logging in is not sufficient; you must complete the app’s device setup and connection procedure.

  1. Install Company Portal from the Microsoft Store on the test PC.
  1. Open the Company Portal and sign in with the organization's company or school account. On the home screen, go to device settings and proceed with Next → Connect, verify the account again, and complete the setup. Read the organization management guidance that appears and return to the Company Portal to confirm the completion status.
  1. The administrator searches for the PC on Devices → All Devices. Do not only look at the name, but also compare the serial number, user, operating system, and management status. Confirm whether the device is displayed on the company portal as well.

If it cannot be found, first check whether the user and organization account are correct and synchronize with the company portal. If there is an error, record the code and time, then check the license, registration restrictions, network, and duplicate registrations. Do not repeatedly start with reinstalling or deleting the device. The screen-by-screen flow can be compared with Windows Company Portal Registration Procedure.

Automatic Enrollment and Windows Autopilot

To enable automatic MDM enrollment, open Devices → Device onboarding → Enrollment → Windows → Automatic Enrollment. Set MDM user scope to Some and choose the pilot group. Confirm that these users have Intune and Microsoft Entra ID P1 or P2 licenses. Keep the default MDM terms of use, discovery, and compliance URLs. Microsoft’s procedure requires Global Administrator for this tenant-level setup; everyday Intune operations should use the appropriate limited roles.

After saving the user scope, perform the join and enrollment procedures set by the organization on a test PC, and check whether it appears in the Intune list. Excluding the scope is a measure to limit future automatic enrollment and should not be treated as an action that automatically unregisters already enrolled devices. For detailed settings, refer to Automatic MDM Enrollment Configuration.

Windows Autopilot helps prepare an organization's device configuration and apps during the initial Windows setup process. Traditional Autopilot registers the device to the service, assigns deployment profiles to target groups, and prepares for automatic enrollment, network, and support editions. It is not the same procedure as installing the company portal on a regular PC. Please conduct deployment tests that require initialization on separate PCs without important data.

Windows Autopilot and Windows Autopilot device preparation are separate deployment methods. Even if the names are similar, do not assume that device identification, policies, or support conditions are the same, and follow the procedures of the method chosen by the organization.

Renaming a company Windows device

The device name should follow the organization's naming rules, like an asset number. For example, a test PC can use an identifiable name such as SEOUL-TEST01. Renaming Windows devices in Intune is intended for company-owned devices and is not supported for Microsoft Entra hybrid joined devices. Hybrid environments should be managed using domain management methods.

  1. Devices → All devices and select the target PC. Verify the device name and serial number to ensure you have not selected another user's PC.
  1. Open the device’s Properties → Edit, then change its name.
  1. Enter according to the organization's naming rules, consult with the user about the restart timing, and then save. If you restart the PC immediately while performing the task, unsaved work may be interrupted.

After confirming that the device is online and has checked in, compare its device action status in the admin center with Windows Settings → System → About. Do not repeat requests merely because the list has not refreshed. To reverse a name change, use a supported method to restore the recorded previous name and restart if required. The management name and Company Portal display name do not all change with it. Review the supported scope of device renaming.

Assess security status with compliance policies

Compliance policies are rules that evaluate whether a device meets the organization's minimum requirements. For example, they can distinguish devices that require antivirus. Antivirus installation/configuration or BitLocker activation should be designed together with the security configuration explained later. The practice below shows the flow of applying antivirus requirements to a test group and checking the results per device.

  1. Go to Devices → Manage devices → Compliance.
  1. Select Create policy .
  1. Select Windows 10 and later and create the policy. This platform option also covers Windows 11.
  1. Enter the target and purpose in the policy name. For example, designate it as TEST-Windows-Antivirus and leave a description that it is a test policy.
  1. Expand the category of compliance settings to check the evaluation conditions. Do not change items that are not covered in the practice to 'required'.
  1. Under System Security → Antivirus, select Require. This evaluates the antivirus product and Windows security status; it does not install antivirus.
  1. Review the schedule and user notifications for marking as non-compliant in the actions for non-compliance. Set the grace period and support procedures for work devices according to the organization’s policy, without adding unnecessary lock or disable actions.
  1. In Assignments, select the pre-prepared test group. Confirm whether it is a user group or device group, and who the actual members are.
  1. On the review screen, check the conditions, actions, and targets again, and then create it.
  1. After synchronizing the test PC, check the device status and the status by setting in the policy. If there are no target devices or they are pending, do not record it as an evaluation completed.

The expected result is the policy arrives on the test device, and the evaluation results of the antivirus requirement are displayed. If it is non-compliant, first check the failed settings in the device details, and examine Windows security status, policy conflicts, and the last check-in. Do not conclude that all devices are safe just by looking at the full pie chart on the screen. For devices with multiple policies, also separately check failures of other policies.

The built-in Mark device noncompliant action defaults to zero days and can be scheduled with a grace period. Blocking resource access requires a linked control such as Conditional Access; creating a compliance policy alone does not impose that restriction. Review creating and evaluating compliance policies and noncompliance actions and grace periods. Validate Conditional Access dependencies and enrollment exclusions in a small pilot before enforcement, so devices can complete enrollment and remediation.

Where do you configure antivirus, BitLocker, and firewall?

Compliance policies assess requirements; configuration policies deploy actual settings. Managing the same setting in multiple configuration profiles and security baselines makes conflicts harder to diagnose. Define which policy owns each setting, and check existing Group Policy and other management tools. See the Intune endpoint security policy overview.

Antivirus

In Endpoint security → Antivirus → Create Policy, select the supported Windows platform and Microsoft Defender Antivirus profile. Review existing antivirus, real-time protection, and update management, then assign required settings to the pilot group. Check per-device policy results alongside actual Windows Security status. Third-party antivirus may behave differently from Microsoft Defender Antivirus as the active antivirus. See Intune antivirus policy requirements and profiles.

Disk Encryption and BitLocker

Create a Windows BitLocker policy under Endpoint security → Disk encryption. Check the Trusted Platform Module (TPM), supported Windows edition, existing encryption, recovery-key backup, and permissions to read that key. Prepare data backups and recovery before assignment. On the pilot PC, verify the policy result and actual drive encryption, then confirm that an authorized administrator can retrieve the recovery key. Unassigning a policy does not decrypt the disk; plan reversal separately. See BitLocker deployment and recovery prerequisites.

Check firewall and policy results

Use Endpoint security → Firewall to manage Windows firewall profiles and rules. Specify the required apps, ports, traffic direction, and network profiles instead of disabling the firewall. In the pilot group, check business apps, virtual private network (VPN) connections, remote support, and per-device policy errors. See the endpoint security policy types for the roles of encryption and firewall profiles.

Connect so that only compliant devices can access

In Microsoft Entra Conditional Access, when requiring devices marked as compliant, you can use the evaluation status from Intune to determine resource access. Conditional Access is not a feature that you turn on via the antivirus settings screen in Intune. It is configured after checking the target users, cloud apps, platforms, and required licenses.

First, according to the testing, exception, and recovery procedures for Conditional Access policies, check the expected impact for reporting only, and inspect actual access with a limited test group. Verify in the sign-in logs whether compliant devices succeed and whether intended restrictions are applied on non-compliant devices. Applying it all at once to all users and all resources without considering emergency access accounts and device enrollment/recovery paths can also block administrative tasks.

Deploy Microsoft 365 Apps to Windows

This practice flows through deploying Microsoft 365 Apps to a test PC registered in Intune. First, check the user's app licenses, the installation method of existing Office, 32/64-bit compatibility, add-in compatibility, and other work being done during installation. Before deployment, guide users to save documents and close Office apps.

  1. Go to Apps → All apps or the Windows app list.
  1. Select Create.
  1. For App type, choose Microsoft 365 Apps → Windows 10 and later.
  1. Confirm the selected app type and press Select.
  1. Enter the name and description of the app bundle. Give it a name so that it can be identified as a test deployment.
  1. Set the installation apps, architecture, language, update channel, etc. Make sure the channel aligns with your organization’s update management method and does not conflict with existing deployment settings.
  1. In Assignments, select the test group. If the goal is automatic installation, choose Required; if you want users to select from the company portal, choose Available, and check which targets and behaviors are supported.
  1. On the review screen, check the product, configuration, and targets, then create it. Allow time for test devices to check in and install.

Check whether to use the configuration designer or XML input. Microsoft 365 Apps for business requires XML data to configure the app suite. Review removal settings for existing MSI-based Office installations: removal affects all existing Office MSI apps, not just the apps selected for installation. Do not enable removal without assessing its impact. Check supported Windows editions and detailed options in the Microsoft 365 Apps deployment guide for Windows.

Creating the policy is not the completion criterion. Check the pilot PC in the app’s Device install status and User install status, then open an assigned app such as Word on the PC and verify activation with the intended account and access to an approved work document. If installation fails, review the error code, last check-in, existing Office conflicts, apps left open during installation, network connectivity, and licensing.

To stop a pilot, remove its group from the app assignment. Removing an assignment or deleting the Intune app entry does not automatically uninstall installed apps. If removal is required, check the supported method and its effect on user data separately. Do not use destructive device actions such as Wipe or Retire as the first response to a policy error.