Schweizerform vs Microsoft Forms

If your organisation runs on Microsoft 365, Microsoft Forms is the form tool you already pay for. It is bundled, decent, well-integrated with Excel, Teams, and Power Automate, and millions of internal surveys and event sign-ups are processed through it every day. For a lot of low-stakes use cases it is exactly the right answer.

It is also a tool that Microsoft itself documents as unsuitable for sensitive personal data. That tension — between the path of least resistance inside an M365 tenant and the actual security and jurisdictional posture of the product — is the substance of this comparison.

How Each Product Positions Itself

Microsoft Forms — bundled, convenient, broad-purpose

Microsoft Forms is included with virtually every Microsoft 365 subscription (Business, Enterprise, Education, and personal). It targets quick, low-friction use: a poll inside Teams, a registration form for an internal event, a quiz for a training module, a Power Automate trigger feeding into SharePoint. Its pitch is convenience, integration depth, and zero marginal cost for organisations already in the Microsoft ecosystem.

Schweizerform — purpose-built for confidential intake

Schweizerform is built around a single architectural decision: every submission is end-to-end encrypted in the respondent's browser, and our servers physically cannot decrypt it. Hosting is in Switzerland, the operating entity is Swiss, and the product is designed for the use cases Microsoft Forms is documented as not being appropriate for — patient intake, legal client onboarding, whistleblower reports, financial KYC, journalism tip lines, HR investigations.

The Security Models — Where the Real Difference Lives

Both tools encrypt data. The word "encryption" hides almost all the detail that matters. Here is what it actually means in each product.

Microsoft Forms — TLS in transit, service-encrypted at rest

Microsoft Forms encrypts traffic between the respondent and Microsoft (TLS) and encrypts data at rest inside Microsoft 365 (BitLocker plus per-file Service Encryption). For some Microsoft 365 SKUs, organisations can layer Customer Key on top so they hold one root key. This is solid baseline security and meets standard enterprise expectations. It is, however, server-held: Microsoft's services see plaintext during processing, and Microsoft administrators in your tenant can view responses through the Forms admin and audit interfaces.

Schweizerform — zero-knowledge end-to-end encryption, by default

Schweizerform encrypts the entire submission inside the respondent's browser before any data reaches our servers. The encryption keys are derived from the form owner's Access Code and never transmitted. Our servers receive ciphertext only. This is true on every form, every field, every plan — including the free tier — and it is not a configuration toggle.

Microsoft's Own Guidance on Sensitive Data

This is the most important slide in any honest comparison of Microsoft Forms. Microsoft's product documentation explicitly tells customers not to put sensitive personal data through Microsoft Forms. The exact language varies across pages, but the substance is consistent across years of Microsoft Learn content:

Don't include personal or sensitive information, such as passwords, social security numbers, or financial information, in the form questions or responses.

Read carefully, this is not a UX suggestion. It is a scope limitation. Microsoft is documenting that the product is not engineered for the threat model that sensitive data demands — irrespective of M365's broader compliance certifications. Many organisations encounter this guidance only after they have already been using Forms for patient intake, exit interviews, or client onboarding. By that point, the cleanup is harder than the initial choice would have been.

Head-to-Head Feature Comparison

Jurisdiction, Hosting, and the EU Data Boundary

Microsoft has invested heavily in regional data residency, including the EU Data Boundary that as of 2024 keeps most Microsoft 365 service data inside EU/EFTA regions for EU customers. This is real and meaningful — disk-level data residency for European tenants is a genuine improvement over the pre-Boundary architecture.

It does not, however, change the parent company's nationality. Microsoft Corporation is a US-headquartered entity, and the US CLOUD Act applies to data held by US providers regardless of the physical location of the servers. Microsoft has resisted overbroad government requests in court (notably the Microsoft Ireland case), and the company publishes detailed law-enforcement transparency reports. But the legal exposure to US compulsory process remains, and is structurally distinct from the position of a Swiss provider operating only under Swiss law.

Compliance Frames — nFADP and GDPR

Microsoft 365 carries a long list of compliance certifications: ISO 27001, ISO 27018, SOC 2, HIPAA BAA availability, GDPR DPA, and a range of regional and sectoral attestations. For most enterprise procurement processes, this list is enough. For sensitive personal data — particularly nFADP and GDPR Article 9 categories — certifications are necessary but not sufficient. The architectural question of whether the processor can read the data still determines what notification, transfer, and breach obligations apply.

