Summary
Modern SharePoint web parts often need data that doesn't live in SharePoint—content from a public service, records from a line-of-business API protected by Microsoft Entra ID, or profile and people data from Microsoft 365. Reaching that data means calling external HTTP APIs correctly, each with its own authentication requirements.
You learned the three SharePoint Framework approaches for those calls: the HttpClient object for anonymous, non-Microsoft REST APIs; the AadHttpClient object for APIs secured with Microsoft Entra ID; and the Microsoft Graph client for Microsoft 365 data—none of which require you to add your own HTTP library or manage access tokens by hand. Through the exercises, you built working web parts for each scenario: one that displays imagery from an anonymous public API, one that lists directory users through an Entra ID secured call, and a persona card that shows the signed-in user's profile from Microsoft Graph.
With these techniques, you can extend SharePoint solutions well beyond the data stored in SharePoint itself—securely integrating virtually any HTTP service to deliver richer, more connected experiences to the people who use them.