docs: add FAQ section for Azure Logs integration v2 preview

packages/azure/_dev/build/docs/events.md

@@ -58,6 +58,30 @@ The processor v2 is in preview. Processor v1 is still the default and is recomme
 
 See the "Event Hub Processor v2 only" section in the integration settings for more details about enabling the processor v2.
 
+### FAQ
+
+Here are a few frequently asked questions about the integration v2 preview.
+
+#### Question: Is the integration v2 production ready?
+
+Yes, the integration v2 is production ready.
+
+The integration v2 is marked with "preview" as we were testing this routing approach, and wanted to keep the option of changing course, if needed. Since the experiment was successful, we'll remove the "preview" from the name as we finalize the plans to transition from v1 to v2.
+
+#### Question: Are all logs routed to the relevant data streams?
+
+Yes, all known logs are routed to the data stream with the best parsing and mapping functionality available.
+
+The `logs-azure.events-default` contains the routing logic based on the `category` field. The routing rules are available in the integrations repo at [packages/azure/data_stream/events/routing_rules.yml](https://github.com/elastic/integrations/blob/main/packages/azure/data_stream/events/routing_rules.yml).
+
+#### Question: How are unsupported Azure logs handled?
+
+The integration v2 inspects the category field to see if there's an integration available with full support. If there isn't a specific integration available, the routing falls back to `logs-azure.platformlogs-default` to apply the standard parsing and mapping.
+
+#### Question: What is in the undocumented data-stream `logs-azure.events-default`?
+
+The `logs-azure.events-default` data stream is the logs entry point for the integration v2. It contains the core logs routing logic.
+
 ## Data streams
 
 The Azure Logs integration (v2 preview) collects logs.

packages/azure/changelog.yml

@@ -1,3 +1,8 @@
+- version: "1.28.6"
+  changes:
+    - description: Add FAQ section to Azure Logs integration v2.
+      type: enhancement
+      link: https://github.com/elastic/integrations/pull/15203
 - version: "1.28.5"
   changes:
     - description: Add support to override `Endpoint Suffix` based on deployment environment.

packages/azure/docs/events.md

@@ -58,6 +58,30 @@ The processor v2 is in preview. Processor v1 is still the default and is recomme
 
 See the "Event Hub Processor v2 only" section in the integration settings for more details about enabling the processor v2.
 
+### FAQ
+
+Here are a few frequently asked questions about the integration v2 preview.
+
+#### Question: Is the integration v2 production ready?
+
+Yes, the integration v2 is production ready.
+
+The integration v2 is marked with "preview" as we were testing this routing approach, and wanted to keep the option of changing course, if needed. Since the experiment was successful, we'll remove the "preview" from the name as we finalize the plans to transition from v1 to v2.
+
+#### Question: Are all logs routed to the relevant data streams?
+
+Yes, all known logs are routed to the data stream with the best parsing and mapping functionality available.
+
+The `logs-azure.events-default` contains the routing logic based on the `category` field. The routing rules are available in the integrations repo at [packages/azure/data_stream/events/routing_rules.yml](https://github.com/elastic/integrations/blob/main/packages/azure/data_stream/events/routing_rules.yml).
+
+#### Question: How are unsupported Azure logs handled?
+
+The integration v2 inspects the category field to see if there's an integration available with full support. If there isn't a specific integration available, the routing falls back to `logs-azure.platformlogs-default` to apply the standard parsing and mapping.
+
+#### Question: What is in the undocumented data-stream `logs-azure.events-default`?
+
+The `logs-azure.events-default` data stream is the logs entry point for the integration v2. It contains the core logs routing logic.
+
 ## Data streams
 
 The Azure Logs integration (v2 preview) collects logs.

packages/azure/manifest.yml

@@ -1,6 +1,6 @@
 name: azure
 title: Azure Logs
-version: "1.28.5"
+version: "1.28.6"
 description: This Elastic integration collects logs from Azure
 type: integration
 icons: