Microsoft Forms known issues and how to fix them quickly

If Microsoft Forms fails for some or all users, first determine whether this is a Microsoft service outage or a tenant/client problem — that decides whether you wait for Microsoft or fix settings locally. Quickly check Microsoft 365 Service health, then run safe tenant and client checks (licenses, Conditional Access, browsers, network). If those don't isolate the problem, collect reproducible steps, HAR/Fiddler traces, timestamps and IDs before opening a support ticket.

Is the service down or is it just me

Forms fails to load, shows a spinning wheel, returns 500/503 errors, or form responses are not saved.

When this appears

• The symptom appears when users open Microsoft Forms in the browser, submit responses, or use Forms inside Teams and the expected UI or response recording does not occur.

Before you start

• Product and versions: Microsoft Forms (web, Teams integration, mobile app).
• Privileges needed: Global admin or Service admin to view tenant Service health.
• Safe checks to run first: check Service health and run the quick scope tests below.

Where to check service status

1. Check Service health in the Microsoft 365 admin center (requires Global admin or Service admin).

Microsoft 365 admin center > Health > Service health

Expected: any tenant-impacting Forms incidents are listed with status and incident ID. If an incident matches your symptoms, use the incident ID when communicating with users or escalating.

2. If you cannot access the admin center, check the Microsoft 365 status page from another network or device.

Quick scope tests (fast, safe)

1. Use a different account: sign in to Forms with another user in your tenant or a test tenant.

Expected: if the other account works, the issue is scoped to user licensing or policies.

2. Try a mobile browser or the Forms mobile app on cellular data.

Expected: success over cellular points to a corporate network or firewall problem.

3. Use an incognito/private browser session or a different browser on the same machine.

Expected: success in a private window indicates client cache, cookies, or extensions are the cause.

4. Test the same form from another tenant or a free Microsoft account if available.

Expected: cross-tenant success indicates a tenant setting or license issue.

What to do next

• If Service health shows an incident that matches your symptoms, communicate the incident and expected updates to affected users and monitor Service health.
• If Service health is clear, continue with tenant, license, client and network checks in the sections below.

Which user reports and scenarios indicate a tenant or licensing problem

Before changing settings, confirm whether the failure pattern matches licensing or tenant controls. The checks below assume you can sign in to the admin center.

Before you start

• Product: Microsoft Forms (web, Teams integration, mobile app).
• Privileges needed: Global admin or User admin for license checks; Conditional Access changes require Security admin or Global admin.
• Restart/backup: none for these checks. Safe checks: verify user licenses and whether internal vs external users are affected.

Signs this is a tenant or license issue

• Errors that mention permissions or show "You don’t have permission" when opening a form.
• Only some SKU types can create or share forms for certain accounts.
• Guests can’t access or submit forms while internal users can.

Checks to run in Microsoft 365 admin center

1. Confirm the user has a license that includes Forms.

Microsoft 365 admin center > Users > Active users > Select user > Licenses and apps

Expected: the Forms toggle or the SKU that includes Forms is assigned. If not assigned, assign the appropriate license and test again.

What it means if that did not happen: assigning the license should restore access; if it doesn't, collect logs and test with another user before escalating.

2. Check tenant Microsoft Forms settings.

Microsoft 365 admin center > Settings > Org settings > Services > Microsoft Forms

Expected: sharing and response collection settings match your intent (for example, external sharing allowed if you expect guest respondents). If settings are too restrictive, adjust and retest.

3. Review Conditional Access policies that might block access.

Azure AD > Security > Conditional Access

Expected: no Conditional Access policy blocks Forms for the affected users or locations. If a policy is blocking, narrow its scope by user, group or app and retest.

4. Check external collaboration settings if guests fail to participate.

Microsoft 365 admin center > Settings > Org settings > External collaboration settings

Expected: external users are allowed to participate if your form sharing requires it. If not, enable the necessary external collaboration options and retest.

What to do if these checks fail

• Missing license or disabled Forms service indicates tenant configuration is the cause; correct that first. If tenant settings look correct but users still fail, collect reproducible steps and logs before contacting Microsoft support.

Quick fixes for browser, device and network problems that often look like Forms failures

Many problems are client-side or network-related. Run these steps from least invasive to more involved.

1. Open a private/incognito window and sign in to Forms.

Expected result: the form loads and functions. If it works, the issue is client cache, cookies, or extensions.

2. Try a different browser on the same machine (Edge, Chrome, Firefox).

Expected result: success in another browser narrows the issue to the original browser.

3. Clear the browser cache and cookies for Microsoft 365 domains and retry.

Browser settings > Privacy & security > Clear browsing data (select cookies and cached images)

Expected result: clearing fixes issues caused by stale tokens or corrupt cached assets. If not fixed, continue.

4. Disable browser extensions (ad blockers, privacy tools) or start the browser with extensions off.

Expected result: if extensions caused the break, disabling them restores Forms. If you find the culprit, configure it to allow Microsoft domains.

5. Check single sign-on (SSO) and authentication flows.

• Test sign-in on a machine not joined to the corporate domain if SAML/IdP or Kerberos-based SSO is used.

Expected result: if sign-in fails only on domain-joined machines, investigate SSO or Kerberos issues.

6. Test on a mobile device using cellular data.

Expected result: if cellular works while the corporate network does not, investigate proxies, firewalls, and TLS interception devices.

7. Bypass corporate proxies or TLS interception appliances for a temporary test.

• Temporary test: connect a test machine directly to the internet or use a mobile hotspot and retest.

