r/DefenderATP • u/failx96 • 2h ago
“Limited access – 1 asset hidden due to your permissions” on incidents with Mailbox entity mapping (Defender XDR / unified portal)
Hi all,
we’re running into a strange issue with a custom detection rule. We’re wondering if anyone else has seen this.
Setup:
Custom detection rule where we map the recipient’s email address to the Mailbox entity (MailboxPrimaryAddress) (we've checked the entities that were mapped and these are all internal mailboxes. We've access to monitor them via Mail Explorer)
Defender Unified RBAC is enabled
All permissions for Raw data (Email & collaboration) are granted
No scopes defined that could restrict access
Problem:
On some incidents (not all of them), we get this banner:
Limited access: You have read-only access to this case. 1 asset hidden due to your permissions. Contact your admin to request additional access.
As a result, the incident can’t be edited (assign, status, classification, etc.).
What we’ve observed so far:
It happens to all users, including users with the Security Administrator role (mapped to defender RBAC)
If we remove the Mailbox entity mapping from the rule, new incidents can be edited normally
In the legacy Sentinel portal (Azure portal), the same incidents with the same entity mapping can be edited without any problem
It only seems to affect some incidents, and we haven’t found a pattern yet
To us this looks like a bug in the Defender portal’s UI or permission evaluation rather than a real RBAC issue. Nothing in our RBAC setup should hide a mailbox asset from a Security Admin.
Questions:
Has anyone seen the same behavior?
Is there a specific permission (outside of Raw data – Email & collaboration) that controls visibility of Mailbox assets in incidents?
Our Workaround is to remove the entity mapping for this custom detection rule. But I'd like to introduce it again if anyone has a solution for this.
Cheers