Skip to content

Commit da43c55

Browse files
authored
Merge pull request #50298 from CarlRabeler/patch-192
Update sql-database-vnet-service-endpoint-rule-overview.md
2 parents 0edbdf3 + f1486cb commit da43c55

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

articles/sql-database/sql-database-vnet-service-endpoint-rule-overview.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ author: DhruvMsft
88
manager: craigg
99
ms.custom: "VNet Service endpoints"
1010
ms.topic: conceptual
11-
ms.date: 07/18/2018
11+
ms.date: 08/28/2018
1212
ms.reviewer: genemi
1313
ms.author: dmalik
1414
ms.reviewer: carlrab
@@ -177,12 +177,11 @@ Azure Storage has implemented the same feature that allows you to limit connecti
177177
If you choose to use this feature with a Storage account that is being used by an Azure SQL Server, you can run into issues. Next is a list and discussion of Azure SQLDB features that are impacted by this.
178178

179179
#### Azure SQLDW PolyBase
180-
PolyBase is commonly used to load data into Azure SQLDW from Storage accounts. If the Storage account that you are loading data from limits access only to a set of VNet-subnets, connectivity from PolyBase to the Account will break. There is a mitigation for this, and you may contact *[email protected]* for more information.
180+
PolyBase is commonly used to load data into Azure SQLDW from Storage accounts. If the Storage account that you are loading data from limits access only to a set of VNet-subnets, connectivity from PolyBase to the Account will break. There is a mitigation for this, and you may contact Microsoft support for more information.
181181

182182
#### Azure SQLDB Blob Auditing
183183
Blob auditing pushes audit logs to your own storage account. If this storage account uses the VENT Service endpoints feature then connectivity from Azure SQLDB to the storage account will break.
184184

185-
186185
## Adding a VNET Firewall rule to your server without turning On VNET Service Endpoints
187186

188187
Long ago, before this feature was enhanced, you were required to turn VNet service endpoints On before you could implement a live VNet rule in the Firewall. The endpoints related a given VNet-subnet to an Azure SQL Database. But now as of January 2018, you can circumvent this requirement by setting the **IgnoreMissingServiceEndpoint** flag.

0 commit comments

Comments
 (0)