Expected result: if bypass works, the proxy or content inspection is altering requests or blocking endpoints.

What to do if tests fail across devices and networks

• If client tests fail everywhere, return to Service health and tenant checks. If failures are intermittent, capture network traces as described in the evidence section before escalating.

Note on Teams-integrated Forms

• If Forms works in the browser but not in Teams, try clearing the Teams desktop cache or check Teams app policy in the Teams admin center. As a workaround, open the form in the browser or add it as a website tab.

Workarounds for known Forms bugs and feature limitations

Forms has documented limitations and occasional bugs. Use these safe workarounds until Microsoft publishes a fix.

• Response export / Excel sync failures: sometimes the "Open in Excel" sync or export hangs.

Workaround: open responses in the web UI and use "Download as CSV" if available, or copy visible responses into a new Excel workbook. If the form is linked to OneDrive/SharePoint and sync fails, download the file directly from the document library.

• Branching logic behaving unexpectedly: complex branching can skip questions or show wrong branches.

Workaround: simplify branching for critical forms, or split the form into multiple shorter forms and route users via links.

• Missing form notifications or delayed emails: notification sends can be delayed or suppressed by tenant email policies.

Workaround: create a Power Automate flow to send notifications on response, which gives more control and retry behavior.

• Forms not appearing in Teams or Forms tab failing to load in Teams:

Workaround: open the form in the browser, add Forms as a website tab with its direct URL in Teams, or clear the Teams cache.

• Large forms or heavy response volumes causing timeouts:

Workaround: split the form into sections or multiple forms and aggregate responses in Excel or Power BI.

What to do when Microsoft has acknowledged a bug

• If Microsoft documents the bug in Service health or support communications, follow the recommended workaround. If no workaround is published, implement a temporary process change (alternate form, manual aggregation) and prepare evidence for escalation.

Check Service health for progress rather than relying only on third-party reports.

How to collect evidence and reproduce the issue before escalation

Good evidence shortens time to resolution. Collect tenant info, reproducible steps, screenshots, network logs and a sample form so Microsoft support can reproduce the issue quickly.

What to capture

• Exact reproduction steps — list each step a user takes and the observed result. Include a minimal set of steps that reliably reproduce the issue.
• Timestamps (UTC), affected user UPNs, tenant ID and correlation or request IDs from any error dialogs.
• Screenshots of error messages and surrounding UI.
• Browser network trace (HAR) or Fiddler capture showing failed requests.

HAR files can contain sensitive tokens. Remove or redact Authorization headers before sending to third parties when possible.

Network trace and console capture steps

1. Reproduce the issue while recording the browser network trace (F12 > Network > Preserve log).
2. Save the HAR file from the Network tab.
3. Capture the Console tab output with errors.

Files and identifiers to include

• HAR file or Fiddler trace.
• Console log text.
• A copy of the form (duplicate the form if the original is sensitive) or a sample form that reproduces the bug.

Exact items Microsoft support will request

• Tenant ID and affected user UPNs.
• Time window when the issue happened (UTC) and any correlation or request IDs shown in errors.
• HAR/Fiddler traces and screenshots.

What to do before opening a ticket

1. Reproduce the issue with a test user if possible and produce a minimal reproducible case.
2. Ensure you have the logs and duplicated form ready to attach.

Expected result: Microsoft support can reproduce the problem with the provided artifacts and request IDs, which speeds resolution.

How to prevent future disruptions and monitor Forms health

Prevent incidents and speed response with monitoring and change controls.

Preventative steps

• Configure Service health alerts in the Microsoft 365 admin center so responsible admins receive notifications.

Microsoft 365 admin center > Health > Service health > Preferences

• Apply change control for tenant settings that affect Forms (Conditional Access, external sharing, license changes). Test changes in a pilot group before full rollout.
• Maintain a short incident template users submit that includes: username, device/browser, time (UTC), and a screenshot. This standardizes reports and speeds triage.
• Build basic test plans to run after major tenant changes (SSO, Conditional Access, network proxy updates): test creating, sharing, and responding to a form from internal and external accounts.

What to document after resolution

• Which change fixed the issue, who approved it, and the timeline. Include the Service health incident ID if Microsoft applied a platform fix.
• Any temporary workarounds used and when they can be removed.
• Lessons learned for runbooks: test steps, the minimal reproducible case, and the evidence files to collect next time.

Regularly review Conditional Access and security appliances that perform TLS interception; these commonly cause intermittent problems for web apps like Forms.

Conclusion

If Service health shows an incident, communicate the incident ID and monitor Microsoft updates. If it’s tenant or client-side, check licenses and tenant settings first, run browser and network tests, apply safe workarounds, and collect HAR/Fiddler traces, timestamps and a minimal reproducible case before opening a support ticket.

Frequently Asked Questions

Why can some users open a form while others cannot?

That pattern usually indicates a tenant setting, license mismatch, Conditional Access policy, or a client/network issue specific to those users. Check licenses, external access settings and Conditional Access scope first, then run the browser and network tests in this article.

Forms shows data but Excel sync is empty — what should I do?

This often reflects a sync or export bug. Use Download CSV from the web UI, copy responses into a new workbook, or open the linked Excel file directly from OneDrive/SharePoint. If the problem persists, collect HAR/Fiddler traces and open a support ticket with the evidence.

Is there an official Microsoft page that lists Forms incidents?

Yes. Service health in the Microsoft 365 admin center shows incidents that affect your tenant. Public social channels can report outages, but Service health is the authoritative source for your tenant.