Microsoft Forms what changed and how it affects your forms

Microsoft Forms is the web tool for creating surveys, quizzes and collecting responses; recently its editor UI and several controls were reorganized. The tool still supports the same core tasks (create surveys/quizzes, apply themes, set branching, share for collaboration and export responses), but many commands moved to new locations: a compact header, a right-hand question properties pane, and overflow menus in the Responses tab. This article summarizes the UI and feature changes, lists what moved or was added, explains effects on common tasks (quizzes, branching, export), clarifies who sees the changes and why, and gives practical workarounds or steps to restore older behavior where possible.

What people are noticing first

Most users notice a different header and a more compact editor layout. The form title, theme control and Share/Collect options are grouped differently; the response count and some settings no longer share the same flyout in some views.

Icons and labels have been trimmed: a gear icon that used to open many settings now opens a subset, and a right-hand pane combines question properties and branching controls. The header often shows the form title on the left, a centered question count, and a cluster of compact icons on the right where Theme, Preview, and Share used to be labeled buttons. That cluster opens a small menu rather than a wide toolbar.

This is a reorganization, not a removal of every capability. Most commands are still present, but they appear under icons, ellipsis menus, or within the right-hand properties pane. For example, the old top "Theme" button may now be a paintbrush icon in the compact header or a tab inside the right-side pane.

Exactly which features changed and where they are now

Start with a short map: these features were added, moved, or consolidated.

• Branching (conditional logic): moved from a per-question menu into the question properties pane on the right. Look for a "Branching" tab or a link labeled "Add branching" in that pane.
• Themes and appearance: consolidated into a compact theming pane. The path is now the paintbrush icon in the header, which opens a small overlay showing theme presets and color choices.
• Collaboration (share for co-authoring): moved from a visible button to the Share menu. Path: header Share icon > choose "Share to collaborate" or "Get a link to collaborate".
• Responses view and analytics: the Responses tab is still present but analytics summaries are more compact and export options sit behind an overflow menu within that tab.
• Excel export: still available but the path changed. Go to Responses > More options (ellipsis) > Open in Excel or Download as Excel.
• Settings (who can respond, accept responses, start/end dates): split between a simplified header gear and additional options in the right-hand pane. Path: header gear > Basic settings, and for advanced options open the right pane > Settings tab.
• Branding and custom images: may be limited by account type and appear under a "Branding" subsection rather than the main theme list.
• Power Automate and connectors: flow creation and editing links are now in the More options menu in Responses and in the three-dot menu at the form level.

For example, to set up branching on question 3 now:

1. Click the question.
2. Open the right-hand properties pane if it isn’t already visible.
3. Select the "Branching" tab and configure destinations for each answer.

exact menu text can vary by tenant and release channel; if you don’t see the name above, look for the equivalent icon or an ellipsis menu.

Who the changes apply to and why Microsoft made them

Rollout is tenant- and program-specific. Targeted Release tenants, EDU tenants and commercial customers see updates on different schedules: targeted release accounts typically see updates first, then general release follows. Some EDU-specific features or layout tweaks may remain restricted to EDU tenants.

Microsoft described the reorganization as an attempt to reduce clutter and group related controls into panes so the editor scales to smaller screens and additional features. Security and permission controls were also moved under admin-managed areas or hidden behind tenant policy in some cases.

Where it does not apply: on-premises or very old account types that use legacy Forms integrations may not see these web changes. If your organization disabled targeted release or applied a custom policy, you may remain on the older layout longer.

For administrators: rollout timing is tenant-specific. If you manage a tenant and need dates or notices, check the Microsoft 365 admin center message center — it’s the authoritative place for scheduled updates. If you are a teacher or office user, your IT team can confirm when your organization will switch or if a tenant policy is restricting features.

How these changes affect the tasks you do every day

The core tasks still work, but the steps and clicks changed. Below are common tasks with before/after notes.

Quizzes:

Before, score settings and correct answers appeared inline with each question. After, the answer key and scoring are in the right-hand pane under an "Answer key" or "Quiz settings" tab.

Effect: setting points and feedback still works, but you open the pane per question rather than using inline controls.

Branching (conditional navigation):

Before, branching was a separate dialog. After, branching is in the question properties pane and may show a compact flow visualization.

Effect: it’s faster to edit multiple branches without leaving the editor, but large branching flows can feel tight in the pane.

