Microsoft Forms limitations: every documented limit in one place

It depends entirely on the account that owns the form. Microsoft's limits page lists 5,000,000 responses per form or quiz for Education, business and GCC tenants, and 50,000 for GCC High and DoD. For personal Microsoft accounts, the cap is 200 responses per form on a free account and 1,000 on a paid one. That personal-account cap is the one people hit by surprise: a free Outlook.com form shared on social media or at an event can fill up in an afternoon.

A response is one submission, however many questions it answers. Microsoft's example: a 100-question form completed by 12 people has 12 responses, not 1,200.

If you reach the cap, Microsoft's own advice is to export the existing responses to Excel and then delete them from the form, which frees the count so the form can collect again. That works, but it splits your data across exports, so export before deleting and keep the files together.

The 5,000,000 figure is how many responses a form can store, not how many it can fully report on. Above 50,000 responses Microsoft says you can export everything as a CSV, but these features are not supported: summary charts and graphs, viewing individual responses on the Forms site, printing, sharing a summary link, and manual grading, commenting or posting scores for quizzes.

Microsoft also blocks its aggregation results API above certain sizes: on business tenants, above 100,000 responses or when responses multiplied by questions exceeds 10 million; in other environments, above 70,000 responses or 5 million response-question cells. In practice, a 200-question form passes the business ceiling just above 50,000 responses.

The quietest limit is on duplicates. “One response per person” is only enforced within a continuous set of 50,000 responses, so on very large forms Microsoft doesn't guarantee one response per person across the full data set. Deduplicate in your export if it matters.

Up to 200 questions per form or quiz. Watch Likert questions: each statement in a Likert grid counts as a separate question, so a single Likert question with 20 statements uses 20 of your 200.

Microsoft doesn't publish a limit on the number of sections, or on the number of options in a choice question. What it does limit is text: each option in a multiple-choice question can hold 1,000 characters. If you are pasting a long list, such as every country or every product, into a choice or dropdown question, test it in Preview on a phone before sending; the documentation doesn't promise a number, so we won't either.

Branching in Microsoft Forms moves forward only. Microsoft's example: in a seven-question form, question 4 can branch to questions 5, 6, 7 or the end of the form, and nothing earlier. If you point a branch backwards, Microsoft warns that respondents skip the remaining questions and land on the Submit button, so a single wrong branch can silently cut your form short.

Each branch is set on one question (or one section) at a time, choosing where each answer leads. The documented feature has no rule builder for combining answers (“if A and B”), no calculations, and no way to route on a score. For branching that needs any of those, you'll either split the form in two or use a different tool; our guide to conditional logic forms explains the difference between section jumps and rule-based logic.

Some of the most frustrating Microsoft Forms limitations aren't numbers. They're rules in the settings pane that turn features off when you use others.

You can stop accepting responses manually or with a start and end date, but the settings pane has no “close after 100 responses” option. For limited places, such as workshop seats, you need Power Automate or a manual check. That's the most common request behind “microsoft forms limit number of responses”.

Record name, one response per person, and file upload are only offered when the form is restricted to people in your organization. A form set to “Anyone can respond” can't limit duplicate submissions or accept files. We cover the file side in detail in our guide to Microsoft Forms file upload for external users.

Microsoft says you can't shuffle questions in a form with multiple sections or pages, and the progress bar is only available on forms that have them. So you choose between randomized order and a paged form with progress.

Besides the 200-response cap, personal accounts can't use the in-organization audience settings or the Shorten URL option, and Microsoft's Power Automate connector only works with organizational accounts. Group forms also don't appear in the connector's form list; Microsoft says to paste the Form Id by hand.

For internal surveys on a Microsoft 365 work account, the numeric limits are generous and most teams never touch them. The limits that push people elsewhere are functional: public forms that need file uploads, forms that should close at a fixed number of sign-ups, conditional logic beyond forward jumps, and a personal account's 200-response cap. If you're weighing Microsoft's tool against Google's on those points, see our Microsoft Forms vs Google Forms comparison.

Zunoform covers the functional gaps: conditional logic rules on answers, closing a form by date or by response count with a custom message, file uploads without respondent sign-in, one-response-per-person options that work on public forms (with honest strength labels; the strongest are signed-in accounts and one-time links), and scored quizzes that route to different endings.

It is not the better choice on raw volume. Zunoform's plans cap responses per account per month: 500 on Free, 5,000 on Pro and 25,000 on Business, while Microsoft allows up to 5,000,000 per form on a work account. It also doesn't offer SSO, SOC 2 or HIPAA agreements, which many Microsoft 365 organizations require. If your form lives inside your tenant and needs neither public uploads nor response caps, Microsoft Forms is already paid for and is the sensible default.