General best practices documentation update

[nteyan]

🛠️ Description

This documentation update introduces new queries to summarize the counts of various resources. The aim is to provide users with an overview of their resource inventory, helping them understand the distribution and quantity of resources in their environment.

📷 Screenshots

📋 Checklist

🔬 How did you test this change?

• 🤏 Lint tests
• 🤞 PS -WhatIf / az validate
• 👍 Manually deployed + verified
• 💪 Unit tests
• 🙌 Integration tests

🙋‍♀️ Do any of the following that apply?

• 🚨 This is a breaking change.
• 🤏 The change is less than 20 lines of code.

📑 Did you update docs/changelog.md?

• ✅ Updated changelog (required for dev PRs)
• ➡️ Will add log in a future PR (feature branch PRs only)
• ❎ Log not needed (small/internal change)

📖 Did you update documentation?

• ✅ Public docs in docs (required for dev)
• ✅ Internal dev docs in src (required for dev)
• ➡️ Will add docs in a future PR (feature branch PRs only)
• ❎ Docs not needed (small/internal change)

[flanakin]

This is not a service. Maybe use "Resource Manager" instead?

[flanakin]

Move this after ACO so it's sorted alphabetically.

[flanakin]

Is this really necessary? It feels too simple to document. What scenario does this actually address? Fwiw, I think we have a larger effort to document scenarios across the entire BPL, but it's fine if we don't do that right now.

[flanakin]

This still feels too simplistic, right? If we think this and the previous one are needed, should we merge both with the next one, which is closer to what I think people are looking for with a resource inventory?

[flanakin]

Query styling

Suggested change

	resources
	| summarize Count=count(id) by subscriptionId
	| order by Count desc
	Resources
	| summarize Count = count(id) by subscriptionId
	| order by Count desc

[flanakin]

nit: I'm on the fence as to whether we should put sorting in the queries. We don't want unnecessary load on the server. I get it may be useful in some scenarios, but I'd probably leave that to the user to decide on their own unless sorting is critical for the scenario.

[flanakin]

This is unmaintainable and not technically accurate, if I'm reading it correctly. We should discuss this one.

[flanakin]

Query styling...

Suggested change

	resources
	| summarize count() by location
	Resources
	| summarize Count = count() by location

[microsoft-github-policy-service]

@nteyan: you have some new feedback!

Please review and resolve all comments and I'll let reviewers know by removing the Needs: Attention label. If I miss anything, just reply with #needs-review and I'll update the status.