Microsoft GH-300 Bundle

The alternative "Use the IDE's supported per-language suggestion settings" fits another situation: A team wants to disable inline suggestions for a distracting file type. Editor presentation settings are distinct from organization content exclusions. Here the condition is A new employee cannot find the organization-managed Copilot settings; use "Check organization-level Copilot policies rather than local editor toggles" instead. Central feature policies and individual display preferences serve different purposes.

The alternative "Apply tool permissions and separate data-access restrictions" addresses An engineer assumes exclusions guarantee a third-party MCP server never reads secrets. Third-party tools are not inherently governed by every Copilot exclusion. It does not resolve A new employee cannot find the organization-managed Copilot settings; the correct choice is "Check organization-level Copilot policies rather than local editor toggles". Central feature policies and individual display preferences serve different purposes.

For the different scenario A developer sees excluded content influencing an agent operation, "Check current mode-specific exclusion limitations and remove tool access" could be appropriate. Exclusion support varies by surface and agent mode. The present requirement is A new employee cannot find the organization-managed Copilot settings, which calls for "Check organization-level Copilot policies rather than local editor toggles". Central feature policies and individual display preferences serve different purposes.

"Ask for a plan or exploratory analysis rather than immediate modifications" targets A user wants an agent to search for implementation details before coding. Separating discovery from writes reduces unwanted changes. That differs from An agent proposes running a destructive shell command to fix formatting; the required decision here is "Reject the command and constrain the task to formatting changes". Edit authorization does not imply approval of arbitrary shell effects.

The action "Inspect the tool call and restrict available integrations" is useful when An agent starts using an external MCP tool without a clear reason. External tools can expand data and action exposure. Under the stated condition An agent proposes running a destructive shell command to fix formatting, instead choose "Reject the command and constrain the task to formatting changes". Edit authorization does not imply approval of arbitrary shell effects.

The alternative "Review the whole proposed diff before accepting it" fits another situation: An editor agent modifies multiple files after receiving a multi-step request. Agent-selected files may extend beyond the developer's original focus. Here the condition is An agent proposes running a destructive shell command to fix formatting; use "Reject the command and constrain the task to formatting changes" instead. Edit authorization does not imply approval of arbitrary shell effects.

"Clarify allowed files and test requirements in the instruction" targets An agent repeatedly edits a generated dependency lockfile. Explicit boundaries improve repeatability of multi-step automation. That differs from An editor agent modifies multiple files after receiving a multi-step request; the required decision here is "Review the whole proposed diff before accepting it". Agent-selected files may extend beyond the developer's original focus.

The action "Reject the command and constrain the task to formatting changes" is useful when An agent proposes running a destructive shell command to fix formatting. Edit authorization does not imply approval of arbitrary shell effects. Under the stated condition An editor agent modifies multiple files after receiving a multi-step request, instead choose "Review the whole proposed diff before accepting it". Agent-selected files may extend beyond the developer's original focus.

The alternative "Ask for a plan or exploratory analysis rather than immediate modifications" fits another situation: A user wants an agent to search for implementation details before coding. Separating discovery from writes reduces unwanted changes. Here the condition is An editor agent modifies multiple files after receiving a multi-step request; use "Review the whole proposed diff before accepting it" instead. Agent-selected files may extend beyond the developer's original focus.

The alternative "Review the whole proposed diff before accepting it" fits another situation: An editor agent modifies multiple files after receiving a multi-step request. Agent-selected files may extend beyond the developer's original focus. Here the condition is A user wants an agent to search for implementation details before coding; use "Ask for a plan or exploratory analysis rather than immediate modifications" instead. Separating discovery from writes reduces unwanted changes.

The alternative "Clarify allowed files and test requirements in the instruction" addresses An agent repeatedly edits a generated dependency lockfile. Explicit boundaries improve repeatability of multi-step automation. It does not resolve A user wants an agent to search for implementation details before coding; the correct choice is "Ask for a plan or exploratory analysis rather than immediate modifications". Separating discovery from writes reduces unwanted changes.

For the different scenario An agent starts using an external MCP tool without a clear reason, "Inspect the tool call and restrict available integrations" could be appropriate. External tools can expand data and action exposure. The present requirement is A user wants an agent to search for implementation details before coding, which calls for "Ask for a plan or exploratory analysis rather than immediate modifications". Separating discovery from writes reduces unwanted changes.

The alternative "Ask for a plan or exploratory analysis rather than immediate modifications" fits another situation: A user wants an agent to search for implementation details before coding. Separating discovery from writes reduces unwanted changes. Here the condition is An agent repeatedly edits a generated dependency lockfile; use "Clarify allowed files and test requirements in the instruction" instead. Explicit boundaries improve repeatability of multi-step automation.

The alternative "Inspect the tool call and restrict available integrations" addresses An agent starts using an external MCP tool without a clear reason. External tools can expand data and action exposure. It does not resolve An agent repeatedly edits a generated dependency lockfile; the correct choice is "Clarify allowed files and test requirements in the instruction". Explicit boundaries improve repeatability of multi-step automation.

"Reject the command and constrain the task to formatting changes" targets An agent proposes running a destructive shell command to fix formatting. Edit authorization does not imply approval of arbitrary shell effects. That differs from An agent repeatedly edits a generated dependency lockfile; the required decision here is "Clarify allowed files and test requirements in the instruction". Explicit boundaries improve repeatability of multi-step automation.

The alternative "Clarify allowed files and test requirements in the instruction" addresses An agent repeatedly edits a generated dependency lockfile. Explicit boundaries improve repeatability of multi-step automation. It does not resolve An agent starts using an external MCP tool without a clear reason; the correct choice is "Inspect the tool call and restrict available integrations". External tools can expand data and action exposure.

