Skip to content

Commit 0aab81f

Browse files
committed
Stuff
1 parent 043d18e commit 0aab81f

File tree

3 files changed

+18
-28
lines changed

3 files changed

+18
-28
lines changed

articles/storage/blobs/TOC.yml

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -303,14 +303,14 @@ items:
303303
items:
304304
- name: Network security overview
305305
href: ../common/storage-network-security-overview.md?toc=/azure/storage/blobs/toc.json&bc=/azure/storage/blobs/breadcrumb/toc.json
306-
- name: Manage public access
306+
- name: Public access
307307
items:
308+
- name: Default access level
309+
href: ../common/storage-network-security-set-default-access.md?toc=/azure/storage/blobs/toc.json&bc=/azure/storage/blobs/breadcrumb/toc.json
308310
- name: Firewalls and virtual networks
309311
items:
310312
- name: Configuration tasks
311313
href: ../common/storage-network-security.md?toc=/azure/storage/blobs/toc.json&bc=/azure/storage/blobs/breadcrumb/toc.json
312-
- name: Default access level
313-
href: ../common/storage-network-security-set-default-access.md?toc=/azure/storage/blobs/toc.json&bc=/azure/storage/blobs/breadcrumb/toc.json
314314
- name: Virtual networks
315315
href: ../common/storage-network-security-virtual-networks.md?toc=/azure/storage/blobs/toc.json&bc=/azure/storage/blobs/breadcrumb/toc.json
316316
- name: IP address ranges
@@ -321,11 +321,11 @@ items:
321321
href: ../common/storage-network-security-manage-exceptions.md?toc=/azure/storage/blobs/toc.json&bc=/azure/storage/blobs/breadcrumb/toc.json
322322
- name: Network security perimeter
323323
href: ../common/storage-network-security-perimeter.md?toc=/azure/storage/blobs/toc.json&bc=/azure/storage/blobs/breadcrumb/toc.json
324-
- name: Use private endpoints
324+
- name: Private endpoints
325325
href: ../common/storage-private-endpoints.md?toc=/azure/storage/blobs/toc.json&bc=/azure/storage/blobs/breadcrumb/toc.json
326-
- name: Restrict copy operations
326+
- name: Copy operation restrictions
327327
href: ../common/security-restrict-copy-operations.md?toc=/azure/storage/blobs/toc.json
328-
- name: Manage secure transfer
328+
- name: Secure transfer
329329
items:
330330
- name: Require secure transfer
331331
href: ../common/storage-require-secure-transfer.md?toc=/azure/storage/blobs/toc.json&bc=/azure/storage/blobs/breadcrumb/toc.json
@@ -335,12 +335,12 @@ items:
335335
href: ../common/transport-layer-security-configure-client-version.md?toc=/azure/storage/blobs/toc.json&bc=/azure/storage/blobs/breadcrumb/toc.json
336336
- name: Migrate to TLS 1.2
337337
href: ../common/transport-layer-security-configure-migrate-to-TLS2.md?toc=/azure/storage/blobs/toc.json&bc=/azure/storage/blobs/breadcrumb/toc.json
338-
- name: Manage network routing
338+
- name: Network routing
339339
href: ../common/network-routing-preference.md?toc=/azure/storage/blobs/toc.json&bc=/azure/storage/blobs/breadcrumb/toc.json
340340
items:
341341
- name: Configure network routing preference
342342
href: ../common/configure-network-routing-preference.md?toc=/azure/storage/blobs/toc.json
343-
- name: Use a custom domain
343+
- name: Custom domains
344344
href: storage-custom-domain-name.md
345345
- name: Authorization
346346
items:

articles/storage/common/storage-network-security-virtual-networks.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,8 @@ ms.author: normesta
1515

