Skip to content

Commit ee788b2

Browse files
committed
wording
1 parent daca1cb commit ee788b2

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ In addition,
3838
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.
3939
> [!NOTE]
4040
> * 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.
41+
> * To enforce time-limited access to APIs, API publishers may be able to use policies with subscription keys, or use a mechanism that provides built-in expiration such as token-based authentication.
4242
4343
## Scope of subscriptions
4444

0 commit comments

Comments
 (0)