Which of the following GitHub Copilot Business related activities can be tracked using the organization audit logs?

The organization audit log for GitHub Copilot Business is designed to track significant administrative and policy-related events, rather than individual user interactions or operational outputs. Changes to content exclusion settings represent a critical policy modification that dictates which files and content GitHub Copilot should ignore. This action directly impacts security, compliance, and data privacy for the organization. Therefore, GitHub explicitly records the copilot.updatecontentexclusionsettings event in the audit log to provide administrators with a clear history of policy changes.

A. Accepted chat suggestions: This is a user-level interaction. The organization audit log tracks administrative policy changes, not the acceptance of individual suggestions by users.

B. Code suggestions made by GitHub Copilot: This is a core operational function. Logging every single suggestion would create an unmanageable volume of data and is not the purpose of an audit log.

D. Suggestions blocked by duplication detection filtering: This is a real-time filtering action. The audit log tracks changes to the policy setting for this filter, not each instance of the filter blocking a suggestion.

1. GitHub Docs. "Audit log events for your organization." GitHub

Inc. Accessed May 2024. In the "Copilot category" section

the documentation explicitly lists copilot.updatecontentexclusionsettings as an event that is recorded in the audit log. This event is triggered "When the content exclusion settings for GitHub Copilot are updated." The other options (A

B

D) are not listed as auditable events.