Microsoft Forms ships with Microsoft 365 (formerly Office 365). It integrates seamlessly with Excel, Teams, and SharePoint, making it a de facto standard for internal surveys alongside Google Forms.
But Microsoft Forms has a distinct shape: strong inside the Microsoft 365 envelope, weaker the moment you step outside it. This guide covers the basics and lays out where Microsoft Forms fits and where it doesn't.
The short answer — Microsoft Forms fit map
| Use case | Fit |
|---|---|
| Internal surveys (Microsoft 365) | Excellent |
| Quick polls inside a Teams meeting | One of a kind |
| Detail analysis assumed to happen in Excel | Seamless |
| External / customer-facing surveys | Workable with extra config |
| Brand-sensitive customer surveys | Poor fit |
| 100+ questions or complex branching | Insufficient capability |
| Organizations without Microsoft 365 | Not available |
The basics — fastest path to a working form
1. Go to forms.office.com
Sign in with a Microsoft 365 account. Organizational accounts include this at no additional cost.
2. Click "New Form"
You can pick "New Form" or "New Quiz." For surveys, choose "New Form."
3. Set title and description
Title in the title field; in the description, include expected time and intent. "3 minutes." "We'll use this to decide A." One line moves response rates.
4. Add questions
"+ Add new" gives you the question types:
- Choice (single or multi)
- Text (short / long)
- Rating (star / numeric scale)
- Date
- Ranking
- Likert (matrix)
- File upload
- Net Promoter Score® (dedicated)
Having a dedicated NPS question type is a real Microsoft Forms strength. The 0–10 scale auto-categorizes Promoters / Passives / Detractors.
5. Distribute from "Responses"
Top-right "Responses" → "Copy link," "QR code," "Email," or "Embed code."
Microsoft Forms' strengths — integration within the Microsoft world
Strength 1: Excel integration is instant
"Open in Excel" loads the response data in Excel with future responses auto-syncing. Pivots, functions, and charts in Excel just work.
Strength 2: Polls inside Teams meetings
Add "Forms" to a Teams meeting via Apps and push polls to attendees in real time. Results appear immediately — invaluable for webinars and workshops. This is difficult to replicate in other tools.
Strength 3: SharePoint and OneDrive integration
Embed forms on a SharePoint site. Internal portals get a natural collection flow.
Strength 4: Power Automate
On submission, automatically:
- Notify a Teams channel
- Send an Outlook email
- Log to a SharePoint list
- Kick off an approval workflow
No-code orchestration of these is a major Microsoft 365 ecosystem benefit.
Mid-level operations — what separates pros from beginners
Branching
Question "︙" → "Add branching." Branching is per-question (more flexible than Google Forms' per-section model).
Q1: Department
- Engineering → Q3
- Sales → Q4
- Other → Q5
That said, the editing UI for complex branching isn't ergonomic — past 3 levels, it gets hard to manage.
Theme customization
The "Theme" icon offers:
- Preset themes (around 10)
- Custom color (hex)
- Background image upload
Slightly more freedom than Google Forms, but font is fixed, branding can't be hidden, thank-you page isn't editable. Not enough for serious brand forms.
Required questions and response limits
Per-question "Required" toggle. "Limit to one response per person" is organization-account-only via "organization-only" mode.
Response cap and deadlines
Settings → Responses → start date, end date, and response cap. Easier to set than in Google Forms.
The real topic — Microsoft Forms' ceilings
Ceiling 1: The "external sharing" trap
By default, only "people in your organization" can respond. For external surveys:
Settings → Who can fill out this form → "Anyone can respond"
You must flip this — and the failure mode "sent the URL externally without flipping it, so external respondents are locked out" happens constantly.
Furthermore, in external mode:
- You can't capture authenticated respondent identity
- Anti-spam is weaker
- File upload gets disabled
The design treats external use as "restricted-feature mode," which leaves external surveys feeling thin.
Ceiling 2: URLs are long and ugly
Microsoft Forms public URLs look like:
https://forms.office.com/Pages/ResponsePage.aspx?id=XXXXXXX...
Very long, and Pages/ResponsePage.aspx screams "generic Microsoft page." Hurts presentation as a branded form.
Ceiling 3: Fonts and layout are constrained
- Asian-language fonts are fixed
- Field width and placement aren't tunable
- No HTML/CSS editing
- Thank-you page layout can't be changed
The "safe, neutral Microsoft look" turns into a constraint when you need brand identity.
Ceiling 4: Organizations without Microsoft 365 can't use it
Microsoft Forms requires a Microsoft 365 subscription to create (free Microsoft accounts get a lightweight version with feature gaps).
Sharing form design with external partners on the same tool is impractical.
Ceiling 5: Branching editor stays weak as logic grows
The feature is there, but there's no holistic view of the branch tree. Past ~10 questions with non-trivial branching, you're keeping the structure in your head, and mistakes accumulate.
Ceiling 6: Free-text AI analysis is thin
Copilot integration is improving, but automatic theme extraction on open-ended responses isn't at production quality. Either pipe out to a text-analytics tool or move to a different platform.
When to use Microsoft Forms — and when not to
Use it when
- Internal surveys at a Microsoft 365–heavy organization
- Real-time polling inside Teams meetings
- You want to integrate with existing Excel / Power BI flows
- You want Power Automate to handle the post-submit workflow
- Employee engagement, training feedback
Don't use it when
- Deploying to organizations without a Microsoft 365 contract
- Brand-sensitive customer-facing research
- Joint surveys with external partner companies
- 100+ questions, 4+ branch levels
- Insight-driven research dominated by free text
- You need a custom domain for distribution
"Microsoft Forms vs. Google Forms"
Functionally similar, philosophically different.
| Dimension | Microsoft Forms | Google Forms |
|---|---|---|
| Ecosystem | Microsoft 365 | Google Workspace |
| Excel integration | Excellent (instant) | Workable (via Sheets) |
| Teams meeting polls | One of a kind | None |
| Question-level branching | Yes | Section-level only |
| External distribution ease | Moderate | Good |
| Free-tier scope | Limited (lightweight) | Good |
| Design freedom | Moderate | Moderate |
| NPS question type | Built-in | None |
So in practice, "Microsoft-centric org → Microsoft Forms; Google-centric org → Google Forms" ends up being the deciding factor.
Where Repoan fits
Repoan aims to combine Microsoft Forms' strengths (lightweight internal use) with what external surveys actually require (brand control, complex branching, AI analysis).
- Ecosystem-agnostic — works whether your org is on Microsoft or Google
- Brand control — logo, color, custom HTML thank-you page
- AI question generation + AI free-text analysis — purpose-built rather than tacked on
- Question-level branching — including numeric range and multi-select bases
- Free plan available — no Microsoft 365 license required
Wrap-up
Microsoft Forms:
- Excellent for internal surveys inside Microsoft 365
- Teams in-meeting polls are unmatched
- External distribution, brand control, and complex branching hit ceilings
- "Inbound" vs. "outbound" use cases diverge sharply on fit
If you take stock of "what's annoying me about Microsoft Forms right now," the resolution of your tooling decision sharpens. A hybrid — use Microsoft Forms' strengths inside the org, fill external use cases with a different tool — is a perfectly reasonable answer.
Related reading: