riweston
commented
2 months ago I really like this idea! 👍
I'm thinking about how best to implement this, few ideas;
- Run
aztx --by-tenantor something like this and then start the program by selecting the tenant first as you've proposed - Start the program normally with an additional column indicating the parent tenant (this could also be configurable to show/hide)
- Start the program normally and have a hotkey to filter by tenant and then, once selected, filter by subscription
Something else to consider is that this program manipulates the config file in $HOME/.azure/azureProfile.json and something that I've noticed, at least in my case, is that I have access to a couple of Azure environments and one is quite locked down so I can't see the tenantDisplayName field. I've sanitised the contents but take a look at this...
azureProfile.json snippet
```json { "subscriptions": [ { "id": "11111111-1111-1111-1111-111111111111", "name": "N/A(tenant level account)", "state": "Enabled", "user": { "name": "user1@example.com", "type": "user" }, "isDefault": false, "tenantId": "11111111-1111-1111-1111-111111111111", "environmentName": "AzureCloud" }, { "id": "22222222-2222-2222-2222-222222222222", "name": "N/A(tenant level account)", "state": "Enabled", "user": { "name": "user1@example.com", "type": "user" }, "isDefault": false, "tenantId": "22222222-2222-2222-2222-222222222222", "environmentName": "AzureCloud" }, { "id": "33333333-3333-3333-3333-333333333333", "name": "User2 MSDN", "state": "Enabled", "user": { "name": "user2@company.com", "type": "user" }, "isDefault": true, "tenantId": "44444444-4444-4444-4444-444444444444", "environmentName": "AzureCloud", "homeTenantId": "44444444-4444-4444-4444-444444444444", "tenantDefaultDomain": "company.com", "tenantDisplayName": "CompanyName", "managedByTenants": [] } ], "installationId": "55555555-5555-5555-5555-555555555555" } ```As you can see in the first 2 subscriptions the tenantDisplayName field is missing we'd need consider whether to present the tenantId UUID field in the tenant selector (which obviously isn't very friendly or readable) or just group all the subscriptions together that don't have a tenantDisplayName field for better usability.
Would be keen to get your thoughts!
lonix
Summary: As a user managing multiple Azure subscriptions on behalf of various customers, I would like the ability to view and organize subscriptions by Tenant in my portfolio. This would significantly improve usability when dealing with a large number of subscriptions.
Description: I manage numerous Azure subscriptions across multiple tenants. It would be highly beneficial to have the option to display the Tenant in its own column within the subscription management interface. Ideally, subscriptions could also be grouped by Tenant, allowing for more efficient navigation and management.
In an ideal scenario, I envision a workflow where I can first select a Tenant and then choose from the associated subscriptions. This hierarchical selection process would streamline the management experience, particularly for users handling a large number of subscriptions.
Considerations:
Conclusion: This feature would greatly enhance the management of multiple Azure subscriptions by simplifying navigation and improving the organization. The current product is already excellent, and this enhancement would make it even better.