Merge pull request #277 from MicrosoftDocs/master

Live publish

Author: KumarVivek

powerquery-docs/Connectors/ODataFeed.md

@@ -69,4 +69,6 @@ To load data from an OData Feed in Power Query Online:
 
    If you have multiple tables that have a direct relationship to one or more of the already selected tables, you can select the **Select Related Tables** button. When you do, all tables that have a direct relationship to one or more of the already selected tables will be imported as well.
 
+## Connecting to Microsoft Graph
 
+Connecting to [Microsoft Graph](https://docs.microsoft.com/graph/overview) REST [APIs](https://graph.microsoft.com) from Power Query isn't recommended or supported. See this [article](../connecting-to-graph.md) for more information.

powerquery-docs/Connectors/SalesforceObjects.md

@@ -26,7 +26,7 @@ LocalizationGroup: reference
 > Some capabilities may be present in one product but not others due to deployment schedules and host-specific capabilities.
 
 >[!Warning]
-> By default, Salesforce does not support Internet Explorer 11, which is used as part of the authentication experience to online services in Power Query Desktop. Please opt-in for [extended support for accessing Lightning Experience Using Microsoft Internet Explorer 11](https://help.salesforce.com/articleView?id=000333934&type=1&mode=1). You may also want to review Salesforce documentation on [configuring Internet Explorer](https://developer.salesforce.com/docs/atlas.en-us.salesforce_supported_browsers_cheatsheet.meta/salesforce_supported_browsers_cheatsheet/getstart_browser_ie.htm). At this time, users will be impaired from authenticating, but stored credentials should continue to work until their existing authentication tokens expire.
+> By default, Salesforce does not support Internet Explorer 11, which is used as part of the authentication experience to online services in Power Query Desktop. Please opt-in for [extended support for accessing Lightning Experience Using Microsoft Internet Explorer 11](https://help.salesforce.com/articleView?id=000333934&type=1&mode=1). You may also want to review Salesforce documentation on [configuring Internet Explorer](https://developer.salesforce.com/docs/atlas.en-us.salesforce_supported_browsers_cheatsheet.meta/salesforce_supported_browsers_cheatsheet/getstart_browser_ie.htm). At this time, users will be impaired from authenticating, but stored credentials should continue to work until their existing authentication tokens expire. To resolve this, review "Enabling Microsoft Edge (Chromium) for OAuth Authentication in Power BI Desktop" at the bottom of this document.
  
 ## Prerequisites
 
@@ -109,10 +109,10 @@ For more information about Salesforce internal API limits, see [Salesforce Devel
 
 ## Troubleshooting
 
-### Enabling OAuth Authentication in Power BI Desktop
+### Enabling Microsoft Edge (Chromium) for OAuth Authentication in Power BI Desktop
 
-Starting in December 2021 Power BI Desktop:
-* Install the new Edge Chromium browser, (at least beta) from https://www.microsoftedgeinsider.com/download.
+Starting in December 2020 Power BI Desktop:
+* Install the new Microsoft Edge (Chromium) browser, (at least beta) from https://www.microsoftedgeinsider.com/download.
 * In your Environment Variables, set the System variable `PQ_EnableEdgeChromiumOAuth` to true . Once that is set it will use Edge Chromium for only QuickBooksOnline. For this release, only QuickBooksOnline is enabled by default.
 * To set it for Salesforce, in System Environment Variables set `PQ_ExtendEdgeChromiumOAuthAllowList` to Salesforce
 

powerquery-docs/Connectors/SalesforceReports.md

@@ -26,7 +26,7 @@ LocalizationGroup: reference
 > Some capabilities may be present in one product but not others due to deployment schedules and host-specific capabilities.
 
 >[!Warning]
-> By default, Salesforce does not support Internet Explorer 11, which is used as part of the authentication experience to online services in Power Query Desktop. Please opt-in for [extended support for accessing Lightning Experience Using Microsoft Internet Explorer 11](https://help.salesforce.com/articleView?id=000333934&type=1&mode=1). You may also want to review Salesforce documentation on [configuring Internet Explorer](https://developer.salesforce.com/docs/atlas.en-us.salesforce_supported_browsers_cheatsheet.meta/salesforce_supported_browsers_cheatsheet/getstart_browser_ie.htm). At this time, users will be impaired from authenticating, but stored credentials should continue to work until their existing authentication tokens expire.
+> By default, Salesforce does not support Internet Explorer 11, which is used as part of the authentication experience to online services in Power Query Desktop. Please opt-in for [extended support for accessing Lightning Experience Using Microsoft Internet Explorer 11](https://help.salesforce.com/articleView?id=000333934&type=1&mode=1). You may also want to review Salesforce documentation on [configuring Internet Explorer](https://developer.salesforce.com/docs/atlas.en-us.salesforce_supported_browsers_cheatsheet.meta/salesforce_supported_browsers_cheatsheet/getstart_browser_ie.htm). At this time, users will be impaired from authenticating, but stored credentials should continue to work until their existing authentication tokens expire. To resolve this, review "Enabling Microsoft Edge (Chromium) for OAuth Authentication in Power BI Desktop" at the bottom of this document.
  
 ## Prerequisites
 
@@ -106,10 +106,10 @@ For more information about Salesforce internal API limits, see [Salesforce Devel
 
 ## Troubleshooting
 
-### Enabling OAuth Authentication in Power BI Desktop
+### Enabling Microsoft Edge (Chromium) for OAuth Authentication in Power BI Desktop
 
-Starting in December 2021 Power BI Desktop:
-* Install the new Edge Chromium browser, (at least beta) from https://www.microsoftedgeinsider.com/download.
+Starting in December 2020 Power BI Desktop:
+* Install the new Microsoft Edge (Chromium) browser, (at least beta) from https://www.microsoftedgeinsider.com/download.
 * In your Environment Variables, set the System variable `PQ_EnableEdgeChromiumOAuth` to true . Once that is set it will use Edge Chromium for only QuickBooksOnline. For this release, only QuickBooksOnline is enabled by default.
 * To set it for Salesforce, in System Environment Variables set `PQ_ExtendEdgeChromiumOAuthAllowList` to Salesforce
 

powerquery-docs/Connectors/Web/web-troubleshoot.md

@@ -11,6 +11,10 @@ LocalizationGroup: reference
 
 # Troubleshooting the Web connector
 
+## Connecting to Microsoft Graph
+
+Connecting to [Microsoft Graph](https://docs.microsoft.com/graph/overview) REST [APIs](https://graph.microsoft.com) from Power Query isn't recommended or supported. See this [article](../../connecting-to-graph.md) for more information.
+
 ## Using a gateway with the Web connector
 
 Every use of the Web connector to get data from an HTML page requires the use of an on-premises data gateway when published to a Cloud service, whether it's Power BI Service for datasets or dataflows, or Power Apps for dataflows. (Currently, Dynamics 365 Customer Insights doesn't support the use of a gateway.) <!-- The only exception is when using Power BI Desktop with the **New web table inference** option turned on, and then publishing that report to the Power BI service. The **New web table inference** option can be enabled or disabled in Power BI Desktop by going to **File** > **Options and settings** > **Options** > **Preview features**. The option is enabled by default. -->

powerquery-docs/Connectors/sap-bw/transform-filter-sap-bw-data.md

@@ -13,7 +13,7 @@ LocalizationGroup: reference
 
 # Transform and filter an SAP BW dataset
 
-With Power Query Editor, you can apply additional data transformations and filtering steps before you bring the dataset from SAP BW into the Power BI Desktop or Power Platform data model.
+With Power Query Editor, you can apply additional data transformations and filtering steps before you bring the dataset from SAP BW into the Power BI Desktop or Microsoft Power Platform data model.
 
 In Power Query Editor, the *Applied Steps* for the query are shown in the **Query Settings** pane on the right. To modify or review a step, select the gear icon next to a step.
 
@@ -68,4 +68,4 @@ The following examples show some descriptions of various cube functions:
 ### See also
 
 * [Power Query M formula language reference](https://docs.microsoft.com/powerquery-m/)
-* [Implementation details](implementation-details.md)
+* [Implementation details](implementation-details.md)

powerquery-docs/TOC.yml

@@ -11,7 +11,9 @@
       - name: "Authentication with a data source"
         href: ConnectorAuthentication.md
       - name: "SharePoint and OneDrive for Business files import"
-        href: sharepoint-onedrive-files.md        
+        href: sharepoint-onedrive-files.md    
+      - name: "Lack of support connecting to Microsoft Graph"    
+        href: connecting-to-graph.md
     - name: Transform data
       items:
       - name: "Use Power Query"

powerquery-docs/connecting-to-graph.md

@@ -0,0 +1,38 @@
+---
+title: Lack of Support for Microsoft Graph in Power Query
+description: This article describes Power Query's lack of support for connecting to Microsoft Graph
+author: mattmasson
+ms.service: powerquery
+ms.reviewer: kvivek
+ms.date: 02/23/2021
+ms.author: mmasson
+
+---
+
+# Lack of Support for Microsoft Graph in Power Query
+
+## Summary
+
+Connecting to [Microsoft Graph](https://docs.microsoft.com/graph/overview) REST [APIs](https://graph.microsoft.com) from Power Query isn't recommended or supported. Instead, we recommend users explore alternative solutions for retrieving analytics data based on Graph, such as [Microsoft Graph data connect](https://docs.microsoft.com/graph/overview#access-microsoft-graph-data-at-scale-using-microsoft-graph-data-connect).
+
+Users may find they can make certain REST calls to Microsoft Graph API endpoints work through the `Web.Contents` or `OData.Feed` functions, but these approaches are not reliable as long-term solutions. 
+
+This article outlines the issues associated with Microsoft Graph connectivity from Power Query and explain why it isn't recommended.
+
+### Authentication
+
+The built-in Organizational Account authentication flow for Power Query’s `Web.Contents` and `OData.Feed` functions isn't compatible with most Graph endpoints. Specifically, Power Query’s Azure Active Directory (Azure AD) client requests the `user_impersonation` scope, which isn't compatible with Graph’s security model. Graph uses a rich set of permissions that aren't available through our generic Web and OData connectors.
+
+Implementing your own Azure AD credential retrieval flows directly from your query, or using hardcoded or embedded credentials, also isn't recommended for security reasons.
+
+### OData Libraries’ Incompatibility
+
+Certain Graph endpoints and extensions to Graph may require the use of OData libraries and features that aren't supported by Power Query’s built-in `OData.Feed` function because Graph and Power Query may be using two different versions of OData libraries. These issues generally result in errors retrieving the service’s $metadata document. Users may discover common guidance related to passing the `Implementation = "2.0"` option to the `OData.Feed` function call to ensure the latest supported OData libraries are used. While this approach does resolve certain OData incompatibilities, users may still encounter errors over time as Graph and Power Query adopt new versions of the OData libraries at different times.
+
+### Performance
+
+The Microsoft Graph API is designed to support many application scenarios but is suboptimal for the large-scale data retrieval required for most analytics scenarios. Users trying to retrieve large amounts of data from Graph APIs may encounter performance issues. Details around scenario applicability can be found in the Graph documentation. 
+
+## Using a Custom Connector
+
+Some Power Query users have enabled Graph connectivity through custom connectors, limiting their functionality to certain parts of the Graph API. This approach allows connector developers to resolve general authentication issues by defining their own Azure AD client with Graph specific permissions. Some custom connectors work around OData challenges by using `Web.Contents` and simulating OData support within their connector logic. However, this approach isn't recommended as users frequently hit the performance and scalability issues described above. Developers who take this route should continue with these limitations in mind.

powerquery-docs/dataflows/computed-entities-scenarios.md

@@ -1,6 +1,6 @@
 ---
 title: Computed entity scenarios and use cases
-description: Computed entity scenarios and use cases
+description: Computed entity scenarios and use cases.
 author: radacad
 ms.service: powerquery
 ms.reviewer: kvivek
@@ -62,7 +62,7 @@ This means that the Orders Aggregated entity will be getting data from the Order
 
 ## Computed entity in other dataflows
 
-You can also create a computed entity in other dataflows. It can be created by getting data from a dataflow with the Power Platform dataflow connector.
+You can also create a computed entity in other dataflows. It can be created by getting data from a dataflow with the Microsoft Power Platform dataflow connector.
 
 :::image type="complex" source="media/getdatafromppdataflows.png" alt-text="<Get data from Power Platform dataflows>":::
    Image emphasizes the Power Platform dataflows connector from the Power Query choos data source window, with a description that states that one dataflow entity can be built on top of the data from another dataflow entity, which is already persisted in storage.

powerquery-docs/dataflows/configuring-storage-and-compute-options-for-analytical-dataflows.md

@@ -1,6 +1,6 @@
 ---
 title: Configuring storage and compute options for analytical dataflows
-description: Configuring storage and compute options for analytical dataflows
+description: Configuring storage and compute options for analytical dataflows.
 author: radacad
 
 ms.service: powerquery
@@ -21,7 +21,7 @@ Analytical dataflows allow an additional storage option: your organizations' Azu
 
 ## Dataflows that use built-in storage
 
-By default, analytical dataflows will use the built-in Data Lake Storage; for example, when you create a dataflow in Power BI or Power Apps. Access to the output of this type of dataflow is only possible through the Power Platform dataflows connector in Power BI Desktop, or from other dataflows.
+By default, analytical dataflows will use the built-in Data Lake Storage; for example, when you create a dataflow in Power BI or Power Apps. Access to the output of this type of dataflow is only possible through the Microsoft Power Platform dataflows connector in Power BI Desktop, or from other dataflows.
 
 ## Dataflows that use customer-provided storage
 

powerquery-docs/dataflows/data-sources.md

@@ -1,6 +1,6 @@
 ---
 title: Connect to data sources for dataflows
-description: Learn how to connect to data sources for dataflows
+description: Learn how to connect to data sources for dataflows.
 author: bensack
 manager: kfile
 ms.reviewer: ''
@@ -16,7 +16,7 @@ LocalizationGroup: Data from files
 
 [!INCLUDE [CDS note](../includes/cc-data-platform-banner.md)]
 
-With Power Platform dataflows, you can connect to many different data sources to create new dataflows, or add new entities to an existing dataflow.
+With Microsoft Power Platform dataflows, you can connect to many different data sources to create new dataflows, or add new entities to an existing dataflow.
 
 This article lists many available data sources for creating or adding to dataflows, and describes how to create those dataflows by using these data sources. For an overview of how to create and use dataflows, see [Creating and using dataflows in Power BI](https://docs.microsoft.com/power-bi/service-dataflows-create-use).