GH-900 GitHub Foundations Exam Guide: Skills, Study Plan, and Scheduling Decisions
GH-900 validates foundational knowledge of GitHub, including Git concepts, repositories, collaboration, project management, modern development practices, privacy, security, administration, and the GitHub community. It is intended for non-developers, developers, and other GitHub users who want to confirm that foundation. This guide helps you decide whether your current experience is sufficient, which domains deserve the most study time, whether the official learning path or course fits your situation, and what to check before scheduling the assessment.
What GH-900 validates and who should take it
GH-900 is a beginner-level GitHub certification for people who need to understand how GitHub is used to collaborate, contribute, and work with software projects. You do not need to approach it as a specialist programming exam; the official audience includes non-developers, developers, and GitHub users improving their fundamentals.
Microsoft describes the expected foundation as knowledge of GitHub and its core features, including Git, repositories, collaboration tools, project management, and modern development practices. The certification page lists Administrator, App Maker, Developer, DevOps Engineer, and Solution Architect among the associated roles, but those labels do not turn GH-900 into an advanced role-based administration exam.
The practical question is whether you can explain why a GitHub feature is used and recognize how related features fit into a workflow. Someone who has only read feature names may need hands-on orientation first. Someone who has used branches, pull requests, issues, and repository settings can use the blueprint to identify gaps rather than beginning every topic from zero.
Choose GH-900 when your goal is a foundation
GH-900 is a sensible starting point when you work with GitHub projects but need a structured understanding of the platform’s terminology and collaboration model. It can also suit a learner moving toward development, DevOps, administration, or solution design who first needs to distinguish Git concepts from GitHub services.
Do not mistake the certification for proof of advanced delivery skills
The certification validates foundational understanding. It does not, by itself, establish that you can design an enterprise GitHub implementation, write production software, operate a complex security program, or build sophisticated automation. Treat those as follow-on capabilities rather than assumptions about what passing GH-900 proves.
How the current skill weighting should change your study order
Start with Git and GitHub basics because that domain accounts for 25–30% of GH-900. Then give focused attention to repositories, collaboration, modern development practices, and privacy, security, and administration, each of which accounts for 10–15% of GH-900. Project management and the GitHub community each account for 5–10% of GH-900. These are official study-guide ranges, not a promise of an exact question distribution.
As of the January 2026 study-guide revision, the seven domains are: Understand Git and GitHub basics (25–30%); Work with GitHub repositories (10–15%); Collaborate using GitHub (10–15%); Apply modern development practices (10–15%); Manage projects with GitHub (5–10%); Understand privacy, security, and administration (10–15%); and Explore the GitHub community (5–10%). Review the current study guide before studying because Microsoft can revise measured skills.
Do not use the percentages as permission to ignore the smaller domains. A candidate who spends all preparation time on Git commands can still be weak on access, repository visibility, project organization, or community concepts. Use the ranges to allocate effort, then use practice results and your own work history to adjust that allocation.
Build a domain checklist before opening a course
Create seven headings in a study document and record, for each one, what you can explain, what you have used, and what remains uncertain. This simple inventory prevents a familiar topic such as commits from crowding out less familiar areas such as GitHub Projects, organization roles, or Marketplace.
Give the largest domain a conceptual foundation
For the 25–30% Git and GitHub basics domain, learn the purpose of version control, the difference between Git and GitHub, and the relationships among repositories, commits, and branches. Add GitHub accounts, organizations, GitHub Flow, Markdown, GitHub Desktop, and GitHub Mobile to the same review block because the study guide associates these subjects with the domain.
What to learn about Git, GitHub, and repositories
You should be able to follow a change from a local or remote working context into a repository, understand why a branch isolates work, and recognize how a commit records a change. You should also know that Git is the version control system while GitHub is the platform that provides collaboration and related services.
Use the official GitHub Foundations learning path as the backbone for this area. Its modules include Introduction to Git, Introduction to GitHub, and Introduction to GitHub's products, alongside modules on code scanning, Copilot, Codespaces, GitHub Projects, and Markdown: https://learn.microsoft.com/en-us/training/paths/github-foundations/. The path is useful because it connects terminology to platform features instead of presenting an isolated glossary.
For repository work, study the purpose of repository files and structures named in the study guide, including README, LICENSE, CONTRIBUTING, CODEOWNERS, and SECURITY. Review repository templates, branches, file management, repository insights, stars, feature previews, repository metrics, and dependency insights. The aim is not to memorize labels; it is to recognize which repository facility supports documentation, contribution guidance, ownership, security reporting, visibility, or maintenance.
A practical exercise is to inspect a repository and explain what a new contributor would learn from its README and CONTRIBUTING file, how a license communicates reuse terms, and how CODEOWNERS or SECURITY supports project operation. Then trace a small change through a branch and commit. Keep the exercise focused on understanding the workflow, not on producing a large application.
Separate Git concepts from GitHub product concepts
A common mistake is treating Git, GitHub, GitHub Desktop, and GitHub Mobile as interchangeable names. Write a one-line purpose for each and include an example of when a user would select it. This makes comparison questions easier because you are reasoning from function rather than recalling a definition without context.
Use repository inspection to test understanding
Reading a real public repository can expose gaps more effectively than copying definitions. Identify its branches, commits, issues, pull requests, documentation files, and visible project information. Record what each item contributes to collaboration, then verify unfamiliar terms in Microsoft Learn rather than inferring a feature’s purpose from its name.
How collaboration features fit together
Issues, pull requests, and discussions serve different collaboration needs. Prepare to explain how a team can use issues to track work, pull requests to review proposed changes, and discussions to exchange broader questions or ideas. Also review linking pull requests to issues, templates, filters, assignments, notifications, Gists, Wikis, and GitHub Pages.
The official GH-900T00-A course describes GitHub Flow through branches, commits, and pull requests and includes collaboration features such as issues and discussions. Microsoft lists the course as beginner level and provides it in English, Japanese, Korean, Portuguese (Brazil), and Spanish, with a course duration of 2 days: https://learn.microsoft.com/en-us/training/courses/gh-900t00. That course can provide structure, but completing it should not be treated as evidence that every domain is exam-ready.
Study collaboration as a sequence rather than as disconnected features. A request begins as a need or task, is recorded and clarified, is addressed through a branch and commits, and is proposed for review through a pull request. Notifications then help participants follow activity. Markdown supports clear communication in issues and pull requests, so practice writing concise headings, lists, links, and descriptions.
A useful preparation task is to create a small issue, assign it, add useful labels, create a branch for the work, make a meaningful commit, and open a pull request that links back to the issue. You can then ask which part of the process would change if the goal were discussion rather than implementation. This trains feature selection and workflow reasoning without relying on live exam content.
Avoid choosing a pull request for every conversation
A pull request is associated with a proposed change that can be reviewed and merged; an issue is suited to tracking work or a problem; a discussion supports open-ended conversation. The exact configuration of a repository may vary, but the exam preparation decision is to match the tool to the collaboration purpose.
Treat notifications as workflow controls
Review why notifications exist and how users configure them for work management. A candidate who knows what an issue is but cannot explain how activity is followed, filtered, or assigned has learned the object without learning its operational role.
Modern development practices: automation, AI, and cloud workspaces
The modern development practices domain accounts for 10–15% of GH-900 and covers GitHub Actions, GitHub Copilot, GitHub Codespaces, development containers, and github.dev. Focus on purpose and distinctions: automation runs workflows, Copilot assists with code-related work, Codespaces provides a configured cloud development environment, and github.dev is a different editor experience.
The GitHub Foundations learning path includes modules for code scanning, GitHub Copilot, Codespaces, GitHub Projects, and Markdown. The path describes Codespaces as a fully configured development environment hosted in the cloud, with the workspace and configured development environments available from any computer with internet access: https://learn.microsoft.com/en-us/training/paths/github-foundations/. Use the official module sequence to connect each product to the problem it addresses.
Review GitHub Actions as an automation capability and learn to identify the kinds of software-development workflow tasks it can support. For Copilot, study the distinctions the study guide names, including Copilot agents, agent mode, multi-model support, and differences among individual, business, and enterprise offerings. Do not reduce this topic to the slogan that AI writes code; the exam scope requires recognition of how the tools and plans differ.
Compare Codespaces with github.dev in your own notes. Both relate to editing in a browser-based context, but they should not be treated as the same environment. Also review how development containers are configured, customized, and used at a foundational level. The study target is understanding when a tool is appropriate, not building a complex container image or automation pipeline.
Study product boundaries before product details
For each modern practice, write three answers: what problem does it solve, where does it operate, and what is it not? This method is more durable than memorizing feature marketing language and helps with scenario questions that ask you to select among Actions, Copilot, Codespaces, and github.dev.
Keep preview awareness separate from core knowledge
Microsoft notes that most questions cover features in general availability and that preview features may appear when they are commonly used. Prioritize stable, generally available concepts first, then check the current study guide for changes instead of building your preparation around every newly announced feature.
Projects, privacy, security, and administration
Project management accounts for 5–10% of GH-900, while privacy, security, and administration accounts for 10–15% of GH-900. Review GitHub Projects, layouts, labels, milestones, workflows, saved replies, assignees, and project insights, then study 2FA, passkeys, permissions, roles, repository visibility, branch protection, teams, organization settings, Enterprise Managed Users, and organization-wide Copilot policy management.
Approach these topics through decisions an administrator or contributor must make. Project features organize work and show progress; labels and milestones add structure; workflows support repeatable project handling; insights help track progress and productivity. Access controls and visibility determine who can see or change work, while branch protection rules help govern changes to important branches.
The most common preparation error here is learning security as a list of acronyms without connecting it to access. Build a comparison table for repository and organization permissions, roles, visibility choices, and branch protection. Then explain what an organization team changes compared with assigning access to people individually. Keep the table descriptive and verify details against the current official study guide.
The official certification page also provides an exam sandbox so candidates can experience different question types in the assessment interface: https://learn.microsoft.com/en-us/credentials/certifications/github-foundations/. Use it after learning the concepts, not as a substitute for them. If an interactive component appears, familiarity with the interface can reduce avoidable uncertainty, but it does not reveal the assessment’s live questions.
Use least-privilege reasoning
When reviewing permissions, ask which user or team needs access, at what scope, and for which action. Do not assume that repository visibility, organization membership, repository roles, and branch rules are interchangeable. If you cannot justify an access choice in a short scenario, return to the relevant Microsoft Learn module.
Do not neglect the smaller project domain
Five to ten percent is still a meaningful part of the exam. A short project exercise using issues, labels, milestones, assignees, and a layout can expose gaps quickly. Focus on what each feature contributes to tracking and communication rather than trying to reproduce a large project-management system.
What the GitHub community domain requires
Explore the GitHub community domain as a set of participation and discovery choices. The study guide places it at 5–10% of GH-900 and includes open source, GitHub Sponsors, following users and organizations, GitHub Marketplace, InnerSource, forks, templates, and discoverable repositories.
Prepare to distinguish why someone would fork a repository, use a template, follow a project, or find a reusable tool in Marketplace. Review how open-source practices can support contribution and how InnerSource applies open-source principles within an organization. GitHub Sponsors belongs in the same conceptual area because it concerns support for open-source maintainers and projects.
A practical exercise is to inspect a public project’s contribution path without attempting to contribute blindly. Find its documentation, contribution guidance, issue or discussion channels, and reuse signals. Consider whether a new project should start from a template or whether an existing project should be forked. These choices strengthen your ability to identify appropriate community and collaboration mechanisms.
Learn participation boundaries
Open source does not mean that every repository has identical contribution rules or visibility settings. Check the repository’s stated guidance and license information. For GH-900 preparation, the important skill is recognizing the platform feature or practice that supports responsible discovery, reuse, contribution, or internal collaboration.
A practical GH-900 preparation roadmap
Use a staged plan: establish terminology, work through the official learning content, perform small GitHub exercises, measure weak domains, and finish with the sandbox and practice assessment. The order matters because practice questions are more useful after you understand the feature relationships they test.
Begin with a baseline inventory. Mark each of the seven domains as confident, familiar, or unfamiliar, and note whether your knowledge comes from actual use or only reading. Give the largest initial block to Git and GitHub basics, then cover repositories and collaboration before moving into modern practices, project management, security, administration, and community topics.
Next, work through the GitHub Foundations learning path and keep a short evidence log. For every module, write the feature’s purpose, one related feature, and one situation in which you would not choose it. The official path is described as beginner-friendly and contains 8 modules: https://learn.microsoft.com/en-us/training/paths/github-foundations/. Do not copy page text into notes; translate it into decisions you can explain.
After the conceptual pass, complete hands-on tasks in a safe repository or learning environment. Create and inspect commits and branches, open an issue and pull request, use Markdown, examine repository files, organize a small project, review visibility and access concepts, and compare Codespaces with github.dev. The goal is transferable understanding, not a simulated dump of questions.
Use Microsoft’s practice assessment to assess wording, style, difficulty, and knowledge gaps. The certification page presents it as a readiness tool and allows previous-attempt reports to be reviewed: https://learn.microsoft.com/en-us/credentials/certifications/github-foundations/. For every missed or uncertain item, identify the domain, explain why the correct concept fits, and return to the official content. Repeating a score without correcting the underlying gap is weak preparation.
Finish with a narrow review. Revisit the 25–30% Git and GitHub basics domain and each 10–15% domain, then check the 5–10% project-management and community domains for omissions. Run the exam sandbox, confirm your account and language choices, and schedule only when you can explain the main workflow and platform distinctions without relying on memorized answer patterns.
A shorter plan for experienced GitHub users
If you already use branches and pull requests regularly, do not automatically repeat beginner exercises for days. Map your experience to all seven domains, study the topics you have not encountered—especially administration, security, Projects, community features, and modern development tools—and use the practice assessment to validate the map.
A longer plan for new users
If GitHub is new to you, learn version-control concepts before attempting product comparisons. Work through the official path sequentially, perform small tasks after each related module, and keep a glossary of repository, branch, commit, issue, pull request, organization, and project terms. Schedule after you can describe the workflow in your own words.
Use the two-day course selectively
Microsoft lists GH-900T00-A as a two-day beginner course and says it can be taken through instructor-led training or self-paced study: https://learn.microsoft.com/en-us/training/courses/gh-900t00. Choose it when external structure or a fixed sequence is valuable. Choose self-directed learning when you need to spend more time on particular domains or fit study around work.
Scheduling and delivery details to verify before booking
Microsoft states that GH-900 is proctored and may include interactive components, and the certification page states that you have 100 minutes to complete the assessment. The listed languages are English, Spanish, Portuguese (Brazil), Korean, and Japanese. Confirm the live scheduling page for current availability and conditions before paying or selecting an appointment.
Microsoft lists the price as US$99 and notes that pricing is based on the country or region where the exam is proctored: https://learn.microsoft.com/en-us/credentials/certifications/github-foundations/. Treat that amount as the official listed reference, not a universal final charge. Pearson Vue handles scheduling, and Microsoft strongly recommends registering with a personal Microsoft account rather than an organizational work or school account.
The study guide says that if the exam is not available in your preferred language, you can request an additional 30 minutes to complete it. It also warns that localized exams may be updated approximately eight weeks after the English version and that localized versions may not always update on that schedule: https://learn.microsoft.com/en-us/credentials/certifications/resources/study-guides/gh-900. Check the current language and accommodation instructions early, not on the day you intend to book.
Microsoft states that a score of 700 or greater is required to pass GH-900. The certification page says a failed exam can be retaken 24 hours after the first attempt, while the timing for subsequent retakes varies. These are scheduling facts, not a reason to book before you are prepared; use the retake policy as a contingency and consult the current official policy for full details.
Register with an account you control
Microsoft recommends using a personal Microsoft account for registration because exam records can be lost and unrecoverable if an organizational account is used and you later leave that organization. Connect the certification profile to Microsoft Learn so you can schedule and renew exams and share and print certificates.
Check language and accommodation needs early
If you need assistive technology, extra time, or another modification to the exam experience, review Microsoft’s accommodation process before scheduling. Language-related extra time and other accommodations should be requested through the official process rather than assumed to be applied automatically.
After passing: credentials and sensible next actions
After passing, sign in to Microsoft Learn with the same account used for GH-900 and check the Credentials page for the GitHub Foundations entry. Microsoft Q&A guidance says that a result may take up to 24 hours to sync; if it remains missing, use Microsoft Credentials Support. Then turn the certification’s gaps into a next-skill plan rather than treating the credential as the end of learning.
The Microsoft Q&A instructions identify the credentials page as https://learn.microsoft.com/users/me/credentials/?tab=credentials-tab and the support route as https://aka.ms/credentialssupport. They also describe using the available view or print option and printing to PDF or saving as PDF to keep a copy. These account and certificate steps are separate from exam preparation, but checking them prevents avoidable confusion after a result.
For professional development, choose the next topic from your weakest domain and your actual work objective. A learner interested in automation can continue with GitHub Actions; someone responsible for repository controls can explore GitHub administration; someone focused on secure delivery can study GitHub Advanced Security. Microsoft’s GitHub training hub links to these learning collections: https://learn.microsoft.com/en-us/training/github/.
Keep your notes and the current study-guide link. The GH-900 blueprint can change, and Microsoft labels the study guide with its revision information. Before a future attempt or a later recommendation to another candidate, recheck the official domains, languages, duration, scoring, and scheduling page rather than reusing old details.
If the credential is not visible
Wait up to 24 hours for synchronization if the exam was passed recently. If the credential still does not appear, sign in to Microsoft Credentials Support with the same Microsoft account, complete the profile information, describe that GH-900 was passed but the certificate is missing, and submit the request through the official support route.
Turn foundational knowledge into applied practice
A useful next action is to maintain a small repository with documentation, issues, pull requests, project tracking, and appropriate access settings. This lets you reinforce the relationships GH-900 measures while developing evidence of practical use that a certification alone cannot provide.
Conclusion
The strongest GH-900 preparation is a coverage-and-application process, not a hunt for memorized answers. Establish the Git and GitHub foundation first, work across all seven official domains, practice the platform’s workflows, and use the practice assessment to locate gaps. Before scheduling, verify the current language, price, timing, proctoring, account, and accommodation information on Microsoft Learn. After passing, confirm the credential in Microsoft Learn and choose a follow-on GitHub skill that matches your work.
Related exams
- GH-100 exam — GitHub Administration
- GH-200 exam — GitHub Actions Exam
- GH-300 exam — GitHub Copilot Exam
- GH-500 exam — GitHub Advanced Security Exam