Skip to content

Commit daca1cb

Browse files
committed
[APIM] Clarify subscription key lifecycle
1 parent 3503c1e commit daca1cb

File tree

1 file changed

+10
-6
lines changed

1 file changed

+10
-6
lines changed

articles/api-management/api-management-subscriptions.md

Lines changed: 10 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: dlepow
77

88
ms.service: api-management
99
ms.topic: conceptual
10-
ms.date: 01/05/2022
10+
ms.date: 09/27/2022
1111
ms.author: danlep
1212
---
1313
# Subscriptions in Azure API Management
@@ -20,14 +20,11 @@ By publishing APIs through API Management, you can easily secure API access usin
2020
* Rejected immediately by the API Management gateway.
2121
* Not forwarded to the back-end services.
2222

23-
To access APIs, you'll need a subscription and a subscription key. A *subscription* is a named container for a pair of subscription keys.
24-
25-
> [!NOTE]
26-
> Regularly regenerating keys is a common security precaution. Like most Azure services requiring a subscription key, API Management generates keys in pairs. Each application using the service can switch from *key A* to *key B* and regenerate key A with minimal disruption, and vice versa.
23+
To access APIs, developers need a subscription and a subscription key. A *subscription* is a named container for a pair of subscription keys.
2724

2825
In addition,
2926

30-
* Developers can get subscriptions without approval from API publishers.
27+
* Developers can get subscriptions without needing approval from API publishers.
3128
* API publishers can create subscriptions directly for API consumers.
3229

3330
> [!TIP]
@@ -36,6 +33,13 @@ In addition,
3633
> - [Client certificates](api-management-howto-mutual-certificates-for-clients.md)
3734
> - [Restrict caller IPs](./api-management-access-restriction-policies.md#RestrictCallerIPs)
3835
36+
## Manage subscription keys
37+
38+
Regularly regenerating keys is a common security precaution. Like most Azure services requiring a subscription key, API Management generates keys in pairs. Each application using the service can switch from *key A* to *key B* and regenerate key A with minimal disruption, and vice versa.
39+
> [!NOTE]
40+
> * API Management doesn't provide built-in features to manage the lifecycle of subscription keys, such as setting expiration dates or automatically rotating keys. You can develop workflows to automate these processes using tools such as Azure PowerShell or the Azure SDKs.
41+
> * To enforce time-limited access to APIs, you may be able to use policies with subscription keys, or use a mechanism that provides built-in expiration such as token-based authentication.
42+
3943
## Scope of subscriptions
4044

4145
Subscriptions can be associated with various scopes: [product](api-management-howto-add-products.md), all APIs, or an individual API.

0 commit comments

Comments
 (0)