This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Since today, when I try to compose an email it will let me type in both the subject and body fields (as normal) but not in the 'To' field to enter the recipient's email address.
I click on the 'To' bit and nothing happens. I hover the cursor over it and try to type - nothing happens. I'm blocked out from entering any email addresses.
It means I cannot send any new emails from my account via my desktop. Seems to be just fine from my phone.
It's bizarre and frustrating and I can't find anything about it online.
Desktop is an older iMac using Safari. Never had a problem before.
Using older versions of Outlook for Mac in business environments
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Probably an issue between changes inf Safari and Office365 or both. Best workaround is still popping the message out into its own window until it gets resolved. Not too much of an inconvenience in this crazy world, hope it works for you!
Excellent workaround, it works and what it does is to save a Draft of the initial message which does not allow to type the recipient address on the Field "To", then open a new window and on this new message you can type the address as it supposed to be. So at the end is the same result as the other workaround which suggest to save the original message as a draft and open a new one.
Who's failure is this from Microsoft or Apple or both? so please whoever are responsible please fix this bug as soon as possible and let us know.
Awesome! Works.
I've had the same issue all week.
While there's the workaround, does anyone know if Microsoft are aware and if a resolution is pending ?
Thanks
Me too!