This issue tracks the feedback received during a UX session where the customer found gaps in the Azure docs.

@zmoog @dedemorton @bmorelli25 @ollyhowell

The required doc fixes might be easier than we expect.
I'm happy to make those changes, if you can assist with the technical details.
In particular, we need to update the section Settings to be more explicit on how to use these three settings:

Eventhub = Needs to specify that this is the main eventhub name. Do we need to add an error message when they don’t specify the main eventhub name? In Azure, this appears as Event Hubs Namespace. “Event hubs where logs are saved”
Consumer Group = Used if you dump all Azure logs into one event hub, then broken out into subgroups. Need more information on this. How does Azure actually use this?
Connection String = Connection string for the event hub where the data is actually being stored.

This is some more feedback we collected during the UX session:
Azure Logs integration seems to encompass all the other Azure integrations, but you still have to install each separate Azure integration.

• For each Azure integration, Azure logs integration only works for one. For all other integrations, Azure Logs integration doesn’t work.
• To get the proper pipeline and categorization, you have to install each separate Azure integration.
• Azure Logs is used to just ingest Azure logs. This is confusing because the settings are misleading.
• The Integrations Settings: There needs to be more information about connection strings and what you’re looking for. The event hub can contain other event hubs. The settings are looking for the main event hub, not the sub event hubs.
  These settings need help:
• These integrations are 1:1, not 1 for many. You can’t use this one agent to pull all logs.

CC @KOTungseth

Relates to #3907, elastic/observability-docs#2174