Merge pull request MicrosoftDocs#274 from MicrosoftDocs/graph-support-update

Graph support update

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/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/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.