Merge pull request #206907 from Clare-Zheng82/0804-Update_Office_365_docs_name

Update Office 365 name in Office 365 docs

Author: v-shils

articles/data-factory/TOC.yml

@@ -74,7 +74,7 @@ items:
       displayName: polybase
     - name: From SAP BW to Azure Data Lake Storage Gen2
       href: load-sap-bw-data.md
-    - name: From Office 365 to Azure Blob storage
+    - name: From Microsoft 365 to Azure Blob storage
       href: load-office-365-data.md
     - name: Multiple tables in bulk
       items:
@@ -468,6 +468,9 @@ items:
       href: connector-mariadb.md
     - name: Marketo
       href: connector-marketo.md
+    - name: Microsoft 365
+      href: connector-office-365.md
+      displayName: active directory
     - name: Microsoft Access
       href: connector-microsoft-access.md
     - name: MongoDB
@@ -486,9 +489,6 @@ items:
       displayName: timeout
     - name: ODBC
       href: connector-odbc.md
-    - name: Office 365
-      href: connector-office-365.md
-      displayName: active directory
     - name: Oracle
       href: connector-oracle.md
     - name: Oracle Cloud Storage

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

@@ -1,55 +1,55 @@
 ---
-title: Copy data from Office 365
+title: Copy data from Microsoft 365 (Office 365)
 titleSuffix: Azure Data Factory & Azure Synapse
-description: Learn how to copy data from Office 365 to supported sink data stores by using copy activity in an Azure Data Factory or Synapse Analytics pipeline.
+description: Learn how to copy data from Microsoft 365 (Office 365) to supported sink data stores by using copy activity in an Azure Data Factory or Synapse Analytics pipeline.
 author: jianleishen
 ms.service: data-factory
 ms.subservice: data-movement
 ms.custom: synapse
 ms.topic: conceptual
-ms.date: 03/04/2022
+ms.date: 08/04/2022
 ms.author: jianleishen
 ---
-# Copy data from Office 365 into Azure using Azure Data Factory or Synapse Analytics
+# Copy data from Microsoft 365 (Office 365) into Azure using Azure Data Factory or Synapse Analytics
 [!INCLUDE[appliesto-adf-asa-md](includes/appliesto-adf-asa-md.md)]
 
