admin管理员组

文章数量:1125590

Is it possible to add a Kusto follower cluster cross-tenant ? Example: my cluster in tenant A would have a follower cluster in tenant B.

The documentation of the New-AzKustoAttachedDatabaseConfiguration command does not give a hint on that.

I am trying to use a very general script according to the documentation. But there is no tenant parameter available.

$FollowerClustername = 'myfollower'
$FollowerClusterSubscriptionID = '9999999-9999-4e39-a325-5c3385999992'
$FollowerResourceGroupName = 'myresourcegroup'
$DatabaseName = "master"  
$LeaderClustername = 'mastercluster'
$LeaderClusterSubscriptionID = '11111111-8fb5-4e39-a325-999999999'
$LeaderClusterResourceGroup = 'myresourcegroup'
$DefaultPrincipalsModificationKind = 'Union'
##Construct the LeaderClusterResourceId and Location
$getleadercluster = Get-AzKustoCluster -Name $LeaderClustername -ResourceGroupName $LeaderClusterResourceGroup -SubscriptionId $LeaderClusterSubscriptionID -ErrorAction Stop
$LeaderClusterResourceid = $getleadercluster.Id
$Location = $getleadercluster.Location
##Table level sharing is not supported when using '*' all databases notation. If you use the all database notation please remove all table level sharing lines from the powershell command.

New-AzKustoAttachedDatabaseConfiguration -ClusterName $FollowerClustername `
    -Name  "myconfig" `
    -ResourceGroupName $FollowerResourceGroupName `
    -SubscriptionId $FollowerClusterSubscriptionID `
    -DatabaseName $DatabaseName `
    -ClusterResourceId $LeaderClusterResourceid `
    -DefaultPrincipalsModificationKind $DefaultPrincipalsModificationKind `
    -Location $Location `
    -TableLevelSharingPropertyMaterializedViewsToInclude "*_view"  `
    -TableLevelSharingPropertyTablesToInclude "someother" `
    -TableLevelSharingPropertyExternalTablesToExclude "*" `
    -ErrorAction Stop

Is it possible to add a Kusto follower cluster cross-tenant ? Example: my cluster in tenant A would have a follower cluster in tenant B.

The documentation of the New-AzKustoAttachedDatabaseConfiguration command does not give a hint on that.

I am trying to use a very general script according to the documentation. But there is no tenant parameter available.

$FollowerClustername = 'myfollower'
$FollowerClusterSubscriptionID = '9999999-9999-4e39-a325-5c3385999992'
$FollowerResourceGroupName = 'myresourcegroup'
$DatabaseName = "master"  
$LeaderClustername = 'mastercluster'
$LeaderClusterSubscriptionID = '11111111-8fb5-4e39-a325-999999999'
$LeaderClusterResourceGroup = 'myresourcegroup'
$DefaultPrincipalsModificationKind = 'Union'
##Construct the LeaderClusterResourceId and Location
$getleadercluster = Get-AzKustoCluster -Name $LeaderClustername -ResourceGroupName $LeaderClusterResourceGroup -SubscriptionId $LeaderClusterSubscriptionID -ErrorAction Stop
$LeaderClusterResourceid = $getleadercluster.Id
$Location = $getleadercluster.Location
##Table level sharing is not supported when using '*' all databases notation. If you use the all database notation please remove all table level sharing lines from the powershell command.

New-AzKustoAttachedDatabaseConfiguration -ClusterName $FollowerClustername `
    -Name  "myconfig" `
    -ResourceGroupName $FollowerResourceGroupName `
    -SubscriptionId $FollowerClusterSubscriptionID `
    -DatabaseName $DatabaseName `
    -ClusterResourceId $LeaderClusterResourceid `
    -DefaultPrincipalsModificationKind $DefaultPrincipalsModificationKind `
    -Location $Location `
    -TableLevelSharingPropertyMaterializedViewsToInclude "*_view"  `
    -TableLevelSharingPropertyTablesToInclude "someother" `
    -TableLevelSharingPropertyExternalTablesToExclude "*" `
    -ErrorAction Stop
Share Improve this question edited yesterday Werner asked 2 days ago WernerWerner 1609 bronze badges 2
  • Could you please share what you have tried? – Balaji Commented yesterday
  • @Balaji I updated the original text and added my current powershell script using New-AzKustoAttachedDatabaseConfiguration. – Werner Commented yesterday
Add a comment  | 

1 Answer 1

Reset to default 0

Add ADX follower cluster - cross tenant

The document which you mentioned describes how to creates or updates an attached database configuration in an Azure Kusto cluster. For Cross-cluster follow the below example it shows how to access the table which is present in the other cluster.

Follow the below steps to provide access for the second cluster and access the data present in the first cluster

  • Below is the table MyLogs stored in first cluster clusterpb1 as shown below:
  • Now open security in the second cluster and select Specify tenants, add Tenant Id of the first cluster.

Run the below query in the second cluster to access the table MyLogs from the first cluster. It successfully retrieves the data present in the MyLogs table as shown in the below output.

cluster("https://clusterpb1.eastus.kusto.windows.net").database("db1").MyLogs

Output:

For more information on cross tenant, please refer to this article.

本文标签: azure data explorerAdd ADX follower clustercross tenantStack Overflow