You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/security/fundamentals/network-overview.md
+7-1Lines changed: 7 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,6 +35,9 @@ This article covers some of the options that Azure offers in the area of network
35
35
* Traffic manager
36
36
* Monitoring and threat detection
37
37
38
+
> [!NOTE]
39
+
> For web workloads, we highly recommend utilizing [**Azure DDoS protection**](../../ddos-protection/ddos-protection-overview.md) and a [**web application firewall**](../../web-application-firewall/overview.md) to safeguard against emerging DDoS attacks. Another option is to deploy [**Azure Front Door**](../../frontdoor/web-application-firewall.md) along with a web application firewall. Azure Front Door offers platform-level [**protection against network-level DDoS attacks**](../../frontdoor/front-door-ddos.md).
40
+
38
41
## Azure networking
39
42
40
43
Azure requires virtual machines to be connected to an Azure Virtual Network. A virtual network is a logical construct built on top of the physical Azure network fabric. Each virtual network is isolated from all other virtual networks. This helps ensure that network traffic in your deployments is not accessible to other Azure customers.
@@ -129,7 +132,7 @@ You can access these enhanced network security features by using an Azure partne
129
132
130
133
Azure Firewall is a cloud-native and intelligent network firewall security service that provides threat protection for your cloud workloads running in Azure. It's a fully stateful firewall as a service with built-in high availability and unrestricted cloud scalability. It provides both east-west and north-south traffic inspection.
131
134
132
-
Azure Firewall is offered in two SKUs: Standardand Premium. [Azure Firewall Standard](../../firewall/features.md) provides L3-L7 filtering and threat intelligence feeds directly from Microsoft Cyber Security. [Azure Firewall Premium](../../firewall/premium-features.md) provides advanced capabilities include signature-based IDPS to allow rapid detection of attacks by looking for specific patterns.
135
+
Azure Firewall is offered in three SKUs: Standard, Premium, and Basic. [Azure Firewall Standard](../../firewall/features.md) provides L3-L7 filtering and threat intelligence feeds directly from Microsoft Cyber Security. [Azure Firewall Premium](../../firewall/premium-features.md) provides advanced capabilities include signature-based IDPS to allow rapid detection of attacks by looking for specific patterns. [Azure Firewall Basic](../../firewall/basic-features.md) is a simplified SKU that provides the same level of security as the Standard SKU but without the advanced capabilities.
133
136
134
137
Learn more:
135
138
@@ -332,6 +335,9 @@ Azure Front Door Service enables you to define, manage, and monitor the global r
332
335
333
336
Front Door platform itself is protected by an Azure infrastructure-level DDoS protection. For further protection, Azure DDoS Network Protection may be enabled at your VNETs and safeguard resources from network layer (TCP/UDP) attacks via auto tuning and mitigation. Front Door is a layer 7 reverse proxy, it only allows web traffic to pass through to back end servers and block other types of traffic by default.
334
337
338
+
> [!NOTE]
339
+
> For web workloads, we highly recommend utilizing [**Azure DDoS protection**](../../ddos-protection/ddos-protection-overview.md) and a [**web application firewall**](../../web-application-firewall/overview.md) to safeguard against emerging DDoS attacks. Another option is to deploy [**Azure Front Door**](../../frontdoor/web-application-firewall.md) along with a web application firewall. Azure Front Door offers platform-level [**protection against network-level DDoS attacks**](../../frontdoor/front-door-ddos.md).
340
+
335
341
Learn more:
336
342
337
343
* For more information on the whole set of Azure Front door capabilities you can review the [Azure Front Door overview](../../frontdoor/front-door-overview.md)
@@ -542,30 +542,53 @@ Resources of some services that are registered in your subscription can access y
542
542
543
543
The following table lists services that can access your storage account data if the resource instances of those services have the appropriate permission.
| Azure Container Registry |`Microsoft.ContainerRegistry/registries`| Through the ACR Tasks suite of features, enables access to storage accounts when you're building container images. |
552
-
| Azure Data Factory |`Microsoft.DataFactory/factories`| Enables access to storage accounts through the Data Factory runtime. |
553
-
| Azure Data Share |`Microsoft.DataShare/accounts`| Enables access to storage accounts. |
| Azure IoT Central |`Microsoft.IoTCentral/IoTApps`| Enables access to storage accounts. |
558
-
| Azure IoT Hub |`Microsoft.Devices/IotHubs`| Allows data from an IoT hub to be written to Blob Storage. [Learn more](../../iot-hub/virtual-network-support.md#egress-connectivity-from-iot-hub-to-other-azure-resources). |
| Azure Machine Learning |`Microsoft.MachineLearningServices`| Enables authorized Azure Machine Learning workspaces to write experiment output, models, and logs to Blob Storage and read the data. [Learn more](../../machine-learning/how-to-network-security-overview.md#secure-the-workspace-and-associated-resources). |
561
-
| Azure Media Services |`Microsoft.Media/mediaservices`| Enables access to storage accounts. |
562
-
| Azure Migrate |`Microsoft.Migrate/migrateprojects`| Enables access to storage accounts. |
563
-
| Microsoft Purview |`Microsoft.Purview/accounts`| Enables access to storage accounts. |
564
-
| Azure Site Recovery |`Microsoft.RecoveryServices/vaults`| Enables access to storage accounts. |
565
-
| Azure SQL Database |`Microsoft.Sql`| Allows [writing audit data to storage accounts behind a firewall](/azure/azure-sql/database/audit-write-storage-account-behind-vnet-firewall). |
566
-
| Azure Synapse Analytics |`Microsoft.Sql`| Allows import and export of data from specific SQL databases via the `COPY` statement or PolyBase (in a dedicated pool), or the `openrowset` function and external tables in a serverless pool. [Learn more](/azure/azure-sql/database/vnet-service-endpoint-rule-overview). |
567
-
| Azure Stream Analytics |`Microsoft.StreamAnalytics`| Allows data from a streaming job to be written to Blob Storage. [Learn more](../../stream-analytics/blob-output-managed-identity.md). |
568
-
| Azure Synapse Analytics |`Microsoft.Synapse/workspaces`| Enables access to data in Azure Storage. |
551
+
| Azure Cognitive Search |`Microsoft.Search/searchServices`| Enables access to storage accounts for indexing, processing, and querying. |
| Azure Container Registry |`Microsoft.ContainerRegistry/registries`| Through the ACR Tasks suite of features, enables access to storage accounts when you're building container images. |
554
+
| Azure Databricks |`Microsoft.Databricks/accessConnectors`| Enables access to storage accounts. |
555
+
| Azure Data Factory |`Microsoft.DataFactory/factories`| Enables access to storage accounts through the Data Factory runtime. |
| Azure Data Share |`Microsoft.DataShare/accounts`| Enables access to storage accounts. |
558
+
| Azure Database for PostgreSQL |`Microsoft.DBForPostgreSQL`| Enables access to storage accounts. |
559
+
| Azure IoT Hub |`Microsoft.Devices/IotHubs`| Allows data from an IoT hub to be written to Blob Storage. [Learn more](../../iot-hub/virtual-network-support.md#egress-connectivity-from-iot-hub-to-other-azure-resources). |
| Azure Machine Learning Studio |`Microsoft.MachineLearning/registries`| Enables authorized Azure Machine Learning workspaces to write experiment output, models, and logs to Blob Storage and read the data. [Learn more](../../machine-learning/how-to-network-security-overview.md#secure-the-workspace-and-associated-resources). |
572
+
| Azure Machine Learning |`Microsoft.MachineLearningServices`| Enables authorized Azure Machine Learning workspaces to write experiment output, models, and logs to Blob Storage and read the data. [Learn more](../../machine-learning/how-to-network-security-overview.md#secure-the-workspace-and-associated-resources). |
573
+
| Azure Machine Learning |`Microsoft.MachineLearningServices/workspaces`| Enables authorized Azure Machine Learning workspaces to write experiment output, models, and logs to Blob Storage and read the data. [Learn more](../../machine-learning/how-to-network-security-overview.md#secure-the-workspace-and-associated-resources). |
574
+
| Azure Media Services |`Microsoft.Media/mediaservices`| Enables access to storage accounts. |
575
+
| Azure Migrate |`Microsoft.Migrate/migrateprojects`| Enables access to storage accounts. |
| Azure ExpressRoute |`Microsoft.Network/expressRoutePorts`| Enables access to storage accounts. |
578
+
| Microsoft Power Platform |`Microsoft.PowerPlatform/enterprisePolicies`| Enables access to storage accounts. |
579
+
| Microsoft Project Arcadia |`Microsoft.ProjectArcadia/workspaces`| Enables access to storage accounts. |
580
+
| Azure Data Catalog |`Microsoft.ProjectBabylon/accounts`| Enables access to storage accounts. |
581
+
| Microsoft Purview |`Microsoft.Purview/accounts`| Enables access to storage accounts. |
582
+
| Azure Site Recovery |`Microsoft.RecoveryServices/vaults`| Enables access to storage accounts. |
583
+
| Security Center |`Microsoft.Security/dataScanners`| Enables access to storage accounts. |
584
+
| Singularity |`Microsoft.Singularity/accounts`| Enables access to storage accounts. |
585
+
| Azure SQL Database |`Microsoft.Sql`| Allows [writing audit data to storage accounts behind a firewall](/azure/azure-sql/database/audit-write-storage-account-behind-vnet-firewall). |
586
+
| Azure SQL Servers |`Microsoft.Sql/servers`| Allows [writing audit data to storage accounts behind a firewall](/azure/azure-sql/database/audit-write-storage-account-behind-vnet-firewall). |
587
+
| Azure Synapse Analytics |`Microsoft.Sql`| Allows import and export of data from specific SQL databases via the `COPY` statement or PolyBase (in a dedicated pool), or the `openrowset` function and external tables in a serverless pool. [Learn more](/azure/azure-sql/database/vnet-service-endpoint-rule-overview). |
588
+
| Azure Stream Analytics |`Microsoft.StreamAnalytics`| Allows data from a streaming job to be written to Blob Storage. [Learn more](../../stream-analytics/blob-output-managed-identity.md). |
589
+
| Azure Stream Analytics |`Microsoft.StreamAnalytics/streamingjobs`| Allows data from a streaming job to be written to Blob Storage. [Learn more](../../stream-analytics/blob-output-managed-identity.md). |
590
+
| Azure Synapse Analytics |`Microsoft.Synapse/workspaces`| Enables access to data in Azure Storage. |
591
+
| Azure Video Indexer |`Microsoft.VideoIndexer/Accounts`| Enables access to storage accounts. |
569
592
570
593
If your account doesn't have the hierarchical namespace feature enabled on it, you can grant permission by explicitly assigning an Azure role to the [managed identity](../../active-directory/managed-identities-azure-resources/overview.md) for each resource instance. In this case, the scope of access for the instance corresponds to the Azure role that's assigned to the managed identity.
0 commit comments