<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Lakebase Data API private access with Public Network Access disabled in Lakebase Discussions</title>
    <link>https://community.databricks.com/t5/lakebase-discussions/lakebase-data-api-private-access-with-public-network-access/m-p/158092#M107</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/228048"&gt;@POCUSER&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;Yes, the Lakebase Data API can be used privately with Public Network Access disabled. Because the Data API is a REST endpoint (&lt;A href="https://learn.microsoft.com/en-us/azure/databricks/oltp/projects/data-api" data-saferedirecturl="https://www.google.com/url?q=https://learn.microsoft.com/en-us/azure/databricks/oltp/projects/data-api&amp;amp;source=gmail&amp;amp;ust=1780444042910000&amp;amp;usg=AOvVaw2ITIfs90A4chvSrnL1S5_R" target="_blank"&gt;Lakebase Data API&lt;/A&gt;), it goes through your workspace’s standard inbound (front-end) Private Link, the &lt;CODE&gt;databricks_ui_api&lt;/CODE&gt; endpoint on port 443, not a dedicated one.&lt;/P&gt;
&lt;P&gt;Service Direct Private Link (the port-5432 endpoint for performance-intensive services) is &lt;STRONG&gt;not&lt;/STRONG&gt; required for the Data API. The docs state it directly: “If your applications connect only through the Data API, you don’t need this endpoint.” See &lt;A href="https://learn.microsoft.com/en-us/azure/databricks/oltp/projects/private-link" data-saferedirecturl="https://www.google.com/url?q=https://learn.microsoft.com/en-us/azure/databricks/oltp/projects/private-link&amp;amp;source=gmail&amp;amp;ust=1780444042910000&amp;amp;usg=AOvVaw1l11jrHEhpDRrZCHy8LOnl" target="_blank"&gt;Private Link for Lakebase Autoscaling&lt;/A&gt; and &lt;A href="https://learn.microsoft.com/en-us/azure/databricks/security/network/front-end/service-direct-privatelink" data-saferedirecturl="https://www.google.com/url?q=https://learn.microsoft.com/en-us/azure/databricks/security/network/front-end/service-direct-privatelink&amp;amp;source=gmail&amp;amp;ust=1780444042910000&amp;amp;usg=AOvVaw1644ygf3dKACpX6irEYFJQ" target="_blank"&gt;Configure inbound Private Link for performance-intensive services&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;So this is a DNS issue, not a missing Private Link. With Public Network Access disabled, your DNS must resolve the Data API hostname to the &lt;STRONG&gt;private&lt;/STRONG&gt; IP of your existing inbound private endpoint (the &lt;CODE&gt;&lt;A href="http://privatelink.azuredatabricks.net" data-saferedirecturl="https://www.google.com/url?q=http://privatelink.azuredatabricks.net&amp;amp;source=gmail&amp;amp;ust=1780444042910000&amp;amp;usg=AOvVaw1vv5KfpmJDcMUWdObpeXnZ" target="_blank"&gt;privatelink.azuredatabricks.&lt;WBR /&gt;net&lt;/A&gt;&lt;/CODE&gt; zone, &lt;CODE&gt;databricks_ui_api&lt;/CODE&gt; A record). The 403 is consistent with DNS still resolving the hostname to a public IP instead of your private endpoint. Confirm with &lt;CODE&gt;nslookup&lt;/CODE&gt; that it returns the private IP. See &lt;A href="https://learn.microsoft.com/en-us/azure/databricks/security/network/front-end/front-end-private-connect" data-saferedirecturl="https://www.google.com/url?q=https://learn.microsoft.com/en-us/azure/databricks/security/network/front-end/front-end-private-connect&amp;amp;source=gmail&amp;amp;ust=1780444042910000&amp;amp;usg=AOvVaw1K6LhCatUaz7IHe4X9z0FA" target="_blank"&gt;Configure Inbound Private Link&lt;/A&gt; for the DNS verification steps.&lt;/P&gt;</description>
    <pubDate>Mon, 01 Jun 2026 23:48:53 GMT</pubDate>
    <dc:creator>stbjelcevic</dc:creator>
    <dc:date>2026-06-01T23:48:53Z</dc:date>
    <item>
      <title>Lakebase Data API private access with Public Network Access disabled</title>
      <link>https://community.databricks.com/t5/lakebase-discussions/lakebase-data-api-private-access-with-public-network-access/m-p/157858#M106</link>
      <description>&lt;P&gt;We are testing Azure Databricks Lakebase Autoscaling with Public Network Access disabled and standard inbound Private Link enabled.&lt;/P&gt;&lt;P&gt;The workspace UI works privately through VPN, but the Lakebase Data API hostname still resolves to a public IP and returns:&lt;/P&gt;&lt;P&gt;HTTP 403: Public access is not allowed for workspace&lt;/P&gt;&lt;P&gt;According to the docs, Service Direct Private Link is not required when using only the Data API.&lt;/P&gt;&lt;P&gt;Has anyone successfully used Lakebase Data API privately with Public Network Access disabled?&lt;/P&gt;&lt;P&gt;If yes, what DNS or Private Link configuration is required? Should the Data API hostname resolve through the workspace inbound Private Link, or is another private endpoint/DNS setup needed?&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Fri, 29 May 2026 07:58:24 GMT</pubDate>
      <guid>https://community.databricks.com/t5/lakebase-discussions/lakebase-data-api-private-access-with-public-network-access/m-p/157858#M106</guid>
      <dc:creator>POCUSER</dc:creator>
      <dc:date>2026-05-29T07:58:24Z</dc:date>
    </item>
    <item>
      <title>Re: Lakebase Data API private access with Public Network Access disabled</title>
      <link>https://community.databricks.com/t5/lakebase-discussions/lakebase-data-api-private-access-with-public-network-access/m-p/158092#M107</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/228048"&gt;@POCUSER&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;Yes, the Lakebase Data API can be used privately with Public Network Access disabled. Because the Data API is a REST endpoint (&lt;A href="https://learn.microsoft.com/en-us/azure/databricks/oltp/projects/data-api" data-saferedirecturl="https://www.google.com/url?q=https://learn.microsoft.com/en-us/azure/databricks/oltp/projects/data-api&amp;amp;source=gmail&amp;amp;ust=1780444042910000&amp;amp;usg=AOvVaw2ITIfs90A4chvSrnL1S5_R" target="_blank"&gt;Lakebase Data API&lt;/A&gt;), it goes through your workspace’s standard inbound (front-end) Private Link, the &lt;CODE&gt;databricks_ui_api&lt;/CODE&gt; endpoint on port 443, not a dedicated one.&lt;/P&gt;
