Skip to content

Commit 249f0fb

Browse files
committed
Updates on the graph docs
1 parent 3204677 commit 249f0fb

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

docs/spfx/web-parts/guidance/connect-to-api-secured-with-aad.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,9 @@ When building SharePoint Framework solutions, you might need to connect to your
1212

1313
This article discusses the different approaches and describes the step-by-step process of building and connecting to an API secured with Azure AD.
1414

15+
> [!IMPORTANT]
16+
> When connecting ot Azure AD secured APIs, it's recommended to use **GraphHttpClient** or **AadHttpClient** classes. These are new capabilities which are currently in preview and planned to be generally released during spring 2018. You can read more information on recommended models from following [article](../../use-msgraph.md)
17+
1518
## Secure an API with Azure AD
1619

1720
If you're using Office 365, securing custom APIs using Azure AD is an architectural option that you should definitely consider. First and foremost, it allows you to secure the access to the API using existing organizational credentials that are already managed through Office 365 and Azure AD. Users with an active account can seamlessly work with applications that leverage APIs secured with Azure AD. Azure AD administrators can centrally manage access to the API, the same way they manage access to all other applications registered with Azure AD.

0 commit comments

Comments
 (0)