Add FAQ section

Updated scenario descriptions and added resolution and FAQ sections regarding the server-side sync identity transition.

Author: foviedoITBA

support/power-platform/dataverse/email-exchange-synchronization/sssadminprod.md

@@ -24,7 +24,7 @@ These are the key differences you can expect:
 
 Below are a few sample scenarios to demonstrate what is changing and what is not. This is not a comprehensive list of scenarios.
 
-### 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
+### Scenario 1: an email in 'Pending Send' state is picked up by server-side sync, sent out, and moved to 'Sent' state through a 'SetState' operation. A synchronous workflow runs on email update to create a contact using the calling identity
 
 |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|
 |-|-|-|-|-|-|-|-|
@@ -66,3 +66,28 @@ Below are a few sample scenarios to demonstrate what is changing and what is not
 |Before|SYSTEM|**Empty**|SYSTEM|**Empty**|**SYSTEM**|SYSTEM|SYSTEM|Empty|SYSTEM|
 |After|SYSTEM|**'# SSSAdminProd'**|SYSTEM|**'# SSSAdminProd'**|**'# SSSAdminProd'**|SYSTEM|SYSTEM|Empty|SYSTEM|
 
+## Resolution
+
+No action should be required, server-side sync would continue functioning as normal after the transition.
+
+## FAQ
+
+### 1. When will this transition take place?
+
+This is currently planned to happen somewhere between November 2025 and March 2026.
+
+### 2. Can I opt out of it?
+
+There is no way to opt out of this change, but you should contact support if anything breaks after transition.
+
+### 3. Moving forward, can we build dependencies (in the form of customizations, processes, etc.) around the fact that server-side sync operations are performed by '# SSSAdminProd'?
+
+No. Much like the identity is changing now, it is also subject to changing again in the future, so any such dependencies could break.
+
+### 4. We have built dependencies or processes around the identities that show up in the audit log or the delegate auditing fields when operations are performed by server-side sync. What should we do?
+
+As these identities can and will be changing, we we advise against building dependencies around observations and assumptions about how the system behaves at a particular point in time, and instead refer to publicly documented system behaviors.
+
+### 5. We are not using server-side sync. Why is this user present? Can we disable it?
+
+The user is present basically for all Dynamics environments, regardless of whether they are currently using server-side sync or not. We do not advise fiddling with this system user in any way, and its presence should not cause any trouble.