An organization member cannot start Copilot CLI, though other features work. What should you check?
Why D is the answer
Whether the Copilot CLI policy is enabled in the organization's settings
When Copilot comes from an organization, the Copilot CLI policy must be enabled.
In detail
- Copilot CLI is controlled by a policy.
- If the policy is off, the CLI will not start, even though other features work.
- Features can have their own policies, so check the right one.
Use case
An illustrative scenario, not a real incident.
Chat works, but Copilot CLI will not start for one developer. An organization admin finds the CLI policy is off, and turning it on solves it.
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 LR S0["CLI will not start"] --> S1["Check organization settings"] --> S2["Enable the policy"] --> S3["CLI works"]
Key point: Organization seats depend on the CLI policy.
Why the other options are wrong
- A. Whether the editor has been updated to the latest version available
- The CLI does not depend on the editor version.
- B. Whether the developer has turned on two-factor authentication this month
- There is no monthly requirement like this.
- C. Whether the developer's repository has a README file in its root folder
- A README has no effect on the CLI.