&lt;P&gt;Service Direct Private Link (the port-5432 endpoint for performance-intensive services) is &lt;STRONG&gt;not&lt;/STRONG&gt; required for the Data API. The docs state it directly: “If your applications connect only through the Data API, you don’t need this endpoint.” See &lt;A href="https://learn.microsoft.com/en-us/azure/databricks/oltp/projects/private-link" data-saferedirecturl="https://www.google.com/url?q=https://learn.microsoft.com/en-us/azure/databricks/oltp/projects/private-link&amp;amp;source=gmail&amp;amp;ust=1780444042910000&amp;amp;usg=AOvVaw1l11jrHEhpDRrZCHy8LOnl" target="_blank"&gt;Private Link for Lakebase Autoscaling&lt;/A&gt; and &lt;A href="https://learn.microsoft.com/en-us/azure/databricks/security/network/front-end/service-direct-privatelink" data-saferedirecturl="https://www.google.com/url?q=https://learn.microsoft.com/en-us/azure/databricks/security/network/front-end/service-direct-privatelink&amp;amp;source=gmail&amp;amp;ust=1780444042910000&amp;amp;usg=AOvVaw1644ygf3dKACpX6irEYFJQ" target="_blank"&gt;Configure inbound Private Link for performance-intensive services&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;So this is a DNS issue, not a missing Private Link. With Public Network Access disabled, your DNS must resolve the Data API hostname to the &lt;STRONG&gt;private&lt;/STRONG&gt; IP of your existing inbound private endpoint (the &lt;CODE&gt;&lt;A href="http://privatelink.azuredatabricks.net" data-saferedirecturl="https://www.google.com/url?q=http://privatelink.azuredatabricks.net&amp;amp;source=gmail&amp;amp;ust=1780444042910000&amp;amp;usg=AOvVaw1vv5KfpmJDcMUWdObpeXnZ" target="_blank"&gt;privatelink.azuredatabricks.&lt;WBR /&gt;net&lt;/A&gt;&lt;/CODE&gt; zone, &lt;CODE&gt;databricks_ui_api&lt;/CODE&gt; A record). The 403 is consistent with DNS still resolving the hostname to a public IP instead of your private endpoint. Confirm with &lt;CODE&gt;nslookup&lt;/CODE&gt; that it returns the private IP. See &lt;A href="https://learn.microsoft.com/en-us/azure/databricks/security/network/front-end/front-end-private-connect" data-saferedirecturl="https://www.google.com/url?q=https://learn.microsoft.com/en-us/azure/databricks/security/network/front-end/front-end-private-connect&amp;amp;source=gmail&amp;amp;ust=1780444042910000&amp;amp;usg=AOvVaw1K6LhCatUaz7IHe4X9z0FA" target="_blank"&gt;Configure Inbound Private Link&lt;/A&gt; for the DNS verification steps.&lt;/P&gt;</description>
      <pubDate>Mon, 01 Jun 2026 23:48:53 GMT</pubDate>
      <guid>https://community.databricks.com/t5/lakebase-discussions/lakebase-data-api-private-access-with-public-network-access/m-p/158092#M107</guid>
      <dc:creator>stbjelcevic</dc:creator>
      <dc:date>2026-06-01T23:48:53Z</dc:date>
    </item>
  </channel>
</rss>

