Skip to content

Commit eb0cc15

Browse files
authored
Merge pull request #94340 from santoshc1/master
Clarification on trusted services access.
2 parents fc9fe46 + 305ca99 commit eb0cc15

File tree

1 file changed

+11
-11
lines changed

1 file changed

+11
-11
lines changed

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

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -258,7 +258,7 @@ Each storage account supports up to 100 IP network rules.
258258
259259
To grant access from your on-premises networks to your storage account with an IP network rule, you must identify the internet facing IP addresses used by your network. Contact your network administrator for help.
260260
261-
If you are using [ExpressRoute](/azure/expressroute/expressroute-introduction) from your premises, for public peering or Microsoft peering, you will need to identify the NAT IP addresses that are used. For public peering, each ExpressRoute circuit by default uses two NAT IP addresses applied to Azure service traffic when the traffic enters the Microsoft Azure network backbone. For Microsoft peering, the NAT IP address(es) that are used are either customer provided or are provided by the service provider. To allow access to your service resources, you must allow these public IP addresses in the resource IP firewall setting. To find your public peering ExpressRoute circuit IP addresses, [open a support ticket with ExpressRoute](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/overview) via the Azure portal. Learn more about [NAT for ExpressRoute public and Microsoft peering.](/azure/expressroute/expressroute-nat#nat-requirements-for-azure-public-peering)
261+
If you are using [ExpressRoute](/azure/expressroute/expressroute-introduction) from your premises, for public peering or Microsoft peering, you will need to identify the NAT IP addresses that are used. For public peering, each ExpressRoute circuit by default uses two NAT IP addresses applied to Azure service traffic when the traffic enters the Microsoft Azure network backbone. For Microsoft peering, the NAT IP addresses used are either customer provided or are provided by the service provider. To allow access to your service resources, you must allow these public IP addresses in the resource IP firewall setting. To find your public peering ExpressRoute circuit IP addresses, [open a support ticket with ExpressRoute](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/overview) via the Azure portal. Learn more about [NAT for ExpressRoute public and Microsoft peering.](/azure/expressroute/expressroute-nat#nat-requirements-for-azure-public-peering)
262262
263263
### Managing IP network rules
264264
@@ -360,11 +360,11 @@ Network rules help to create a secure environment for connections between your a
360360
361361
Some Microsoft services operate from networks that can't be included in your network rules. You can grant a subset of such trusted Microsoft services access to the storage account, while maintaining network rules for other apps. These trusted services can then use strong authentication to connect to your storage account securely. We enable two types of trusted access for Microsoft services.
362362
363-
- Resources of some services, if registered in your subscription, can access storage accounts in the same subscription for only select operations, such as writing logs or for backup.
364-
- A particular instance of some services can be explicitly granted access by [assigning an RBAC role](storage-auth-aad.md#assign-rbac-roles-for-access-rights) to the resource instance.
363+
- Resources of some services, **if registered in your subscription**, can access storage accounts **in the same subscription** for only select operations, such as writing logs or for backup.
364+
- Resource instances of some services can be granted explicit access to your storage account by [**assigning an RBAC role**](storage-auth-aad.md#assign-rbac-roles-for-access-rights) to the resource instance.
365365
366366
367-
When you enable the **Allow trusted Microsoft services...** exception, the following services (if registered in your subscription) are granted access to the storage account for select operations as described:
367+
When you enable the **Allow trusted Microsoft services...** exception, these services (if registered in your subscription) are granted access to the storage account for select operations as described:
368368
369369
| Service | Resource Provider Name | Purpose |
370370
|:------------------------ |:-------------------------- |:---------------------------------- |
@@ -379,15 +379,15 @@ When you enable the **Allow trusted Microsoft services...** exception, the follo
379379
| Azure Networking | Microsoft.Network | Store and analyze network traffic logs. [Learn more](/azure/network-watcher/network-watcher-packet-capture-overview). |
380380
| Azure Site Recovery | Microsoft.SiteRecovery | Enable replication for disaster-recovery of Azure IaaS virtual machines when using firewall-enabled cache, source, or target storage accounts. [Learn more](https://docs.microsoft.com/azure/site-recovery/azure-to-azure-tutorial-enable-replication). |
381381
382-
The **Allow trusted Microsoft services...** exception enables the particular instance of the below services to access the storage account, if you explicitly assign an RBAC role to the [system-assigned managed identity](../../active-directory/managed-identities-azure-resources/overview.md) for that resource instance.
382+
The **Allow trusted Microsoft services...** exception enables a particular instance of the below services to access the storage account, if you explicitly assign an RBAC role to the [system-assigned managed identity](../../active-directory/managed-identities-azure-resources/overview.md) for that resource instance.
383383
384-
| Service | Resource Provider Name | Purpose |
385-
| :----------------------- | :------------------------------ | :--------------------------------- |
386-
| Azure Data Factory | Microsoft.DataFactory/factories | Allows access to storage accounts through the ADF runtime. |
387-
| Azure Logic Apps | Microsoft.Logic/workflows | Enables logic apps to access storage accounts. |
384+
| Service | Resource Provider Name | Purpose |
385+
| :----------------------------- | :------------------------------ | :--------------------------------- |
386+
| Azure Data Factory | Microsoft.DataFactory/factories | Allows access to storage accounts through the ADF runtime. |
387+
| Azure Logic Apps | Microsoft.Logic/workflows | Enables logic apps to access storage accounts. |
388388
| Azure Machine Learning Service | Microsoft.MachineLearningServices | Authorized Azure Machine Learning workspaces write experiment output, models, and logs to Blob storage. [Learn more](/azure/machine-learning/service/how-to-enable-virtual-network#use-a-storage-account-for-your-workspace). |
389-
| Azure SQL Data Warehouse | Microsoft.Sql | Allows import and export of data from specific SQL Database instances using PolyBase. [Learn more](/azure/sql-database/sql-database-vnet-service-endpoint-rule-overview). |
390-
| Azure Stream Analytics | Microsoft.StreamAnalytics | Allows data from a streaming job to be written to Blob storage. This feature is currently in preview. [Learn more](../../stream-analytics/blob-output-managed-identity.md). |
389+
| Azure SQL Data Warehouse | Microsoft.Sql | Allows import and export of data from specific SQL Database instances using PolyBase. [Learn more](/azure/sql-database/sql-database-vnet-service-endpoint-rule-overview). |
390+
| Azure Stream Analytics | Microsoft.StreamAnalytics | Allows data from a streaming job to be written to Blob storage. This feature is currently in preview. [Learn more](../../stream-analytics/blob-output-managed-identity.md). |
391391
392392
393393
### Storage analytics data access

0 commit comments

Comments
 (0)