Security Officer Role for Workspace Outbound & Inbound Access Controls

Hello,

Inbound and outbound security features of Fabric workspaces are wonderful, giving you strong controls regardless of Azure tenant settings.

Currently, privilege for enabling and disabling these features, and their configurations is part of workspace admin role. And since workspace admin role is bundled with bulk of privileges, even developers may need to have this role for their development workspaces, which makes this important privilege very accesible.

If there would be a Security Officer role, and not in workspace but overall Fabric level, having control of outbound and inbound security privilege (and only security related privileges, nothing else), that can give more assurance this privilege will not be misused.

Thank you,