cosmos.azure.com doesn't load subscriptions when the user has access to more than 18,000 subscriptions
- Dominant language
- TypeScript
- Stars
- 131
- Forks
- 67
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 10
Description
In cosmos.azure.com if you sign in as a user that has access to more than 18,000 subscriptions then you are unable to select a subscription or database account. No error is shown in the portal, but the Subscription and CosmosDB Account Name dropdowns remain empty.
Network trace shows that Data Explorer is using Azure Resource Graph to query for microsoft.documentdb/databaseaccounts resources, and ARG fails with error:
> {
> "error": {
> "code": "BadRequest",
> "message": "Please provide below info when asking for support: timestamp = 2024-10-02T18:34:36.1937751Z, correlationId = 3217cea2-db7e-45d3-9c50-d2c459fe8be0.",
> "details": [
> {
> "code": "TooManySubscriptionsUnderScope",
> "message": "The number of subscriptions under provided tenant or management groups in the request has exceeded the allowed limit 18000. Please select a more granular scope or allow partial scopes results by passing AllowPartialScopes flag in the query options."
> }
> ]
> }
> }
Contributor guide
Research direction
No source file or test is named. Start at the Data Explorer subscription and Cosmos DB account loading path in cosmos.azure.com, then inspect the Azure Resource Graph request described in the network trace. Done means users with access to more than 18,000 subscriptions can populate and select both dropdowns without the reported empty state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, typescript
- Domain
- cloud, databases, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100