Microsoft Forms: branching logic and quiz mode

Microsoft Forms is the tool everyone uses and nobody designs for. It's on every licence, it takes thirty seconds to make a form, and that's roughly the depth most people reach. Underneath, there's a set of features — branching, quiz mode, response controls, the live Excel sync, and now Copilot — that turn it into something you can run a real intake process or a compliance quiz on. This guide walks through those, honestly, including the point where Forms stops being the right tool.

Branching

Branching shows different questions depending on earlier answers. It's configured per question (the "…" menu → Add branching), and for each answer option you choose which question comes next — or End of form.

What people get wrong:

• Branching is per option, not per rule. You can't say "if score above 5"; you say "if they picked Yes, go to Q7." For numeric or text questions, branching applies to the question as a whole (go to Qn after this question) rather than to specific values. Design the form with choice questions at the decision points.
• Order matters. Branching jumps forward only. If the branch target is before the current question, Forms rejects it. Lay out the form in the order of the longest path, then branch around sections.
• Sections are the sane way to branch. Group questions into sections (Insert → Section) and branch to sections rather than to individual questions. A "Which department?" question that sends people to the HR section, the IT section, or the Finance section is readable and maintainable; a web of question-level jumps is not.
• Test every path. Preview the form and walk each branch. The classic failure is a branch that skips the required question the summary depends on.
• Skipped questions are blank in the results. In Excel, the row shows empty cells, not "not applicable." Anyone analysing the output needs to know which blanks are branching and which are refusals.

Branching is enough for intake forms with three or four paths. Beyond that — nested conditions, calculations, dynamic lists — you've left Forms' design envelope.

Quiz mode

A quiz is a form with correct answers, points, and feedback. Create it as New Quiz (converting a form later isn't supported, so choose up front). Per question you mark the correct option(s), assign points, and optionally add a message shown for each answer. Choice, text (exact match), and some other types can be auto-graded; free-text questions can be graded manually after submission.

Details that matter:

• Math mode lets you type equations and, for choice questions, generate suggested wrong answers.
• Practice mode (in the quiz settings) shows respondents whether each answer is right immediately and lets them retry, which is what you want for training and not for assessment.
• Show results automatically controls whether respondents see their score and the correct answers on submission. For anything summative, turn it off and release results later from the Responses tab.
• Shuffle questions and shuffle options reduce copying; combine with a time limit and a start/end date for exam-style use. There's no lockdown browser and no proctoring — it's a quiz, not an exam platform.
• Grading free text is done in Review answers, per response; scores then flow into the Excel export. It's workable for a class; it's tedious at a thousand responses.
• Certificates and pass/fail don't exist. Add a "you passed" message with branching on a final self-scored question, or handle it in Power Automate.

Quiz mode is mature and reliable for compliance knowledge checks, onboarding quizzes, and classroom use. It's the feature most organisations forget they already have when they go shopping for a quiz tool.

Response settings

Under the form's settings:

• Who can fill out: anyone with the link, only people in the organisation, or specific people and groups. The org-only options can record name (or not) and one response per person. External forms can't do either — an anonymous form has no identity to enforce it with.
• Start and end dates, a response limit, and a custom thank-you message with an optional link (the poor man's confirmation page).
• Email receipt to respondents (org forms) and notification to the owner on each submission — or, better, a Power Automate flow.
• Shuffle, progress bar, and "customise theme" are presentation settings; theme supports a logo and colours, not real branding.

Forms ownership is the governance gap people hit: a form belongs to its creator unless it's a group form (created in a Microsoft 365 group). Personal forms vanish from admin view when the creator leaves; group forms don't. Any form that runs a process should be a group form.

Excel and the live sync

Forms exports responses to Excel — and for forms created from Excel for the web ("Forms for Excel") or with the newer live sync, responses update the workbook automatically. The sync is real-time enough for a dashboard and it's the simplest way to get form data into Power BI without a flow. Caveats: the workbook lives in the creator's OneDrive (or the group's SharePoint), the sync is one-way, and editing the workbook's response rows doesn't change the form's data.

Copilot in Forms

With a Microsoft 365 Copilot licence, Forms can draft a form from a description ("a ten-question onboarding survey for new engineers"), suggest questions, and summarise responses in plain language. The drafting is decent — it produces sensible question types and reasonable wording — and the response summary is a fast way to read a few hundred free-text comments. Neither replaces designing the form for the analysis you'll actually do.

When to leave Forms

Forms is the right tool until you need one of: conditional logic on values or calculations; more than one form talking to each other; a lookup against live data (a list of current projects); saving and resuming; role-based views; or anything that writes to a system other than Excel and Power Automate. At that point it's Power Apps (with SharePoint or Dataverse behind it) for a process, or a proper survey platform for research-grade surveys with quotas and panels.

Until then: build it as a group form, branch with sections, and put Power Automate behind it for anything that needs to happen after submit. That covers the majority of "we need a form" requests without buying anything.