You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/power-platform/dataverse/email-exchange-synchronization/sssadminprod.md
+22-3Lines changed: 22 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,6 +9,25 @@ This article provides an overview of the changes customers can expect and observ
9
9
10
10
## Symptoms
11
11
12
-
> - A new system user named SSSAdminProd is present in Dynamics 365
13
-
> - Some operations performed by server-side sync show up as being performed by SSSAdminProd instead of SYSTEM in the audit logs
14
-
> - Some records created or updated by server-side sync have the SSSAdminProd system user in the delegate auditing fields, such as "Created By (delegate)" and "Modified By (delegate)"
12
+
> - A new system user named '# SSSAdminProd' is present in Dynamics 365
13
+
> - Some operations performed by server-side sync show up as being performed by '# SSSAdminProd' instead of SYSTEM in the audit logs
14
+
> - Some records created or updated by server-side sync have the '# SSSAdminProd' system user in the delegate auditing fields, such as "Created By (delegate)" and "Modified By (delegate)"
15
+
16
+
## Cause
17
+
18
+
Server-side sync is changing the the identity used for its operations against Dataverse. Historically, server-side sync would simply leverage the user named SYSTEM that all environments have. Moving forward, server-side sync operations will transition to use the '# SSSAdminProd' user. However, to preserve backward compatibility, the SYSTEM identity will still be leveraged for some key server-side sync operations. This is to ensure that customer dependencies built on this identity are not impacted by this change.
19
+
20
+
These are the key differences you can expect:
21
+
1. For records created or updated by server-side sync, the delegate auditing fields "Created By (delegate)" and "Mofieid By (delegate)" will start showing the '# SSSAdminProd' user instead of being empty. The content of the "Created By" and "Modified By" fields remains unchanged.
22
+
2. For records created by synchronous customizations (such as workflows or plug-inss) running upon server-side sync operations and using the calling identity, the "Created By (delegate)" field will start showing the '# SSSAdminProd' user instead of being empty.
23
+
3. The audit log entries for server-side sync operations that do not impersonate a system user will change from SYSTEM to '# SSSAdminProd'
24
+
25
+
Below are a few sample scenarios to demonstrate what is changing and what is not:
26
+
27
+
### Scenario 1: an email in 'Pending Send' state is picked up by server-side sync, sent out, and moved to 'Sent' state. A synchronous workflow runs on email update to create a contact using the calling identity
28
+
29
+
|Scenario|Email Modified By|Email Modified By (delegate)|Email audit log|Contact owner|Contact Created By|Contact Created By (delegate)|Contact audit log identity|
0 commit comments