<?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: Network Connectivity Configurations - assign to workspace in Administration &amp; Architecture</title>
    <link>https://community.databricks.com/t5/administration-architecture/network-connectivity-configurations-assign-to-workspace/m-p/119160#M3353</link>
    <description>&lt;P&gt;Thanks for the reply. The region is the same and the workspace is running.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 14 May 2025 10:52:01 GMT</pubDate>
    <dc:creator>giladba</dc:creator>
    <dc:date>2025-05-14T10:52:01Z</dc:date>
    <item>
      <title>Network Connectivity Configurations - assign to workspace</title>
      <link>https://community.databricks.com/t5/administration-architecture/network-connectivity-configurations-assign-to-workspace/m-p/119021#M3344</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;Following these api calls Databricks has not actually applied the NCC to the workspace, despite returning a success status. All values are correct (ncc id , workspace id) What could be the issue?:&lt;/P&gt;&lt;P&gt;# 1. Get list of NCCs to confirm ID and region - the ncc id is correct&amp;nbsp;&lt;BR /&gt;GET /accounts/{account_id}/network-connectivity-configs&lt;/P&gt;&lt;P&gt;# 2. Apply the PATCH again and confirm 200 - patch succeeds&amp;nbsp;&lt;BR /&gt;PATCH /accounts/{account_id}/workspaces/{workspace_id}&lt;BR /&gt;{&lt;BR /&gt;"network_connectivity_config_id": "my-ncc-id"&lt;BR /&gt;}&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 13 May 2025 09:24:54 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/network-connectivity-configurations-assign-to-workspace/m-p/119021#M3344</guid>
      <dc:creator>giladba</dc:creator>
      <dc:date>2025-05-13T09:24:54Z</dc:date>
    </item>
    <item>
      <title>Re: Network Connectivity Configurations - assign to workspace</title>
      <link>https://community.databricks.com/t5/administration-architecture/network-connectivity-configurations-assign-to-workspace/m-p/119140#M3352</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/84268"&gt;@giladba&lt;/a&gt;, even if the patch call returns a 200 status, Databricks may not apply the NCC if there’s a region mismatch between the workspace and the NCC, or if the workspace isn’t in a running state. And also changes might take a few minutes to propagate. To ensure everything works as expected, double-check that both the workspace and the NCC are in the same region.&lt;/P&gt;</description>
      <pubDate>Wed, 14 May 2025 09:23:30 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/network-connectivity-configurations-assign-to-workspace/m-p/119140#M3352</guid>
      <dc:creator>Renu_</dc:creator>
      <dc:date>2025-05-14T09:23:30Z</dc:date>
    </item>
    <item>
      <title>Re: Network Connectivity Configurations - assign to workspace</title>
      <link>https://community.databricks.com/t5/administration-architecture/network-connectivity-configurations-assign-to-workspace/m-p/119160#M3353</link>
      <description>&lt;P&gt;Thanks for the reply. The region is the same and the workspace is running.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 14 May 2025 10:52:01 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/network-connectivity-configurations-assign-to-workspace/m-p/119160#M3353</guid>
      <dc:creator>giladba</dc:creator>
      <dc:date>2025-05-14T10:52:01Z</dc:date>
    </item>
  </channel>
</rss>

