Dear @Pedro Bajana,
Thank you for posting your question in the Microsoft Q&A forum.
I understand how inconvenient it must be to encounter this restriction, especially when you're trying to collect important information through your form.
To help me better understand the situation and assist you effectively, could you please share a few details such as:
1/ Is your account a personal account (such as @gmail.com, @outlook.com, @hotmail.com) or a work or school account managed by your organization?
2/ If your account is a work or school account, are you the IT administrator?
3/ Are you the owner of this form?
4/ Does your form include any questions that request personally identifiable information (PII) or sensitive data?
5/ Are you experiencing this issue with just one specific form, or does it affect all the forms you've created previously?
6/ Are you currently able to create and edit new forms without any problems?
This will help us better understand the context and provide more targeted support. Any additional information will help us better understand and support you.
In the meantime, you can refer to this information to verify the issue:
This message usually appears when Microsoft Forms detects that your form may be requesting personally identifiable or sensitive information such as full names, email addresses, phone numbers, or government-issued IDs.
Microsoft Forms has built-in security features to help protect users and prevent phishing. Even if the questions are not intended to collect sensitive data, they may still be flagged automatically.
Here are some workarounds you can try:
Option 1: Duplicate the form and review questions
You can try duplicating the form and testing the new version.
If you're able to access the edit mode in the copied form, please carefully review all questions to ensure none are requesting sensitive or personal information. Even common words like password, SSN, credit card, bank, or ID can trigger the block. Consider rephrasing or removing such terms if possible.
If you’re an end-user with a work or school account, this restriction may be due to security settings enabled by your organization’s IT admin. In such cases, you’ll need to contact your IT administrator to review and unblock the form.
Option 2: Contact your IT admin
Note: Only global admins or security admins can perform this action.
1/ Review Microsoft Forms settings in Admin Center
To unblock a flagged Microsoft Form:
Go to Microsoft Admin Center. Sign in with admin credentials.
In the left-hand navigation pane, go to Settings > Org settings.
Scroll down and select Microsoft Forms.
Review the settings and, if appropriate, the IT admin can consider disabling the “Add internal phishing protection” option.

2/ Unblock the Form via Microsoft Defender
This article provides further guidance on the topic: Review and unblock forms or users detected and blocked for potential phishing - Microsoft Forms Adm…
Additional information is available in the following resource: Microsoft Forms and proactive phishing prevention - Microsoft Support
As community moderators, we kindly ask for your understanding that our access to internal development details is limited. Our primary role is to guide users toward the appropriate resources and support channels. While we may not have visibility into performing deeper backend analysis, we’ll continue doing our best to support you within the scope of our responsibilities.
I hope the information provided proves useful. Please proceed with the outlined steps and let me know whether they resolve the issue. If not, I’ll be glad to continue working with you to find a solution.
Thank you for your patience and understanding throughout this process. Should you have any questions or need further assistance, feel free to reach out at any time.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have any extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.