# Ensure Private Endpoints are used to access Storage Accounts

- Source: https://support.icompaas.com/support/solutions/articles/62000229806-ensure-private-endpoints-are-used-to-access-storage-accounts
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [General](https://support.icompaas.com/support/solutions/62000037933) › [Azure Compliance / Control / Check](https://support.icompaas.com/support/solutions/folders/62000168797)
- Last updated: 2026-05-29
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

Description:

This control ensures that Azure Storage Accounts are accessed through Private Endpoints, which provide private IP addresses within a virtual network (VNet). Private Endpoints enable secure, private connectivity between Azure Storage and trusted networks, reducing exposure to the public internet.

  

Rationale:

-   Enhances security by limiting storage access to private networks
    
-   Reduces risk of unauthorized access or data interception
    
-   Supports compliance requirements for network isolation of sensitive data
    

  

Impact:

-   Reduces the attack surface of Azure Storage Accounts
    
-   Improves overall security posture and data confidentiality
    

  

Default Value:

-   By default, Azure Storage Accounts allow public network access and do not require Private Endpoints.
    

  

Pre-requirements:

-   An existing Azure Storage Account
    
-   Permissions: Owner, Contributor, or Storage Account Contributor
    
-   Network permissions to create resources in the target VNet
    

  

Test Plan:

1.  Sign in to the Microsoft Azure Portal:[https://portal.azure.com](https://portal.azure.com/)
    
2.  Navigate to Storage Accounts
    
3.  Select the target storage account
    
4.  Under Security + networking, select Networking
    
5.  Verify that at least one Private Endpoint is configured for the storage account
    
6.  If no Private Endpoint is configured, follow the implementation steps.
    

![](https://support.icompaas.com/assets/kb/f0041fcbb5893bfc.png)

Implementation Steps:

1.  Sign in to the Microsoft Azure Portal:[https://portal.azure.com](https://portal.azure.com/)
    
2.  Navigate to Storage Accounts
    
3.  Select the target storage account
    
4.  Under Security + networking, select Networking
    

                           ![](https://support.icompaas.com/assets/kb/9ab3db27974aee5c.png)

5.  Select Private endpoint
    
6.  Click + Private endpoint
    

![](https://support.icompaas.com/assets/kb/570a9562e7edb219.png)

7.  Select the appropriate Resource Group, Virtual Network, and Subnet
    
8.  Select the required storage service (for example, Blob)
    
9.  Review the configuration and click Create
    

![](https://support.icompaas.com/assets/kb/f2efc91024ead23f.png)

  

Backout Plan:

1.  Sign in to the Microsoft Azure Portal
    
2.  Navigate to Storage Accounts
    
3.  Select the target storage account
    
4.  Under Security + networking, select Networking
    
5.  Select Private endpoint connections
    
6.  Identify the configured Private Endpoint
    
7.  Delete the Private Endpoint
    
8.  Confirm changes are saved
    

Reference:

-   [https://learn.microsoft.com/en-us/azure/private-link/tutorial-private-endpoint-storage-portal?tabs=dynamic-ip](https://learn.microsoft.com/en-us/azure/private-link/tutorial-private-endpoint-storage-portal?tabs=dynamic-ip)

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.
