[bug] Using login authentication method doesn't show any subscriptions

[rtheil-growlink]

Using new feature added from #446 doesn't seem to result in any subscriptions showing up for us. I've logged into the app, which works fine, but once I'm logged in, it just says "No subscriptions to show". I've had my boss try this also, and he has all the permissions, and he gets the same result.

[YingXue]

We return the results as is using the following api: https://learn.microsoft.com/en-us/rest/api/resources/subscriptions/list?tabs=HTTP
There is not any filter logic that we are applying.
If you can give this API a try (using postman or anything else), it will give us some hint.

[YingXue]

If you'd like to get some answers from the service team, Microsoft Q&A forum will be a good place to ask questions.

[rtheil-growlink]

Have started that process, but getting Azure AD set up to be able to authenticate and make those calls is a process and I don't have the permissions to do in our org, so it will take some time .

How is the process for getting this information different from Azure Storage Explorer? One thing I notice when logging in there is that there's a selection for different tenants. The "home tenant" in my case doesn't have any subscriptions. It is all in a secondary tenant, so I'm assuming this is part of the issue since there's no option in IoT Explorer to chose a tenant.

Here's what it looks like for me in Storage Explorer

[TechWatching]

Same issue, @YingXue, when I want to try the API, the tenant needs to be selected. So the issue is indeed not to be able to select the tenant. I agree with @rtheil-growlink , the process should be similar to Azure Storage Explorer which works fine.

[YingXue]

Will this post be able to provide a workaround?
https://docs.microsoft.com/en-us/answers/questions/947467/cannot-access-34azure-active-directory34-from-the.html
It looks like users should be able to login with their tenant account like: user1@yourTenantName.onmicrosoft.com

[TechWatching]

No, it does not because it does not cover the case where your user is a guest on the tenant.

[rtheil-growlink]

After finding the correct username for the tenant, I was able to get the login to recognize that username but I was unable to get password accepted for some reason, so I can't log in as the tenant-specific account.