Microsoft Forms

What Microsoft Forms is

Microsoft Forms is Microsoft’s web service for surveys, registration forms, polls and quizzes. It belongs to the Microsoft 365 environment and also supports personal accounts, with differences in features and capacity. Authors design questions and rules; participants respond through a link; the team reviews responses and, where appropriate, transfers them into analysis or a subsequent workflow.

Its basic unit is a form, not a complete case file. Receiving a request does not automatically assign an owner, verify the submitted claims or document a resolution. This distinction makes it useful as an information intake tool while requiring explicit design of subsequent steps. As a web service, it can accept responses across devices without a dedicated desktop application.

Reference documentation: Microsoft — Forms launch for Education · Microsoft Support — Create a form · Microsoft Support — Send a form.

History and products to distinguish

Microsoft announced Forms availability for Office 365 Education on 20 June 2016. Its educational origins explain the emphasis on quizzes, marking and rapid feedback. The preview expanded to commercial Office 365 customers in 2017 and to personal users in 2018.

Forms Pro followed a separate path, becoming Dynamics 365 Customer Voice in 2020 for customer-experience and relationship scenarios. Old Forms Pro documentation should not be treated as a feature list for ordinary Forms. Nor should Forms be assumed to be automatically equivalent to complex InfoPath form solutions.

Subsequent development added live presentation of results and Copilot-assisted creation. These changes broaden how a survey is prepared and used; they do not remove the need for appropriate questions or a defined response-review process.

Reference documentation: Microsoft — Forms launch for Education · Microsoft — Commercial preview · Microsoft — Consumer preview · Microsoft Learn — Forms Pro transition · Microsoft — Live presentation · Microsoft Support — Copilot in Forms.

Collecting responses through a defined route

Microsoft Forms creates forms and quizzes. Branching directs participants to relevant questions based on their answers, so not everyone follows identical content. The logic should represent an understandable decision: which answer changes the route and what information each route still needs.

Settings also determine who can respond. Certain organisational configurations can record names and limit responses to one per person. Decide whether identification is necessary or whether aggregated responses are sufficient before enabling these options. The technical settings must match the explanation given to participants.

Reference documentation: Microsoft Support — Use branching logic in Microsoft Forms · Microsoft Support — Choose who can fill out a form or quiz.

Questions, sections and languages

Question types collect choices, text, ratings or dates; other types support ranking, Likert scales, file uploads or an NPS question. Match the type to the information required: ranking preferences is different from rating every option, and a satisfaction scale does not measure hazard exposure.

Sections divide the journey. Branching can move forward to later questions or the end, but should not be designed as a loop back to earlier questions. A route map helps identify mandatory questions that would be irrelevant to some participants.

Multilingual support combines versions of one form and records the response language. Authors supply and review translations of questions and options. Spanish, Catalan and English versions should preserve intention and scale: translating a label with a different intensity can create differences later mistaken for differences between groups.

Reference documentation: Microsoft Support — Create a form · Microsoft Support — Multilingual forms · Microsoft Support — Use branching logic in Microsoft Forms.

Quizzes, results and live presentation

A quiz adds correct answers, scoring and review options. It can provide a brief concept check after an explanation. Review the answer key before distribution: an incorrectly marked answer consistently propagates an incorrect score. Open questions may require the author’s judgement and individual feedback.

Forms provides question summaries and individual response inspection. Presentation mode updates as responses arrive and supports access through a QR code or link. This is useful during sessions, although showing results while people are responding can influence those who have not finished.

Excel supports detailed inspection and further analysis. Retain the questionnaire version, original responses and rules for excluding test submissions. Percentages for a multiple-selection question can total more than one hundred; each chart should explain whether it counts people, submissions or selected options.

Reference documentation: Microsoft Support — Quiz results · Microsoft Support — Form results · Microsoft — Live presentation.

Identity, collaboration and files

Responding, coauthoring and viewing results are different access paths. A collaboration link should not circulate as a participation link: coauthors can work with both questions and response data. A summary-sharing link also needs review before distribution.

Organisational settings restrict respondents and, depending on configuration, record identity or limit submissions. File uploads use the owner’s OneDrive or the group’s SharePoint, making storage and permissions part of the process. Ownership changes or SharePoint restrictions can affect attachment collection.

For a survey maintained over several months, document its owner, replacement arrangements, file destination and access removal. Continuity should not depend on one person keeping an account indefinitely or remembering every place a link was shared.

Reference documentation: Microsoft Support — Choose who can fill out a form or quiz · Microsoft Support — Coauthoring · Microsoft Support — Send a form · Microsoft Learn — File upload storage.

Integrations, licensing and Copilot

The Forms connector in Power Automate can trigger a flow when a response is submitted and retrieve its details. This supports an authorised registration or notification process. The response identifier helps prevent duplicates; check what happens if a later action fails and the flow runs again.

