Not sure what went wrong. I couldn’t reproduce the issue and we didn’t change anything with the feature in recent updates.
I tried it again today and I see that it is correctly parsing safelinks (like links that start with “nam12.safelinks.protection.outlook…“ ) again. I guess it was a glitch? Thanks for fixing 
1 Like