Forum Discussion
Are critical asset management rules incompatible with Entra ID?
I am trying to create some custom asset management rules based on filters like logged on username, user criticality, and user groups. No matter what I try no assets show up. Even if I use the format azuread\<username>, no assets are returned by the filter. Are these filters incompatible with Entra ID? Do they only work with on-premise AD?
4 Replies
I've run into this too. It looks like critical asset management rules rely on legacy attributes that aren't in Entra ID. A workaround might be custom attributes, but it's not straightforward.
I did get confirmation from MS Support, eventually, that confirmed this. The critical asset management rules are not compatible with Entra groups.
Did you get it work? When I looked I didnt see any assets either for the AD Group I picked. Where does it pull this information from for this? Or where else can we check?
Hi SKadish!
No, the filters you’re using should work with Entra ID as long as the data is synced correctly. The issue might be with how the data is being pulled or how the filters are set up. Double-check the filter format and make sure the attributes are correctly synced from Entra ID. If everything’s synced, it should work for cloud based assets too, not just on-prem AD. You might also want to check if there's a delay in data sync or a different issue with the specific setup.
Hope it helps!
