Skip to content

Commit 77b692b

Browse files
authored
Made heading imperative on line 22 for consistency
1 parent 97c5f9e commit 77b692b

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/azure-fluid-relay/how-tos/azure-function-token-provider.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ In the [Fluid Framework](https://fluidframework.com/), TokenProviders are respon
1919

2020
Each Azure Fluid Relay service tenant you create is assigned a **tenant ID** and its own unique **tenant secret key**. The secret key is a **shared secret**. Your app/service knows it, and the Azure Fluid Relay service knows it. TokenProviders must know the secret key to sign requests, but the secret key cannot be included in client code.
2121

22-
## Implementing an Azure Function to sign tokens
22+
## Implement an Azure Function to sign tokens
2323

2424
One option for building a secure token provider is to create HTTPS endpoint and create a TokenProvider implementation that makes authenticated HTTPS requests to that endpoint to retrieve tokens. This enables you to store the *tenant secret key* in a secure location, such as [Azure Key Vault](../../key-vault/general/overview.md).
2525

0 commit comments

Comments
 (0)