Merge pull request #114988 from tamram/tamram-build-routing

storage routing prefs preview

Author: SyntaxC4

articles/storage/blobs/TOC.yml

@@ -150,6 +150,8 @@
         href: ../common/storage-security-controls.md?toc=%2fazure%2fstorage%2fblobs%2ftoc.json
       - name: Use Azure Private Endpoints
         href: ../common/storage-private-endpoints.md?toc=%2fazure%2fstorage%2fblobs%2ftoc.json
+      - name: Configure network routing preference
+        href: ../common/network-routing-preference.md?toc=%2fazure%2fstorage%2fblobs%2ftoc.json        
     - name: Data redundancy
       href: ../common/storage-redundancy.md?toc=%2fazure%2fstorage%2fblobs%2ftoc.json
     - name: Data protection

articles/storage/common/media/network-routing-preference/routing-options-diagram.png

@@ -0,0 +1,80 @@
+---
+title: Configure network routing preference (preview)
+titleSuffix: Azure Storage
+description: Configure network routing preference (preview) for your Azure storage account to specify how network traffic is routed to your account from clients over the Internet.
+services: storage
+author: santoshc
+
+ms.service: storage
+ms.topic: article
+ms.date: 05/12/2020
+ms.author: santoshc
+ms.reviewer: tamram
+ms.subservice: common
+---
+
+# Configure network routing preference for Azure Storage (preview)
+
+You can configure network [routing preference](../../virtual-network/routing-preference-overview.md) (preview) for your Azure storage account to specify how network traffic is routed to your account from clients over the Internet. By default, traffic from the Internet is routed to the public endpoint of your storage account over the [Microsoft global network](../../networking/microsoft-global-network.md). Azure Storage provides additional options for configuring how traffic is routed to your storage account.
+
+Configuring routing preference gives you the flexibility to optimize your traffic either for premium network performance or for cost. When you configure a routing preference, you specify how traffic will be directed to the public endpoint for your storage account by default. You can also publish route-specific endpoints for your storage account.
+
+## Microsoft global network versus Internet routing
+
+By default, clients outside of the Azure environment access your storage account over the Microsoft global network. The Microsoft global network is optimized for low-latency path selection to deliver premium network performance with high reliability. Both inbound and outbound traffic are routed through the point of presence (POP) that is closest to the client. This default routing configuration ensures that traffic to and from your storage account traverses over the Microsoft global network for the bulk of its path, maximizing network performance.
+
+You can change the routing configuration for your storage account so that both inbound and outbound traffic are routed to and from clients outside of the Azure environment through the POP closest to the storage account. This route minimizes the traversal of your traffic over the Microsoft global network, handing it off to the transit ISP at the earliest opportunity. Utilizing this routing configuration lowers networking costs.
+
+The following diagram shows how traffic flows between the client and the storage account for each routing preference:
+
+![Overview of routing options for Azure Storage](media/network-routing-preference/routing-options-diagram.png)
+
+For more information on routing preference in Azure, see [What is routing preference (preview)?](../../virtual-network/routing-preference-overview.md).
+
+## Routing configuration
+
+You can choose between the Microsoft global network and Internet routing as the default routing preference for the public endpoint of your storage account. The default routing preference applies to all traffic from clients outside Azure and affects the endpoints for Azure Data Lake Storage Gen2, Blob storage, Azure Files, and static websites. Configuring routing preference is not supported for Azure Queues or Azure Tables.
+
+You can also publish route-specific endpoints for your storage account. When you publish route-specific endpoints, Azure Storage creates new public endpoints for your storage account that route traffic over the desired path. This flexibility enables you to direct traffic to your storage account over a specific route without changing your default routing preference.
+
+For example, publishing an Internet route-specific endpoint for the 'StorageAccountA' will publish the following endpoints for your storage account:
+
+| Storage service        | Route-specific endpoint                                  |
+| :--------------------- | :------------------------------------------------------- |
+| Blob service           | `StorageAccountA-internetrouting.blob.core.windows.net`  |
+| Data Lake Storage Gen2 | `StorageAccountA-internetrouting.dfs.core.windows.net`   |
+| File service           | `StorageAccountA-internetrouting.file.core.windows.net`  |
+| Static Websites        | `StorageAccountA-internetrouting.web.core.windows.net`   |
+
+If you have a read-access geo-redundant storage (RA-GRS) or a read-access geo-zone-redundant storage (RA-GZRS) storage account, publishing route-specific endpoints also automatically creates the corresponding endpoints in the secondary region for read access.
+
+| Storage service        | Route-specific read-only secondary endpoint                        |
+| :--------------------- | :----------------------------------------------------------------- |
+| Blob service           | `StorageAccountA-internetrouting-secondary.blob.core.windows.net`  |
+| Data Lake Storage Gen2 | `StorageAccountA-internetrouting-secondary.dfs.core.windows.net`   |
+| File service           | `StorageAccountA-internetrouting-secondary.file.core.windows.net`  |
+| Static Websites        | `StorageAccountA-internetrouting-secondary.web.core.windows.net`   |
+
+The connection strings for the published route-specific endpoints can be copied via the [Azure portal](https://portal.azure.com). These connection strings can be used for Shared Key authorization with all existing Azure Storage SDKs and APIs.
+
+## About the preview
+
+Routing preference for Azure Storage is available in the following regions:
+
+- France South
+- North Central US
+- West Central US
+
+The following known issues affect the routing preference preview for Azure Storage:
+
+- Access requests for the route-specific endpoint for the Microsoft global network fail with HTTP error 404 or equivalent. Routing over the Microsoft global network works as expected when it is set as the default routing preference for the public endpoint.
+
+## Pricing and billing
+
+For pricing and billing details, see the **Pricing** section in [What is routing preference (preview)?](../../virtual-network/routing-preference-overview.md#pricing).
+
+## Next steps
+
+- [What is routing preference (preview)?](../../virtual-network/routing-preference-overview.md)
+- [Configure Azure Storage firewalls and virtual networks](storage-network-security.md)
+- [Security recommendations for Blob storage](../blobs/security-recommendations.md)

articles/storage/common/network-routing-preference.md

@@ -48,6 +48,8 @@
     items:
     - name: Customer-managed keys with Azure Key Vault
       href: ../common/encryption-customer-managed-keys.md?toc=%2fazure%2fstorage%2ffiles%2ftoc.json
+  - name: Configure network routing preference
+    href: ../common/network-routing-preference.md?toc=%2fazure%2fstorage%2ffiles%2ftoc.json      
   - name: Compliance offerings
     href: ../common/storage-compliance-offerings.md?toc=%2fazure%2fstorage%2ffiles%2ftoc.json
   - name: Development