Change propagation and synchronization log
Change propagation and synchronization log
Source changes show in the subsidiary after about a minute. Logs and job rescheduling work as for single-environment sync.
Area: Integration (Fabric, Shopify, MDM). Status: GA. Developer relevance: low. Airtime: 1 min across 1 video, demoed.
Status evidence
- Nothing said about status; launch event convention: generally available unless stated otherwise.
Where they talk about it
- What's new: Cross-environment Master Data Management: 8:12 to 9:40, demo at 8:12 (called "Automatic change propagation and synchronization log" there)
Quotes
- 8:31 "And after about a minute in the in the source environment, we should see the change." - Gives the expected delay for change propagation.
Caveats mentioned
- Change appeared after about a minute
Documented features match
- No documented item matched. Not documented
- Product documentation (partial, the article describes the broader feature or mentions this in passing): Manage master data synchronization, checked 2026-10-02. Open the Integration Synchronization Jobs page to investigate what happened each time a job queue entry ran. Note: Covers logs and job queue for same-environment master data sync only; the cross-environment propagation timing is not documented.
Docs checked on 2026-10-02: the match is against Microsoft's what's new pages for the wave as they were on that date. Microsoft keeps filling the documentation, so "no documented item" can go stale.
Tags: mdm, synchronization, log, ux
Generated by pipeline step 06. Source: YouTube auto-captions of the launch event videos, see the deep links. Not official.