Merge pull request #2542 from MicrosoftDocs/main638747431764765616sync_temp

For protected branch, push strategy should use PR and merge to target branch method to work around git push error

Author: learn-build-service-prod[bot]

data-explorer/ingest-data-cross-tenant.md

@@ -3,50 +3,77 @@ title: Create a cross-tenant data connection for Azure Data Explorer
 description: Learn how to create a cross-tenant data connection for an Azure Event Hubs or Azure Event Grid service in a different tenant
 ms.reviewer: vilauzon
 ms.topic: reference
-ms.date: 11/13/2023
+ms.date: 02/06/2025
 ---
 # Cross-tenant data connection
 
-When you need to create a data connection for an Azure Event Hubs or Azure Event Grid service in a different tenant, use our [API](/rest/api/azurerekusto/dataconnections/createorupdate) to build the connection.
+When you need to create a data connection for an Azure Event Hubs or Azure Event Grid service in a different tenant, use the [Create Data Connections API](/rest/api/azurerekusto/dataconnections/createorupdate) to build the connection.
 
-In the following example, you'll use PowerShell to create a cross-tenant Event Hubs data connection and [auxiliary tokens](/azure/azure-resource-manager/management/authenticate-multi-tenant) to authenticate.
+In this article, you learn how to use PowerShell to create a cross-tenant Event Hubs data connection and [auxiliary tokens](/azure/azure-resource-manager/management/authenticate-multi-tenant) to authenticate.
 
 ## Prerequisites
 
 * If you don't have an Azure subscription, create a [free Azure account](https://azure.microsoft.com/free/) before you begin.
-* Create an [event hub with data for ingestion](ingest-data-event-hub-overview.md) with an account in *Tenant1*, [email protected].
-* Create [a test cluster and database](create-cluster-and-database.md), with an account in *Tenant2*, [email protected].
+* Create an Event Hub in *Tenant1*. This is the tenant that hosts the source Event Hubs.
+* Create [a test cluster and database](create-cluster-and-database.md) in *Tenant2*. This is the tenant that hosts the destination cluster.
+* A single Entra account with access to both tenants or a [multitenant service principal](/entra/identity-platform/howto-convert-app-to-be-multi-tenant).
 
-## Assign role to Tenant2 in Event Hubs
+## Permissions
 
