Skip to content

Commit 68ead46

Browse files
authored
Merge pull request #95565 from ahmedelnably/master
[Functions] Move note for auth in GitHub Action doc
2 parents d98d4e7 + 84b551d commit 68ead46

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/azure-functions/functions-how-to-github-actions.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -28,6 +28,9 @@ For an Azure Functions workflow, the file has three sections:
2828
| **Build** | <ol><li>Set up the environment.</li><li>Build the function app.</li></ol> |
2929
| **Deploy** | <ol><li>Deploy the function app.</li></ol>|
3030

31+
> [!NOTE]
32+
> You do not need to create a service principal if you decide to use publishing profile for authentication.
33+
3134
## Create a service principal
3235

3336
You can create a [service principal](../active-directory/develop/app-objects-and-service-principals.md#service-principal-object) by using the [az ad sp create-for-rbac](/cli/azure/ad/sp?view=azure-cli-latest#az-ad-sp-create-for-rbac) command in the [Azure CLI](/cli/azure/). You can run this command using [Azure Cloud Shell](https://shell.azure.com) in the Azure portal or by selecting the **Try it** button.
@@ -38,9 +41,6 @@ az ad sp create-for-rbac --name "myApp" --role contributor --scopes /subscriptio
3841

3942
In this example, replace the placeholders in the resource with your subscription ID, resource group, and function app name. The output is the role assignment credentials that provides access to your function app. Copy this JSON object, which you can use to authenticate from GitHub.
4043

41-
> [!NOTE]
42-
> You do not need to create a service principal if you decide to use publishing profile for authentication.
43-
4444
> [!IMPORTANT]
4545
> It is always a good practice to grant minimum access. This is why the scope in the previous example is limited to the specific function app and not the entire resource group.
4646

0 commit comments

Comments
 (0)