Forum Discussion
Issue with Email Not Recognized as Clickable Link in Microsoft Forms
I am currently creating a form for my research work. When I enter my email address in the subtitle field after the title, it is not being recognized as a clickable link. I have noticed that other email addresses from my institute are correctly recognized as clickable links, but mine is not.
- I have ensured that the email is correctly formatted and manually typed it to avoid any hidden formatting issues.
- I have also tried clearing any formatting, using different browsers, and even recreating the form, but the issue persists.
- Other email addresses from the same domain are recognized without any problems.
I am using the same email address for creating the form as well. I would greatly appreciate your assistance in resolving this issue as it is crucial for my research work.
Thank you for your time and support. I look forward to your prompt response.
I have verified the issue based on the information you provided. The service does not recognize email formats like x.x@x.x, but it works correctly with formats like x@x.x. I have reported this bug to the product team for a fix. In the meantime, considering it may take a few weeks to resolve and deploy the fix, you can avoid the issue by using an email address that does not contain a ".".
5 Replies
I have a similar issue: my email address is not being recognized as a clickable link in the "custom thank you" message at the end of the form. My email address is in the format "x.x.x@x.x.x.x" and only the text after the @ symbol is recognised as clickable (i.e. x.x.x.x), but this is not a valid email address. I would be grateful if you could help resolve this issue.
An email address in the format "x.x@x.x" works.
Thank you for your help.
- DingkunXie
Microsoft
It could be a bug in recognizing the email address within the form content. Please send me a private message with your email address. I will try to reproduce the issue and forward it to the product team for further investigation.
- Sent, Private message.
- DingkunXie
The fix is deploying to the production environment, and I have verified that the issue has been resolved.