-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 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 Office 365.  Please refer to [this link](/graph/data-connect-concept-overview) for an overview on Microsoft Graph data connect and refer to [this link](/graph/data-connect-policies#licensing) for licensing information.
+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 on Microsoft Graph data connect and refer to [this link](/graph/data-connect-policies#licensing) for licensing information.
 
-This article outlines how to use the Copy Activity to copy data from Office 365. It builds on the [copy activity overview](copy-activity-overview.md) article that presents a general overview of copy activity.
+This article outlines how to use the Copy Activity to copy data from Microsoft 365 (Office 365). It builds on the [copy activity overview](copy-activity-overview.md) article that presents a general overview of copy activity.
 
 ## Supported capabilities
 
-This Office 365 connector is supported for the following capabilities:
+This Microsoft 365 (Office 365) connector is supported for the following capabilities:
 
 | Supported capabilities|IR |
 |---------| --------|
 |[Copy activity](copy-activity-overview.md) (source/-)|① ②|
 
 <small>*&#9312; Azure integration runtime &#9313; Self-hosted integration runtime*</small>
 
-ADF Office 365 connector and Microsoft Graph data connect enables at scale ingestion of different types of datasets from Exchange Email enabled mailboxes, including address book contacts, calendar events, email messages, user information, mailbox settings, and so on.  Refer [here](/graph/data-connect-datasets) to see the complete list of datasets available.
+ADF Microsoft 365 (Office 365) connector and Microsoft Graph data connect enables at scale ingestion of different types of datasets from Exchange Email enabled mailboxes, including address book contacts, calendar events, email messages, user information, mailbox settings, and so on.  Refer [here](/graph/data-connect-datasets) to see the complete list of datasets available.
 
-For now, within a single copy activity you can only **copy data from Office 365 into [Azure Blob Storage](connector-azure-blob-storage.md), [Azure Data Lake Storage Gen1](connector-azure-data-lake-store.md), and [Azure Data Lake Storage Gen2](connector-azure-data-lake-storage.md) in JSON format** (type setOfObjects). If you want to load Office 365 into other types of data stores or in other formats, you can chain the first copy activity with a subsequent copy activity to further load data into any of the [supported ADF destination stores](copy-activity-overview.md#supported-data-stores-and-formats) (refer to "supported as a sink" column in the "Supported data stores and formats" table).
+For now, within a single copy activity you can only **copy data from Microsoft 365 (Office 365) into [Azure Blob Storage](connector-azure-blob-storage.md), [Azure Data Lake Storage Gen1](connector-azure-data-lake-store.md), and [Azure Data Lake Storage Gen2](connector-azure-data-lake-storage.md) in JSON format** (type setOfObjects). If you want to load Microsoft 365 (Office 365) into other types of data stores or in other formats, you can chain the first copy activity with a subsequent copy activity to further load data into any of the [supported ADF destination stores](copy-activity-overview.md#supported-data-stores-and-formats) (refer to "supported as a sink" column in the "Supported data stores and formats" table).
 
 >[!IMPORTANT]
->- The Azure subscription containing the data factory or Synapse workspace and the sink data store must be under the same Azure Active Directory (Azure AD) tenant as Office 365 tenant.
->- Ensure the Azure Integration Runtime region used for copy activity as well as the destination is in the same region where the Office 365 tenant users' mailbox is located. Refer [here](concepts-integration-runtime.md#integration-runtime-location) to understand how the Azure IR location is determined. Refer to [table here](/graph/data-connect-datasets#regions) for the list of supported Office regions and corresponding Azure regions.
+>- The Azure subscription containing the data factory or Synapse workspace and the sink data store must be under the same Azure Active Directory (Azure AD) tenant as Microsoft 365 (Office 365) tenant.
+>- Ensure the Azure Integration Runtime region used for copy activity as well as the destination is in the same region where the Microsoft 365 (Office 365) tenant users' mailbox is located. Refer [here](concepts-integration-runtime.md#integration-runtime-location) to understand how the Azure IR location is determined. Refer to [table here](/graph/data-connect-datasets#regions) for the list of supported Office regions and corresponding Azure regions.
 >- Service Principal authentication is the only authentication mechanism supported for Azure Blob Storage, Azure Data Lake Storage Gen1, and Azure Data Lake Storage Gen2 as destination stores.
 
 > [!Note]
 > Please use Azure integration runtime in both source and sink linked services. The self-hosted integration runtime and the managed virtual network integration runtime are not supported. 
 
 ## Prerequisites
 
-To copy data from Office 365 into Azure, you need to complete the following prerequisite steps:
+To copy data from Microsoft 365 (Office 365) into Azure, you need to complete the following prerequisite steps:
 
-- Your Office 365 tenant admin must complete on-boarding actions as described [here](/events/build-may-2021/microsoft-365-teams/breakouts/od483/).
+- Your Microsoft 365 (Office 365) tenant admin must complete on-boarding actions as described [here](/events/build-may-2021/microsoft-365-teams/breakouts/od483/).
 - Create and configure an Azure AD web application in Azure Active Directory.  For instructions, see [Create an Azure AD application](../active-directory/develop/howto-create-service-principal-portal.md#register-an-application-with-azure-ad-and-create-a-service-principal).
-- Make note of the following values, which you will use to define the linked service for Office 365:
+- Make note of the following values, which you will use to define the linked service for Microsoft 365 (Office 365):
     - Tenant ID. For instructions, see [Get tenant ID](../active-directory/develop/howto-create-service-principal-portal.md#get-tenant-and-app-id-values-for-signing-in).
     - Application ID and Application key.  For instructions, see [Get application ID and authentication key](../active-directory/develop/howto-create-service-principal-portal.md#get-tenant-and-app-id-values-for-signing-in).
 - Add the user identity who will be making the data access request as the owner of the Azure AD web application (from the Azure AD web application > Settings > Owners > Add owner). 
-    - The user identity must be in the Office 365 organization you are getting data from and must not be a Guest user.
+    - The user identity must be in the Microsoft 365 (Office 365) organization you are getting data from and must not be a Guest user.
 
 ## Approving new data access requests
 
@@ -61,7 +61,7 @@ Refer [here](/graph/data-connect-faq#how-can-i-approve-pam-requests-via-microsof
 ## Getting started
 
 >[!TIP]
->For a walkthrough of using Office 365 connector, see [Load data from Office 365](load-office-365-data.md) article.
+>For a walkthrough of using Microsoft 365 (Office 365) connector, see [Load data from Microsoft 365 (Office 365)](load-office-365-data.md) article.
 
 You can create a pipeline with the copy activity by using one of the following tools or SDKs. Select a link to go to a tutorial with step-by-step instructions to create a pipeline with a copy activity. 
 
@@ -72,9 +72,9 @@ You can create a pipeline with the copy activity by using one of the following t
 - [REST API](quickstart-create-data-factory-rest-api.md)
 - [Azure Resource Manager template](quickstart-create-data-factory-resource-manager-template.md). 
 
-## Create a linked service to Office 365 using UI
+## Create a linked service to Microsoft 365 (Office 365) using UI
 
-Use the following steps to create a linked service to Office 365 in the Azure portal UI.
+Use the following steps to create a linked service to Microsoft 365 (Office 365) in the Azure portal UI.
 
 1. Browse to the Manage tab in your Azure Data Factory or Synapse workspace and select Linked Services, then click New:
 
@@ -86,34 +86,34 @@ Use the following steps to create a linked service to Office 365 in the Azure po
 
     :::image type="content" source="media/doc-common-process/new-linked-service-synapse.png" alt-text="Screenshot of creating a new linked service with Azure Synapse UI.":::
 
-2. Search for Office and select the Office 365 connector.
+2. Search for Microsoft 365 (Office 365) and select the Microsoft 365 (Office 365) connector.
 
-    :::image type="content" source="media/connector-office-365/office-365-connector.png" alt-text="Screenshot of the Office 365 connector.":::    
+    :::image type="content" source="media/connector-office-365/office-365-connector.png" alt-text="Screenshot of the Microsoft 365 (Office 365) connector.":::    
 
 1. Configure the service details, test the connection, and create the new linked service.
 
-    :::image type="content" source="media/connector-office-365/configure-office-365-linked-service.png" alt-text="Screenshot of linked service configuration for Office 365.":::
+    :::image type="content" source="media/connector-office-365/configure-office-365-linked-service.png" alt-text="Screenshot of linked service configuration for Microsoft 365 (Office 365).":::
 
 ## Connector configuration details
 
-The following sections provide details about properties that are used to define Data Factory entities specific to Office 365 connector.
+The following sections provide details about properties that are used to define Data Factory entities specific to Microsoft 365 (Office 365) connector.
 
 ## Linked service properties
 
-The following properties are supported for Office 365 linked service:
+The following properties are supported for Microsoft 365 (Office 365) linked service:
 
 | Property | Description | Required |
 |:--- |:--- |:--- |
 | type | The type property must be set to: **Office365** | Yes |
-| office365TenantId | Azure tenant ID to which the Office 365 account belongs. | Yes |
+| office365TenantId | Azure tenant ID to which the Microsoft 365 (Office 365) account belongs. | Yes |
 | servicePrincipalTenantId | Specify the tenant information under which your Azure AD web application resides. | Yes |
 | servicePrincipalId | Specify the application's client ID. | Yes |
 | servicePrincipalKey | Specify the application's key. Mark this field as a SecureString to store it securely. | Yes |
 | connectVia | The Integration Runtime to be used to connect to the data store.  If not specified, it uses the default Azure Integration Runtime. | No |
 
 >[!NOTE]
 > The difference between **office365TenantId** and **servicePrincipalTenantId** and the corresponding value to provide:
->- If you are an enterprise developer developing an application against Office 365 data for your own organization's usage, then you should supply the same tenant ID for both properties, which is your organization's AAD tenant ID.
+>- If you are an enterprise developer developing an application against Microsoft 365 (Office 365) data for your own organization's usage, then you should supply the same tenant ID for both properties, which is your organization's AAD tenant ID.
 >- If you are an ISV developer developing an application for your customers, then office365TenantId will be your customer's (application installer) AAD tenant ID and servicePrincipalTenantId will be your company's AAD tenant ID.
 
 **Example:**
@@ -124,7 +124,7 @@ The following properties are supported for Office 365 linked service:
     "properties": {
         "type": "Office365",
         "typeProperties": {
-            "office365TenantId": "<Office 365 tenant id>",
+            "office365TenantId": "<Microsoft 365 (Office 365) tenant id>",
             "servicePrincipalTenantId": "<AAD app service principal tenant id>",
             "servicePrincipalId": "<AAD app service principal id>",
             "servicePrincipalKey": {
@@ -138,14 +138,14 @@ The following properties are supported for Office 365 linked service:
 
 ## Dataset properties
 
-For a full list of sections and properties available for defining datasets, see the [datasets](concepts-datasets-linked-services.md) article. This section provides a list of properties supported by Office 365 dataset.
+For a full list of sections and properties available for defining datasets, see the [datasets](concepts-datasets-linked-services.md) article. This section provides a list of properties supported by Microsoft 365 (Office 365) dataset.
 
-To copy data from Office 365, the following properties are supported:
+To copy data from Microsoft 365 (Office 365), the following properties are supported:
 
 | Property | Description | Required |
 |:--- |:--- |:--- |
 | type | The type property of the dataset must be set to: **Office365Table** | Yes |
-| tableName | Name of the dataset to extract from Office 365. Refer [here](/graph/data-connect-datasets#datasets) for the list of Office 365 datasets available for extraction. | Yes |
+| tableName | Name of the dataset to extract from Microsoft 365 (Office 365). Refer [here](/graph/data-connect-datasets#datasets) for the list of Microsoft 365 (Office 365) datasets available for extraction. | Yes |
 
 If you were setting `dateFilterColumn`, `startTime`, `endTime`, and `userScopeFilterUri` in dataset, it is still supported as-is, while you are suggested to use the new model in activity source going forward.
 
@@ -157,7 +157,7 @@ If you were setting `dateFilterColumn`, `startTime`, `endTime`, and `userScopeFi
     "properties": {
         "type": "Office365Table",
         "linkedServiceName": {
-            "referenceName": "<Office 365 linked service name>",
+            "referenceName": "<Microsoft 365 (Office 365) linked service name>",
             "type": "LinkedServiceReference"
         },
         "schema": [],
@@ -170,18 +170,18 @@ If you were setting `dateFilterColumn`, `startTime`, `endTime`, and `userScopeFi
 
 ## Copy activity properties
 
-For a full list of sections and properties available for defining activities, see the [Pipelines](concepts-pipelines-activities.md) article. This section provides a list of properties supported by Office 365 source.
+For a full list of sections and properties available for defining activities, see the [Pipelines](concepts-pipelines-activities.md) article. This section provides a list of properties supported by Microsoft 365 (Office 365) source.
 
-### Office 365 as source
+### Microsoft 365 (Office 365) as source
 
-To copy data from Office 365, the following properties are supported in the copy activity **source** section:
+To copy data from Microsoft 365 (Office 365), the following properties are supported in the copy activity **source** section:
 
 | Property | Description | Required |
 |:--- |:--- |:--- |
 | type | The type property of the copy activity source must be set to: **Office365Source** | Yes |
 | allowedGroups | Group selection predicate.  Use this property to select up to 10 user groups for whom the data will be retrieved.  If no groups are specified, then data will be returned for the entire organization. | No |
-| userScopeFilterUri | When `allowedGroups` property is not specified, you can use a predicate expression that is applied on the entire tenant to filter the specific rows to extract from Office 365. The predicate format should match the query format of Microsoft Graph APIs, e.g. `https://graph.microsoft.com/v1.0/users?$filter=Department eq 'Finance'`. | No |
-| dateFilterColumn | Name of the DateTime filter column. Use this property to limit the time range for which Office 365 data is extracted. | Yes if dataset has one or more DateTime columns. Refer [here](/graph/data-connect-filtering#filtering) for list of datasets that require this DateTime filter. |
+| userScopeFilterUri | When `allowedGroups` property is not specified, you can use a predicate expression that is applied on the entire tenant to filter the specific rows to extract from Microsoft 365 (Office 365). The predicate format should match the query format of Microsoft Graph APIs, e.g. `https://graph.microsoft.com/v1.0/users?$filter=Department eq 'Finance'`. | No |
+| dateFilterColumn | Name of the DateTime filter column. Use this property to limit the time range for which Microsoft 365 (Office 365) data is extracted. | Yes if dataset has one or more DateTime columns. Refer [here](/graph/data-connect-filtering#filtering) for list of datasets that require this DateTime filter. |
 | startTime | Start DateTime value to filter on. | Yes if `dateFilterColumn` is specified |
 | endTime | End DateTime value to filter on. | Yes if `dateFilterColumn` is specified |
 | outputColumns | Array of the columns to copy to sink. | No |
@@ -195,7 +195,7 @@ To copy data from Office 365, the following properties are supported in the copy
         "type": "Copy",
         "inputs": [
             {
-                "referenceName": "<Office 365 input dataset name>",
+                "referenceName": "<Microsoft 365 (Office 365) input dataset name>",
                 "type": "DatasetReference"
             }
         ],