Skip to content

Commit 64f8d6e

Browse files
authored
Update connector-office-365.md
Removed transformation section as per Eng input.
1 parent 1512e8a commit 64f8d6e

File tree

1 file changed

+2
-30
lines changed

1 file changed

+2
-30
lines changed

articles/data-factory/connector-office-365.md

Lines changed: 2 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -7,10 +7,10 @@ ms.service: data-factory
77
ms.subservice: data-movement
88
ms.custom: synapse
99
ms.topic: conceptual
10-
ms.date: 10/20/2023
10+
ms.date: 10/29/2024
1111
ms.author: jianleishen
1212
---
13-
# Copy and transform data from Microsoft 365 (Office 365) into Azure using Azure Data Factory or Synapse Analytics
13+
# Copy from Microsoft 365 (Office 365) into Azure using Azure Data Factory or Synapse Analytics
1414
[!INCLUDE[appliesto-adf-asa-md](includes/appliesto-adf-asa-md.md)]
1515

1616
Azure Data Factory and Synapse Analytics pipelines integrate with [Microsoft Graph data connect](/graph/data-connect-concept-overview), allowing you to bring the rich organizational data in your Microsoft 365 (Office 365) tenant into Azure in a scalable way and build analytics applications and extract insights based on these valuable data assets. Integration with Privileged Access Management provides secured access control for the valuable curated data in Microsoft 365 (Office 365). Please refer to [this link](/graph/data-connect-concept-overview) for an overview of Microsoft Graph data connect.
@@ -333,33 +333,5 @@ To copy data from Microsoft 365 (Office 365), the following properties are suppo
333333
]
334334
```
335335

336-
## Transform data with the Microsoft 365 connector
337-
338-
Microsoft 365 datasets can be used as a source with mapping data flows. The data flow will transform the data by flattening the dataset automatically. This allows users to concentrate on leveraging the flattened dataset to accelerate their analytics scenarios.
339-
340-
### Mapping data flow properties
341-
342-
To create a mapping data flow using the Microsoft 365 connector as a source, complete the following steps:
343-
344-
1. In ADF Studio, go to the **Data flows** section of the **Author** hub, select the **** button to drop down the **Data flow actions** menu, and select the **New data flow** item. Turn on debug mode by using the **Data flow debug** button in the top bar of data flow canvas.
345-
346-
:::image type="content" source="media/connector-office-365/connector-office-365-mapping-data-flow-data-flow-debug.png" alt-text="Screenshot of the data flow debug button in mapping data flow.":::
347-
348-
2. In the mapping data flow editor, select **Add Source**.
349-
350-
:::image type="content" source="media/connector-office-365/connector-office-365-mapping-data-flow-add-source.png" alt-text="Screenshot of add source in mapping data flow.":::
351-
352-
3. On the tab **Source settings**, select **Inline** in the **Source type** property, **Microsoft 365 (Office 365)** in the **Inline dataset type**, and the Microsoft 365 linked service that you have created earlier.
353-
354-
:::image type="content" source="media/connector-office-365/connector-office-365-mapping-data-flow-select-dataset.png" alt-text="Screenshot of the select dataset option in source settings of mapping data flow source.":::
355-
356-
4. On the tab **Source options** select the **Table name** of the Microsoft 365 table that you would like to transform. Also select the **Auto flatten** option to decide if you would like data flow to auto flatten the source dataset.
357-
358-
:::image type="content" source="media/connector-office-365/connector-office-365-mapping-data-flow-source-options.png" alt-text="Screenshot of the source options of mapping data flow source.":::
359-
360-
5. For the tabs **Projection**, **Optimize** and **Inspect**, please follow [mapping data flow](concepts-data-flow-overview.md).
361-
362-
6. On the tab **Data preview** click on the **Refresh** button to fetch a sample dataset for validation.
363-
364336
## Related content
365337
For a list of data stores supported as sources and sinks by the copy activity, see [supported data stores](copy-activity-overview.md#supported-data-stores-and-formats).

0 commit comments

Comments
 (0)