Skip to content

Commit 0ab265e

Browse files
Tutorials to heft (#10699)
* Revise Azure AD API tutorial for SharePoint Framework Updated the tutorial to reflect changes in the Azure AD integration and SharePoint Framework usage, including updated dates and instructions. * Revise tutorial to heft Updated the tutorial to reflect recent changes and improvements in the process of consuming multi-tenant enterprise APIs secured with Azure AD in SharePoint Framework solutions.
1 parent 21ab6f2 commit 0ab265e

2 files changed

Lines changed: 6 additions & 8 deletions

File tree

docs/spfx/use-aadhttpclient-enterpriseapi-multitenant.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,14 @@
11
---
22
title: Consume multi-tenant enterprise APIs secured with Azure AD in SharePoint Framework
33
description: Tutorial on using the AadHttpClient to connect to a multi-tenant enterprise API secured with Azure AD in SharePoint Framework solutions.
4-
ms.date: 06/13/2022
4+
ms.date: 03/05/2026
55
ms.localizationpriority: medium
66
---
77

88
# Consume multi-tenant enterprise APIs secured with Azure AD in SharePoint Framework
99

1010
This article illustrates how you would connect to a multi-tenant enterprise API secured with Azure Active Directory from a SharePoint Framework solution. It covers both creating and securing the API as well building the SharePoint Framework solution.
1111

12-
[!INCLUDE [spfx-gulp-heft-migration-wip](../../includes/snippets/spfx-gulp-heft-migration-wip.md)]
13-
1412
## Create a multi-tenant enterprise API secured with Azure AD
1513

1614
Start with creating a multi-tenant enterprise API secured with Azure Active Directory. While there are no restrictions how the API should be implemented from the SharePoint Framework point of view, in this tutorial, you'll build the API using Azure Functions and secure it using Azure App Service Authentication.
@@ -423,7 +421,7 @@ After completing the implementation of the SharePoint Framework solution, the ne
423421
First, build, and package the project, by executing in the command line:
424422

425423
```console
426-
gulp bundle --ship && gulp package-solution --ship
424+
heft build --production && heft package-solution --production
427425
```
428426

429427
Next, in the explorer, open the project folder and navigate to the **sharepoint/solution** folder.
@@ -489,3 +487,4 @@ Select the **+** option to open the toolbox. In the search box type `Orders` to
489487
Select the **Orders** web part to add it to the page. You should see the list of orders retrieved from the enterprise API.
490488

491489
![List of recent orders retrieved from an enterprise API displayed on a SharePoint page](../images/use-aadhttpclient-enterpriseapi-webpart-orders.png)
490+

docs/spfx/use-aadhttpclient-enterpriseapi.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,14 @@
11
---
22
title: Consume enterprise APIs secured with Azure AD in SharePoint Framework
33
description: Tutorial on using the AadHttpClient to connect to an enterprise API secured with Azure AD in SharePoint Framework solutions.
4-
ms.date: 12/21/2020
4+
ms.date: 03/05/2026
55
ms.localizationpriority: high
66
---
77

88
# Consume enterprise APIs secured with Azure AD in SharePoint Framework
99

1010
This article illustrates how you would connect to an enterprise API secured with Azure Active Directory from a SharePoint Framework solution. It covers both creating and securing the API as well as building the SharePoint Framework solution.
1111

12-
[!INCLUDE [spfx-gulp-heft-migration-wip](../../includes/snippets/spfx-gulp-heft-migration-wip.md)]
13-
1412
## Create an enterprise API secured with Azure AD
1513

1614
Start with creating an enterprise API secured with Azure Active Directory. While there are no restrictions on how the API should be implemented from the SharePoint Framework point of view, in this tutorial, you'll build the API using Azure Functions and secure it using Azure App Service Authentication.
@@ -388,7 +386,7 @@ After completing the implementation of the SharePoint Framework solution, the ne
388386
First, build, and package the project using the command line:
389387

390388
```console
391-
gulp bundle --ship && gulp package-solution --ship
389+
heft build --production && heft package-solution --production
392390
```
393391

394392
Next, in file explorer, open the project folder and navigate to the **sharepoint/solution** folder:
@@ -459,3 +457,4 @@ Select the **Orders** web part to add it to the page. You should see the list of
459457
![List of recent orders retrieved from an enterprise API displayed on a SharePoint page](../images/use-aadhttpclient-enterpriseapi-webpart-orders.png)
460458

461459
> If you receive an error with the technical details of "Failed to open pop-up window", you have a pop-up blocker enabled. You will need to disable the browser's pop-up blocker for your site in order to show the page correctly.
460+

0 commit comments

Comments
 (0)