Microsoft 365 Licensing

Defender for Identity license: which plans include it

Defender for Identity license: which plans include it. Microsoft 365 Licensing article banner on grbadhon.com

A Defender for Identity license is sold per user, yet the service cannot be aimed at only some of them. Microsoft’s own service description says the features are enabled at tenant level for every user, so a plan to license the domain admins and leave everyone else out does not match how the product works. This post lists the plans that carry the right today, where two Microsoft pages disagree on the bundle names, and what the sensor needs on your servers before the licence does anything.

It sits under how the Microsoft 365 licensing pieces fit together, and for most organisations the question arrives as part of the Microsoft 365 E3 vs E5 decision rather than as a separate purchase. I have not run Defender for Identity in production; my tenant is a lab with no enrolled devices and no domain controllers, so what follows is Microsoft’s documentation, read on 5 November 2026, plus where I would expect it to bite.

Which plans include a Defender for Identity license

The Microsoft Defender service description on Microsoft Learn is the page to start from. Its Defender for Identity section, in a version updated on 3 November 2026, describes the product as a per-user subscription license available standalone and inside a short list of plans. The sensor deployment pages carry their own licensing list. Both are below, as each page states them today.

Defender service description (updated 3 Nov 2026)Sensor deployment pages (v3.x updated 20 Oct 2026)
Enterprise Mobility + Security E5/A5Enterprise Mobility + Security E5 (EMS E5/A5)
Microsoft 365 E5/A5/G5Microsoft 365 E5 (Microsoft E5/A5/G5)
Microsoft Defender Suite/EDU/GOV/FLWMicrosoft 365 E5/A5/G5/F5 Security
Microsoft Defender + Purview Suite FLWMicrosoft 365 F5 Security + Compliance
Microsoft Defender for Identity for Users (standalone)A standalone Defender for Identity license (listed on the v2.x page, not on the v3.x page)

Two plans are missing from both columns. Microsoft 365 E3 is not there, and neither is Microsoft 365 Business Premium. If a tenant runs on either, Defender for Identity is a separate purchase or part of a step up, which is the gap Business Premium vs E5 works through for smaller organisations.

The F5 rows carry a condition on the deployment pages: both F5 licences require Microsoft 365 F1 or F3, or Office 365 F3, and Enterprise Mobility + Security E3. An F5 Security add-on on its own is not the whole entitlement.

Two Microsoft pages, two sets of bundle names

The columns above do not line up, and that is the first thing to settle before a renewal. The service description names the Microsoft Defender Suite and the Microsoft Defender + Purview Suite FLW. The sensor deployment pages, updated in June and October 2026, still name Microsoft 365 E5 Security and Microsoft 365 F5 Security + Compliance, and do not mention the suites at all.

I am not going to guess whether one set of names replaced the other. Neither page says so. What I take from it is narrower. The service description was updated this week and is the page written for licensing; the deployment pages exist to get a sensor running. Read your agreement against the service description, and treat the deployment page list as a prerequisite check rather than a buying guide.

The sensor v2.x prerequisites page lists the same four bundles as the v3.x page and adds a standalone Defender for Identity license. The v3.x page drops that standalone line. I would not read that as the standalone offer going away, because the service description, updated later, still lists Microsoft Defender for Identity for Users.

Per user, but switched on for everyone

The service description is direct about this. Defender for Identity features are enabled at the tenant level for all users within the tenant, and the page says some tenant services, Defender for Identity among them, are not currently capable of limiting benefits to specific users.

That has two consequences. First, there is no technical control that keeps unlicensed users out of scope, so the licence count is a compliance question, not a configuration one. Second, the people who benefit are not only the analysts who open the Microsoft Defender portal. The service description says end users benefit by having their data monitored, which is why counting only the security team understates what the agreement expects.

How users are counted under your agreement is set by the Product Terms the service description links to, not by a blog post. I would check that wording with whoever owns the agreement before settling on a standalone count.

Standalone or bundled: where the decision really sits

The standalone Defender for Identity license makes sense in a narrow case: a tenant on Microsoft 365 E3 or Business Premium that runs on-premises Active Directory and wants identity threat detection without moving the whole estate up a tier. Everywhere else the bundle question decides it.

  • Already on Microsoft 365 E5 or EMS E5. The right is already there. The work is deploying sensors, not buying anything.
  • On Microsoft 365 E3 with a wider security gap. Defender for Identity is rarely the only thing missing. Compare the standalone cost with a security bundle that also brings Defender for Endpoint Plan 2, and price both against your own quote.
  • No domain controllers or identity servers. The sensor runs on domain controllers and on AD FS, AD CS or Microsoft Entra Connect servers. A tenant with none of those has nowhere to put a sensor, so check what you would actually feed the service before paying for it.

Prices are left out on purpose. They vary by agreement, channel and region, and a figure I cannot check against your quote is one I will not print.

The newsletter

Get the next licensing fix like this one by email

Subscribe and get the free 8-page Intune troubleshooting field guide (PDF), then new fixes about twice a month. From a Microsoft MVP.

