Outlook changing special characters to HTML encoded form

Sandeep Singh 6 Reputation points
2022-05-23T18:06:31.54+00:00

Hello,
I am trying to add an event to outlook by using following link:

https://outlook.live.com/calendar/0/deeplink/compose?rru=addevent&subject=Testing+%26&startdt=2022-07-09T07:00:00Z&enddt=2022-07-10T07:00:00Z&allday=true&location=somelocation&body=hello&path=/calendar/action/compose

But when outlook extract info from this URL and renders Add Event modal, then subject displays the HTML encoded value for the special characters added. Above example shows the text i added to subject was as follows:
Original Subject: Testing &
In URL it was URL encoded as: Testing+%26
Rendered Subject: Testing &

Please help here how we can pass on the special characters in the URL itself so that outlook can display them properly.

Outlook Windows Classic Outlook for Windows For business
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Faery Fu-MSFT 19,751 Reputation points Moderator
    2022-05-24T06:38:36.2+00:00

    Hi @Sandeep Singh ,

    Welcome to Microsoft Q&A forum and posting your question using the tag” office-outlook-itpro” which mainly focus on general issues about Outlook desktop client, and we do know little about URL Encoding.

    From your description, do you want to create an Add to calendar link in an email message?

    As far as I know, from Outlook iteself, you can create an event then forword it as icalendar, now the .ice file will be an attachment in message.
    More information in this sofficial document for your reference: Create an Add to calendar link in an email message

    204953-ics.jpg
    204936-attachment.jpg

    Hope this can help you!


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment". 
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


  2. Robert Sparnaaij [MVP] 1,816 Reputation points MVP Volunteer Moderator
    2022-05-24T09:51:41.15+00:00

    Nice find!

    I've done some additional testing and it looks like the issue restricts itself to just the ampersand character within the subject definition.

    Other URL encoded characters seem to work correctly and the URL encoded ampersand also gets interpreted correctly within the location and body definition.

    As I can also reproduce the issue for Exchange Online, I've alerted the Exchange Team about this issue.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.