Skip to content

Commit e0300c5

Browse files
committed
add internal nav
1 parent 00dbfa9 commit e0300c5

1 file changed

Lines changed: 7 additions & 2 deletions

File tree

articles/api-center/authorize-api-access.md

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Configure access to APIs in your Azure API Center inventory using A
44

55
ms.service: azure-api-center
66
ms.topic: how-to
7-
ms.date: 03/02/2026
7+
ms.date: 03/10/2026
88

99
ms.custom:
1010
# Customer intent: As an API program manager, I want to store API authorization information in my API center and enable authorized users to test APIs in the API Center portal.
@@ -75,6 +75,8 @@ Access the key vault using your API center's managed identity.
7575

7676
1. Select **Create**.
7777

78+
After completing this configuration, go to the [Add authentication configuration to an API version](#add-authentication-configuration-to-an-api-version) section to associate the API key configuration with an API version.
79+
7880
## Option 2: Configure OAuth 2.0 authorization
7981

8082
For an API that supports OAuth 2.0 authorization, complete the following steps. You can configure one or both of the following flows:
@@ -152,6 +154,8 @@ Access the key vault using your API center's managed identity.
152154

153155
1. Select **Create** to save the configuration.
154156

157+
After completing this configuration, go to the [Add authentication configuration to an API version](#add-authentication-configuration-to-an-api-version) section to associate the OAuth 2.0 configuration with an API version.
158+
155159
## Option 3: Configure settings for another HTTP security scheme
156160

157161
For APIs that use another HTTP security scheme, such as Basic authentication or bearer tokens that don't use OAuth 2.0, complete the following steps. You might need to choose this option for legacy APIs.
@@ -173,7 +177,8 @@ In the [portal](https://azure.microsoft.com), go to your API center.
173177
| **Bearer** | Sends a token other than an OAuth 2.0 access token in the `Authorization: Bearer <token>` header. |
174178
| **Digest** | A challenge-response mechanism where the server sends a nonce; the client responds with a hash of credentials + nonce. |
175179
| **Custom** | Another mechanism scheme such as a vendor-specific scheme. |
176-
180+
181+
After completing this configuration, go to the next section to [associate the configuration with an API version](#add-authentication-configuration-to-an-api-version).
177182

178183
## Add authentication configuration to an API version
179184

0 commit comments

Comments
 (0)