Microsoft Forms supported features and where they apply

Microsoft Forms is a lightweight form, quiz and survey builder that runs in a browser, in Teams, and on mobile. It provides choice, text, rating, date, ranking, Likert and NPS question types, branching, file upload, themes, quizzes with scoring, and collaboration — but specific features and storage behavior depend on whether the form is owned by a personal Microsoft account, a Microsoft 365 work/school account, or a Team. This article lists the core features, shows which features vary by environment or SKU, documents common limits and gotchas, and summarizes integrations and privacy/security considerations.

What Microsoft Forms is and what 'supported features' means

Microsoft Forms is a form-building service you use for quick surveys, quizzes and simple data collection. It appears as a standalone web app at the Forms page, as an app inside Microsoft Teams, and as a mobile app.

What I mean by "supported features": the UI and functionality available to build or respond to a form (question types, branching, file upload), platform differences (Forms web, Forms in Teams, mobile), license- or SKU-based differences (consumer vs Microsoft 365 Business/Enterprise or Education), integration points (Excel export, Power Automate connectors, Teams embedding) and operational constraints (storage location, response quotas, accessibility and privacy controls). Where a feature depends on storage, sign-in, or subscription, that distinction is called out.

Which question types and core features you can expect

Here are the concrete features you will find in Microsoft Forms and what each does.

• Choice: multiple choice questions with single or multiple answers; supports branching based on selected options.
• Text (short or long): single-line or multi-line free-text answers for open feedback.
• Rating: star or numeric ratings for quick sentiment or satisfaction measures.
• Date: lets respondents pick a date for scheduling or sign-ups.
• Ranking: respondents order items by preference.
• Likert: multiple statement items sharing the same agreement/scale options.
• Net Promoter Score (NPS): a standard NPS question type with the typical 0–10 scale and scoring.
• File upload: respondents upload files; uploaded files are stored in the form owner’s OneDrive for Business or the Team/SharePoint site depending on ownership.
• Branching and sections: conditional show/hide or jumps between sections based on prior answers; useful for conditional flows and skipping irrelevant questions.
• Quizzes with points and automatic grading: assign points to correct answers; Forms auto-grades objective questions and can display scores to respondents.
• Themes and images: built-in themes, custom headers and images for questions and sections.
• Collaboration and co-authoring: share a form for multiple people to edit, and share response viewing rights with colleagues.

For example, for a course quiz you can use multiple choice and text questions, assign points to objective items for automatic grading, add branching to skip review questions for correct answers, and enable collaboration so another instructor can edit and review the form before publishing.

Where features differ by account, license, or host (Forms web, Forms in Teams, mobile)

Decide which account will own the form: a personal Microsoft account, a Microsoft 365 work/school account, or a Team/SharePoint site. Ownership affects storage, sharing and some features.

• Personal Microsoft accounts: core question types, basic branching and themes are available. Enterprise features tied to tenant controls, tenant data residency, and SharePoint-based storage are not available.
• Microsoft 365 Business/Enterprise and Education: tenant administration, data residency alignment, integration with Power Automate and Teams, and storage of uploads in OneDrive for Business or the owning SharePoint site. Education tenants often include additional quiz/assignment features for grading workflows.
• Forms in Teams: creating a form as a Team app/tab makes the form owned by the Team (SharePoint/Group). Files uploaded to a Team-owned form are stored in the Team’s SharePoint/OneDrive. The Teams editor can be a reduced interface; some advanced settings require opening the full Forms web app.
• Mobile app and mobile browser: most question types and response collection are supported on mobile, but building or troubleshooting complex branching is easier in the web editor.

Short example: file upload requires authenticated storage. If a Microsoft 365 user owns the form, uploads save to that user’s OneDrive (or the Team SharePoint for Team-owned forms). For a personal account, uploads use the consumer OneDrive associated with that account.

Common limitations and quota gotchas to watch for

Administrators should document these practical limits and behaviors.

• Response limits: Forms enforces limits on how many responses a form will accept. The exact limit can change and can vary by tenant and license. If you expect large volumes, check current Microsoft documentation and consider routing responses to another store in real time.
• File upload size and storage: uploaded files are subject to per-file size limits and to the owner’s OneDrive or the Team’s SharePoint quota. Those quotas follow your tenant storage policies. Confirm available space before enabling uploads and warn respondents about allowed file types.
• Branching and section complexity: very deep or numerous branching rules can be hard to manage and can behave unexpectedly in the mobile interface. There are practical limits on the number of sections and branching rules; test all branch paths.
• Question-count limits: a form can contain many questions, but very long forms may slow the editor and degrade the respondent experience on mobile.
• Anonymous and external responses: some features don’t work with anonymous or external responses. File upload typically requires sign-in because files must be saved to authenticated storage; some analytics and audit features require authenticated responses.
• Multilingual support: you can add multiple languages for the question text, but Forms does not provide automatic translation of responses. Managing localized branching and labels is manual.

Workarounds: if you need higher limits or stronger control, route submissions via Power Automate to SharePoint, Dataverse, SQL or another system of record, or use a more feature-rich survey platform for enterprise-scale needs.

