1. Mobile Device Management (MDM): Intune lets IT teams manage:
Windows PCs
macOS computers
iPhones and iPads
Android devices
They can:
Enforce password policies
Require encryption
Push Wi-Fi/VPN settings
Remotely lock or wipe devices
2. Mobile Application Management (MAM):
Deploy apps to devices
Restrict copy/paste between work and personal apps
Protect company data inside apps (even on personal devices)
This is useful for BYOD (Bring Your Own Device) environments.
3. Security & Compliance
Intune works with:
Microsoft Entra ID (formerly Azure AD)
Microsoft Defender for Endpoint
It can:
Block non-compliant devices from accessing company resources
Enforce security baselines
Monitor device health










1️⃣ Registers the device with the organization
When a user signs in with their work account (Azure AD / Entra ID), the device is automatically enrolled into Intune.
2️⃣ Applies security policies automatically
Examples:
Enforce PIN/password
Enable disk encryption (BitLocker)
Configure firewall settings
Block rooted/jailbroken devices
3️⃣ Installs required apps
Microsoft 365 apps
Company apps
VPN profiles
Wi-Fi configurations
4️⃣ Enables compliance monitoring
Ensures the device:
Has antivirus enabled
Is up to date
Meets company security requirements
5️⃣ Allows remote management
IT can:
Wipe lost/stolen devices
Lock devices remotely
Reset passwords
Remove company data
🔹 When Is It Used?
MDM auto-enrollment is commonly used when:
Joining a device to Azure AD (Entra ID)
During Windows Autopilot setup
When a user logs into a corporate PC for the first time
Enrolling mobile devices into company management
🔹 Why It’s Important
Without auto-enrollment:
Users must manually enroll devices.
Devices might miss security policies.
IT has less control and visibility.
With auto-enrollment:
Zero-touch provisioning
Strong security from day one
Reduced IT workload
Better compliance and auditing
🔹 Simple Example
An employee buys a new laptop.
They sign in with their company email.
The device automatically enrolls into Intune.
Company apps install automatically.
Security settings are applied.
The device becomes compliant.
No IT intervention required.















dsregcmd /status in an elevated command prompt on the PC to verify join and auth health.dsregcmd /status. Verify that AzureAdJoined says YES. Verify that MdmUrl is populated. If it is blank, the device joined Entra but failed to trigger Intune enrollment.
























Join the device with the Intune: When a user signs in with their work account (Entra ID), the device is automatically enrolled into Entra ID and with the configuration of Automatic Enrollment into Intune.
2️⃣ Applies security policies automatically
Examples:
Enforce PIN/password
Enable disk encryption (BitLocker)
Configure firewall settings
Block rooted/jailbroken devices
3️⃣ Installs required apps
Microsoft 365 apps
Company apps
VPN profiles
Wi-Fi configurations
4️⃣ Enables compliance monitoring
Ensures the device:
Has antivirus enabled
Is up to date
Meets company security requirements
5️⃣ Allows remote management
IT can:
Wipe lost/stolen devices
Lock devices remotely
Reset passwords
Remove company data
🔹 When Is It Used?
MDM auto-enrollment is commonly used when:
Joining a device to Azure AD (Entra ID)
During Windows Autopilot setup
When a user logs into a corporate PC for the first time
Enrolling mobile devices into company management
🔹 Why It’s Important
Without auto-enrollment:
Users must manually enroll devices.
Devices might miss security policies.
IT has less control and visibility.
With auto-enrollment:
Zero-touch provisioning
Strong security from day one
Reduced IT workload
Better compliance and auditing
🔹 Simple Example
An employee buys a new laptop.
They sign in with their company email.
The device automatically enrolls into Intune.
Company apps install automatically.
Security settings are applied.
The device becomes compliant.
No IT intervention required.


















| Compliance requirement | Lab 1 |
|---|---|
| BitLocker | Require |
| Secure Boot | Require |
| Code integrity | Require |
| Firewall | Require |
| Antivirus | Require |
| Minimum OS version | 10.0.26200 |
| Password complexity | Require |
| Firewall, TPM, AV, Antispyware, Defender | Require |














































Unlike Win32 apps, which are downloaded and managed by the Intune Management Extension (IME) agent, Line-of-Business (LoB) apps are downloaded directly by the native Windows MDM agent using the Windows OMSettings/DiagnosticLog CSPs and the Background Intelligent Transfer Service (BITS) or Delivery Optimization.
Because all LoB apps are failing to download, the failure is usually caused by one of three specific architectural conflicts:
If you are deploying both Win32 apps and LoB .msi apps to the same devices, they will frequently collide.








Unlike Win32 apps, which are downloaded and managed by the Intune Management Extension (IME) agent, Line-of-Business (LoB) apps are downloaded directly by the native Windows MDM agent using the Windows OMSettings/DiagnosticLog CSPs and the Background Intelligent Transfer Service (BITS) or Delivery Optimization.
Because all LoB apps are failing to download, the failure is usually caused by one of three specific architectural conflicts:
If you are deploying both Win32 apps and LoB .msi apps to the same devices, they will frequently collide.






















| Task | Main portal | Location |
|---|---|---|
| Connect MDE ↔ Intune | Intune | Endpoint security → Microsoft Defender for Endpoint |
| Enable MDE enforcement | Intune | Endpoint security → Microsoft Defender for Endpoint |
| Onboard Windows devices | Intune | Endpoint security → Endpoint detection and response |
| Defender Antivirus | Intune | Endpoint security → Antivirus |
| Defender Firewall | Intune | Endpoint security → Firewall |
| Firewall rules | Intune | Endpoint security → Firewall |
| ASR rules | Intune | Endpoint security → Attack surface reduction |
| Defender security baseline | Intune | Endpoint security → Security baselines |
| EDR configuration | Intune | Endpoint security → Endpoint detection and response |
| Device onboarding/offboarding | Defender | Settings → Endpoints → Device management |
| MDE device inventory | Defender | Assets → Devices |
| Incidents & alerts | Defender | Incidents & alerts |
| Advanced hunting | Defender | Hunting → Advanced hunting |
| Automated investigation/response | Defender | Incidents / device investigation |
| Threat intelligence / indicators | Defender | Settings → Endpoints / Indicators |
| MDE RBAC | Defender | Settings → Endpoints → Permissions |
| MDE security settings management | Defender + Intune | Configuration management / Endpoint security |
If you're sitting in Intune and configuring:
If you're sitting in Defender XDR and looking at:







|
Action |
Result |
|---|---|
|
Remove the device from the assigned group |
The device stops receiving the policy after Intune processes the assignment change. |
|
Exclude the device from the BitLocker policy |
The existing drive remains encrypted. |
|
Delete the BitLocker policy |
The drive normally remains encrypted. |
|
Change the policy to disable BitLocker |
This depends on the policy setting and how it is applied; don't assume it will decrypt the drive. |
|
Manually turn off BitLocker |
Windows starts decrypting the drive. |


Enable Domain Network Firewall True
Default Outbound Action Allow
Default Inbound Action for Domain Profile Block
Enable Private Network Firewall True
Default Inbound Action for Private Profile Block
Default Outbound Action Allow
Enable Public Network Firewall True
Default Outbound Action Allow
Default Inbound Action for Public Profile Block






dsregcmd /status in an elevated command prompt on the PC to verify join and auth health.dsregcmd /status. Verify that AzureAdJoined says YES. Verify that MdmUrl is populated. If it is blank, the device joined Entra but failed to trigger Intune enrollment.