Is it possible to block users from creating Forms via the Microsoft Forms web app?

Question

As a general rule of thumb, we try to discourage our users from creating Forms from the MS Forms website (https://forms.office.com/). There are several reasons for this including data residency concerns and more often than not users will make themselves an owner of a Form rather than a group, which causes issue if their account gets disabled/deleted. For a time we advised to create Lists in SharePoint and then generate Forms from them, however now that users have the ability to create a Form directly in SharePoint document library , we'd prefer that they only do it this way. Is it possible to enforce this?

Answer 1

Hi @DeanNeedsAnswers,    

Welcome to the Microsoft Q&A forum.    

Thank you very much for sharing your experience regarding how users in your organization are creating Microsoft Forms. I truly appreciate you taking the time to outline your concerns around data residency and form ownership when users create surveys directly from forms.office.com. 

Currently, Microsoft does not provide a built‑in admin policy that forces users to create Forms exclusively from SharePoint while blocking forms.office.com at the same time. The existing controls mainly allow enabling/disabling Microsoft Forms at the service level there is no policy to restrict where Forms can be created. 

You may consider using Conditional Access to block access to the Forms web app; however, because SharePoint’s Forms experience also uses the Forms service, such a policy would likely break SharePoint‑embedded Forms as well. If you test this route, it must be done carefully in Report‑only mode first.  

I'd like to provide the following information:
A - Practical workarounds 

1/ Standardize the “entry point” 
Train users to create Forms only inside SharePoint document libraries/folders, where files and metadata automatically stay inside SharePoint. 

2/ Enforce “Group ownership” for business‑critical Forms 

• Establish an internal policy requiring all operational Forms to be owned by a Microsoft 365 Group or Team. 
• Provide instructions for users to “Move your Form to a group” to avoid orphaned Forms.  

3/ Monitor & gently remind 
Use audit logs to detect personal Forms that may carry operational risk. Send automated reminders (e.g., via Power Automate) requesting owners to transfer Forms to a Group. 

4/ Technical nudges (not hard enforcement) 
Hide the Forms tile in the app launcher, update your internal documentation, and if required run a small Conditional Access POC to evaluate impact before considering anything broader.  

5/ Data residency alignment 
Collecting files via SharePoint‑embedded Forms ensures uploaded files and metadata reside within your SharePoint region, aligned to your tenant’s data residency, unlike Forms created in the standalone Forms service. 

For additional information, you can refer to these articles: 

• microsoft-365-docs/microsoft-365/admin/manage/manage-feedback-ms-org.md at public · MicrosoftDocs/m… 
• SharePoint: Document Libraries - A new forms experience for streamlined document collection - M365 … 
• Understanding Microsoft Forms: Security & Compliance Features 

Please note that this information is being provided by the moderator solely for your convenience. The referenced sites are not managed or overseen by the moderator, and therefore we cannot guarantee the accuracy, security, or suitability of any software or content available there. We recommend reviewing all information carefully and ensuring you understand any associated risks before following suggestions from the provided link.  

B - Submit feedback to Microsoft 

As a forum moderator, I hope you understand that I don’t have the ability to modify or escalate product issues directly. However, I strongly recommend submitting your feedback through the Microsoft Forms · Community. This is the most effective way to ensure your voice reaches the product team and can be considered for future improvements.  

Once you've submitted your feedback, feel free to share the link here in the comments. I’ll be happy to upvote it to help bring more visibility.  

If you are unable to submit feedback from your side, please let me know and I will be happy to submit it on your behalf.    

Additionally, since many other users have expressed similar concerns but may not know where to submit feedback, if my response has helped you better understand the situation and guided you toward a possible next step, please mark it as the "Accepted Answer". Your action will help pin this post to the top, making it easier for others in the community who are experiencing the same issue to find your feedback and support it.    

I hope this information is helpful. Should you have any further questions or need additional assistance, feel free to reach out.     

Thank you again for your time and for raising this important usability concern.

---

If you have any extra questions about this answer, please click "Comment".  

Note: Follow the steps in our documentation to enable email notifications if you want to receive email notifications related to this topic.  

Answer 2

Based on the available information, there is no setting that selectively blocks users from creating forms via the Microsoft Forms web app while still allowing them to create forms from SharePoint or other entry points.

What is available at tenant level is:

• Turn Microsoft Forms on or off for the entire organization.
• Turn Microsoft Forms on or off for specific users.
• Control external sharing, name recording, and phishing protection.

These controls apply to Microsoft Forms usage in general and do not distinguish between where the form is created (Forms web app vs. SharePoint document library vs. other integrations). The documentation does not describe any policy or configuration that enforces “Forms can only be created from SharePoint.”

To influence behavior, the supported options are therefore:

1. Disable Forms entirely for users who should not create forms at all.
2. Leave Forms enabled but use guidance, training, and governance (for example, instructing users to create group-owned forms or to start from SharePoint) rather than a technical enforcement.

---

References:

• Set up Microsoft Forms
• Administrator settings for Microsoft Forms
• Microsoft Forms and user accounts
• Admin information