GH-900
GitHub Foundations
GH-900 GitHub Foundations Exam Guide: Skills, Preparation, and Scheduling Decisions
GH-900 validates foundational knowledge of GitHub concepts, products, collaboration, contribution, repositories, project management, and modern development practices. Microsoft positions it for non-developers, developers, and other GitHub users who want to confirm their understanding of the platform rather than prove advanced programming ability. This guide helps you decide whether your current experience is enough to schedule the exam, which measured domains deserve the most study time, and how to turn Microsoft’s learning resources into a practical preparation plan.
Is GH-900 the right certification for you?
GH-900 is a beginner-level GitHub certification for candidates who need a reliable foundation in using and working with GitHub. It is a sensible starting point if you contribute to repositories, review changes, manage work, support development teams, or use GitHub without being a specialist developer.
Microsoft identifies non-developers, developers, and all GitHub users seeking stronger fundamentals as the intended audience. The stated background includes Git, repositories, collaboration tools, project management, and modern development practices. That audience is broader than people who write production code every day: a project coordinator or technical contributor can still need to understand branches, pull requests, issues, permissions, and automation.
The certification page classifies GitHub Foundations as beginner level. Its listed product is GitHub, and its role context includes Administrator, App Maker, Developer, DevOps Engineer, and Solution Architect. Those labels describe possible work contexts, not prerequisites that every candidate must satisfy.
Use the certification as a foundation check, not as evidence of advanced GitHub administration, secure software engineering, or deep programming expertise. If you already work with GitHub daily, compare your experience against the study guide domains rather than assuming familiarity with the interface covers the whole assessment.
What does the exam measure?
The current study-guide outline divides GH-900 into seven domains covering Git and GitHub basics, repositories, collaboration, modern development practices, project management, privacy and security, and the GitHub community. Preparation should follow those domains, with extra attention to the largest area: Git and GitHub basics.
As of the January 2026 study-guide revision, Understand Git and GitHub basics accounts for 25–30% of GH-900. Work with GitHub repositories accounts for 10–15% of GH-900, Collaborate using GitHub accounts for 10–15% of GH-900, Apply modern development practices accounts for 10–15% of GH-900, Manage projects with GitHub accounts for 5–10% of GH-900, Understand privacy, security, and administration accounts for 10–15% of GH-900, and Explore the GitHub community accounts for 5–10% of GH-900.
The percentages are planning evidence, not a promise about a particular form. They also should not be treated as isolated scores or as a reason to ignore smaller domains. A candidate who knows Git but cannot distinguish repository visibility, organization roles, project features, or community concepts still has meaningful gaps.
The study guide says the bullets under each measured skill illustrate how that skill is assessed and that related topics may also appear. Most questions cover general availability features; preview features may be included when they are commonly used. Check the current study guide again before final revision of your notes: Microsoft can update localized versions after the English version changes.
How should you prioritize the seven domains?
Start with the domain that carries the largest published range, then use practice results to adjust the order. A useful sequence is Git and GitHub basics, repositories, collaboration, modern development practices, privacy and administration, project management, and the GitHub community.
For Git and GitHub basics, learn the purpose of version control, the difference between Git and GitHub, and the relationship between repositories, commits, and branches. Also connect GitHub accounts, organizations, enterprise options, GitHub Flow, Markdown, GitHub Desktop, and GitHub Mobile to practical situations rather than memorizing names.
For repositories, study the purpose of common repository files such as README, LICENSE, CONTRIBUTING, CODEOWNERS, and SECURITY. Review how repositories are created and organized, how files are managed, and how templates, branches, insights, stars, dependency insights, and repository metrics support maintenance or visibility.
For collaboration, separate the jobs of issues, pull requests, and discussions. Then review linking pull requests to issues, using templates, filtering and assigning work, configuring notifications, and sharing documentation through Gists, Wikis, or GitHub Pages.
For modern development practices, understand what GitHub Actions is used for, the role of GitHub Copilot, the purpose of Codespaces and development containers, and when github.dev is a better fit than a cloud development environment. Treat these as product-purpose and scenario topics, not as a requirement to become an automation engineer.
For project management, review GitHub Projects, views or layout options, labels, milestones, workflows, custom fields, saved replies, assignees, and project insights. For privacy, security, and administration, focus on 2FA, passkeys, repository and organization permissions, visibility, branch protection, teams, roles, Enterprise Managed Users, and organization-wide Copilot policy management.
For the community domain, cover open source, GitHub Sponsors, following users and organizations, GitHub Marketplace, InnerSource, forks, templates, and discoverable repositories. Its smaller weighting makes it easy to postpone, but a short, deliberate review is more efficient than leaving it untouched.
Which official learning path should you use?
Use Microsoft Learn’s GitHub Foundations path as the backbone of preparation, then supplement it with targeted review and hands-on work. The listed path is beginner-friendly and includes eight modules, so it gives a structured route without requiring you to search randomly across GitHub documentation.
The path includes Introduction to Git, Introduction to GitHub, Introduction to GitHub’s products, code scanning on GitHub, GitHub Copilot, GitHub Codespaces, GitHub Projects, and communication using Markdown. These modules map well to the assessed foundations, repositories, collaboration, development-practice, project, and communication themes.
Do not treat completion indicators as proof of readiness. After each module, write a short explanation of what the feature does, when a team would use it, and what nearby feature it should not be confused with. For example, distinguish Git from GitHub, an issue from a pull request, github.dev from Codespaces, and a repository permission from an organization role.
The associated GH-900T00-A course is listed as a beginner course with a two-day duration and is available in English, Japanese, Korean, Portuguese (Brazil), and Spanish. Microsoft says preparation can be instructor-led or self-paced. Choose the course when you benefit from a fixed syllabus or guided instruction; choose self-paced modules when you need to spend more time on selected domains.
Official learning path: https://learn.microsoft.com/en-us/training/paths/github-foundations/ and course information: https://learn.microsoft.com/en-us/training/courses/gh-900t00
How can hands-on practice close the knowledge gaps?
Create a small practice repository and use it to reproduce the relationships described in the syllabus. The goal is not to build an impressive application; it is to make each GitHub concept concrete enough that you can explain its purpose and choose it in a scenario.
A practical sequence is to create a repository with a README, make a branch, commit a change, and open a pull request. Add an issue for the work, link the pull request to that issue, and inspect the review and notification flow. Use Markdown in the issue and pull request so that formatting is part of the exercise rather than a definition in your notes.
Next, create a simple project view and organize work with issues, labels, milestones, custom fields, or a workflow where available to you. Compare project tracking with repository-level collaboration. Record which object represents the work, which object proposes a code change, and which object gives a broader planning view.
Use Microsoft Learn’s modules to explore Actions, code scanning, Copilot, Codespaces, and github.dev. Access may vary by account, plan, permissions, or environment, so focus on understanding the documented purpose and relationships when you cannot run a feature. The learning path explains Codespaces as a fully configured development environment hosted in the cloud and describes github.dev as a distinct editor experience.
Keep a feature matrix with four columns: feature, primary purpose, related feature, and decision trigger. This is more useful than copying interface labels because it trains the comparison skill that foundational scenario questions commonly require.
What study method works when your Git experience is limited?
Learn the conceptual chain before learning product details: version control supports change history; Git implements version control; GitHub hosts and extends collaboration around Git repositories; branches isolate work; commits record changes; pull requests propose and review changes. This chain prevents isolated memorization from breaking down when a question uses unfamiliar wording.
If Git is new to you, spend your first study block on repositories, commits, branches, merging, and GitHub Flow. Explain each term in your own words and draw the path from a proposed change to a reviewed change. Then practice the same flow in a repository, even if the code is only a text file.
If you already use Git daily, do not spend all your time repeating commands. Your likely gaps are platform distinctions: account versus organization, repository visibility, permissions and roles, notifications, Projects, Pages, Marketplace, security settings, and the purpose of GitHub’s newer development tools.
Use active recall after every module. Close the page and answer questions such as: Why would a team use a pull request? What belongs in a repository’s SECURITY file? When would a project view be preferable to labels alone? What does branch protection control? What is the difference between a cloud development environment and a browser-based editor?
Use the official practice assessment only after an initial study pass, then classify every missed or guessed item by domain and by cause. A miss caused by an unknown term needs content review; a miss caused by confusing two similar features needs a comparison note; a miss caused by reading too quickly needs a question-reading correction.
How do you build a practical GH-900 roadmap?
A four-stage roadmap works well: establish the vocabulary, follow the official path, apply the concepts in a small workspace, and verify readiness with the official assessment and exam sandbox. Adjust the pace to your background rather than treating the sequence as an official Microsoft timetable.
Stage one is orientation. Read the current certification page and study guide, list the seven domains, and mark each as known, partly known, or unfamiliar. Confirm that your Microsoft Learn profile is connected to your certification profile before scheduling. Microsoft says this connection supports scheduling and renewing exams and sharing and printing certificates.
Stage two is structured learning. Complete the Git and GitHub modules first, then repositories and collaboration. Continue with modern development practices and Projects, and finish with privacy, security, administration, and community topics. After each topic, create a one-page comparison sheet and one practical example.
Stage three is application. Use a practice repository to perform a branch-and-pull-request workflow, manage an issue, organize a project, write Markdown, and inspect relevant repository or organization settings. Where a feature is unavailable, read the official material and document what decision the feature supports instead of attempting to simulate access you do not have.
Stage four is verification. Take the Microsoft practice assessment, review reports from previous attempts, and revisit only the domains that produce uncertainty. Use the exam sandbox to become familiar with the interface and interactive components before scheduling. Schedule only when you can explain the domain objectives without relying on copied wording.
The roadmap is a preparation recommendation, not a Microsoft requirement. Microsoft does not state that completing a particular number of modules or performing a particular lab guarantees a pass.
What are the delivery, language, and scoring details?
Microsoft states that GH-900 is a proctored assessment, may include interactive components, and gives candidates 100 minutes to complete it. Review the exam sandbox before test day so the interface is not a new source of friction during the assessment.
The certification page lists English, Spanish, Portuguese (Brazil), Korean, and Japanese as available exam languages. The study guide notes that localized exams are generally updated approximately eight weeks after the English version, although localized updates may not always follow that schedule. Confirm the available language in the Schedule Exam section before booking.
If the exam is not available in your preferred language, Microsoft says you can request an additional 30 minutes. This is an accommodation or language-support decision to resolve before the appointment, not something to assume will be added automatically at the start of the exam.
A score of 700 or greater is required to pass GH-900. Microsoft does not publish a simple percentage conversion that candidates can use to predict that score, so do not turn a practice-assessment percentage into an invented pass threshold.
The certification page says the exam is scheduled through Pearson VUE. Microsoft strongly recommends registering with a personal Microsoft account rather than an organizational work or school account because exam records can be lost and unrecoverable if you leave the organization.
What should you confirm before scheduling?
Confirm four items before paying or selecting an appointment: your account identity, the current exam language, the regional price, and your readiness by domain. These checks prevent administrative problems from undermining otherwise adequate preparation.
Microsoft lists the GH-900 price as US$99 and notes that pricing is based on the country or region where the exam is proctored. Treat that as official price guidance, not a universal final checkout amount; verify the amount and local conditions in Pearson VUE when you schedule.
Use a personal Microsoft account for the exam registration and connect the certification profile to Microsoft Learn. Check that the name and account you intend to use are consistent with the credential record you want to retain.
Review the current study guide immediately before scheduling, especially if your notes are based on an earlier blueprint. The January 2026 revision is the basis for the published domain ranges in this guide, while Microsoft notes that exam content and localized versions can be updated.
Schedule after a practice review shows no neglected domain. A strong result in Git basics does not compensate for an inability to reason about permissions, project tracking, security settings, or community features. If one domain remains weak, use the blueprint range to decide whether focused review or a broader second pass is appropriate.
Which mistakes make preparation less efficient?
The most expensive preparation mistakes are studying only Git commands, memorizing product names, ignoring smaller domains, and using unofficial recollections as if they were the blueprint. Replace each mistake with a decision-based study action tied to Microsoft’s measured skills.
Mistake one is treating GitHub as only a code-hosting site. GH-900 also covers collaboration, project management, security and administration, modern development practices, and community participation. Corrective action: build a seven-domain checklist and require evidence of understanding in every category.
Mistake two is confusing adjacent features. Issues, pull requests, discussions, Projects, Wikis, Pages, Gists, Actions, Codespaces, and github.dev all serve different purposes. Corrective action: write a purpose-and-contrast sentence for each feature and test yourself without looking at the source.
Mistake three is assuming that an interface tour equals understanding. A candidate may recognize a button but still be unable to select the right repository visibility, permission, workflow, or collaboration mechanism. Corrective action: study short scenarios and justify the choice in one sentence.
Mistake four is relying on exam dumps, leaked questions, or recalled questions. They are not a dependable substitute for the official objectives, and memorization cannot guarantee a passing result. Corrective action: use Microsoft Learn, the official practice assessment, the study guide, and legitimate hands-on exercises.
Mistake five is scheduling with an organizational account or overlooking language and accommodation needs. Corrective action: verify the personal account, language, timing, price, and support requirements before confirming the appointment.
What should you do after passing?
After passing, use Microsoft Learn to verify that the credential is attached to the account used for the exam, then save or share it through the available credential tools. Do not assume an immediate display problem means the result was lost.
Microsoft’s Q&A guidance says to sign in to Microsoft Learn with the same account used for GH-900 and open the Credentials page to find the GitHub Foundations entry. It describes using the view or print option and then printing to PDF or saving as PDF to keep a copy.
The same guidance says that if the certification does not appear even though the exam was passed yesterday, you should wait up to 24 hours for the result to synchronize. If it still does not appear, use Microsoft Credentials Support and describe that GH-900 was passed but the certificate is missing.
For a preparation record, keep your study guide version, completed learning modules, practice-assessment reports, and notes about weak domains. That record is useful when you decide whether to move toward GitHub administration, Actions, Advanced Security, Copilot, or another GitHub learning path; it is not a replacement for checking the current requirements of a future credential.
Certificate guidance: https://learn.microsoft.com/en-us/answers/questions/5816497/how-do-access-recently-given-exam-gh-900-github-fo
Your next actions for GH-900
Begin with the official study guide and certification page, not with a question bank. Record the seven domains, identify your weakest two, and reserve hands-on time for the GitHub features you can access. Then use the practice assessment and exam sandbox to decide whether to schedule or continue studying.
A practical next-action checklist is: connect your personal Microsoft Learn and certification profile; read the current domain objectives; complete the GitHub Foundations learning path; practice a repository workflow; review Projects, modern development tools, security, administration, and community topics; take the official practice assessment; inspect the exam sandbox; and verify Pearson VUE language, account, timing, and regional price details.
Schedule when your knowledge is explainable rather than merely recognizable. You should be able to state why a GitHub feature exists, distinguish it from a related feature, and identify the appropriate use in a straightforward team scenario. That standard gives your preparation a clearer basis than chasing an unofficial prediction of exam questions.
Conclusion
GH-900 preparation is most effective when you treat the exam as a platform-foundation assessment, not a narrow Git command test. Build the core Git and GitHub model first, cover every published domain, practice the collaboration and project relationships, and verify administrative details through Microsoft’s current pages. The final decision is simple: schedule when your practice review confirms balanced coverage and your account, language, and support arrangements are ready.
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