Processes in Microsoft 365 for setting up Office apps, redeeming product keys, and activating licenses.
Hi @Munoz, Blanca [PlanAsmtAcct],
I hope you’re having a great day. Thank you for reaching out and I really appreciate you sharing the details of what you’re trying to achieve.
After reviewing your request, I’d like to provide the following information:
Certainly, Microsoft Bookings lets you add custom questions to your booking page and you can mark questions as Required, which prevents customers from completing the booking if they leave required fields blank.
However, Microsoft Bookings does not currently have built-in conditional logic/branching (e.g., “if user selects No, show another textbox” or “if answer is X, block booking”) or native “eligibility rules” that automatically stop submission based on values like age range, grade level, or specific answers.
Below are a few practical approaches depending on how strict you need the “block booking” behavior to be:
Option 1: Pre-screen eligibility before showing the Bookings link
If you must prevent ineligible users from booking at all, the best approach is to do an eligibility step first (e.g., Microsoft Forms or Power Apps) where you can apply your rules (age range, grade, required selections). Then:
- If eligible > show/send the Bookings link
- If not eligible > display a message and do not provide the booking link
This option provides the cleanest user experience because it prevents invalid bookings upfront.
Additional guide:
- Use branching logic in Microsoft Forms - Microsoft Support
- Validate open text responses in Microsoft Forms | Microsoft Community Hub
Option 2: Use Power Automate to validate after a booking is created (then take action)
If it’s acceptable that the appointment may be created first and then evaluated, you can use Power Automate with the Microsoft Bookings connector to run checks after an appointment is created/updated and then:
- Notify staff
- Email the customer next steps
- Cancel/adjust the booking based on policy
Note: This approach can automate rule enforcement, but the user experience may involve booking first and then receiving a follow-up action if they’re not eligible.
If your process requires a human to confirm eligibility:
- Booking is created
- Power Automate sends an approval request
- If rejected > send message and cancel/decline booking
This is a common pattern when eligibility is complex or requires exceptions, and it can be built using Power Automate with Bookings triggers.
For further information, you can refer to this article: Use Power Automate connectors to build Bookings workflows | Microsoft Learn
In case you require more in-depth guidance or support for these steps, I’d recommend posting your query in the Microsoft Power Automate Community. This is a dedicated channel for Power Automate discussions. The reason I suggest posting a new topic there is that in the general Q&A Forum, resources and expertise on Power Automate are limited. In the Microsoft Power Platform Community Forum, you’ll find the most qualified group of respondents, and other partners who regularly read the forums can share their knowledge or learn from your interaction.
Option 3: 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 Bookings · 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.