Overview
Configure privacy, content exclusions, and safeguards is the configuration and support domain of GH-300. It has two official groups. Managing privacy settings and exclusions covers configuring content exclusions and editor settings, and describing the ownership and limitations of outputs. Applying safeguards and troubleshooting covers enabling filtering of suggestions that match public code and resolving issues with suggestions and content exclusions. Microsoft marked the safeguards group as having minor changes in the August 7, 2026 update.
Content exclusions are set by repository administrators, organization owners and enterprise owners on Copilot Business and Enterprise. They stop chosen files from being used as context and from receiving inline suggestions, but GitHub documents gaps, such as edit and agent modes in IDEs. The public code filter either blocks matching suggestions or allows them with code references that show where similar code appears and its license.
How it's tested
Questions in this domain describe a privacy or legal requirement, or a support problem, and ask which setting, role or troubleshooting step applies. Expect content exclusion scope, the public code filter and code references, output ownership, and diagnosing why suggestions or exclusions are not working.
-
Who configures it
A requirement to exclude files is described, and you choose the role and level, such as repository, organization or enterprise settings.
-
Filter or reference
A legal concern about public code is described, and you choose to block matching suggestions or allow them with code references.
-
Troubleshoot
Suggestions are missing or an exclusion seems ignored, and you choose the likely cause, such as propagation delay, unsupported mode or settings.
An administrator adds a content exclusion for secrets.yaml, but a developer still sees Copilot use that file's content minutes later. Deleting the file or disabling Copilot is excessive. Exclusion changes can take time to reach IDEs, and reloading the editor fetches the updated policy, so waiting for propagation and reloading is the expected first step.
Functional groups 2
Official functional groups from the GitHub (Microsoft) outline, in outline order.
6.1 Manage privacy settings and exclusionsContent exclusions, editor settings, and ownership and limitations of outputs.
- What it means
- This group covers two official skills: configure content exclusions and editor settings, and describe the ownership and limitations of Copilot outputs. It addresses which content Copilot may use and who owns what it produces.
- What to understand
- Content exclusions list paths or repositories that Copilot must ignore for context and inline suggestions; repository admins, organization owners and enterprise owners can set them on Business and Enterprise plans. Editor settings let users enable or disable Copilot per language and adjust behavior. GitHub does not claim ownership of suggestions, so the user owns and is responsible for code they accept. Exclusions have limits, including edit and agent modes, symbolic links, remote filesystems and indirect IDE information such as type data.
- How it shows up
- Expect a requirement to keep specific files out of Copilot and a choice of role, level or limitation.
- Common confusion
- Assuming an individual Copilot Pro user can configure content exclusions; the feature is for Business and Enterprise.
6.2 Apply safeguards and troubleshootPublic code filtering, and resolving issues with suggestions and content exclusions.
- What it means
- This group covers two official skills: enable filtering of suggestions that match public code, and resolve issues with suggestions and content exclusions. Microsoft marked it as having minor changes in the August 2026 update.
- What to understand
- The setting for suggestions matching public code can block matches or allow them; when allowed, Copilot shows code references with the matching repositories and license details. Administrators set it for Business and Enterprise users, and individuals set it in their account settings. Troubleshooting covers checking sign-in and seat assignment, whether Copilot is enabled for the language and file, network and firewall access, extension logs, and propagation delays or unsupported modes when exclusions seem ignored.
- How it shows up
- Look for a support scenario and pick the most likely cause or the correct filter setting.
- Common confusion
- Thinking that allowing public code matches removes all information about them; code references still show the source and license.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Content exclusion
A setting that stops Copilot using specified files or repositories.
- Remember
- Available on Copilot Business and Enterprise.
- Tested as
- Configuration questions.
- Trap
- Assuming it exists on individual plans.
-
Exclusion levels
Repository, organization and enterprise settings.
- Remember
- Repository admins scope their own repositories.
- Tested as
- Who-configures questions.
- Trap
- Thinking only enterprise owners can set them.
-
Exclusion gaps
Cases exclusions do not cover.
- Remember
- Edit and agent modes in IDEs, symlinks and remote filesystems.
- Tested as
- Limitation questions.
- Trap
- Treating exclusions as complete protection.
-
Propagation delay
Time for exclusion changes to reach IDEs.
- Remember
- Reload the editor to fetch the latest policy.
- Tested as
- Troubleshooting questions.
- Trap
- Assuming changes apply instantly.
-
Public code filter
Setting to block or allow suggestions matching public code.
- Remember
- Matching is checked on output.
- Tested as
- Safeguard questions.
- Trap
- Placing the check on input.
-
Code references
Details of matching public code shown when matches are allowed.
- Remember
- Include repository and license information.
- Tested as
- Filter versus reference questions.
- Trap
- Thinking allowed matches are hidden.
-
Output ownership
GitHub does not claim ownership of Copilot suggestions.
- Remember
- The user is responsible for code they accept.
- Tested as
- Ownership questions.
- Trap
- Believing GitHub owns the output.
-
Editor settings
User-level options such as enabling Copilot per language.
- Remember
- A disabled language shows no suggestions.
- Tested as
- Troubleshooting questions.
- Trap
- Overlooking language toggles.
-
Network access
Copilot needs access to GitHub endpoints.
- Remember
- Firewalls and proxies can block it.
- Tested as
- Troubleshooting questions.
- Trap
- Reinstalling the IDE first.
-
Extension logs
Diagnostic output from the Copilot extension.
- Remember
- First place to find connection or auth errors.
- Tested as
- Troubleshooting questions.
- Trap
- Guessing without checking logs.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Block vs. allow suggestions matching public code
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Block | Matching suggestions are not shown | Prevents verbatim public code | Expecting code references to appear |
| Allow | Matching suggestions can appear | Shown with code references | Thinking there is no license information |
Who can configure content exclusions
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Repository administrator | Excludes paths in their repository | Scoped to that repository | Expecting org-wide effect |
| Organization owner | Excludes content for org seat holders | Applies across repositories they specify | Assuming individual users can override it |
| Enterprise owner | Sets exclusions at enterprise level | Broadest scope | Thinking it is the only level |
| Individual plan user | No content exclusion feature | Uses personal settings only | Expecting exclusion controls |
Missing suggestions: likely causes
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Not signed in or no seat | No valid Copilot access | Fix account or seat | Reinstalling the extension |
| Language disabled | Editor setting turns Copilot off | Re-enable for that language | Blaming the network |
| File excluded | Content exclusion applies | Expected behavior | Treating it as a bug |
| Network blocked | Firewall or proxy blocks GitHub endpoints | Allow required domains | Changing prompts |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Exclusions are universal
- What candidates pick
- Rely on a content exclusion to keep a file out of agent mode.
- Why it looks right
- Exclusions sound like a global block.
- Why it's wrong
- GitHub documents that edit and agent modes in IDEs do not support content exclusions, so other safeguards are needed.
Clue to watch for The scenario uses agent mode or edit mode.
-
Pro users can exclude
- What candidates pick
- Tell an individual Pro user to configure a content exclusion.
- Why it looks right
- They pay for Copilot.
- Why it's wrong
- Content exclusion is a Copilot Business and Enterprise feature managed by admins and owners.
Clue to watch for The user has an individual subscription.
-
Instant exclusion
- What candidates pick
- Assume the exclusion failed because it did not apply immediately.
- Why it looks right
- Settings usually apply at once.
- Why it's wrong
- Exclusion changes can take time to reach IDEs; reloading the editor fetches the updated policy.
Clue to watch for The change was made only minutes earlier.
-
Allow means no visibility
- What candidates pick
- Assume allowing public code matches hides their origin.
- Why it looks right
- Blocking seems like the only safe setting.
- Why it's wrong
- When matches are allowed, Copilot shows code references with source repositories and licenses for review.
Clue to watch for The team wants matches but needs license information.
-
GitHub owns suggestions
- What candidates pick
- State that code from Copilot belongs to GitHub.
- Why it looks right
- GitHub's model generated it.
- Why it's wrong
- GitHub does not claim ownership of suggestions; the developer is responsible for code they choose to use.
Clue to watch for The question concerns ownership or licensing duties.
-
Reinstall first
- What candidates pick
- Reinstall the IDE when suggestions stop.
- Why it looks right
- It feels like a reset.
- Why it's wrong
- Checking sign-in, seat, language settings, exclusions, network access and logs finds the cause faster.
Clue to watch for Suggestions stopped for one user or one file type.
Answer framework
For a privacy, safeguard or troubleshooting scenario, use these steps to find the answer GH-300 expects.
- Decide whether the scenario is about keeping content out of Copilot, controlling public code matches, output ownership, or fixing a problem.
- For exclusions, confirm the plan is Business or Enterprise and choose the right level: repository administrator, organization owner or enterprise owner.
- Check whether the Copilot mode in the scenario supports exclusions, remembering the documented gaps for edit and agent modes and symlinks.
- For public code concerns, choose block to prevent matches, or allow with code references when the team reviews licenses itself.
- For missing suggestions, check access and seat, language settings, exclusions, network access and logs, and allow time for policy propagation.
Practice question
Want more like this? The GH-300 practice test has questions for every domain.
Checklist
0 of 10
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Treat this domain as a settings tour. If you have access to a Copilot Business or Enterprise organization, open the Copilot settings and find content exclusions, the public code setting and policies. Add an exclusion for a test file, reload your editor, and confirm that inline suggestions stop for that file. If you lack an organization, read GitHub Docs pages on content exclusion and public code matching closely and write down every role, plan and limitation they mention.
Next, learn the boundaries. Make a list of where exclusions apply and where they do not, including edit and agent modes, symbolic links, remote filesystems and indirect IDE information. Then study the block and allow options for public code and what code references display.
Finish with troubleshooting. Build a checklist for missing suggestions: sign-in and seat, language settings, exclusions, network or proxy access and extension logs, then propagation delays for new exclusions. Link this domain to the data flow in Domain 3 so you understand where filters run. Microsoft noted minor changes to the safeguards group in August 2026, so confirm your notes against the current study guide before your exam.
FAQ
How much of GH-300 is Domain 6, Configure privacy, content exclusions, and safeguards?
Configure privacy, content exclusions, and safeguards is 10–15% of the exam, about six to nine questions.
Who can configure content exclusions?
Repository administrators, organization owners and enterprise owners, for users with Copilot Business or Copilot Enterprise seats.
Do content exclusions work in agent mode?
GitHub's documentation states that edit and agent modes of Copilot Chat in IDEs do not support content exclusions, so plan other controls for sensitive files.
What happens when suggestions matching public code are allowed?
Matching suggestions can appear, and Copilot shows code references that list matching public repositories and their licenses.
Who owns code that Copilot suggests?
GitHub does not claim ownership of suggestions. The developer or organization that uses the code is responsible for it, including license compliance.
Why might an exclusion not take effect right away?
Policy changes can take time to reach IDEs. Reloading the editor fetches the updated settings, and some modes and file types are not covered at all.
What changed in this domain in August 2026?
Microsoft marked the Apply safeguards and troubleshoot group as having minor changes; the other group was unchanged.
Other Artificial Intelligence & Machine Learning certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
Test your Domain 6 knowledge
You have covered content exclusions, editor settings, output ownership, public code filtering and troubleshooting. Test whether you can apply the right safeguard in each scenario.
Keep going
- Training Training Built on your Weak areas
- Practice test Questions by domain, with explanations
- Mock exam Full length, timed like the real exam
- Readiness test Find your weakest domain in minutes
- Cheat sheet Key terms and formulas on one page
- Ask the GH-300 AI tutor Get any concept explained your way