Hovering over a hyperlink in the "new" outlook doesn't display the actual URL. How can this be remedied.

Anonymous
2024-06-22T00:02:14+00:00

A very dangerous behavior in the new outlook is that hoving the mouse pointer over a hyperlink in an email no longer displays the actual URL of the link.

Seeing the true URL is the #1 way people can avoid getting email scammed. Removing this tool is inviting people to get defrauded. This should not be a default behavior and I cannot see how to resolve this.

Outlook | Windows | New Outlook for Windows | For business

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.

0 comments No comments

99 answers

Sort by: Newest
  1. Anonymous
    2024-11-06T12:43:57+00:00

    Amazing! It works for me, too, as of today.

    And, very relevant question regarding the content of the tooltip.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-11-06T09:19:25+00:00

    Very nice! It works for me too since today.

    One concern/Question: the URL appears as a popup next to the Link element, similar to what an HTML title attribute would display.

    So... if the Link also has a html title attribute set, what gets displayed?

    Because if the title wins, then this can be very easily exploited.

    Is anyone able to check/confirm what happens in such scenario?

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2024-11-06T06:28:00+00:00

    This appears to have been fixed at last - took some time to get there but at least it is fixed!!!!!!!! :)

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-11-05T22:32:08+00:00

    Our only solution so far is to move all companies over the GMAIL pro.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2024-11-05T22:25:35+00:00

    Just to join in with everyone else, this issue appears to be resolved for our end-users today as well. HUZZAH!

    Was this answer helpful?

    0 comments No comments