Analytics and responses:

Before, analytics summaries were expanded and included prominent charts. After, summaries are more compact; you must click to expand certain charts.

Effect: quick stats remain visible, but you may need an extra click to reach detailed views or to export.

Collaboration:

Before, a visible "Share to collaborate" button was always present. After, collaboration links are in the Share menu.

Effect: sharing for co-authoring requires opening the Share menu first, adding a step but centralizing sharing options (responders, collaborate, copy link).

Export and integrations:

Before, an "Open in Excel" button often lived directly on Responses. After, Excel and Power Automate integration appear under More options in Responses.

Effect: exports and automations are still supported; flow creation may open Power Automate and require an extra confirmation.

Example: if you create a scored quiz with conditional branching and export results to Excel, you now open the question pane for scoring and branching, then go to Responses > More options to export. The net time difference is small, but you will need to relearn the clicks.

Quick fixes and workarounds if something moved or disappeared

If a control moved or seems missing, try these steps first.

1. Refresh and sign out/in. A session refresh can show the updated UI or revert to the expected pane.
2. Look for icons instead of labels: a paintbrush (theme), a gear (settings), three dots (more), a share arrow (Share/collect). The option you want is often under an ellipsis.
3. Use the right-hand properties pane for question-level actions. Click a question and check that pane for branching, points and validation.

if an item genuinely isn’t present for your account, your tenant policy or license may hide it.

4. Export data if you need older formatting:

Responses > More options (ellipsis) > Open in Excel

5. Recreate exports or routing with Power Automate if a built-in option is limited. Create a flow that triggers on Forms response and writes to Excel, SharePoint or sends a notification.
6. If you prefer the older appearance, some tenants temporarily offer a classic view toggle. Check header menus for "Return to classic" or ask your admin if a temporary setting exists.
7. For collaboration when the link option is hard to find: open Share > Get a link to collaborate > copy. If that exact label isn’t present, choose the option that mentions co-authoring or editing rights.

If none of the above works, document the missing feature and raise it with your IT help desk. Include a screenshot and the account type (consumer/edu/business) so they can check tenant-level controls.

What IT admins should know and next steps for users

Admins control part of the rollout and can reduce user confusion. Key actions for admins:

• Check the Microsoft 365 admin center message center for Forms-related notifications.
• Review tenant settings and targeted release configuration; decide if you want early updates or to wait for general release.
• Determine whether any features have been disabled by policy (for example, external sharing of forms or brand customization) and communicate those policies to users.
• Prepare a short internal note or training that shows the new header, where to find Share/Theme/Responses, and where branching now lives. A single screenshot with marked icons is often enough for most users.

Recommended communication steps for users:

1. Send a brief email or intranet post with a screenshot of the new header and three bullet points: where to share, where to export, and how to find branching.
2. Offer a short 15–20 minute demo session the first week after rollout.
3. Provide a contact for issues that might be tenant policy related (e.g., missing features), not a styling change.

For admins who need precise timeline or change details: use the Message center and the Microsoft 365 roadmap entries. If you need to delay updates for a subset of users, targeted release settings in the admin center are the mechanism to control that.

Conclusion

If you use Forms regularly, expect the same capabilities with a different layout and a few extra clicks for some tasks. Look for features under header icons, ellipsis menus and the right-hand properties pane; use Responses > More options for exports and flows. If a feature truly seems missing, check tenant policy with your admin and share a screenshot so IT can verify account-level controls. A short internal note and a quick walkthrough will resolve most user friction.

Frequently Asked Questions

Why can’t I find branching where it used to be?

Branching is usually moved into the right-hand question properties pane. Click the question you want to add branching to and check the pane tabs for "Branching" or "Add branching." If you still don’t see it, your tenant policy or license might limit branching features; contact your IT admin.

Can I get the old Forms editor back?

Some tenants offer a temporary "classic" toggle, but that depends on Microsoft’s rollout and tenant settings. Ask your admin to check the Microsoft 365 admin center message center or targeted release controls. If no toggle exists, you’ll need to adapt to the new UI or request a pilot delay for your organization.

Has Excel export been removed?

No. Excel export lives under Responses > More options (ellipsis) and may be labeled "Open in Excel" or "Download as Excel." If you use automated exports, set up a Power Automate flow as a workaround.