Devices missing as location in DLP policy

Question

Devices missing as location in DLP policy

Anonymous

Hello

Please i need your help on this issue.

Devices missing as location in DLP policy.

I have been using Endpoint DLP for many months now and created several policies that target "Devices" as the location in my DLP policy.

This week when either creating new policies or editing any existing policies, the location for "Devices" is not present in the list of locations available to target my policy to.

Devices are still showing as onboarded and visible in Purview, so this is not a cause.

Serigne Mbaye (c) 5 Reputation points

2025-09-01T08:04:25.97+00:00

Hi there did you manage to get this resolved? I’m seeing the exact same issue. If you found a workaround or got confirmation from Microsoft, could you share the steps? Thanks!
Cameron Stephens 10 Reputation points

2025-09-02T00:31:59.2666667+00:00

We've got the same issue and for at least the past 24 hours. Nothing has changed on our side and now we cannot manage existing DLP policies targeting onboarded devices or create new ones. Fortunately, we are a Microsoft partner, and we've only detected the problem in our 3x E5 developer tenancies.

The problem is either due to a change in licensing or a backend change.
Anonymous

2025-09-02T06:11:04.2433333+00:00

Hi @Ibn,
Hope you had a chance to review our earlier response. If it addressed your query, please confirm at your convenience. Let us know if we can assist further.
Linas 5 Reputation points

2025-09-25T12:01:23.1866667+00:00

Hello,

same issue, E5 Dev license, devices location missing. Currently investigating with Microsoft Support but it is taking a while. There is news in another thread that this issue was resolved for some tenants.

Let us know if this was resolved for you and whether there were any steps which can be taken.
Stonkus, Linas 0 Reputation points

2025-11-03T08:52:13.3866667+00:00

MS Support reports that Devices location is not available as part of the E5 Developer license.

2 answers

Your answer

Serigne Mbaye (c) 5 Reputation points

2025-09-01T08:04:25.97+00:00

Hi there did you manage to get this resolved? I’m seeing the exact same issue. If you found a workaround or got confirmation from Microsoft, could you share the steps? Thanks!
Cameron Stephens 10 Reputation points

2025-09-02T00:31:59.2666667+00:00

We've got the same issue and for at least the past 24 hours. Nothing has changed on our side and now we cannot manage existing DLP policies targeting onboarded devices or create new ones. Fortunately, we are a Microsoft partner, and we've only detected the problem in our 3x E5 developer tenancies.

The problem is either due to a change in licensing or a backend change.
Anonymous

2025-09-02T06:11:04.2433333+00:00

Hi @Ibn,
Hope you had a chance to review our earlier response. If it addressed your query, please confirm at your convenience. Let us know if we can assist further.
Linas 5 Reputation points

2025-09-25T12:01:23.1866667+00:00

Hello,

same issue, E5 Dev license, devices location missing. Currently investigating with Microsoft Support but it is taking a while. There is news in another thread that this issue was resolved for some tenants.

Let us know if this was resolved for you and whether there were any steps which can be taken.
Stonkus, Linas 0 Reputation points

2025-11-03T08:52:13.3866667+00:00

MS Support reports that Devices location is not available as part of the E5 Developer license.

Answer 1

Anonymous

Hi @Ibn

Welcome to the Microsoft Q&A Platform.

Follow this step-by-step checklist to find out why the “Devices” option isn’t showing up.

Endpoint DLP Settings
- Location: Purview → Settings → Data loss prevention → Endpoint settings
- Action: Enable Endpoint DLP ( Devices won’t appear unless it's enabled )
Licensing Validation
- Check: Users and tenant have Microsoft 365 E5, E5 Compliance, or equivalent with Endpoint DLP
Policy Wizard Path
- Create via: Purview → Data loss prevention → Policies → Create policy → Custom policy (from scratch)
Admin Units / Role Scoping
- Action: Set scope to Full directory
Device Inventory & Signals
- Location: Purview → Devices → Open onboarded device
- Confirm: Valid signed-in user ,Recent activity in Explorer
Microsoft Defender for Endpoint (MDE)
- Confirm: Use MDE Analyzer for sync/health
- Run DisplayDlpPolicy.exe to check applied DLP
Cross-Tenant Comparison
- Try: Test in another E5 tenant
- Why: Helps identify tenant-specific issues.
If still is not solved, feel free to respond in this same thread.

Jimmy Lindö 0 Reputation points

2025-09-25T09:46:19.0733333+00:00

Is this an E5 dev tenant or full E5 tenant? I have the same issue in my DEV tenant.
Anonymous

2025-09-26T05:57:31.1366667+00:00

Hi @Jimmy Lindö ,

Welcome to the Microsoft Q&A Platform.

To help us better assist you, please create a separate question thread. This will make it easier for us to track your issue and provide the right guidance.
Linas 5 Reputation points

2025-09-26T06:33:42.9833333+00:00

@Jimmy Lindö - E5 Dev problem only, regular E5 or E5 for CDX works fine.
Pauline Mbabu 1,840 Reputation points Microsoft Employee

2025-10-01T10:53:42.31+00:00

Feeback, I received is that the EndpointDlpLocation param is assigned to EndpointDlp feature. And the EndpointDlp feature needs Microsoft_Endpoint_DLP service plan to be assigned which this tenant. E5 Developer licenses, do not support Endpoint DLP, you will need a separate License for that. https://learn.microsoft.com/en-us/office365/servicedescriptions/microsoft-365-service-descriptions/microsoft-365-tenantlevel-services-licensing-guidance/microsoft-purview-service-description#microsoft-data-loss-prevention-endpoint-data-loss-protection-dlp
AJ007 20 Reputation points

2026-08-19T18:14:17.53+00:00

got the same problem in my dev tenant as well. i created policies back in 2025 now i cant edit them but the policy still works.

This is well annoying that they keep changing stuff.

how do you get that license i dont see it in the market place

Answer 2

Pauline Mbabu 1,840 Microsoft Employee

Hello Cameron,
I am following up on this internally, the issues seem to have been resolved in some tenants but is still persistent on others. I will keep you updated on what I am able to get

0 comments