How to Hide EULA During Windows Autopilot Deployment in Intune

Open your web browser and navigate to the Microsoft Intune admin center. Sign in with your administrator credentials that have the necessary permissions to manage Autopilot profiles.

https://endpoint.microsoft.com

Once logged in, you'll see the main dashboard. The interface has been reorganized in recent updates, so we'll navigate to the correct location for Autopilot deployment profiles.

From the main dashboard, navigate to the Autopilot deployment profiles section. Microsoft has reorganized this location in recent updates.

Follow this navigation path:

1. Click Devices in the left navigation panel
2. Select Windows from the submenu
3. Choose Device onboarding
4. Click Enrollment
5. Select Windows Autopilot Deployment Profiles

This section displays all existing Autopilot deployment profiles in your tenant. You'll see columns for profile name, platform, enrollment type, and assignment status.

You can either modify an existing deployment profile or create a new one specifically for hiding the EULA. For this tutorial, we'll create a new profile to demonstrate the complete process.

Click Create profile and select the appropriate deployment type:

• User-driven: Most common for standard deployments
• Pre-provisioning: For White Glove scenarios
• Self-deploying: For kiosk or shared devices

For this example, select User-driven as it's the most commonly used deployment type.

Fill in the basic profile information:

Name: Hide EULA Autopilot Profile
Description: Autopilot profile configured to hide EULA during OOBE
Convert all targeted devices to Autopilot: Yes (recommended)

This is the critical step where we configure the profile to hide the End User License Agreement. On the Out-of-box experience (OOBE) settings page, locate the Microsoft Software License Terms setting.

Configure the following OOBE settings:

Microsoft Software License Terms: Hide
Privacy settings: Hide (optional but recommended)
Hide change account options: Yes
User account type: Standard
Language (Region): Operating system default
Automatically configure keyboard: Yes
Apply device name template: No (or configure as needed)

The key setting is Microsoft Software License Terms: Hide. This setting has two options:

• Show: Users will see the EULA during OOBE (default behavior)
• Hide: EULA is automatically accepted and hidden from users

Additional recommended settings for a streamlined experience:

• Set Privacy settings to Hide to skip privacy configuration screens
• Enable Hide change account options to prevent users from switching account types during setup

Configure how devices will join your organization's directory. This setting determines the authentication and management method for deployed devices.

On the device join settings page, configure:

Join to Microsoft Entra ID as: Microsoft Entra joined
(Alternative options: Microsoft Entra hybrid joined, Microsoft Entra registered)

Choose the appropriate join type based on your environment:

For most modern deployments, Microsoft Entra joined is the recommended option as it provides full cloud-based management without requiring on-premises domain controllers.

Review all the configuration settings before creating the profile. This is your opportunity to verify that all settings align with your deployment requirements.

The review page should show:

Profile name: Hide EULA Autopilot Profile
Deployment mode: User-driven
Join type: Microsoft Entra joined
Microsoft Software License Terms: Hide
Privacy settings: Hide
Other OOBE settings: As configured

If everything looks correct, click Create to save the deployment profile. The profile will be created and added to your list of available Autopilot deployment profiles.

After creation, you'll see the profile in the main list with a status indicating it's ready for assignment.

Now assign the newly created profile to the appropriate device groups. This determines which devices will receive the EULA-hidden experience during Autopilot deployment.

From the deployment profiles list, select your newly created profile and click Assignments. You have several assignment options:

• All devices: Applies to all Autopilot-registered devices
• Selected groups: Applies to specific Microsoft Entra device groups
• All users: Applies based on user group membership

For targeted deployment, create or select a device group:

Assignment type: Selected groups
Included groups: Autopilot Devices - EULA Hidden
Excluded groups: (none or specify exceptions)

To create a dynamic device group for Autopilot devices, use this membership rule:

(device.devicePhysicalIDs -any (_ -contains "[ZTDId]"))

This rule automatically includes all devices registered in Windows Autopilot.

Test the configuration with a device to ensure the EULA is properly hidden during the Autopilot deployment process. This verification step is crucial before rolling out to production devices.

To test the deployment:

1. Ensure you have a test device registered in Windows Autopilot
2. Reset the device to factory settings or boot a new device
3. Connect to a network with internet access
4. Proceed through the initial setup screens

During the OOBE process, monitor for these behaviors:

Expected behavior:
- No EULA/License Agreement screen appears
- Privacy settings screen is hidden (if configured)
- Device automatically proceeds to sign-in
- Autopilot profile downloads and applies automatically

If the EULA still appears, check these common issues:

• Profile assignment: Verify the device is in the assigned group
• Network connectivity: Ensure internet access during OOBE
• Profile sync: Allow 15-30 minutes for profile propagation
• Device registration: Confirm the device is properly registered in Autopilot

After deploying the profile, monitor device deployments and address any issues that arise. Proper monitoring ensures consistent user experiences across all Autopilot deployments.

Monitor deployment status through multiple channels:

Intune Admin Center:
Devices > Windows > Windows enrollment > Devices

Autopilot deployment reports:
Reports > Windows Autopilot deployments

Device-specific logs:
Event Viewer > Applications and Services Logs > Microsoft > Windows > Provisioning-Diagnostics-Provider

Common troubleshooting scenarios and solutions:

For advanced troubleshooting, collect Autopilot logs using:

Get-AutopilotDiagnostics -OutputPath C:\AutopilotLogs