You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/spfx/use-aad-tutorial.md
+10-10Lines changed: 10 additions & 10 deletions
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Consume the Microsoft Graph in the SharePoint Framework
3
3
description: Tutorial on using the AadHttpClient or MSGraphClient class to connect to the Microsoft Graph in SharePoint Framework solutions.
4
-
ms.date: 06/13/2022
4
+
ms.date: 01/06/2023
5
5
ms.localizationpriority: high
6
6
---
7
7
@@ -14,7 +14,7 @@ Introduced in v1.4.1, you can use the SharePoint Framework to consume Microsoft
14
14
In this article, you'll learn how to create a SharePoint Framework solution that uses the Microsoft Graph API with a custom set of permissions. For a conceptual overview of this technology, see [Connect to Azure AD-secured APIs in SharePoint Framework solutions](use-aadhttpclient.md).
15
15
16
16
> [!IMPORTANT]
17
-
> You can consume the Microsoft Graph API with versions of SharePoint Framework earlier than v1.4.1, either via the native **GraphHttpClient**, or by directly using [Microsoft identity platfomr authentication libraries](https://learn.microsoft.com/en-us/azure/active-directory/develop/reference-v2-libraries) implicit OAuth flow. However, the former approach is bound to a predefined set of permissions, which presents some limitations, and the latter is complex from a development perspective. For details about how to implement an implicit OAuth flow, see [Connect to APIs secured with Azure Active Directory](./web-parts/guidance/connect-to-api-secured-with-aad.md).
17
+
> You can consume the Microsoft Graph API with versions of SharePoint Framework earlier than v1.4.1, either via the native **GraphHttpClient**, or by directly using [Microsoft identity platfomr authentication libraries](/azure/active-directory/develop/reference-v2-libraries) implicit OAuth flow. However, the former approach is bound to a predefined set of permissions, which presents some limitations, and the latter is complex from a development perspective.
18
18
19
19
## Solution overview
20
20
@@ -252,7 +252,7 @@ Now you can update the **GraphConsumer** React component under the **./src/webpa
252
252
} from "office-ui-fabric-react";
253
253
import * as React from "react";
254
254
255
-
import { AadHttpClient, MSGraphClient } from "@microsoft/sp-http";
255
+
import { AadHttpClient, MSGraphClientV3 } from "@microsoft/sp-http";
256
256
import { escape } from "@microsoft/sp-lodash-subset";
257
257
258
258
import { ClientMode } from "./ClientMode";
@@ -453,11 +453,11 @@ When you package and deploy your solution, you (or an admin) will have to grant
0 commit comments