Merge pull request #235157 from dlepow/subs

[APIM] Update to subscription concepts

Author: prmerger-automator[bot]

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

@@ -7,14 +7,17 @@ author: dlepow
 
 ms.service: api-management
 ms.topic: conceptual
-ms.date: 12/16/2022
+ms.date: 04/19/2023
 ms.author: danlep
 ms.custom: engagement-fy23
 ---
 # Subscriptions in Azure API Management
 
 In Azure API Management, *subscriptions* are the most common way for API consumers to access APIs published through an API Management instance. This article provides an overview of the concept.
 
+> [!NOTE]
+> An API Management subscription is used specifically to call APIs through API Management. It's not the same as an Azure subscription.
+
 ## What are subscriptions?
 
 By publishing APIs through API Management, you can easily secure API access using subscription keys. Developers who need to consume the published APIs must include a valid subscription key in HTTP requests when calling those APIs. Without a valid subscription key, the calls are:
@@ -76,7 +79,7 @@ Each API Management instance comes with an immutable, all-APIs subscription (als
 
 ### Standalone subscriptions
 
-API Management also allows *standalone* subscriptions, which are not associated with a developer account. This feature proves useful in scenarios similar to several developers or teams sharing a subscription.
+API Management also allows *standalone* subscriptions, which aren't associated with a developer account. This feature proves useful in scenarios similar to several developers or teams sharing a subscription.
 
 Creating a subscription without assigning an owner makes it a standalone subscription. To grant developers and the rest of your team access to the standalone subscription key, either:
 * Manually share the subscription key.
@@ -88,6 +91,17 @@ API publishers can [create subscriptions](api-management-howto-create-subscripti
 
 When created in the portal, a subscription is in the **Active** state, meaning a subscriber can call an associated API using a valid subscription key. You can change the state of the subscription as needed - for example, you can suspend, cancel, or delete the subscription to prevent API access.
 
+## Use a subscription key
+
+A subscriber can use an API Management subscription key in one of two ways:
+
+* Add the **Ocp-Apim-Subscription-Key** HTTP header to the request, passing the value of a valid subscription key.
+
+* Include the **subscription-key** query parameter and a valid value in the URL. The query parameter is checked only if the header isn't present.
+
+> [!TIP]
+> **Ocp-Apim-Subscription-Key** is the default name of the subscription key header, and **subscription-key** is the default name of the query parameter. If desired, you may modify these names in the settings for each API. For example, in the portal, update these names on the **Settings** tab of an API.
+
 ## Enable or disable subscription requirement for API or product access
 
 By default when you create an API, a subscription key is required for API access. Similarly, when you create a product, by default a subscription key is required to access any API that's added to the product. Under certain scenarios, an API publisher might want to publish a product or a particular API to the public without the requirement of subscriptions. While a publisher could choose to enable unsecured (anonymous) access to certain APIs, configuring another mechanism to secure client access is recommended.