Dynamic 365 Customer Insights - Journeys – Action
Microsoft announcement
Starting with the April 2026 release, we are updating how Email personalization works when the source data contains HTML tags. This type of personalization will no longer be rendered correctly, unless they are updated to use the explicit opt-in option to prevent HTML encoding before June 29, 2026.
Affected Environment: 805c3e80-b205-41d5-b825-bd0c76b6d21f
daae0c63-64c9-4139-818a-dbd116b49c72
How does this affect me?
Dynamic Text and Lists in emails will now encode, instead of rendering, any HTML tags present in personalization source data by default.
What action do I need to take?
Users must update any email that includes personalization using source data with HTML by selecting the “Prevent HTML encoding” checkbox, as shown in the Allow HTML content in source content article.
HTML encoding changes are not currently enforced in the environment(s) listed above. This is to provide users with sufficient time to take action. Enforcement of these new rules will begin on or after June 29, 2026.
Affected Environment: 805c3e80-b205-41d5-b825-bd0c76b6d21f
daae0c63-64c9-4139-818a-dbd116b49c72
How does this affect me?
Dynamic Text and Lists in emails will now encode, instead of rendering, any HTML tags present in personalization source data by default.
What action do I need to take?
Users must update any email that includes personalization using source data with HTML by selecting the “Prevent HTML encoding” checkbox, as shown in the Allow HTML content in source content article.
HTML encoding changes are not currently enforced in the environment(s) listed above. This is to provide users with sufficient time to take action. Enforcement of these new rules will begin on or after June 29, 2026.
Change history
- 2026-08-07 · Created · All