Error in: samples/manage/azure-arc-enabled-sql-server/modify-license-type/modify-arc-sql-license-type.ps1

[djcampbell]

Issue: The script uses Search-AzGraph to locate resources. Search-AzGraph does not honor AzContext when executing in Cloud Shell. This is a problem when you have more than 1000 subscriptions. The Search-AzGraph commandlet only returns results from the first 1000 subscriptions even though AzContext is filtered to 1 sub and you have only passed 1 sub to the modify-arc-sql-license-type script.

In my test case, I am attempting to run the script against a device in a specific sub, but it cannot be found. I have access to over 2800 subs and the device I am looking for is not in the first 1000 subs.

Possible solution: Update Search-AzGraph to honor AzContext.

[anosov1960]

Hi, @djcampbel, in Azure graph subscription is another resource that can used in filters. In that sense the only "context" it uses is tenant. If you have an updated script that worked at your scale, can pls share?
Thank you

[djcampbell]

I ended up working around the issue by logging into that tenant directly - rather than using my federated login which has access to thousands of tenants. I have not found a solution to use with my federated login yet.
-Daniel

[djcampbell]

@anosov1960 It looks like you can add the -Subscription parameter to the Search-AzGraph command on

sql-server-samples/samples/manage/azure-arc-enabled-sql-server/modify-license-type/modify-arc-sql-license-type.ps1

Line 310 in 74c60b5

$resources = Search-AzGraph -Query "$($query)" -First $batchSize -SkipToken $skipToken

ie:
$resources = Search-AzGraph -Query "$($query)" -First $batchSize -SkipToken $skipToken -Subscription $($sub.Id)

[djcampbell]

@anosov1960 Also, I noticed an error from line

sql-server-samples/samples/manage/azure-arc-enabled-sql-server/modify-license-type/modify-arc-sql-license-type.ps1

Line 435 in 74c60b5

$ext | Set-AzConnectedMachineExtension -Name $setID.Name -ResourceGroupName $setID.ResourceGroup -MachineName $setID.MachineName -NoWait -ErrorAction SilentlyContinue | Out-Null

I was able to resolve it by using Update-AzConnectedMachineExtension rather than Set-AzConnectedMachineExtension.