Device Firmware Configuration Interface (DFCI) Management

Applies to:

  • Windows 11
  • Windows 10

With Windows Autopilot Deployment and Intune, you can manage Unified Extensible Firmware Interface (UEFI) settings after they're enrolled by using the Device Firmware Configuration Interface (DFCI). DFCI enables Windows to pass management commands from Intune to UEFI for Autopilot deployed devices. This capability allows you to limit end user's control over BIOS settings. For example, you can lock down the boot options to prevent users from booting up another OS, such as one that doesn't have the same security features.

If a user reinstalls a previous Windows version, installs a separate OS, or formats the hard drive, they can't override DFCI management. This feature can also prevent malware from communicating with OS processes, including elevated OS processes. DFCI's trust chain uses public key cryptography, and doesn't depend on local UEFI password security. This layer of security blocks local users from accessing managed settings from the device's UEFI menus.

For an overview of DFCI benefits, scenarios, and prerequisites, see Device Firmware Configuration Interface (DFCI) Introduction.


Devices enabled for DFCI by the OEM and registered for Autopilot via the OEM or a CSP in Partner Center automatically enroll in DFCI management during Autopilot provisioning. Enrollment in DFCI management triggers an additional reboot during OOBE.

DFCI management lifecycle

The DFCI management lifecycle includes the following processes:

  • UEFI integration
  • Device registration
  • Profile creation
  • Enrollment
  • Management
  • Retirement
  • Recovery

See the following figure.




Devices manually registered for Autopilot (such as by importing from a csv file) are not allowed to use DFCI. By design, DFCI management requires external attestation of the device's commercial acquisition through an OEM or a Microsoft CSP partner registration to Windows Autopilot. When your device is registered, its serial number is displayed in the list of Windows Autopilot devices.

Managing DFCI profile with Windows Autopilot

There are four basic steps in managing DFCI profile with Windows Autopilot:

  1. Create an Autopilot Profile
  2. Create an Enrollment status page profile
  3. Create a DFCI profile
  4. Assign the profiles

See Create the profiles and Assign the profiles, and reboot for details.

You can also change existing DFCI settings on devices that are in use. In your existing DFCI profile, change the settings and save your changes. Since the profile is already assigned, the new DFCI settings take effect when next time the device syncs or the device reboots.

To identify whether a device is DFCI ready, you can use the following Intune Graph API call:


For more information, see Intune devices and apps API overview and Working with Intune in Microsoft Graph .

OEMs that support DFCI

Other OEMs are pending.

See also

Microsoft DFCI Scenarios
Windows Autopilot and Surface devices