Configuring Security Copilot Plugin Permissions
Short answer
D Select Owners only at the tenant scope in Plugin settings to prevent contributors from managing organization-wide plugins while allowing them to create plugins for their own sessions.
Question
Security Copilot contributors currently create custom plugins for their own sessions and manage organization-wide custom plugins.
You need to prevent the contributors from managing the organization-wide custom plugins. The solution must NOT affect the contributors' ability to create custom plugins for their own sessions.
What should you select in the Plugin settings?
Key Takeaways
The exam tests the distinction between tenant-scope (org-wide) and user-scope (personal) plugin permissions in Microsoft Security Copilot.
This page explains how to configure Microsoft Security Copilot plugin settings to restrict organizational access while maintaining user autonomy. The correct setting is Owners only at the tenant scope.
Common mistake: Choosing Option A (Contributors and Owners at the tenant scope) incorrectly grants contributors org-wide management rights, failing to secure the environment against unauthorized plugin distribution.
Expert Analysis
The question requires configuring Microsoft Security Copilot plugin settings to separate organizational governance from individual user capabilities. The core constraint is preventing contributors from managing organization-wide plugins while preserving their ability to create personal session plugins.
Security Copilot distinguishes between two scopes for custom plugins: the user scope (personal sessions) and the tenant scope (organization-wide). Contributors are granted permissions at these distinct levels. To meet the requirement, you must restrict the tenant-level management rights without altering user-level creation rights.
- Option D (Owners only at the tenant scope) is the correct configuration. By setting the tenant scope to "Owners only," you revoke the contributors' ability to publish or manage plugins that affect the entire organization. Crucially, this change does not impact the user scope settings, meaning contributors can still create and use custom plugins within their own isolated sessions.
A common trap is selecting Option A (Contributors and Owners at the tenant scope), which would leave contributors with full management rights over organization-wide plugins, violating the security requirement. Another potential error is confusing the scopes; reducing permissions to the user scope alone (Options B or C) fails to address the tenant-level governance issue entirely. The solution hinges on understanding that these are independent permission layers.
Exam Strategy
When dealing with role-based access control (RBAC) questions involving granular features like Security Copilot, always identify the specific scope mentioned in the requirement (e.g., 'organization-wide' vs. 'own sessions'). Map these requirements to the available permission levels and verify that the selected option satisfies all constraints without granting excess privileges.
Frequently Asked Questions
What is the difference between user scope and tenant scope in Security Copilot plugins?
Can contributors create custom plugins if they don't have tenant scope permissions?
Discussion 1 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 1
-
newlife.org.pl 👍 1 Answered DD) - Plugin settings have two separate options: one for custom plugins in your own sessions (user scope) and one for custom plugins for everyone in the organization (tenant scope). Setting tenant scope to “Owners only” removes contributors’ ability to manage org-wide plugins, while leaving user scope at “Owners and Contributors” keeps their ability to create plugins for their own sessions. Setting user scope to “Owners only” would break the second requirement. https://learn.microsoft.com/en-us/copilot/security/manage-plugins
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All SC-500 Questions
Access 100 questions with complete answers and detailed explanations.
View Full SC-500 Practice Test →