Why I can not reply any message for the https://answers.microsoft.com/en-us/outlook_com/forum/all/why-embedded-url-from-azure-monitor-is-not-encoded/79c3a9aa-1ee5-4329-8c18-831af4ab6e2c
The following is the answer for the above post.
Dear De Paul N. Kwizera MSFT,
Thanks for your reply.
Below is the information:
- Have you confirmed that the settings for company B are similar to those in company A?
Reply: What we confirmed is that company B is not doing special setting in the mail client(like link protection plugin running for his email client) for their outlook. The company B is our customer and company A is the consultant firm based on US. So without knowing the possible reason, it's hard to compare setting directly.
- Can you confirm that all users at Company B are using the same versions of Outlook? If they have the same versions but are not the same as those in company A, we should focus on the outlook versions.
**Reply:**We have confirmed that company A and company B use different outlook version.
Company A: Version 2205(Build 15225.20204)
Company B: Version 2018(Build 14326.20962)
3.Have they checked Outlook Web to see if there is any change?
**Reply:**Could you please specify what should we check for outlook web? I used one Hotmail to do test and URL is encoded correctly, there is no issue to access directly.
- Do they have the same issue as company B if the message is sent as Rich Text/HTML?
**Reply:**The email is sent from Azure Monitor Alert Email(azure-noreply@microsoft.com) directly, we can not change to Rich Text/HTML actually.
BTW, we have requested MS Azure support team to check the issue. Previously, we thought it's the issue for Azure Monitor. I don't know whether you are able to check the details for the following ticket. TrackingID#2204080060000622
Basically, this is the information provided by MS Azure support team for this ticket.
Issue:
The hyperlink in Alert notification email is not working for some email address.
Solution:
- We checked that user has the correct role to access the query.
- We let the customer queried the same alert query against the same scope in portal, which was working fine.
- We checked that there is a difference between working link and non-working link, which is non-working link was not URL encoded.
- Based on the previous step, we decide to forward the working email to the non-working email address and let customer open it. Proved the encoded link worked.
- Provided all previous tested solutions and basic information to product group.
- Received explanation from product group. They noticed me that this issue was cause by your customer’s link protection plugin running for his email client, since they notice the link in the email is wrapped with a URL “http://linkprotect.cudasv.com”. They also pulled the original raw URL created by the system and checked but did not find any error.