Resource '47******b188d3' does not exist or one of its queried reference-property objects are not present.

Question

Resource '47******b188d3' does not exist or one of its queried reference-property objects are not present.

Jennifer A Bergsneider 0

what does this error mean in purview dlp: Resource '47******b188d3' does not exist or one of its queried reference-property objects are not present.

Smaran Thoomu 29,415 Reputation points Microsoft External Staff Moderator

2025-08-18T18:38:26.8866667+00:00
Hi Jennifer A Bergsneider

That error in Purview DLP typically indicates that the resource ID being referenced in the policy or alert no longer exists or one of its dependent objects (like a data source, sensitivity label, rule package, or policy assignment) has been deleted or is missing.

Recommended checks:

Verify if the referenced resource (47***-b**188d3) still exists in Purview or Microsoft 365 Compliance.

Confirm that the policy is pointing to active data sources / locations (e.g., Exchange, SharePoint, OneDrive, Teams).

If the object was recently deleted or moved, you may need to re-create or re-map the DLP policy to valid resources.

If the GUID doesn’t match anything you can see in the portal, it’s often tied to a back-end dependency, and re-saving or re-publishing the policy usually resolves it.

If after re-publishing the error persists, you may want to open a support case since backend cleanup may be required.
Reference:

Troubleshooting Microsoft Purview DLP

Common DLP policy errors and solutions

I hope this information helps. Please do let us know if you have any further queries.

Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.
Smaran Thoomu 29,415 Reputation points Microsoft External Staff Moderator

2025-08-19T18:55:21.5333333+00:00

Jennifer A Bergsneider We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Jennifer A Bergsneider 0 Reputation points

2025-08-19T19:52:01.0233333+00:00

How can I figure out what the resource (47***-b**188d3) is? To be clear, this only happens when I try to remove a device listed as an exclusion for Scope in a DLP Policy for Device.
Smaran Thoomu 29,415 Reputation points Microsoft External Staff Moderator

2025-08-20T19:18:17.83+00:00

Jennifer A Bergsneider We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

1 answer

Your answer

Smaran Thoomu 29,415 Reputation points Microsoft External Staff Moderator

2025-08-18T18:38:26.8866667+00:00

Hi Jennifer A Bergsneider

That error in Purview DLP typically indicates that the resource ID being referenced in the policy or alert no longer exists or one of its dependent objects (like a data source, sensitivity label, rule package, or policy assignment) has been deleted or is missing.

Recommended checks:

Verify if the referenced resource (47***-b**188d3) still exists in Purview or Microsoft 365 Compliance.

Confirm that the policy is pointing to active data sources / locations (e.g., Exchange, SharePoint, OneDrive, Teams).

If the object was recently deleted or moved, you may need to re-create or re-map the DLP policy to valid resources.

If the GUID doesn’t match anything you can see in the portal, it’s often tied to a back-end dependency, and re-saving or re-publishing the policy usually resolves it.

If after re-publishing the error persists, you may want to open a support case since backend cleanup may be required.
Reference:

Troubleshooting Microsoft Purview DLP

Common DLP policy errors and solutions

I hope this information helps. Please do let us know if you have any further queries.

Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.
Smaran Thoomu 29,415 Reputation points Microsoft External Staff Moderator

2025-08-19T18:55:21.5333333+00:00

Jennifer A Bergsneider We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Jennifer A Bergsneider 0 Reputation points

2025-08-19T19:52:01.0233333+00:00

How can I figure out what the resource (47***-b**188d3) is? To be clear, this only happens when I try to remove a device listed as an exclusion for Scope in a DLP Policy for Device.
Smaran Thoomu 29,415 Reputation points Microsoft External Staff Moderator

2025-08-20T19:18:17.83+00:00

Jennifer A Bergsneider We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Answer 1

Jennifer A Bergsneider When you see a GUID like 47******b188d3 in a Purview DLP policy, that’s an internal identifier for a directory object (in your case, the device you added as an exclusion in the policy scope).

Since you mentioned the error only appears when trying to remove a device exclusion, the most likely causes are:

The device object has already been deleted or is no longer resolvable in Azure AD / Intune, so Purview can’t map the GUID back to a live object.
There’s a sync delay or mismatch between Purview policy scope and the underlying device directory.

Ways to figure it out:

Go to Microsoft Entra admin center → Devices and search by the device name/ID you excluded. If it no longer exists there, that’s why the GUID shows as “not found.”
If the device does exist, compare its Object ID with the GUID shown in the error.
If the object is missing but still listed in the DLP policy, you’ll need to edit the policy scope and re-select valid devices. Sometimes simply re-saving the policy clears stale references.

If the device does exist but Purview still throws this error, it usually requires support intervention because the backend resource mapping is stuck.

I hope this information helps. Please do let us know if you have any further queries.

Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.

Smaran Thoomu 29,415 Reputation points Microsoft External Staff Moderator

2025-08-25T20:15:42.1966667+00:00

Jennifer A Bergsneider Following up to see if the above answer was helpful. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Share via

Resource '47******b188d3' does not exist or one of its queried reference-property objects are not present.

1 answer

Your answer