Free. Confirm by email, unsubscribe in one click. Privacy.

What the licence does not give you: sensor prerequisites

A Defender for Identity license grants the right. Detection only starts when a sensor runs on your identity servers, and the Defender for Identity sensor v3.x deployment page, updated on 20 October 2026, sets the bar for that. According to that page, the server you activate the v3.x sensor on must:

  1. Be onboarded to Defender for Endpoint, with Microsoft Defender Antivirus in active or passive mode. For eligible servers the page also describes v3.x onboarding without a Defender for Endpoint deployment.
  2. Not already have a v2.x sensor deployed.
  3. Run Windows Server 2019 or later.
  4. Have the September 2026 cumulative update or later installed, which brings sensor version 3.0.10 or later.

The v3.x sensor supports domain controllers, and servers that are not domain controllers but run AD FS, AD CS or Microsoft Entra Connect. If you deploy it only on those identity servers, the page says you must also install at least one v3.x sensor on a domain controller. It lists three limitations of v3.x: no VPN integration, no syslog notifications, and limitations with Azure ExpressRoute.

The v2.x prerequisites page recommends v3.x for servers on Windows Server 2019 or later. Domain controllers older than that cannot meet the v3.x requirement, so an estate with older domain controllers will run v2.x on them. That is a deployment cost the licence line does not show.

Defender for Identity license failure modes

  1. Licensing only the admins. The service description says the benefits cannot be limited to specific users. Buying a handful of standalone seats for the domain admins does not narrow what the service watches.
  2. Assuming E3 covers it. Microsoft 365 E3 is not on either list. Neither is Business Premium.
  3. An F5 Security add-on without its base. Both F5 entries require F1 or F3, or Office 365 F3, plus EMS E3. The add-on alone does not meet the condition the deployment pages state.
  4. Licence bought, sensor blocked. A domain controller that is not onboarded to Defender for Endpoint, or is missing the September 2026 cumulative update, cannot activate the v3.x sensor. The licence is on the invoice and nothing is being monitored.
  5. Sensors only on AD FS or Entra Connect. The v3.x page requires at least one v3.x sensor on a domain controller when identity servers are covered.

What I would do differently

I would read the bundle name off the agreement before reading any comparison page, including this one. With two Microsoft pages naming different bundles in the same month, the SKU on the paperwork is the only list that matters for your tenant.

I would treat Defender for Identity as a domain controller project with a licence attached, not the other way round. Onboarding domain controllers to Defender for Endpoint and patching them to the September 2026 update is where the effort goes, and it is worth knowing that before the licence term starts.

And if the reason for buying is a single on-premises domain that is due to be retired, I would ask whether the money is better spent retiring it. Defender for Identity is built to watch Active Directory; it does not make keeping Active Directory a better idea. If Defender for Endpoint Plan 2 is also on the order, Windows Enterprise E3 vs E5 covers the other route to it through the Windows licence.

Last verified: 5 November 2026.

Common questions

No. Neither the Microsoft Defender service description nor the Defender for Identity deployment pages on Microsoft Learn list Microsoft 365 E3 as a plan that includes it. An E3 tenant gets the right through a standalone Defender for Identity licence, a security add-on named on those pages, or a move to Microsoft 365 E5. Check the SKU names against your own agreement.

You can buy any number of licences, but the service cannot be limited to them. The Microsoft Defender service description says Defender for Identity features are enabled at tenant level for all users, and that the service is not currently capable of limiting benefits to specific users. Size the count to everyone it protects and check the counting rules in the Product Terms.

Not according to Microsoft Learn on 5 November 2026. Business Premium is absent from both the Defender service description list and the sensor deployment page list. A Business Premium tenant that wants Defender for Identity needs a standalone licence or a move to a plan that carries it, such as Microsoft 365 E5. Confirm against your agreement before buying.

A sensor on your identity servers. For sensor v3.x, Microsoft Learn says the server must be onboarded to Defender for Endpoint, or use the v3.x onboarding route for eligible servers, run Windows Server 2019 or later, have no v2.x sensor, and carry the September 2026 cumulative update or later. At least one v3.x sensor must sit on a domain controller.

The Defender for Identity deployment pages list Microsoft 365 F5 Security and Microsoft 365 F5 Security + Compliance. Both carry a condition: the user also needs Microsoft 365 F1 or F3, or Office 365 F3, plus Enterprise Mobility + Security E3. The Defender service description names a Microsoft Defender + Purview Suite FLW instead, so match the name on your agreement.

The newsletter

Free: the Intune troubleshooting field guide

Subscribe and get my 8-page PDF: 13 common Intune problems, the order to check them in, and the fix for each. Then Microsoft 365 fixes from the field, about twice a month. From G.R Badhon, Microsoft MVP.

  • The field guide, sent the moment you confirm
  • New Intune, Entra ID and Purview guides as they publish
  • One field-tested fix or script per issue

Free. Confirm by email, unsubscribe in one click. Privacy.