For the different scenario An agent proposes running a destructive shell command to fix formatting, "Reject the command and constrain the task to formatting changes" could be appropriate. Edit authorization does not imply approval of arbitrary shell effects. The present requirement is An agent starts using an external MCP tool without a clear reason, which calls for "Inspect the tool call and restrict available integrations". External tools can expand data and action exposure.

"Review the whole proposed diff before accepting it" targets An editor agent modifies multiple files after receiving a multi-step request. Agent-selected files may extend beyond the developer's original focus. That differs from An agent starts using an external MCP tool without a clear reason; the required decision here is "Inspect the tool call and restrict available integrations". External tools can expand data and action exposure.

"Review workspace permissions and agent tool approvals" targets Chat works but an agent cannot modify files in a read-only workspace. Chat access and write permissions are independent capabilities. That differs from Inline suggestions disappeared after an IDE upgrade; the required decision here is "Verify extension compatibility and effective signed-in status". Upgrades may alter client integration or authentication state.

The action "Check plan, policy, IDE and model availability documentation" is useful when A user sees only some model choices available in the editor. Model selection depends on current entitlement and client support. Under the stated condition Inline suggestions disappeared after an IDE upgrade, instead choose "Verify extension compatibility and effective signed-in status". Upgrades may alter client integration or authentication state.

The alternative "Confirm the trusted working folder and permitted workspace scope" addresses An agent cannot access the intended repository directory. An incorrect or untrusted project root can hide necessary context. It does not resolve Inline suggestions disappeared after an IDE upgrade; the correct choice is "Verify extension compatibility and effective signed-in status". Upgrades may alter client integration or authentication state.

The action "Confirm the trusted working folder and permitted workspace scope" is useful when An agent cannot access the intended repository directory. An incorrect or untrusted project root can hide necessary context. Under the stated condition Chat works but an agent cannot modify files in a read-only workspace, instead choose "Review workspace permissions and agent tool approvals". Chat access and write permissions are independent capabilities.

The alternative "Consult the supported feature matrix for their exact client" addresses A developer assumes all IDEs expose identical features. Copilot functionality is not uniform across platforms and versions. It does not resolve Chat works but an agent cannot modify files in a read-only workspace; the correct choice is "Review workspace permissions and agent tool approvals". Chat access and write permissions are independent capabilities.

For the different scenario A user sees only some model choices available in the editor, "Check plan, policy, IDE and model availability documentation" could be appropriate. Model selection depends on current entitlement and client support. The present requirement is Chat works but an agent cannot modify files in a read-only workspace, which calls for "Review workspace permissions and agent tool approvals". Chat access and write permissions are independent capabilities.

The alternative "Consult the supported feature matrix for their exact client" fits another situation: A developer assumes all IDEs expose identical features. Copilot functionality is not uniform across platforms and versions. Here the condition is A user sees only some model choices available in the editor; use "Check plan, policy, IDE and model availability documentation" instead. Model selection depends on current entitlement and client support.

The alternative "Verify extension compatibility and effective signed-in status" addresses Inline suggestions disappeared after an IDE upgrade. Upgrades may alter client integration or authentication state. It does not resolve A user sees only some model choices available in the editor; the correct choice is "Check plan, policy, IDE and model availability documentation". Model selection depends on current entitlement and client support.

"Confirm the trusted working folder and permitted workspace scope" targets An agent cannot access the intended repository directory. An incorrect or untrusted project root can hide necessary context. That differs from A user sees only some model choices available in the editor; the required decision here is "Check plan, policy, IDE and model availability documentation". Model selection depends on current entitlement and client support.

The alternative "Verify extension compatibility and effective signed-in status" addresses Inline suggestions disappeared after an IDE upgrade. Upgrades may alter client integration or authentication state. It does not resolve An agent cannot access the intended repository directory; the correct choice is "Confirm the trusted working folder and permitted workspace scope". An incorrect or untrusted project root can hide necessary context.

For the different scenario Chat works but an agent cannot modify files in a read-only workspace, "Review workspace permissions and agent tool approvals" could be appropriate. Chat access and write permissions are independent capabilities. The present requirement is An agent cannot access the intended repository directory, which calls for "Confirm the trusted working folder and permitted workspace scope". An incorrect or untrusted project root can hide necessary context.

The action "Consult the supported feature matrix for their exact client" is useful when A developer assumes all IDEs expose identical features. Copilot functionality is not uniform across platforms and versions. Under the stated condition An agent cannot access the intended repository directory, instead choose "Confirm the trusted working folder and permitted workspace scope". An incorrect or untrusted project root can hide necessary context.

"Review workspace permissions and agent tool approvals" targets Chat works but an agent cannot modify files in a read-only workspace. Chat access and write permissions are independent capabilities. That differs from A developer assumes all IDEs expose identical features; the required decision here is "Consult the supported feature matrix for their exact client". Copilot functionality is not uniform across platforms and versions.

The action "Check plan, policy, IDE and model availability documentation" is useful when A user sees only some model choices available in the editor. Model selection depends on current entitlement and client support. Under the stated condition A developer assumes all IDEs expose identical features, instead choose "Consult the supported feature matrix for their exact client". Copilot functionality is not uniform across platforms and versions.

The alternative "Verify extension compatibility and effective signed-in status" fits another situation: Inline suggestions disappeared after an IDE upgrade. Upgrades may alter client integration or authentication state. Here the condition is A developer assumes all IDEs expose identical features; use "Consult the supported feature matrix for their exact client" instead. Copilot functionality is not uniform across platforms and versions.