9 versions · FEATURES.md
v93 days agomarkdown import
… 3 unchanged lines …| Date | Change || ---- | ------ |+ | 2026-10-28 | Updated: **Conversational journeys** — context variables (static and dynamic) passed to Contact Center, with the three-place naming requirement. || 2026-10-11 | Added **[Editing Live Segments Used by Live Journeys](02-segments-and-audiences/feature-edit-live-segments.md)** — preview: change a segment under a live journey without stopping it or versioning; timing by journey type and segment role, narrowing does not eject people, static groups read-only. || 2026-10-10 | Added **[Tracking Consent in Customer Insights - Journeys](08-administration/feature-tracking-consent.md)** — Tracking consent — Restrictive enforcement, global versus regional compliance profiles that can't be unlinked later, channel scope beyond email, and the drop in engagement data to expect. || 2026-10-08 | New: **[Event registration counts and pending registrations](04-event-management/feature-event-registration-counts-and-pending.md)** — registration count now reflects confirmed registrations only; pending tickets get their own tab with retry/delete, and hold capacity until cleared. |
v83 weeks agomarkdown import
… 3 unchanged lines …| Date | Change || ---- | ------ |+ | 2026-10-11 | Added **[Editing Live Segments Used by Live Journeys](02-segments-and-audiences/feature-edit-live-segments.md)** — preview: change a segment under a live journey without stopping it or versioning; timing by journey type and segment role, narrowing does not eject people, static groups read-only. || 2026-10-10 | Added **[Tracking Consent in Customer Insights - Journeys](08-administration/feature-tracking-consent.md)** — Tracking consent — Restrictive enforcement, global versus regional compliance profiles that can't be unlinked later, channel scope beyond email, and the drop in engagement data to expect. || 2026-10-08 | New: **[Event registration counts and pending registrations](04-event-management/feature-event-registration-counts-and-pending.md)** — registration count now reflects confirmed registrations only; pending tickets get their own tab with retry/delete, and hold capacity until cleared. || 2026-09-27 | New: **[Customer Insights skills in Copilot Cowork](06-copilot-in-ci-journeys/feature-copilot-cowork-skills.md)** — three skills (customer brief, outreach, email content advisor) letting Cowork chat resolve unified profiles, check consent and draft/publish journeys and email, grounded via the Dataverse MCP server on the caller's own permissions. |… 10 unchanged lines …| Category | Docs || -------- | ---- || Real-time Journeys | 9 |- | Segments & Audiences | 6 |+ | Segments & Audiences | 7 || Email & SMS Marketing | 7 || Event Management | 6 || Lead Scoring | 5 |
v73 weeks agomarkdown import
… 3 unchanged lines …| Date | Change || ---- | ------ |+ | 2026-10-10 | Added **[Tracking Consent in Customer Insights - Journeys](08-administration/feature-tracking-consent.md)** — Tracking consent — Restrictive enforcement, global versus regional compliance profiles that can't be unlinked later, channel scope beyond email, and the drop in engagement data to expect. || 2026-10-08 | New: **[Event registration counts and pending registrations](04-event-management/feature-event-registration-counts-and-pending.md)** — registration count now reflects confirmed registrations only; pending tickets get their own tab with retry/delete, and hold capacity until cleared. || 2026-09-27 | New: **[Customer Insights skills in Copilot Cowork](06-copilot-in-ci-journeys/feature-copilot-cowork-skills.md)** — three skills (customer brief, outreach, email content advisor) letting Cowork chat resolve unified profiles, check consent and draft/publish journeys and email, grounded via the Dataverse MCP server on the caller's own permissions. || 2026-09-24 | Updated: **[Compliance profiles, purposes and consent](08-administration/feature-admin-compliance-profiles-consent.md)** — journeys **always** use the contacts unsubscribe URL, whatever entity the journey targets; the leads and customer-profile URL fields (and any `{{contact.*}}`/`{{lead.*}}` tokens in them) apply to shared consent only and are ignored in journeys. Added that `contextId` and `msdynmkt_trackingcontext` are internal and must not be used to identify users to an external consent system, and that contact point consent supersedes `DoNotEmail`/`DoNotBulkEmail`/`DoNotTrack`. |
v63 weeks agomarkdown import
… 3 unchanged lines …| Date | Change || ---- | ------ |+ | 2026-10-08 | New: **[Event registration counts and pending registrations](04-event-management/feature-event-registration-counts-and-pending.md)** — registration count now reflects confirmed registrations only; pending tickets get their own tab with retry/delete, and hold capacity until cleared. || 2026-09-27 | New: **[Customer Insights skills in Copilot Cowork](06-copilot-in-ci-journeys/feature-copilot-cowork-skills.md)** — three skills (customer brief, outreach, email content advisor) letting Cowork chat resolve unified profiles, check consent and draft/publish journeys and email, grounded via the Dataverse MCP server on the caller's own permissions. || 2026-09-24 | Updated: **[Compliance profiles, purposes and consent](08-administration/feature-admin-compliance-profiles-consent.md)** — journeys **always** use the contacts unsubscribe URL, whatever entity the journey targets; the leads and customer-profile URL fields (and any `{{contact.*}}`/`{{lead.*}}` tokens in them) apply to shared consent only and are ignored in journeys. Added that `contextId` and `msdynmkt_trackingcontext` are internal and must not be used to identify users to an external consent system, and that contact point consent supersedes `DoNotEmail`/`DoNotBulkEmail`/`DoNotTrack`. || 2026-09-23 | Updated: **[Copilot content rewrite and image suggestions](06-copilot-in-ci-journeys/feature-copilot-content-rewrite-and-image-suggestions.md)** — content rewrite **left preview on 22 Sept 2026** and is now GA. Image suggestion and AI tagging for images stay preview, so the two halves of this doc no longer share a maturity. Still US-only and English-only, which remains the fact that decides whether it belongs in a UK or EU scope at all. |
v5last monthmarkdown import
… 3 unchanged lines …| Date | Change || ---- | ------ |+ | 2026-09-27 | New: **[Customer Insights skills in Copilot Cowork](06-copilot-in-ci-journeys/feature-copilot-cowork-skills.md)** — three skills (customer brief, outreach, email content advisor) letting Cowork chat resolve unified profiles, check consent and draft/publish journeys and email, grounded via the Dataverse MCP server on the caller's own permissions. || 2026-09-24 | Updated: **[Compliance profiles, purposes and consent](08-administration/feature-admin-compliance-profiles-consent.md)** — journeys **always** use the contacts unsubscribe URL, whatever entity the journey targets; the leads and customer-profile URL fields (and any `{{contact.*}}`/`{{lead.*}}` tokens in them) apply to shared consent only and are ignored in journeys. Added that `contextId` and `msdynmkt_trackingcontext` are internal and must not be used to identify users to an external consent system, and that contact point consent supersedes `DoNotEmail`/`DoNotBulkEmail`/`DoNotTrack`. || 2026-09-23 | Updated: **[Copilot content rewrite and image suggestions](06-copilot-in-ci-journeys/feature-copilot-content-rewrite-and-image-suggestions.md)** — content rewrite **left preview on 22 Sept 2026** and is now GA. Image suggestion and AI tagging for images stay preview, so the two halves of this doc no longer share a maturity. Still US-only and English-only, which remains the fact that decides whether it belongs in a UK or EU scope at all. || 2026-09-23 | Updated: **[Create a record tile](01-real-time-journeys/feature-create-a-record-tile.md)** — a second excluded table prefix, `msdyncrm_`, joins `msevtmgt_`, ruling out writes back to Customer Insights – Journeys' own tables; and the entity picker is now explicitly documented as listing only what **both** principals can create, confirming that a missing table is a permissions symptom rather than an unsupported one. |… 11 unchanged lines …| Email & SMS Marketing | 7 || Event Management | 6 || Lead Scoring | 5 |- | Copilot in CI Journeys | 5 |+ | Copilot in CI Journeys | 6 || Analytics | 5 || Administration | 6 || Licensing | 4 || Decision Guides | 6 |- | **Total** | **59** |+ | **Total** | **60** |
v4last monthmarkdown import
- Published docs in the Dynamics 365 Customer Insights – Journeys KB: Consultant-focused KB for Microsoft Dynamics 365 Customer Insights – Journeys (formerly Marketing): implementation notes, gotchas, and configuration decisions beyond the official docs — across real-time journeys, segments, email and SMS marketing, event management, lead scoring, Copilot, analytics, and administration. The daily monitor task adds a row here when it publishes or updates a doc. Browse the live KB at https://apps.pr1vacy.cloud/almanac/kb/d365ci-journeys.+ Published docs in the Dynamics 365 Customer Insights – Journeys KB: Consultant-focused KB for Microsoft Dynamics 365 Customer Insights – Journeys (formerly Marketing): implementation notes, gotchas, and configuration decisions beyond the official docs — across real-time journeys, segments, email and SMS marketing, event management, lead scoring, Copilot, analytics, and administration. The daily monitor task adds a row here when it publishes or updates a doc. Browse the live KB at https://365-almanac.app/kb/d365ci-journeys.## 🆕 New & Updated| Date | Change || ---- | ------ |+ | 2026-09-24 | Updated: **[Compliance profiles, purposes and consent](08-administration/feature-admin-compliance-profiles-consent.md)** — journeys **always** use the contacts unsubscribe URL, whatever entity the journey targets; the leads and customer-profile URL fields (and any `{{contact.*}}`/`{{lead.*}}` tokens in them) apply to shared consent only and are ignored in journeys. Added that `contextId` and `msdynmkt_trackingcontext` are internal and must not be used to identify users to an external consent system, and that contact point consent supersedes `DoNotEmail`/`DoNotBulkEmail`/`DoNotTrack`. |+ | 2026-09-23 | Updated: **[Copilot content rewrite and image suggestions](06-copilot-in-ci-journeys/feature-copilot-content-rewrite-and-image-suggestions.md)** — content rewrite **left preview on 22 Sept 2026** and is now GA. Image suggestion and AI tagging for images stay preview, so the two halves of this doc no longer share a maturity. Still US-only and English-only, which remains the fact that decides whether it belongs in a UK or EU scope at all. |+ | 2026-09-23 | Updated: **[Create a record tile](01-real-time-journeys/feature-create-a-record-tile.md)** — a second excluded table prefix, `msdyncrm_`, joins `msevtmgt_`, ruling out writes back to Customer Insights – Journeys' own tables; and the entity picker is now explicitly documented as listing only what **both** principals can create, confirming that a missing table is a permissions symptom rather than an unsupported one. || 2026-09-12 | New: **[Conversational journeys (voice and SMS via Contact Center)](01-real-time-journeys/feature-conversational-journeys.md)** — journeys call a Contact Center proactive engagement so a Copilot Studio agent holds a two-way voice or SMS conversation, then branch on disposition code, result or agent-set attribute; SMS conversation step added in the September 2026 update; same-environment prerequisite, contact-based audiences only. || 2026-09-12 | New: **[Create a record tile](01-real-time-journeys/feature-create-a-record-tile.md)** — record and activity creation from the journey canvas left preview on 11 Sept 2026; dual-principal security model (journey publisher plus the new **Create Record Role Extensible** service role), ownership options, and the Sales assignment-rule override. || 2026-09-11 | Updated: **Contact and lead interaction timeline** — retention raised from 90 days to one year, bringing it in line with journey, channel and contact insights; the explicit "no Customer Insights - Data profiles" limitation was deleted upstream without a positive replacement, so the doc now says treat it as contact and lead only until Microsoft says otherwise. |
v3last monthmarkdown import
… 3 unchanged lines …| Date | Change || ---- | ------ |+ | 2026-09-12 | New: **[Conversational journeys (voice and SMS via Contact Center)](01-real-time-journeys/feature-conversational-journeys.md)** — journeys call a Contact Center proactive engagement so a Copilot Studio agent holds a two-way voice or SMS conversation, then branch on disposition code, result or agent-set attribute; SMS conversation step added in the September 2026 update; same-environment prerequisite, contact-based audiences only. |+ | 2026-09-12 | New: **[Create a record tile](01-real-time-journeys/feature-create-a-record-tile.md)** — record and activity creation from the journey canvas left preview on 11 Sept 2026; dual-principal security model (journey publisher plus the new **Create Record Role Extensible** service role), ownership options, and the Sales assignment-rule override. || 2026-09-11 | Updated: **Contact and lead interaction timeline** — retention raised from 90 days to one year, bringing it in line with journey, channel and contact insights; the explicit "no Customer Insights - Data profiles" limitation was deleted upstream without a positive replacement, so the doc now says treat it as contact and lead only until Microsoft says otherwise. || 2026-09-10 | Initial backfill — 57 docs published across all 10 categories. |… 1 unchanged line …| Category | Docs || -------- | ---- |- | Real-time Journeys | 7 |+ | Real-time Journeys | 9 || Segments & Audiences | 6 || Email & SMS Marketing | 7 || Event Management | 6 |… 3 unchanged lines …| Administration | 6 || Licensing | 4 || Decision Guides | 6 |- | **Total** | **57** |+ | **Total** | **59** |
v2last monthmarkdown import
… 3 unchanged lines …| Date | Change || ---- | ------ |+ | 2026-09-11 | Updated: **Contact and lead interaction timeline** — retention raised from 90 days to one year, bringing it in line with journey, channel and contact insights; the explicit "no Customer Insights - Data profiles" limitation was deleted upstream without a positive replacement, so the doc now says treat it as contact and lead only until Microsoft says otherwise. || 2026-09-10 | Initial backfill — 57 docs published across all 10 categories. |## By category
v1last monthmarkdown import
Initial version.