Cognitive Services should use private link
Azure Private Link lets you connect your virtual networks to Azure services without a public IP address at the source or destination. By mapping private endpoints to Cognitive Services, you'll reduce the potential for data leakage.
The Private Link platform reduces data leakage risks by handling the connectivity between the consumer and services over the Azure backbone network. Without an approved private endpoint, clients reach the account over its public endpoint.
What this control checks
Cognitive Services accounts must have an Approved private endpoint connection (private link used).
Common pitfalls
Only Approved connections carry traffic
Only connections in the Approved state carry traffic; Pending and Rejected connections do not.
Audit evidence
Evidence that deployed resources meet this control: Azure Policy compliance results for the built-in policy definition "Azure AI Services resources should use Azure Private Link" (d6759c02-b87f-42b7-892e-71b3f471d782); Prowler check aiservices_account_uses_private_endpoint (prowler azure --checks aiservices_account_uses_private_endpoint); PowerPipe control azure_compliance.control.cognitive_account_private_link_used.
Framework-specific interpretation
NIST SP 800-53 Rev 5: Mapped to AC-17 (Remote Access), AC-17(1) (Monitoring and Control), AC-4 (Information Flow Enforcement) and 2 more clauses.
Framework mappings
The clauses this control is mapped to in each framework.
- AC-17 Remote Access
- AC-17(1) Monitoring And Control
- Information Flow Enforcement (AC-4)
- SC-7: Boundary Protection
- SC-7(3) Access Points
- 3.1.1 Limit system access to authorized users, processes acting on behalf of authorized users, and devices (including other systems)
- 3.1.3 Control the flow of CUI in accordance with approved authorizations
- 3.1.12: Monitor and control remote access sessions.
- 3.1.13 Employ cryptographic mechanisms to protect the confidentiality of remote access sessions
- 3.1.14 Route remote access via managed access control points
3 more clauses
- 3.13.1: Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems.
- 3.13.2 Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems
- 3.13.5 Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks
- 2.2.2.1 Ensure Private Endpoints are used to access {service}
- AC-4 Information Flow Enforcement
- AC-17 Remote Access
- AC-17(1) Automated Monitoring / Control
- SC-7 Boundary Protection
- SC-7(3) Access Points
Related controls
Tool mappings
Use these identifiers to cross-reference this control across tools, reports, and evidence.
- Compliance.tf Control:
cognitive_account_private_link_used - Powerpipe Control:
azure_compliance.control.cognitive_account_private_link_used - Prowler Check:
aiservices_account_uses_private_endpoint - Azure Policy Definition:
d6759c02-b87f-42b7-892e-71b3f471d782
Last reviewed: 2026-10-11