Merge pull request #6 from KrishnakumarRukmangathan/KrishnakumarRukmangathan-patch-4

Update concepts-change-data-capture-resource.md

Author: KrishnakumarRukmangathan

articles/data-factory/concepts-change-data-capture-resource.md

@@ -9,7 +9,7 @@ ms.service: data-factory
 ms.subservice: data-movement
 ms.custom:
 ms.topic: conceptual
-ms.date: 08/08/2023
+ms.date: 08/18/2023
 ---
 
 # Change data capture resource overview
@@ -51,6 +51,7 @@ The new Change Data Capture resource in ADF allows for full fidelity change data
 * JSON
 * ORC
 * Parquet
+* Azure Synapse Analytics
 
 ## Known limitations
 * Currently, when creating source/target mappings, each source and target is only allowed to be used once. 
@@ -59,8 +60,16 @@ The new Change Data Capture resource in ADF allows for full fidelity change data
 
 For more information on known limitations and troubleshooting assistance, please reference [this troubleshooting guide](change-data-capture-troubleshoot.md).
 
+## Azure Synapse Analytics as Target
+When using Azure Synapse Analytics as target, the **Staging Settings** is available on the main table canvas. Enabling staging is mandatory when selecting Azure Synapse Analytics as the target. This significantly enhances write performance by utilizing performant bulk loading capability such as COPY INTO command. **Staging Settings** can be configured in two ways: utilizing **Factory settings** or opting for a **Custom settings**. **Factory settings** apply at the factory level. For the first time, if these settings aren't configured, you'll be directed to the global staging setting section for configuration. Once set, all CDC top-level resources will adopt this configuration. **Custom settings** is scoped only for the CDC resource for which it is configured and overrides the **Factory settings**.
+
+> [!NOTE]
+> As we utilize the COPY INTO command to transfer data from the staging location to Azure Synapse Analytics, it is advisable to ensure that all required permissions are pre-configured within Azure Synapse Analytics.
+
+
 > [!NOTE]
 > We always use the last published configuration when starting a CDC. For running CDCs, while your data is being processed, you will be billed 4 v-cores of General Purpose Data Flows.
 
 ## Next steps
 - [Learn how to set up a change data capture resource](how-to-change-data-capture-resource.md).
+- [Learn how to set up a change data capture resource with schema evolution](how-to-change-data-capture-resource-with-schema-evolution.md).