|
1 | 1 | --- |
2 | 2 | title: Upcoming Changes to Server-Side Sync Identity in Dynamics |
3 | | -description: Learn about the upcoming changes to the identity used by server-side sync in Dynamics 365, including impacts on audit logs and delegate fields. |
| 3 | +description: Learn about the upcoming changes to the identity that's used by server-side sync in Dynamics 365, including effects on audit logs and delegate fields. |
4 | 4 | ms.date: 11/13/2025 |
5 | 5 | ms.reviewer: FERNAN.OVIEDO, v-shaywood |
6 | 6 | ms.custom: sap:Email and Exchange Synchronization\Set up and configuration of server-side synchronizatio |
7 | 7 | --- |
8 | 8 |
|
9 | | -# Upcoming changes to the identity used by server-side sync for Dataverse communications |
| 9 | +# Changes to server-side sync identity for Dataverse communications |
10 | 10 |
|
11 | | -This article provides an overview of the upcoming change to the identity used by server-side sync for Dataverse communications. It includes a detailed list of the changes you can expect to see once the new identity is in use, as well as example scenarios comparing record fields before and after the switch. |
| 11 | +This article provides an overview of the upcoming changes to the identity that's used by server-side sync for Dataverse communications in Microsoft Dynamics 365. This article includes a detailed list of the changes that you can expect to see after the new identity is active. It also provides example scenarios that compare record fields before and after the switch. |
12 | 12 |
|
13 | 13 | ## Expected changes |
14 | 14 |
|
15 | | -Server-side sync is changing the identity used for communications with Dataverse. Previously, server-side sync used the `SYSTEM` identity that all environments have. Server-side sync operations will transition to using the `# SSSAdminProd` identity moving forward. This transition is currently planned to happen between November 2025 and March 2026. |
| 15 | +Server-side sync is changing the identity that's used for Dataverse communications. Previously, server-side sync used the `SYSTEM` identity that all environments have. Server-side sync operations will transition to using the `# SSSAdminProd` identity moving forward. This transition is currently planned to occur between November 2025 and March 2026. |
16 | 16 |
|
17 | 17 | > [!IMPORTANT] |
18 | | -> To preserve backward compatibility, the `SYSTEM` identity will still be used for some key server-side sync operations. This approach ensures that the identity transition doesn't impact customers that have built dependencies around the `SYSTEM` identity. |
| 18 | +> To preserve backward compatibility, the `SYSTEM` identity will continue to be used for some key server-side sync operations. This approach makes sure that the identity transition doesn't affect users that built dependencies around the `SYSTEM` identity. |
19 | 19 |
|
20 | | -The key differences you can expect to see after the identity transition are: |
| 20 | +The key differences that you can expect to see after the identity transition are: |
21 | 21 |
|
22 | | -- A new system user named `# SSSAdminProd` is present in Dynamics 365. |
23 | | -- The audit log entries for server-side sync operations that don't impersonate a system user show as being performed by `# SSSAdminProd` instead of `SYSTEM`. |
24 | | -- For records created or updated by server-side sync, the delegate auditing fields _Created By (delegate)_ and _Modified By (delegate)_ show `# SSSAdminProd` instead of being empty. The content of the _Created By_ and _Modified By_ fields remains unchanged. |
25 | | -- For records created by synchronous customizations, such as workflows or plug-ins, that run upon server-side sync operations and use the calling identity, the _Created By (delegate)_ field shows `# SSSAdminProd` instead of being empty. |
| 22 | +- A new Dynamics 365 system user that's named `# SSSAdminProd` is added. |
| 23 | +- The audit log entries for server-side sync operations that don't impersonate a system user are shown as performed by `# SSSAdminProd` instead of `SYSTEM`. |
| 24 | +- For records that are created or updated by server-side sync: |
| 25 | + - The delegate auditing fields _Created By (delegate)_ and _Modified By (delegate)_ now shows `# SSSAdminProd` instead of being empty. |
| 26 | + - The content of the _Created By_ and _Modified By_ fields remains unchanged. |
| 27 | +- For records that are created by synchronous customizations, such as workflows or plug-ins, and that run on server-side sync operations and use the calling identity: |
| 28 | + - The _Created By (delegate)_ field now shows `# SSSAdminProd` instead of being empty. |
26 | 29 |
|
27 | 30 | ## Example scenarios |
28 | 31 |
|
29 | | -The following example scenarios demonstrate which record fields will be changing. This is not a comprehensive list: |
| 32 | +The following example scenarios demonstrate which record fields will change. (This is not a comprehensive list.) |
30 | 33 |
|
31 | | -### Server-side sync picks up an email in 'Pending Send' state, sends it out, and then moves it to 'Sent' state through a 'SetState' operation. A synchronous workflow runs on email updates to create a contact using the calling identity. |
| 34 | +#### Scenario 1 |
| 35 | + |
| 36 | +Server-side sync picks up an email message in 'Pending Send' state, sends it, and then moves it to the 'Sent' state through a 'SetState' operation. A synchronous workflow runs on email updates to create a contact using the calling identity. |
32 | 37 |
|
33 | 38 | | Scenario | Email Modified By | Email Modified By (delegate) | Email audit log identity | Contact owner | Contact Created By | Contact Created By (delegate) | Contact audit log identity | |
34 | 39 | | -------- | ----------------- | ---------------------------- | ------------------------ | ------------- | ------------------ | ----------------------------- | -------------------------- | |
35 | 40 | | Before | SYSTEM | **Empty** | **SYSTEM** | SYSTEM | SYSTEM | **Empty** | SYSTEM | |
36 | 41 | | After | SYSTEM | **# SSSAdminProd** | **# SSSAdminProd** | SYSTEM | SYSTEM | **# SSSAdminProd** | SYSTEM | |
37 | 42 |
|
38 | | -### An email is automatically tracked into Dynamics. A synchronous workflow runs on email creation to create a contact by using the calling identity. |
| 43 | +#### Scenario 2 |
| 44 | + |
| 45 | +An email message is automatically tracked into Dynamics. A synchronous workflow runs on email creation to create a contact by using the calling identity. |
39 | 46 |
|
40 | 47 | | Scenario | Email Created By | Email Created By (delegate) | Email Modified By | Email Modified By (delegate) | Email audit log identity | Contact owner | Contact Created By | Contact Created By (delegate) | Contact audit log identity | |
41 | 48 | | -------- | ---------------- | --------------------------- | ----------------- | ---------------------------- | ------------------------ | ------------- | ------------------ | ----------------------------- | -------------------------- | |
42 | 49 | | Before | SYSTEM | **SYSTEM** | SYSTEM | **SYSTEM** | **SYSTEM** | SYSTEM | SYSTEM | **Empty** | SYSTEM | |
43 | 50 | | After | SYSTEM | **# SSSAdminProd** | SYSTEM | **# SSSAdminProd** | **# SSSAdminProd** | SYSTEM | SYSTEM | **# SSSAdminProd** | SYSTEM | |
44 | 51 |
|
45 | | -### An email is automatically tracked into Dynamics. A plug-in runs synchronously on email creation to create a contact by using the calling identity. |
| 52 | +#### Scenario 3 |
| 53 | + |
| 54 | +An email message is automatically tracked into Dynamics. A plug-in runs synchronously on email creation to create a contact by using the calling identity. |
46 | 55 |
|
47 | 56 | | Scenario | Email Created By | Email Created By (delegate) | Email audit log identity | Contact owner | Contact Created By | Contact Created By (delegate) | Contact audit log identity | |
48 | 57 | | -------- | ---------------- | --------------------------- | ------------------------ | ------------- | ------------------ | ----------------------------- | -------------------------- | |
49 | 58 | | Before | SYSTEM | **SYSTEM** | **SYSTEM** | SYSTEM | SYSTEM | **Empty** | SYSTEM | |
50 | 59 | | After | SYSTEM | **# SSSAdminProd** | **# SSSAdminProd** | SYSTEM | SYSTEM | **# SSSAdminProd** | SYSTEM | |
51 | 60 |
|
52 | | -### An email is manually tracked into Dynamics. A synchronous workflow runs on email creation to create a contact by using the calling identity. |
| 61 | +#### Scenario 4 |
| 62 | + |
| 63 | +An email message is manually tracked into Dynamics. A synchronous workflow runs on email creation to create a contact by using the calling identity. |
53 | 64 |
|
54 | 65 | | Scenario | Email Created By | Email Created By (delegate) | Email audit log identity | Contact owner | Contact Created By | Contact Created By (delegate) | Contact audit log identity | |
55 | 66 | | -------- | ---------------- | --------------------------- | ------------------------ | ------------- | ------------------ | ----------------------------- | -------------------------- | |
56 | 67 | | Before | SYSTEM | **SYSTEM** | **SYSTEM** | SYSTEM | SYSTEM | **Empty** | SYSTEM | |
57 | 68 | | After | SYSTEM | **# SSSAdminProd** | **# SSSAdminProd** | SYSTEM | SYSTEM | **# SSSAdminProd** | SYSTEM | |
58 | 69 |
|
59 | | -### Server-side sync tracks a task into Dynamics while impersonating the actual user. A synchronous workflow runs on task creation to create a contact by using the calling identity. |
| 70 | +#### Scenario 5 |
| 71 | + |
| 72 | +Server-side sync tracks a task into Dynamics while impersonating the actual user. A synchronous workflow runs on task creation to create a contact by using the calling identity. |
60 | 73 |
|
61 | 74 | | Scenario | Task Created By | Task Created By (delegate) | Task Modified By | Task Modified By (delegate) | Task audit log identity | Contact owner | Contact Created By | Contact Created By (delegate) | Contact audit log identity | |
62 | 75 | | -------- | --------------- | -------------------------- | ---------------- | --------------------------- | ----------------------- | ------------- | ------------------ | ----------------------------- | -------------------------- | |
63 | 76 | | Before | User | **Empty** | User | **Empty** | User | User | User | **Empty** | User | |
64 | 77 | | After | User | **# SSSAdminProd** | User | **# SSSAdminProd** | User | User | User | **# SSSAdminProd** | User | |
65 | 78 |
|
66 | | -### Server-side sync tracks an appointment into Dynamics. The tracking mailbox belongs to a user that's different from the appointment organizer, so server-side sync doesn't use impersonation. A synchronous workflow runs on appointment create to create a contact by using the calling identity. |
| 79 | +#### Scenario 6 |
| 80 | + |
| 81 | +Server-side sync tracks an appointment into Dynamics. The tracking mailbox belongs to a user that's different from the appointment organizer. Therefore, server-side sync doesn't use impersonation. A synchronous workflow runs on appointment creation to create a contact by using the calling identity. |
67 | 82 |
|
68 | 83 | | Scenario | Appointment Created By | Appointment Created By (delegate) | Appointment Modified By | Appointment Modified By (delegate) | Appointment audit log identity | Contact owner | Contact Created By | Contact Created By (delegate) | Contact audit log identity | |
69 | 84 | | -------- | ---------------------- | --------------------------------- | ----------------------- | ---------------------------------- | ------------------------------ | ------------- | ------------------ | ----------------------------- | -------------------------- | |
70 | 85 | | Before | SYSTEM | **Empty** | SYSTEM | **Empty** | **SYSTEM** | SYSTEM | SYSTEM | Empty | SYSTEM | |
71 | 86 | | After | SYSTEM | **# SSSAdminProd** | SYSTEM | **# SSSAdminProd** | **# SSSAdminProd** | SYSTEM | SYSTEM | Empty | SYSTEM | |
72 | 87 |
|
73 | | -## FAQs |
| 88 | +## Frequently asked questions |
74 | 89 |
|
75 | | -### Can I opt out of it? |
| 90 | +**Q1: Can I opt out of this change?** |
76 | 91 |
|
77 | | -You can't opt out of this change, but you should contact support if you experience any issues after the transition. |
| 92 | +**A1:** You can't opt out of this change. However, you should contact Microsoft Support if you experience any issues after the transition. |
78 | 93 |
|
79 | | -### In the future, can we build dependencies (in the form of customizations, processes, etc.) around the fact that server-side sync performs its operations by using the "# SSSAdminProd" user? |
| 94 | +**Q2: In the future, can we build dependencies (in the form of customizations, processes, etc.) around the fact that server-side sync performs its operations by using the "# SSSAdminProd" user?** |
80 | 95 |
|
81 | | -No, the new identity is also subject to potential change in the future. Any dependencies built on the `# SSSAdminProd` identity could break. |
| 96 | +**A2:** No, the new identity is also subject to potential change in the future. Any dependencies that are built on the `# SSSAdminProd` identity could break. |
82 | 97 |
|
83 | | -### We built dependencies or processes around the identities that show up in the audit log or the delegate auditing fields when server-side sync performs certain operations. These identities are now changing. What should we do? |
| 98 | +**Q3: We built dependencies or processes around the identities that appear in the audit log or the delegate auditing fields when server-side sync performs certain operations. These identities are now changing. What should we do?** |
84 | 99 |
|
85 | | -As these identities can change in the future, only build dependencies on the publicly documented system behavior rather than observed system behaviors. For more information, see [Server-side synchronization](/power-platform/admin/server-side-synchronization) |
| 100 | +**A3:** Because these identities can change in the future, we recommend that you build dependencies on only the publicly documented system behavior instead of observed system behaviors. For more information, see [Server-side synchronization](/power-platform/admin/server-side-synchronization) |
86 | 101 |
|
87 | | -### We're not using server-side sync. Why is this user present? Can we disable it? |
| 102 | +**Q4: We're not using server-side sync. Do we need this user? Can we disable it?** |
88 | 103 |
|
89 | | -The new identity is present for almost every Dynamics environment, regardless of whether you're currently using server-side sync or not. Don't change system identities in any way. |
| 104 | +**A4:** The new identity exists for almost every Dynamics environment, regardless of whether you're currently using server-side sync. Don't change system identities in any way. |
0 commit comments