Manage the deception capability in Microsoft Defender XDR


Want to experience Microsoft Defender XDR? Learn more about how you can evaluate and pilot Microsoft Defender XDR.

Applies to:

  • Microsoft Defender XDR
  • Microsoft Defender for Endpoint


Some information in this article relates to prereleased products/services that might be substantially modified before commercially release. Microsoft makes no warranties, express or implied, with respect to the information provided here.

Microsoft Defender XDR, through built-in deception capability, delivers high confidence detections of human-operated lateral movement, preventing attacks from reaching an organization's critical assets. Various attacks like business email compromise (BEC), ransomware, organizational breaches, and nation-state attacks often use lateral movement and can be hard to detect with high confidence in the early stages. Defender XDR's deception technology provides high confidence detections based on deception signals correlated with Microsoft Defender for Endpoint signals.

The deception capability automatically generates authentic-looking decoy accounts, hosts, and lures. The fake assets generated are then automatically deployed to specific clients. When an attacker interacts with the decoys or lures, the deception capability raises high confidence alerts, helping in security team's investigations and allowing them to observe an attacker's methods and strategies. All alerts raised by the deception capability are automatically correlated into incidents and are fully integrated into Microsoft Defender XDR. In addition, the deception technology is integrated into Defender for Endpoint, minimizing deployment needs.

This article gives you an overview of Defender XDR's deception technology, prerequisites, and additional resources.


The following table lists the requirements to enable the deception capability in Microsoft Defender XDR.

Requirement Details
Subscription requirements One of these subscriptions:
- Microsoft 365 E5
- Microsoft Security E5
- Microsoft Defender for Endpoint Plan 2
Deployment requirements Requirements:
- Defender for Endpoint is the primary EDR solution
- Automated investigation and response capabilities in Defender for Endpoint is configured
- Devices are joined or hybrid joined in Microsoft Entra
- PowerShell is enabled on the devices
- The deception feature covers clients operating on Windows 10 RS5 and later in preview
Permissions You must have one of the following roles assigned in the Microsoft Entra admin center or in the Microsoft 365 admin center to configure deception capabilities:
- Global administrator
- Security administrator

What is deception technology?

Deception technology is a security measure that provides immediate alerts of a potential attack to security teams, allowing them to respond in real-time. Deception technology creates fake assets like devices, users, and hosts that appear to belong to your network.

Attackers interacting with the fake network assets set up by the deception capability can help security teams prevent potential attacks from compromising an organization and monitor the attackers' actions so defenders can improve their environment's security further.

How does the Microsoft Defender XDR deception capability work?

The built-in deception capability in the Microsoft Defender portal uses rules to make decoys and lures that match your environment. The feature applies machine learning to suggest decoys and lures that are tailored to your network. You can also use the deception feature to manually create the decoys and lures. These decoys and lures are then automatically deployed to your network and planted to devices you specify using PowerShell.

Screenshot of an attack with lateral movement and where deception intercepts the attack Figure 1. Deception technology, through high confidence detections of human-operated lateral movement, alerts security teams when an attacker interacts with fake hosts or lures

Decoys are fake devices and accounts that appear to belong to your network. Lures are fake content planted on specific devices or accounts and are used to attract an attacker. The content can be a document, a configuration file, cached credentials, or any content that an attacker can likely read, steal, or interact with. Lures imitate important company information, settings, or credentials.

There are two types of lures available in the deception feature:

  • Basic lures – planted documents, link files, and the like that have no or minimal interaction with the customer environment.
  • Advanced lures – planted content like cached credentials and interceptions that respond or interact with the customer environment. For example, attackers might interact with decoy credentials that were injected responses to Active Directory queries, which can be used to sign in.


Lures are only planted on Windows clients defined in the scope of a deception rule. However, attempts to use any decoy host or account on any Defender for Endpoint-onboarded client raises a deception alert. Learn how to onboard clients in Onboard to Microsoft Defender for Endpoint. Planting lures on Windows Server 2016 and later is planned for future development.

You can specify decoys, lures, and the scope in a deception rule. See Configure the deception feature to learn more about how to create and modify deception rules.

When an attacker uses a decoy or a lure on any Defender for Endpoint-onboarded client, the deception capability triggers an alert that indicates possible attacker activity, regardless of whether deception was deployed on the client or not.

Identify incidents and alerts activated by deception

Alerts based on deception detection contain deceptive in the title. Some examples of alert titles are:

  • Sign-in attempt with a deceptive user account
  • Connection attempt to a deceptive host

The alert details contain:

  • The Deception tag
  • The decoy device or user account where the alert originated
  • The type of attack like sign in attempts or lateral movement attempts

Screenshot of a deception alert highlighting the tag and the attempt Figure 2. Details of a deception-related alert

Next step


Do you want to learn more? Engage with the Microsoft Security community in our Tech Community: Microsoft Defender XDR Tech Community.