Always validate limits against current Microsoft documentation for your tenant because service limits and licensing rules change.

How Microsoft Forms integrates and what data you can export or automate

These are the common integration points and what they preserve in exports.

• Export to Excel: you can export responses to an Excel workbook. Basic responses, timestamps and selected choices export cleanly. Uploaded files export as links or file references; the files themselves remain in OneDrive/SharePoint. Quiz scores appear in the workbook; some quiz metadata and auto-grading rules are not preserved for re-import.
• Live response view and built-in analytics: Forms shows summary charts and individual responses in the UI. The numeric data exports; chart formatting and the UI-only visuals do not transfer to the workbook.
• Power Automate connector: use the When a new response is submitted trigger and the Get response details action to start flows. Common automations include writing responses to a SharePoint list, sending notifications to Teams or email, and saving uploaded files to specific document libraries.
• Teams and SharePoint embeds: embedding a form in Teams or SharePoint preserves respondent functionality, but ownership determines where files are stored. Editing advanced settings often requires opening Forms in the browser.
• What may not transfer perfectly: rich text formatting in long answers, some quiz scoring configuration, and visual themes. If you change or delete questions after collecting responses, exported columns can become misaligned with the original meaning of older responses.

Example automation:

1. Create a flow that triggers when a new Forms response is submitted.

When a new response is submitted
Get response details
Create item in SharePoint list
Copy uploaded file to document library

2. Use Get response details to map individual question responses to SharePoint columns and to handle file link copying.

Accessibility, data residency, and privacy/security features

Microsoft Forms includes several controls and behaviors relevant to compliance and privacy.

• Sign-in requirement and anonymous responses: you can require sign-in to collect authenticated responses, which supports auditing and identity-based restrictions. Allowing anonymous responses disables some identity-dependent features such as file upload and detailed per-user analytics.
• Data residency: when a form is owned in a Microsoft 365 tenant, stored responses and uploaded files follow your tenant’s data residency rules. For personal Microsoft accounts, storage follows consumer OneDrive rules.
• GDPR and privacy: tenant-level compliance and administrative controls apply to Forms when used in Microsoft 365. Administrative controls include the ability to manage who can create forms, external sharing options, and retention policies set at the tenant level.
• Accessibility: Forms supports keyboard navigation and screen readers; run the preview and an accessibility checker during design. Complex layouts or custom images can reduce accessibility if not captioned or described.
• Security of uploaded files: uploaded files are saved to OneDrive for Business or the Team’s SharePoint site and inherit the document library permissions of that location. Manage sharing and retention via your existing OneDrive/SharePoint policies.

Confirm tenant-specific policies for retention, external sharing and auditing with your compliance team before broad deployment.

Quick checklist: choose and deploy Microsoft Forms features safely

1. Decide ownership and storage path.

Create the form under: your work/school account (OneDrive) or the Team (SharePoint)

2. Confirm whether respondents must sign in.

• If you require file uploads or authenticated audit trails, require sign-in.

3. Check storage quotas.

• Confirm OneDrive/SharePoint available space before enabling file upload.

4. Map expected response volume.

• If you expect high volume, pilot the form and consider Power Automate to offload responses in real time.

5. Design branching conservatively.

• Test every branch path on desktop and mobile.

6. Plan integrations and exports.

• If you need data in Excel or a system of record, define the target schema and test how uploads and long answers export.

7. Verify privacy and compliance settings.

• Confirm where data is stored and whether sign-in is required to meet data-residency and GDPR needs.

Enable anonymous responses only when you do not need authenticated auditing or uploaded files. After enabling anonymous responses, identity-based features will not work.

8. Run an accessibility check.

• Use the form preview and an accessibility checker to ensure screen reader compatibility and keyboard navigation.

9. Document your setup for the team.

• Note owner, storage location, retention policy and any automations that move or copy responses.

Conclusion

Pick the account and ownership model first — it determines storage, sharing and many feature differences. Use Microsoft Forms for light-to-moderate surveys, quizzes and simple workflows. If you need higher limits, structured enterprise storage, or stronger auditing, route responses via Power Automate into SharePoint, Dataverse or another system of record. Before rollout, test branching and uploads, confirm storage quotas and sign-in requirements, and document the owner, storage location and any automations that move or copy responses.

Frequently Asked Questions

Can external users upload files to a form?

Usually not unless the form requires sign-in and your tenant allows external authentication. File upload needs authenticated storage, so allowing anonymous responses typically prevents file uploads.

Will Excel export include uploaded files?

The Excel export contains links or references to uploaded files; it does not embed the files. The actual files remain in OneDrive or SharePoint where the form owner stores them.

Does Forms store data in a specific region?

Responses and uploaded files follow your tenant’s data residency rules when the form is owned in a Microsoft 365 account. For personal Microsoft accounts, storage follows consumer OneDrive rules. Check your tenant documentation for exact residency details.

Is branching supported the same in Teams and the Forms web app?

Branching works in both, but complex branching is easier to build and test in the full Forms web app. The Teams-embedded editor can be a reduced interface; open the web app to access advanced editing features.