Schweizerform's architectural argument is simpler. Because we cannot decrypt submissions, we are not a meaningful processor of the personal data inside them — we process ciphertext. This narrows the surface of GDPR Article 28 obligations, simplifies cross-border transfer analysis (Swiss adequacy applies to the metadata we do see), and changes the breach-notification calculation under GDPR Article 33 and nFADP Article 24: a breach that exposes ciphertext is, by definition, not exposing identifiable personal data.

Pricing — Bundled vs Standalone

Microsoft Forms and Schweizerform compete on different cost axes, and a fair comparison has to acknowledge that.

Microsoft Forms' model

Microsoft Forms is included at no marginal cost in any Microsoft 365 subscription you already pay for. There is no Forms-specific upgrade path; capability tiers come from the underlying M365 SKU (Business Basic, Standard, Premium, E1, E3, E5, etc.). Forms is, in practical terms, a free feature of a subscription you have for other reasons.

Schweizerform's model

Schweizerform is a paid product with a free tier (1 form, 25 submissions per month, full encryption) and three paid tiers (Basic, Plus, Business) that scale form count and submission volume. There is no "secure" upgrade — every plan is end-to-end encrypted, including the free tier. The cost is for capacity and convenience, never for the cryptographic guarantees themselves.

Which Tool Fits Which Use Case

Pick Microsoft Forms when

• The form collects no sensitive personal data — internal polls, event RSVPs, satisfaction surveys, training quizzes
• Respondents are inside your tenant and you want native M365 sign-in / Entra ID enforcement
• Tight integration with Excel, SharePoint, Teams, or Power Automate is the primary value
• Quiz mode with auto-grading is a core requirement (training, certification, classroom)
• You need zero marginal cost and your buyers already pay for Microsoft 365
• The data you collect is acceptable to disclose to your tenant administrators and to Microsoft as a processor

Pick Schweizerform when

• The form collects health data, financial data, identification numbers, or any nFADP/GDPR Article 9 special category
• You handle whistleblower reports, journalism source intake, or any workflow where the respondent's safety depends on confidentiality
• You are subject to nFADP and want a Swiss-hosted, Swiss-operated provider with no US legal exposure
• Zero-knowledge — the operator physically cannot read submissions — is a procurement requirement
• Localisation into German, French, and Italian for Swiss/EU respondents is essential
• You need encryption on every form including the free tier without a paid upgrade path
• Your respondents are external — patients, clients, sources, applicants — and are not in your M365 tenant

When You Might Use Both

The honest answer for most M365 organisations is: keep Microsoft Forms for what it is good at, and add Schweizerform for what Microsoft itself recommends against. Microsoft Forms handles the operational, internal-facing forms that flow naturally through your M365 stack — team retrospectives, all-hands surveys, training quizzes, event sign-ups. Schweizerform handles the externally-facing or sensitive-internal forms — patient intake, legal client onboarding, exit interviews, whistleblower reports, sensitive HR investigations.

Splitting the workload this way is not a workaround — it is the architecture both vendors are pointing you toward when you read the documentation carefully.

Moving Sensitive Forms Off Microsoft Forms

Most organisations get to this comparison with a small number of Microsoft Forms that — on review — should not have been Microsoft Forms in the first place. Migrating just those is straightforward.

The Bottom Line

Microsoft Forms is a competent tool for the use cases it is built for. It is bundled with a subscription you already have, integrates beautifully with the rest of M365, and is the right answer for hundreds of internal-survey and quiz workflows. Nothing in this comparison argues otherwise.

Microsoft also documents — clearly, in its own product guidance — that Forms is not the tool for sensitive personal data. That guidance is not a marketing footnote; it is a scope statement, and it lines up exactly with how the product is engineered: server-held keys, US-headquartered processor, no client-side encryption. When the data crosses the line Microsoft itself draws, a different tool is required.

Schweizerform is built for the workloads on the other side of that line — patient intake, legal client onboarding, whistleblower reports, financial KYC, journalism source intake. The cryptographic guarantee is the same on the free tier as on the largest plan, the hosting is Swiss, and the operator physically cannot read submissions. That is the comparison, stripped of marketing.