{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreif4fwxj5hkfxf6gymyhcvypyjkktc2verujzbtjxvplpamq3hqzvq",
    "uri": "at://did:plc:xxrzfynfiasdpbxteqxi4jgq/app.bsky.feed.post/3mkqt4c54bwc2"
  },
  "description": "We are announcing the ability to set message expirations to keep communication relevant in Dynamics 365 Customer Insights - Journeys. This feature will reach general availability on May 30, 2026.\n\nHow does this affect me?\nThis feature enables you to set expiration dates on your messages, ensuring that only current and relevant information reaches your audience.\n\nKey functionality of this feature includes:\n\n * Set an expiration date on any message in your journeys (emails, text messages, push not",
  "path": "/m365-message-center/message/mc1296204/",
  "publishedAt": "2026-05-01T00:00:04.000Z",
  "site": "https://blog.tophhie.cloud",
  "tags": [
    "Set message expirations to keep communication relevant"
  ],
  "textContent": "We are announcing the ability to set message expirations to keep communication relevant in Dynamics 365 Customer Insights - Journeys. This feature will reach general availability on May 30, 2026.\n\n**How does this affect me?**\nThis feature enables you to set expiration dates on your messages, ensuring that only current and relevant information reaches your audience.\n\nKey functionality of this feature includes:\n\n  * Set an expiration date on any message in your journeys (emails, text messages, push notifications, or custom).\n  * Choose from different expiration options (no expiry, expiration based on a date and time, or a trigger).\n  * Review analytics to understand which customers didn't receive messages due to expiration dates.\n\n\n\n**What action do I need to take?**\nThis message is for awareness, and no action is required.\n\nIf you would like more information on this feature, please visit Set message expirations to keep communication relevant.",
  "title": "MC1296204: Dynamics 365 Customer Insights - Journeys - Set message expirations to keep communication relevant",
  "updatedAt": "2026-05-01T00:00:05.137Z"
}