An enterprise wants each organization to set its own Copilot CLI rule. What should it choose?
Why C is the answer
Let organizations decide
Enterprises set policies first and can leave the decision to organizations. Users assigned Copilot directly by the enterprise are covered by a separate setting.
In detail
- "Let organizations decide" leaves the choice with each organization.
- Enterprise settings override organizations when they are not delegated.
Use case
An illustrative scenario, not a real incident.
An enterprise has teams with different needs. It sets the Copilot CLI policy to "Let organizations decide", so each organization chooses for itself.
See it in different ways
flowchart TD
A{"Enterprise policy"} -->|"Enabled or disabled"| B["Applies to all organizations"]
A -->|"Let organizations decide"| C["Each organization chooses"]stateDiagram-v2 [*] --> Enterprise Enterprise --> Enabled: applies everywhere Enterprise --> Disabled: applies everywhere Enterprise --> Organizations: let organizations decide Organizations --> [*]
flowchart TD
Q{"Where should the decision sit?"}
Q -->|"One rule for all"| A0["Enable or disable at enterprise level"]
Q -->|"Each organization"| A1["Let organizations decide"]Key point: Delegate with "Let organizations decide".
Why the other options are wrong
- A. Disable the policy for the whole enterprise, then enable it per repository
- Enterprise-wide disabling removes their choice as well.
- B. Remove all of the Copilot seats, then assign them again one team at a time
- Seats have nothing to do with the policy.
- D. Enable the policy for the whole enterprise, then ask organizations to ignore it
- Enabling it for everyone removes their choice.

