Register-AzsWithMyDirectoryTenant fails

[bitsharper]

Hi all,
Getting the following when trying to register a tenant.

An error occurred while trying to make a graph API call: {"odata.error":{"code":"Request_ResourceNotFound","message":{"lang":"en","value":"Resource '' does not exist or one of its queried reference-property objects are not
present."},"requestId":"3b109c48-bae5-40dd-8135-5b62b57dea11","date":"2020-04-09T10:31:05"}}
Additional details: {
"Method": "GET",
"ResponseUri": "https://graph.windows.net/ccstagetesting.onmicrosoft.com/oauth2PermissionGrants?%24filter=resourceId+eq+%27333bff02-629a-461a-a11f-7442b1be1f06%27+and+clientId+eq+%27a1afc375-73ec-4e71-8385-94c3486edc59%27&%24top=500&api-version=1.6",
"StatusCode": 404,
"StatusDescription": "Not Found",
"IsFromCache": false,
"LastModified": "/Date(1586428257413)/"
}
At C:\AzureStack-Tools-master\Identity\GraphAPI\GraphAPI.psm1:707 char:9

•     throw New-Object System.InvalidOperationException($traceMessa ...
  

•     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  

  • CategoryInfo : OperationStopped: (:) [], InvalidOperationException
  • FullyQualifiedErrorId : An error occurred while trying to make a graph API call: {"odata.error":{"code":"Request_ResourceNotFound","message":{"lang":"en","value":"Resource '' does not exist or one of its queried reference-property objects are not pre
    sent."},"requestId":"3b109c48-bae5-40dd-8135-5b62b57dea11","date":"2020-04-09T10:31:05"}}
    Additional details: {
    "Method": "GET",
    "ResponseUri": "https://graph.windows.net/ccstagetesting.onmicrosoft.com/oauth2PermissionGrants?%24filter=resourceId+eq+%27333bff02-629a-461a-a11f-7442b1be1f06%27+and+clientId+eq+%27a1afc375-73ec-4e71-8385-94c3486edc59%27&%24top=500&api-version=1.
    6",
    "StatusCode": 404,
    "StatusDescription": "Not Found",
    "IsFromCache": false,
    "LastModified": "/Date(1586428257413)/"
    }

[keystroke]

Hi @bitsharper, can you share more details? Does this consistently occur for you? Have you tried with other directories / accounts? Are you a CSP integrated with partner center or anything like that? I am not able to reproduce this issue on my end, especially on a query like this which is a GET call on a collection with some odata filter properties (if no objects are implicated by the filter, then the response should simply be an empty collection, not a 404).

[bitsharper]

Hi keystroke,

Thank you for your reply.
I have reproduced the problem and it works fine now. Looks like something went wrong during initial Register-AzsGuestDirectoryTenant.
My apologies this can be closed now.

[bitsharper]

Hi guys,

My apologies, I would like to re-open this problem. I have tested from 2 different environments and when I run Register-AzsWithMyDirectoryTenant I am getting the same results:

An error occurred while trying to make a graph API call: {"odata.error":{"code":"Request_ResourceNotFound","message":{"lang":"en","value":"Resource '' does not exist or one of its queried
reference-property objects are not present."}

Additional details: {
"Method": "GET",
"ResponseUri": "https://graph.windows.net/ccstaging.onmicrosoft.com/oauth2PermissionGrants?%24filter=resourceId+eq+%271ad44b80-9e7f-495b-b2f8-22ead1f8cc90%27+and+clientId+eq+%27876d88c1
-7322-47d5-9c80-f43c5764a19b%27&%24top=500&api-version=1.6",
"StatusCode": 404,
"StatusDescription": "Not Found",
"IsFromCache": false,
"LastModified": "/Date(1587085867819)/"
}

First part Register-AzsGuestDirectoryTenant completed without any issue. Then I am trying to run the second part and getting the error above. I simply run command from the documentation replacing $tenantARMEndpoint and $guestDirectoryTenantName

_`$tenantARMEndpoint = "https://management.location.azurestack.domain"
$guestDirectoryTenantName = "myaccoun.onmicrosoft.com" # this is the new tenant that needs to be onboarded to Azure Stack

Register-AzsWithMyDirectoryTenant -TenantResourceManagerEndpoint $tenantARMEndpoint -DirectoryTenantName $guestDirectoryTenantName`_

We are csp and current azure stack version is 1908 presumably we started getting this error after we updated to 1908.
Please let me know if any other details required.