1616
You can deny all public access to your storage account, and then configure Azure network settings to accept requests that originate from specific virtual network subnets. To learn more, see [Permit access to virtual network subnets](storage-network-security.md#grant-access-from-a-virtual-network).
1717

18+
To apply a virtual network rule to a storage account, the user must have the appropriate permissions for the subnets that are being added. A [Storage Account Contributor](../../role-based-access-control/built-in-roles.md#storage-account-contributor) or a user who has permission to the `Microsoft.Network/virtualNetworks/subnets/joinViaServiceEndpoint/action` [Azure resource provider operation](../../role-based-access-control/resource-provider-operations.md#microsoftnetwork) can apply a rule by using a custom Azure role.
19+
1820
## [Portal](#tab/azure-portal)
1921

2022
> [!NOTE]

articles/storage/common/storage-network-security.md

Lines changed: 8 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -11,21 +11,15 @@ ms.author: normesta
1111

1212
---
1313

14-
# Manage public access configuration of a storage account
14+
# Configure Azure Storage firewalls and virtual networks
1515

16-
Put something here.
17-
18-
<a id="change-the-default-network-access-rule"></a>
19-
20-
## Changing the default network rule
21-
22-
Put something here.
16+
When you disable public network access to your storage account, all incoming requests for data are blocked by default. Traffic is permitted only if it originates from sources that you specify in the firewall settings of the storage account. Sources can include virtual network subnets, IP address ranges, specific resource instances, or trusted Azure services.
2317

2418
<a id="grant-access-from-a-virtual-network"></a>
2519

26-
## Grant access from a virtual network
20+
## Allowing traffic from virtual networks
2721

28-
You can configure storage accounts to allow access only from specific subnets. The allowed subnets can belong to a virtual network in the same subscription or a different subscription, including those that belong to a different Microsoft Entra tenant. With [cross-region service endpoints](#azure-storage-cross-region-service-endpoints), the allowed subnets can also be in different regions from the storage account.
22+
Virtual network service endpoints are public and accessible via the internet. You can configure storage accounts to allow access only from specific subnets in a virtual network. Virtual networks can be in the same subscription or a different subscription, including those that belong to a different Microsoft Entra tenant. With [cross-region service endpoints](#azure-storage-cross-region-service-endpoints), the allowed subnets can also be in different regions from the storage account.
2923

3024
You can enable a [service endpoint](../../virtual-network/virtual-network-service-endpoints-overview.md) for Azure Storage within the virtual network. The service endpoint routes traffic from the virtual network through an optimal path to the Azure Storage service. The identities of the subnet and the virtual network are also transmitted with each request. Administrators can then configure network rules for the storage account that allow requests to be received from specific subnets in a virtual network. Clients granted access via these network rules must continue to meet the authorization requirements of the storage account to access the data.
3125

@@ -36,19 +30,13 @@ Each storage account supports up to 400 virtual network rules. You can combine t
3630
>
3731
> Additionally, it's recommended that you honor the time-to-live (TTL) of the DNS record and avoid overriding it. Overriding the DNS TTL may result in unexpected behavior.
3832
39-
### Required permissions
40-
41-
To apply a virtual network rule to a storage account, the user must have the appropriate permissions for the subnets that are being added. A [Storage Account Contributor](../../role-based-access-control/built-in-roles.md#storage-account-contributor) or a user who has permission to the `Microsoft.Network/virtualNetworks/subnets/joinViaServiceEndpoint/action` [Azure resource provider operation](../../role-based-access-control/resource-provider-operations.md#microsoftnetwork) can apply a rule by using a custom Azure role.
42-
4333
The storage account and the virtual networks that get access can be in different subscriptions, including subscriptions that are a part of a different Microsoft Entra tenant.
4434

45-
Configuration of rules that grant access to subnets in virtual networks that are a part of a different Microsoft Entra tenant are currently supported only through PowerShell, the Azure CLI, and REST APIs. You can't configure such rules through the Azure portal, though you can view them in the portal.
46-
4735
<a id="azure-storage-cross-region-service-endpoints"></a>
4836

4937
### Azure Storage cross-region service endpoints
5038

51-
Cross-region service endpoints for Azure Storage became generally available in April 2023. They work between virtual networks and storage service instances in any region. With cross-region service endpoints, subnets no longer use a public IP address to communicate with any storage account, including those in another region. Instead, all the traffic from subnets to storage accounts uses a private IP address as a source IP. As a result, any storage accounts that use IP network rules to permit traffic from those subnets no longer have an effect.
39+
Cross-region service endpoints work between virtual networks and storage service instances in any region. With cross-region service endpoints, subnets no longer use a public IP address to communicate with any storage account, including those in another region. Instead, all the traffic from subnets to storage accounts uses a private IP address as a source IP. As a result, any storage accounts that use IP network rules to permit traffic from those subnets no longer have an effect.
5240

5341
Configuring service endpoints between virtual networks and service instances in a [paired region](../../best-practices-availability-paired-regions.md) can be an important part of your disaster recovery plan. Service endpoints allow continuity during a regional failover and access to read-only geo-redundant storage (RA-GRS) instances. Network rules that grant access from a virtual network to a storage account also grant access to any RA-GRS instance.
5442

@@ -59,7 +47,7 @@ Local and cross-region service endpoints can't coexist on the same subnet. To re
5947
<a id="grant-access-from-an-internet-ip-range"></a>
6048
<a id="managing-ip-network-rules"></a>
6149

62-
## Grant access from an internet IP range
50+
## Allowing traffic from IP address ranges
6351

6452
You can use IP network rules to allow access from specific public internet IP address ranges by creating IP network rules. Each storage account supports up to 400 rules. These rules grant access to specific internet-based services and on-premises networks and block general internet traffic.
6553

@@ -96,7 +84,7 @@ To allow access to your service resources, you must allow these public IP addres
9684

9785
<a id="grant-access-from-azure-resource-instances"></a>
9886

99-
## Grant access from Azure resource instances
87+
## Allow traffic from Azure resource instances
10088

10189
In some cases, an application might depend on Azure resources that can't be isolated through a virtual network or an IP address rule. But you still want to secure and restrict storage account access to only your application's Azure resources. You can configure storage accounts to allow access to specific resource instances of trusted Azure services by creating a resource instance rule.
10290

@@ -107,7 +95,7 @@ The Azure role assignments of the resource instance determine the types of opera
10795
<a id="trusted-microsoft-services"></a>
10896
<a id="exceptions"></a>
10997

110-
## Grant access to trusted Azure services
98+
## Allowing traffic from trusted Azure services
11199

112100
Some Azure services operate from networks that you can't include in your network rules. You can grant a subset of such trusted Azure services access to the storage account, while maintaining network rules for other apps. These trusted services will then use strong authentication to connect to your storage account.
113101

0 commit comments

Comments
 (0)