Skip to content

Commit 774f0e3

Browse files
authored
Update api-management-faq.yml
Clarify use of subscription key authentication. Fixes https://github.com/MicrosoftDocs/azure-docs/issues/102291
1 parent f798345 commit 774f0e3

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/api-management/api-management-faq.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ sections:
3636
answer: |
3737
You have several options to secure the connection between the API Management gateway and your backend services, including:
3838
39-
* Use subscription key authentication. For more information, see [Import and publish your first API](import-and-publish.md).
39+
* Use subscription key authentication. On its own, a subscription key isn't a strong form of authentication, but is often used along with another method. For more information, see [Authentication and authorization in API Management](authentication-authorization-overview.md).
4040
* Use TLS mutual authentication as described in [How to secure back-end services by using client certificate authentication in Azure API Management](api-management-howto-mutual-certificates.md).
4141
* Use IP filtering on your back-end service. In all tiers of API Management except the Consumption tier, the IP address of the gateway remains constant. For more information, see [IP addresses of Azure API Management](api-management-howto-ip-addresses.md).
4242
* Connect your API Management instance to an [Azure virtual network](virtual-network-concepts.md).

0 commit comments

Comments
 (0)