Wish: Add 'Customer Name' to Azure Portal Views as a Column (or 'Group By') Option
I work for a CSP and use Azure Lighthouse to manage many customer environments. All of the Azure portal views are focused on the concept of the subscription being the top level management object in Azure (I'm excluding Management Groups for policy management). I'm sure this works well for single organisations that use Azure portal, but for CSPs we need to be able to order/arrange/group lists based on customer name first and then by subscription. In other words, our administration view has to start one level above subscription compared with most organisations. I know you can change the directory filter if you want to work on a single customer's environment and limit the view to their resources, but most often we are managing at scale and operating on multiple customer estates at once and as such we need lists to be built around the customer as the topmost object rather than the subscription. When we are confronted with a long list of subscriptions (some of which being unhelpfully named 'Subscription 1' or 'Azure' by customers who have not followed CAF...) it is impossible to determine which customer that sub relates to without following each and every subscription link. It's onerous. Not all customers allow us to impress a subscription naming convention on their Azure environment (we might be contracted to only support a subset of their subscriptions and they are unwilling to change them). An example would be the Virtual Machines list. Microsoft offers no fewer than 33 'Group By' attribute options, none of which is 'Customer'. Some views allow you to add a column and Group By tag, but a surprisingly small number of views support column manipulation. I'm hoping someone from the MSFT PG sees this and hears my plea: please keep CSPs in mind when designing Azure Portal and allow us to add a column for 'Customer Name' throughout, it would be of huge benefit to us!
Group by view not showing all groups
Hello, I have a document library with multiple tags. One of the fields is a dropdown with 3 items. When I do a 'group by' using the dropdown field I can only see groups for 2 items. The 3rd one is just invisible. I have documents tagged to all three options. So all the 3 tags are in use. When I ungroup them they are all visible. Any help will be appreciated.
Modern grouped view not displaying results
I have a Modern library filtered and grouped view that displays "Show All" when the expanded group exceeds 30 items. Upon clicking "Show All" or the group heading itself to view all items in that group, it does not display any results, however it works perfectly in Classic experience. The library has hundreds of document sets – one for each Job Request – so we have created a view that filters for Document Sets only and excludes several values of a Calculated Column (i.e. "Job Status" is not equal to...), then group by the items by the same calculated column ("Job Status"). The problem appears to be grouping using THIS calculated column (contains IF statements) – the same view works when I select any non-calculated column or another concatenated calculated column to group by. When I re-introduce this particular calculated column for grouping (even at a second level) it fails to display results again but again will do so correctly in the Classic Experience! PS: Also, is there some way to configure for more than 30 items before "Show All" appears (PS: I have increased the collapsed number of groups to display value but this doesn't affect Modern "Show All".