docs: document connecting Azure Private Link to native Azure resources#3138
docs: document connecting Azure Private Link to native Azure resources#3138jwhartley wants to merge 3 commits into
Conversation
The Azure Private Link page only covered building a customer-managed Private Link Service, but est-dry-dock also supports linking directly to a PaaS resource (SQL, Storage, etc.) via its sub-resource type, and optionally provisioning a DNS name for the endpoint. Neither was documented.
|
Note for whoever picks this up next: we're hoping to ship self-service private link setup this quarter (Q3 2026). Once that lands, this page (and the customer-facing PrivateLink instructions in general) should be revisited since the manual request flow described here may no longer be the primary path. |
|
🚀 Preview deployed to https://docs.estuary.dev/pr-preview/pr-3138/ 📄 Changed pages: |
aeluce
left a comment
aeluce
left a comment
There was a problem hiding this comment.
The structure of the section may make it confusing on what's required for one method or another, since there's no indication when the PaaS resource section ends and the two threads come together again.
I pushed a possible solution that reorders the information. If that doesn't seem quite right, another option would be to use tabs.
Though as you say, self-service is coming soon and that sounds great.
Trim redundant phrasing after the PaaS-resource restructuring: fix an ungrammatical intro clause, cut a restatement the two fork bullets already cover, and de-duplicate the sub-resource-type examples that appeared both in the shared checklist and the detail section below it.
|
Hey @aeluce I tweaked it slightly to make it a little more succinct and readable if you wouldn't mind re-reviewing. |
2 participants
Summary
Test plan
npm run startinsite/) and confirm the new "Connecting to a native Azure resource" subsection renders correctly under Azure Private Link