Capacity differs between personal, education, business and specialised environments. Limits on forms, questions, responses and characters are not interchangeable. A free personal account should not be assessed as though it had the capacity of a work account. Check whether subsequent integrations need additional licences.

Copilot helps draft forms and quizzes from a description and requires the corresponding account and licence. Review generated questions, choices, marking and language. Asking AI to produce a survey does not establish that it validly measures the phenomenon of interest.

Reference documentation: Microsoft Learn — Forms connector · Microsoft Support — Forms limits · Microsoft Support — Copilot in Forms.

Phishing abuse and respondent trust

Security researchers have documented surveys hosted on legitimate Microsoft services being used to deceive people and collect credentials. The issue is the form’s content and purpose: a familiar provider’s domain does not establish that the request is genuine.

Microsoft uses automated review to detect malicious collection of sensitive information and block suspicious forms; administrators can review flagged cases. These measures do not make every accessible form a verified communication. A preventive-work survey should identify its owner clearly and never request passwords or access codes. Someone receiving an unexpected request should be able to confirm its origin through an established channel.

Reference documentation: Microsoft Learn — Phishing review · OpenText security research — Abuse of surveys.

Uses in consultation and preventive preparation

• Training needs: ask about activities and difficulties to prepare a subsequent review with owners, without turning self-perception into an automatic competence diagnosis.
• Material comprehension: collect answers about reviewed communication and identify questions needing further explanation.
• Activity organisation: confirm availability or required resources without requesting unrelated information.

Sabentis proposes these as structured information-collection examples. An internally created form does not thereby become a validated risk-assessment instrument or sufficient proof of competence.

Worked example: identifying questions before training

Hypothetical example. A team is preparing sessions for several roles and wants to identify aspects of a procedure requiring clarification.

1. Define purpose and audience. Ask only for context needed to adapt the session and explain who will review responses.
2. Write clear questions covering one idea each, with options for not applicable or not known where appropriate.
3. Use branching to display questions specific to the declared activity. Prepare a route matrix and check that every relevant answer leads to a valid ending.
4. Test with different roles and devices. Verify identification, required fields and the final message, excluding test submissions from real analysis.
5. Review results with the training owner, examine recurring questions and document changes to the session.

Acceptance is more than receiving submissions: each route must be understandable and results must support a concrete decision. Distinguish a reported question from a need confirmed through review. Preserve the form version so later readers know which questions produced the answers.

Proposed numerical check: 60 people are invited and 42 valid responses arrive, giving 70% coverage. Only 18 follow the section for a particular activity and six report uncertainty: the result is 6/18, or 33.3% of those shown the question, not 6/42 or 6/60. The 24 people who did not see it are not counted as negative answers. This check detects denominator errors before the session is planned.

Before collection, prepare a short data dictionary recording each question, its unit, permitted options, route and meaning of a blank answer. Define which changes require a new version. If an option changes during collection, preserving its earlier wording prevents two different responses from being interpreted as answers to an identical question. This documentation allows someone else to reproduce the analysis and understand the decisions made.

Reference documentation: Microsoft Support — Use branching logic in Microsoft Forms · Microsoft Support — Choose who can fill out a form or quiz.

Anonymity, bias and poorly defined questions

Do not promise anonymity without checking settings and collected fields. Even without a name, combinations of site, role and free-text answers may identify a person. Avoid collecting health information unnecessary to the stated purpose.

An ambiguous question or one combining two issues produces difficult-to-interpret results. Branching can introduce bias if groups receive different questions later compared as equivalent. Document routes and do not treat a missing answer to an unshown question as a negative response. Review access to the form and its results separately. A technically successful submission does not validate the wording or sampling method.

Reference documentation: Microsoft Support — Use branching logic in Microsoft Forms · Microsoft Support — Choose who can fill out a form or quiz.

When to choose Microsoft Forms

It may fit organisations using Microsoft 365 that need a bounded consultation or quiz with defined respondents. Verify account features and restrictions before designing the process.

Microsoft Teams can support coordination and Excel authorised analysis. When comparing Google Forms, consider identity, permissions and maintenance as well as appearance. Test the actual respondent experience before distribution.

Frequently asked questions about Microsoft Forms in OSH

Does a quiz prove someone can perform a task?

It may provide evidence about particular answers, but does not replace practical assessment where performance must be observed.

Does one response per person guarantee a representative sample?

No. It reduces certain repetitions according to settings, but does not establish who responds, who is missing or which biases remain.

How should branching be checked?

Follow every relevant combination, verifying displayed questions, required fields and final outcomes against the intended design.

Reference documentation: Microsoft Support — Use branching logic in Microsoft Forms · Microsoft Support — Choose who can fill out a form or quiz.