A custom Defender for Cloud standard exists in the tenant, but lock-lab dashboards stay empty for those controls. What is the most likely missing step?
Select an answer to reveal the explanation.
Short Explanation
Creating the standard parks it in the library; assigning it puts it on the lock-lab shelves. Empty dashboards usually mean nobody checked it out to those subscriptions yet.
Full Explanation
Custom standards must be assigned or enabled on the target subscriptions (or supported scope), just like built-in standards. Creation alone does not populate compliance dashboards. Custom standards do not auto-expire daily, and removing MCSB or using administrative units does not assign a Defender standard.