Skip to content

Commit 03386af

Browse files
authored
Merge pull request #231279 from kevinjaku/mssparkutils-mount-using-blob
Mssparkutils mount - adding blob managed private endpoint in case of managed VNET workspaces
2 parents 9bf0bc9 + 3d00ea6 commit 03386af

File tree

2 files changed

+7
-0
lines changed

2 files changed

+7
-0
lines changed
199 KB
Loading

articles/synapse-analytics/spark/synapse-file-mount-api.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -57,6 +57,13 @@ You can create a linked service for Data Lake Storage Gen2 or Blob Storage. Curr
5757

5858
![Screenshot of selections for creating a linked service by using a managed identity.](./media/synapse-file-mount-api/synapse-link-service-using-managed-identity.png)
5959

60+
> [!IMPORTANT]
61+
>
62+
> - If the above created Linked Service to Azure Data Lake Storage Gen2 uses a [managed private endpoint](../security/synapse-workspace-managed-private-endpoints.md) (with a *dfs* URI) , then we need to create another secondary managed private endpoint using the Azure Blob Storage option (with a **blob** URI) to ensure that the internal [fsspec/adlfs](https://github.com/fsspec/adlfs/blob/main/adlfs/spec.py#L400) code can connect using the *BlobServiceClient* interface.
63+
> - In case the secondary managed private endpoint is not configured correctly, then we would see an error message like *ServiceRequestError: Cannot connect to host [storageaccountname].blob.core.windows.net:443 ssl:True [Name or service not known]*
64+
>
65+
> ![Screenshot of creating a managed private end-point to an ADLS Gen2 storage using blob endpoint.](./media/synapse-file-mount-api/create-mpe-blob-endpoint.png)
66+
6067
> [!NOTE]
6168
> If you create a linked service by using a managed identity as the authentication method, make sure that the workspace MSI file has the Storage Blob Data Contributor role of the mounted container.
6269

0 commit comments

Comments
 (0)