Skip to content

Updated documentation for setting different endpoints#552

Open
anjaliratnam-msft wants to merge 3 commits into
fsspec:mainfrom
anjaliratnam-msft:protocol-suffix-bug
Open

Updated documentation for setting different endpoints#552
anjaliratnam-msft wants to merge 3 commits into
fsspec:mainfrom
anjaliratnam-msft:protocol-suffix-bug

Conversation

@anjaliratnam-msft

@anjaliratnam-msft anjaliratnam-msft commented Jun 15, 2026

Copy link
Copy Markdown
Collaborator

This PR updates the documentation to instruct users how to set different endpoints. This resolves #402.

@kyleknap

Copy link
Copy Markdown
Collaborator

Hey @anjaliratnam-msft I'm thinking we hold off updating any of the URL parsing for now as end users can set a different endpoint, they just have to use the account_url and account_name parameters in tandem. I put an example of it in the original GitHub issue: #402 (comment)

Mainly, to my understanding the abfs://<file_system>@<account_name>.dfs.core.windows.net/<path>/<file_name> format was specifically to handle the ABFS driver style of URIs and I'm not sure if it supports URIs outside of dfs.core.windows.net per the documentation: https://learn.microsoft.com/en-us/azure/storage/blobs/data-lake-storage-introduction-abfs-uri#uri-syntax. So, I'm hesitant to start supporting different URIs in adlfs especially if the ABFS driver does not support these URIs and because there is already a way to specify different endpoint in adlfs via parameters.

I'm thinking maybe we can repurpose this PR to update the documentation on how to connect to different endpoints? Support of Microsoft OneLake is a similar story (where a different endpoint needs to be set to use with adlfs): #515 So maybe we can include that in the doc update as well? Thoughts?

@anjaliratnam-msft anjaliratnam-msft changed the title Fixed url parsing to work with sovereign clouds Updated documentation for setting different endpoints Jun 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Maybe fsspec can't working well in Azure CN

2 participants