-1. In the Azure portal, browse to your Event Hubs namespace.
-1. In the left menu, select **Access control (IAM)** > **Add role assignments**
+The Entra account or multitenant service principal must have at least the following permissions:
+
+- Data Explorer: Contributor
+- Event Hubs Namespace: [Azure Event Hubs Data Owner](/azure/role-based-access-control/built-in-roles#azure-event-hubs-data-owner)
 
-    :::image type="content" source="media/cross-tenant-ingestion/access-control.png" alt-text="Screenshot of Event Hubs namespace.":::
+> [!NOTE]
+> The account can be local or guest to Tenant1 or Tenant2, as long as it has the prerequisite permissions.
+> Permissions must be at the Namespace level, and not at the Event Hubs level.
 
-1. In the **Add role assignment** window, fill out the following information, and then select **Save**.
+## Assign role to the Entra Account or Service Principal in Event Hubs for Tenant1
+
+1. In the Azure portal, browse to your Event Hubs namespace.
 
-    :::image type="content" source="media/cross-tenant-ingestion/add-role-assignment.png" alt-text="Screenshot of Add role assignment window in the Azure portal.":::
+1. In the left menu, select **Access control (IAM)** > **Add role assignments**.
 
-    |**Setting** | **Suggested value** |
-    |---|---|
+1. In the **Add role assignment** window, enter the settings in the table, and then select **Save**.
+
+    | **Setting** | **Suggested value** |
+    |--|--|
     | Role | [Azure Event Hubs Data Owner](/azure/role-based-access-control/built-in-roles#azure-event-hubs-data-owner) |
     | Assign access to | User, group, or service principal |
-    | Select | The email address of the user in *Tenant2* |
+    | Select | The email address of the Entra user or Service Principal ID |
+
+## Assign role to the Entra Account or Service Principal in the cluster for Tenant2
+
+1. In the Azure portal, browse to your Data Explorer cluster.
+
+1. In the left menu, select **Access control (IAM)** > **Add role assignments**.
+
+1. In the **Add role assignment** window, enter the settings in the table and then select **Save**.
+
+    | **Setting** | **Suggested value** |
+    |--|--|
+    | Role | [Contributor](/azure/role-based-access-control/built-in-roles/privileged#contributor)|
+    | Assign access to | User, group, or service principal |
+    | Select | The email address of the Entra user or Service Principal ID |
+
+## Set up the cross-tenant data connection
+
+Set up a cross-tenant data connection between the cluster and Event Hubs using PowerShell.
 
-1. When you receive an email invite on the selected address (`[email protected] account`), accept the invitation.
+**Before you begin**
 
-## Get an access token for Tenant1
+Create the `Get-AzCachedAccessToken` function to get the access token for *Tenant1*. The source code for the function can be found in the [PowerShell gallery](https://www.powershellgallery.com/packages/AzureSimpleREST/0.2.64/Content/internal%5Cfunctions%5CGet-AzCachedAccessToken.ps1). You can include this code in your personal PowerShell profile to make it easier to call, or you can run it and then use it in these steps.
 
-Before you begin, you'll need the `Get-AzCachedAccessToken` function to get the access token for *Tenant1*. The source code for the function can be found in the [PowerShell gallery](https://www.powershellgallery.com/packages/AzureSimpleREST/0.2.64/Content/internal%5Cfunctions%5CGet-AzCachedAccessToken.ps1). You can include this code in your personal PowerShell profile to make it easier to call, or you can run it and then use it in these steps.
+# [Entra account](#tab/entra)
 
-1. Run the following command to connect to *Tenant1*:
+1. Run the following command to connect to the Event Hubs subscription in *Tenant1*:
 
     ```PowerShell
-    Connect-AzAccount
+    Connect-AzAccount -TenantId <Tenant ID> -Subscription "<SubscriptionName>"
     ```
 
-1. Add a variable with the token for *Tenant1*:
+1. Add a variable to store the access token for *Tenant1*:
 
     ```PowerShell
     $tokenfromtenant1 = Get-AzCachedAccessToken
@@ -58,11 +85,10 @@ Before you begin, you'll need the `Get-AzCachedAccessToken` function to get the
     $auxpat="Bearer $tokenfromtenant1"
     ```
 
-1. Grant `[email protected]` access to the cluster.
-1. Set the cluster's subscription ID:
+1. Run the following command to connect to the cluster subscription in *Tenant2*:
 
     ```PowerShell
-    Set-AzContext -SubscriptionId "<subscription ID>"
+    Connect-AzAccount -TenantId <Tenant ID> -SubscriptionId "<SubscriptionName>"
     ```
 
 1. Add a variable with the token for *Tenant2*:
@@ -77,30 +103,110 @@ Before you begin, you'll need the `Get-AzCachedAccessToken` function to get the
     $pat="Bearer $tokenfromtenant2"
     ```
 
-1. Add an HTTP body request variable to use when invoking the web request:
+1. Add an HTTP body request variable to use as an Event Hub resource, when invoking the web request:
 
     ```PowerShell
-    $requestbody ='{"location": "Australia East","kind": "EventHub","properties": { "eventHubResourceId": "/subscriptions/<subscription ID>/resourceGroups/<resource group name>/providers/Microsoft.EventHub/namespaces/<event hub namespace name>/eventhubs/<event hub name>","consumerGroup": "$Default","dataFormat": "JSON", "tableName": "<ADX table name>", "mappingRuleName": "<ADX table mapping name>"}}'
+    $requestbody ='{"location": "Australia East","kind": "EventHub","properties": { "eventHubResourceId": "/subscriptions/<subscription ID>/resourceGroups/<ResourceGroupName>/providers/Microsoft.EventHub/namespaces/<EventHubNamespaceName>/eventhubs/<EventHubName>","consumerGroup": "$Default","dataFormat": "JSON", "tableName": "<ADXTableName>", "mappingRuleName": "<ADXTableMappingName>"}}'
     ```
 
-1. Add a URI variable to use when invoking the web request:
+1. Add a URI variable to use as a cluster resource, when invoking the web request:
 
     ```PowerShell
-    $adxdcuri="https://management.azure.com/subscriptions/<subscription ID>/resourceGroups/<resource group name>/providers/Microsoft.Kusto/clusters/<adx cluster name>/databases/<adx db name>/dataconnections/<adx data connection name>?api-version=2020-02-15"
+    $adxdcuri="https://management.azure.com/subscriptions/<subscriptionID>/resourceGroups/<resource group name>/providers/Microsoft.Kusto/clusters/<ADXClusterName>/databases/<ADXdbName>/dataconnections/<ADXDataConnectionName>?api-version=2020-02-15"
     ```
 
-1. Add `[email protected]` as a contributor in the cluster.
-1. Invoke the following web request that uses the previously defined variables.
+1. Invoke the following web request, that uses the previously defined variables, to create the data connection:
 
     ```PowerShell
     Invoke-WebRequest -Headers @{Authorization = $pat; 'x-ms-authorization-auxiliary' = $auxpat} -Uri $adxdcuri -Body $requestbody -Method PUT -ContentType 'application/json'
     ```
 
-You should now be able to see the newly created data connection in the Azure portal.
+# [Service Principal account](#tab/spa)
 
-> [!NOTE]
-> If the access used to build the data connection is revoked on Event Hubs, make sure you delete the data connection. Otherwise, Azure Data Explorer will continue to ingest data even if access on Event Hubs is revoked.
+1. Define the Service Principal ID:
+
+    ```PowerShell
+    $ServicePrincipalID = "<Application(Client)ID>"
+    ```
+
+1. Set the Service Principal secret:
+
+    ```PowerShell
+    $Password = ConvertTo-SecureString -String "<Secret>" -AsPlainText -Force
+    ```
+
+1. Create a new PSCredential object to securely store and pass credentials:
+
+    ```PowerShell
+    $Credential = New-Object -TypeName "System.Management.Automation.PSCredential" -ArgumentList $ServicePrincipalID, $Password
+    ```
+
+1. Connect to the Event Hub subscription in *Tenant1*:
+
+    ```PowerShell
+    Connect-AzAccount -TenantId <Tenant ID> -Subscription "<SubscriptionName>" -ServicePrincipal -Credential $Credential
+    ```
+
+1. Store the cached access token in the $tokenfromtenant1 variable:
+
+    ```PowerShell
+    $tokenfromtenant1 = Get-AzCachedAccessToken
+    ```
+
+1. Create a string that includes the cached access token in the format required for authorization headers:
+
+    ```PowerShell
+    $auxpat="Bearer $tokenfromtenant1"
+    ```
+
+1. Connect to the cluster subscription in *Tenant2*:
+
+    ```PowerShell
+    Connect-AzAccount -TenantId <Tenant ID> -Subscription "<SubscriptionName>" -ServicePrincipal -Credential $Credential
+    ```
+
+1. Store the cached access token in the $tokenfromtenant2 variable.
+
+    ```powershell
+    $tokenfromtenant2 = Get-AzCachedAccessToken
+    ```
+
+1. Create a string that includes the cached access token in the format required for authorization headers:
+
+    ```powershell
+    $pat="Bearer $tokenfromtenant2"
+    ```
+
+1. Add Event hub resource details to a variable:
+
+    ```PowerShell
+    $requestbody = '{"location": "East US", "kind": "EventHub", "properties": { "eventHubResourceId": "/subscriptions/<subscriptionID>/resourceGroups/<ResourceGroupName>/providers/Microsoft.EventHub/namespaces/<EventHubNamespaceName>/eventhubs/<EventHubName>", "consumerGroup": "$Default", "dataFormat": "MultiJSON", "tableName": "<ADXTableName>", "mappingRuleName": "<ADXTableMappingName>"}}'
+    ```
+
+1. Add cluster details to a variable:
+
+    ```PowerShell
+    $adxdcuri="https://management.azure.com/subscriptions/<subscriptionID>/resourceGroups/<ResourceGroupName>/providers/Microsoft.Kusto/clusters/<ADXClusterName>/databases/<ADXdbName>/dataconnections/<ADXDataConnectionName>?api-version=2020-02-15"
+    ```
+
+1. Send the request to create the data connection:
+
+    ```PowerShell
+    Invoke-WebRequest -Headers @{Authorization = $pat; 'x-ms-authorization-auxiliary' = $auxpat} -Uri $adxdcuri -Body $requestbody -Method PUT -ContentType 'application/json'
+    ```
+
+---
+
+**After you finish**
+
+1. Verify that you can now see the newly created data connection in the Azure portal.
+
+1. *Optional*: After establishing the data connection, you can revoke or delete the previously granted permissions for the Entra Account or Service Principal. Since the cluster ingestion uses the Event Hubs keys, these permissions are no longer required.
+
+> [!IMPORTANT]
+> If the primary or secondary Event Hubs keys are rotated, data ingestion might stop working. In that case, you need to drop and recreate the data connection.
 
 ## Related content
 
 * [Query data in Azure Data Explorer](web-query-data.md)
+* [Convert to multitenant](/entra/identity-platform/howto-convert-app-to-be-multi-tenant)