<?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 How to setup service principal to assing account-level groups to workspaces using terraform in Administration &amp; Architecture</title>
    <link>https://community.databricks.com/t5/administration-architecture/how-to-setup-service-principal-to-assing-account-level-groups-to/m-p/65396#M1042</link>
    <description>&lt;P&gt;Based on best practices, we have set up &lt;A href="https://docs.databricks.com/en/administration-guide/users-groups/scim/aad.html" target="_self"&gt;SCIM provisioning using Microsoft Entra ID&lt;/A&gt; to synchronize Entra ID groups to our Databricks account. All workspaces have identity federation enabled.&lt;/P&gt;&lt;P&gt;However, how should workspace administrators assign account-level groups to their workspaces via terraform once they have been synchronized to the Databricks account? The Databricks provider documentation for the "&lt;A href="http://databricks_permission_assignment" target="_self"&gt;databricks_permission_assignment&lt;/A&gt;" resource provides an example that uses a dedicated provider on account level. When attempting to read the group on account-level using a service principal with workspace adminstrator rights only returns an error (status 401). Based on some (more or less cryptic) descriptions, &lt;STRONG&gt;&lt;EM&gt;any&lt;/EM&gt;&lt;/STRONG&gt;&amp;nbsp;account-level API can only be accessed by credentials with "Account Admin" rights (&lt;A href="https://docs.databricks.com/api/azure/account/introduction" target="_self"&gt;example reference&lt;/A&gt;).&lt;/P&gt;&lt;P&gt;For obvious reasons, service principals used to manage terraform state of a specific workspace should not be granted "Account Admin" rights. How can the service principal set up in a way that allows fetching the group id without granting "Account Admin" rights? Are there additional workspace-level APIs that I'm not aware of that can be used instead?&lt;/P&gt;</description>
    <pubDate>Wed, 03 Apr 2024 11:11:27 GMT</pubDate>
    <dc:creator>DavidZS</dc:creator>
    <dc:date>2024-04-03T11:11:27Z</dc:date>
    <item>
      <title>How to setup service principal to assing account-level groups to workspaces using terraform</title>
      <link>https://community.databricks.com/t5/administration-architecture/how-to-setup-service-principal-to-assing-account-level-groups-to/m-p/65396#M1042</link>
      <description>&lt;P&gt;Based on best practices, we have set up &lt;A href="https://docs.databricks.com/en/administration-guide/users-groups/scim/aad.html" target="_self"&gt;SCIM provisioning using Microsoft Entra ID&lt;/A&gt; to synchronize Entra ID groups to our Databricks account. All workspaces have identity federation enabled.&lt;/P&gt;&lt;P&gt;However, how should workspace administrators assign account-level groups to their workspaces via terraform once they have been synchronized to the Databricks account? The Databricks provider documentation for the "&lt;A href="http://databricks_permission_assignment" target="_self"&gt;databricks_permission_assignment&lt;/A&gt;" resource provides an example that uses a dedicated provider on account level. When attempting to read the group on account-level using a service principal with workspace adminstrator rights only returns an error (status 401). Based on some (more or less cryptic) descriptions, &lt;STRONG&gt;&lt;EM&gt;any&lt;/EM&gt;&lt;/STRONG&gt;&amp;nbsp;account-level API can only be accessed by credentials with "Account Admin" rights (&lt;A href="https://docs.databricks.com/api/azure/account/introduction" target="_self"&gt;example reference&lt;/A&gt;).&lt;/P&gt;&lt;P&gt;For obvious reasons, service principals used to manage terraform state of a specific workspace should not be granted "Account Admin" rights. How can the service principal set up in a way that allows fetching the group id without granting "Account Admin" rights? Are there additional workspace-level APIs that I'm not aware of that can be used instead?&lt;/P&gt;</description>
      <pubDate>Wed, 03 Apr 2024 11:11:27 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/how-to-setup-service-principal-to-assing-account-level-groups-to/m-p/65396#M1042</guid>
      <dc:creator>DavidZS</dc:creator>
      <dc:date>2024-04-03T11:11:27Z</dc:date>
    </item>
    <item>
      <title>Re: How to setup service principal to assing account-level groups to workspaces using terraform</title>
      <link>https://community.databricks.com/t5/administration-architecture/how-to-setup-service-principal-to-assing-account-level-groups-to/m-p/65544#M1048</link>
      <description>&lt;P&gt;Have you tried giving Manager role on the group to the service principal which is workspace admin? Once you do this you may be able to use the settings to&amp;nbsp;&amp;nbsp;&lt;SPAN&gt;In workspace context, adding account-level group to a workspace in&amp;nbsp;&lt;/SPAN&gt;databricks_permission_assignment&lt;/P&gt;</description>
      <pubDate>Fri, 05 Apr 2024 00:50:45 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/how-to-setup-service-principal-to-assing-account-level-groups-to/m-p/65544#M1048</guid>
      <dc:creator>Walter_C</dc:creator>
      <dc:date>2024-04-05T00:50:45Z</dc:date>
    </item>
  </channel>
</rss>

