Microsoft Forms “Next” and “Back” buttons freeze after selecting a language on iPhone

AA 0 Reputation points
2026-11-02T13:30:18.8333333+00:00

I have created a Microsoft Form where the first question asks the respondent to choose a language. After selecting a language and proceeding to the next branch, the form freezes. The “Next” and “Back” buttons no longer respond, so the respondent cannot continue or return to the previous page.

The issue occurs with all language options. The form contains multiple sections and branching logic, and I have tried adjusting the branching and section settings, but the problem remains.

The form works on Android and older iOS versions, but the problem occurs on iPhones running newer versions of iOS.

Could this be caused by an error in the form’s branching or section setup, or could it be a compatibility issue between Microsoft Forms and the latest iOS version? What steps can I take to fix the problem?

Microsoft 365 and Office | Microsoft Forms | For business
0 comments

2 answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-11-02T13:31:22.3166667+00:00

    Treat this as an iOS/Safari compatibility regression if every branch moves forward and the same published form works on Android and older iOS, then submit a minimal reproduction through Microsoft Forms feedback.

    1. Exclude the one branching pattern known to break navigation

    Since general branching and section adjustments have not helped, do not rebuild the whole form again. Check only whether any language answer or section uses one of these unsupported routes:

    • A question branches to an earlier question.
    • A section branches to an earlier section.
    • A route returns respondents to the language-selection section.

    Microsoft Forms supports branching only to a subsequent question or the end of the form. Branching to a preceding question can break the respondent’s navigation experience.^1^

    If no route moves backward, the reported device pattern is stronger evidence of a client-side problem than a form-design error.

    2. Isolate the iPhone failure

    Create a temporary diagnostic copy rather than changing the production form:

    1. Retain the language question.
    2. Retain one destination section with one simple required question.
    3. Configure each language answer to branch forward to that same section.
    4. Publish it and open its direct response link in the latest Safari on an affected iPhone.
    5. Compare it with the original form:
      • Minimal form also freezes: record this as an iOS/Safari reproduction.
      • Minimal form works: add the original sections one at a time until the freeze returns. The last added section or transition identifies the trigger.

    Also test the direct Forms link rather than a link opened inside Outlook, Teams, or another app’s embedded browser. Record the exact iPhone model, iOS version, Safari version, form URL type, selected language, and whether the buttons fail visually or simply ignore taps.

    Microsoft states that Forms is optimized for the latest Safari on iOS.^2^ Therefore, a reproducible freeze in current Safari is appropriate to report as a Forms product issue, not merely an unsupported-browser limitation.

    3. Provide an interim workaround

    Until the regression is resolved:

    • Ask affected respondents to use Android or a desktop browser.
    • If the minimal test identifies one section transition as the trigger, temporarily replace that transition with separate language-specific form links.
    • Avoid directing users to an earlier section as a workaround; backward branching is not supported.

    4. Report the reproduction to Microsoft

    In the form editor, select:

    More form settings → Feedback

    Include:

    • A concise description: “Next and Back stop responding after language-based branching.”
    • Exact iOS and iPhone versions.
    • Confirmation that it reproduces in current Safari.
    • Whether the minimal diagnostic form reproduces it.
    • A screen recording if organizational privacy rules permit.
    • Confirmation that the same form works on Android and older iOS.

    Microsoft documents this Feedback command as the channel for Forms bugs and feature feedback.^3^

    If the affected phones are running an iOS beta, repeat the test on the latest stable iOS release before escalating. Compatibility failures are expected more often on prerelease operating systems, and downgrading can erase the device, so it should not be attempted without a suitable pre-beta backup.^4^

    References

    1. Use branching logic in Microsoft Forms
    2. Which web browsers work with Forms? | Microsoft Support
    3. Set up Microsoft Forms
    4. Office Applications not working in IOS 26 Beta Public - Microsoft Q&A
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. BabybooHN 3,810 Reputation points Independent Advisor
    2026-11-02T13:34:53.4833333+00:00

    Dear @AA

    Because the same form works on Android and older iOS versions, I would investigate a browser compatibility issue alongside the branching configuration. However, this pattern alone does not confirm an iOS defect. Microsoft lists the latest Safari on iOS as an optimized browser for Forms.

    I recommend these checks:

    1. Open the response link directly in Safari, rather than inside Teams, Outlook, or another app. Test in a Private tab and temporarily disable any Safari extensions or content blockers for the page.
    2. Test a simplified copy of the form. Keep only the language question and two destination sections, each containing one optional question. Test it on an affected iPhone. If it works, add the remaining sections gradually to identify the trigger.
    3. Review question-level and section-level branching. All destinations must move forward to a later question/section or the end of the form. Microsoft does not support branching back to an earlier question. Ensure each language section has the intended exit destination.

    If the simplified form also freezes in Safari, ask your Microsoft 365 administrator to open a support request through Admin Center > Help & support. Include the exact iOS version, iPhone model, a screen recording, and a test form containing no sensitive information.

    As a temporary workaround, respondents can use a device/browser combination you have confirmed wửoks.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.