elastic · shmsr · Aug 7, 2025 · Aug 1, 2025 · Aug 1, 2025 · Aug 1, 2025
@@ -1,3 +1,8 @@
+- version: "0.6.0"
+  changes:
+    - description: Add a flag `fips_compatible` to control whether the package is allowed in the ECH FedRAMP High environment.
+      type: enhancement
+      link: https://github.com/elastic/integrations/pull/14769
 - version: "0.5.3"
   changes:
     - description: Rename billing dashboard to cognitive billing.

@@ -1,7 +1,7 @@
 format_version: 3.3.2
 name: azure_ai_foundry
 title: "Azure AI Foundry"
-version: "0.5.3"
+version: "0.6.0"
 source:
   license: "Elastic-2.0"
 description: "Collects Azure AI Foundry logs and metrics"
@@ -56,6 +56,7 @@ policy_templates:
   - name: azure_ai_foundry
     title: Collects Azure AI Foundry logs and metrics
     description: Azure AI Foundry metrics with Elastic Agent.
+    fips_compatible: false
     data_streams:
       - logs
       - metrics

@@ -1,4 +1,9 @@
 # newer versions go on top
+- version: "0.7.0"
+  changes:
+    - description: Add a flag `fips_compatible` to control whether the package is allowed in the ECH FedRAMP High environment.
+      type: enhancement
+      link: https://github.com/elastic/integrations/pull/14769
 - version: "0.6.0"
   changes:
     - description: Add support for Kibana `9.0.0`.

@@ -1,7 +1,7 @@
 format_version: "3.0.2"
 name: azure_app_service
 title: "Azure App Service"
-version: "0.6.0"
+version: "0.7.0"
 source:
   license: "Elastic-2.0"
 description: "Collect logs from Azure App Service with Elastic Agent."
@@ -72,6 +72,7 @@ policy_templates:
   - name: app_service_logs
     title: Azure App Service logs
     description: Azure App Service logs integration
+    fips_compatible: false
     data_streams:
       - app_service_logs
     inputs:

@@ -1,3 +1,8 @@
+- version: "1.9.0"
+  changes:
+    - description: Add a flag `fips_compatible` to control whether the package is allowed in the ECH FedRAMP High environment.
+      type: enhancement
+      link: https://github.com/elastic/integrations/pull/14769
 - version: "1.8.0"
   changes:
     - description: Add support for Kibana `9.0.0`.

@@ -1,6 +1,6 @@
 name: azure_application_insights
 title: Azure Application Insights Metrics Overview
-version: "1.8.0"
+version: "1.9.0"
 description: Collect application insights metrics from Azure Monitor with Elastic Agent.
 type: integration
 icons:
@@ -41,6 +41,7 @@ policy_templates:
   - name: app_insights
     title: Azure Application Insights Metrics
     description: Collect application insights metrics from Azure Monitor with Elastic Agent.
+    fips_compatible: false
     data_streams:
       - app_insights
     inputs:
@@ -61,6 +62,7 @@ policy_templates:
   - name: app_state
     title: Azure Application State Insights Metrics
     description: Collect application state related metrics from Azure Monitor with Elastic Agent.
+    fips_compatible: false
     data_streams:
       - app_state
     inputs:

@@ -1,3 +1,8 @@
+- version: "1.9.0"
+  changes:
+    - description: Add a flag `fips_compatible` to control whether the package is allowed in the ECH FedRAMP High environment.
+      type: enhancement
+      link: https://github.com/elastic/integrations/pull/14769
 - version: "1.8.0"
   changes:
     - description: Add support for Kibana `9.0.0`.

@@ -1,6 +1,6 @@
 name: azure_billing
 title: Azure Billing Metrics
-version: "1.8.0"
+version: "1.9.0"
 description: Collect billing metrics with Elastic Agent.
 type: integration
 icons:
@@ -78,6 +78,7 @@ policy_templates:
   - name: billing
     title: Azure Billing Metrics
     description: Collect billing information with Elastic Agent.
+    fips_compatible: false
     data_streams:
       - billing
     inputs:

@@ -1,4 +1,9 @@
 # newer versions go on top
+- version: "0.10.0"
+  changes:
+    - description: Add a flag `fips_compatible` to control whether the package is allowed in the ECH FedRAMP High environment.
+      type: enhancement
+      link: https://github.com/elastic/integrations/pull/14769
 - version: "0.9.0"
   changes:
     - description: Add support for Kibana `9.0.0`.

@@ -1,7 +1,7 @@
 format_version: "3.0.2"
 name: azure_functions
 title: "Azure Functions"
-version: "0.9.0"
+version: "0.10.0"
 source:
   license: "Elastic-2.0"
 description: "Get metrics and logs from Azure Functions"
@@ -44,6 +44,7 @@ policy_templates:
   - name: azure_functions
     title: Azure Functions logs and metrics
     description: Azure Functions logs and metrics with Elastic Agent.
+    fips_compatible: false
     data_streams:
       - functionapplogs
       - metrics

@@ -1,4 +1,9 @@
 # newer versions go on top
+- version: "0.4.0"
+  changes:
+    - description: Add a flag `fips_compatible` to control whether the package is allowed in the ECH FedRAMP High environment.
+      type: enhancement
+      link: https://github.com/elastic/integrations/pull/14769
 - version: "0.3.1"
   changes:
     - description: Add storage_account_container settings in the advanced options.

@@ -1,7 +1,7 @@
 format_version: 3.3.0
 name: azure_logs
 title: "Custom Azure Logs"
-version: 0.3.1
+version: "0.4.0"
 source:
   license: Elastic-2.0
 description: "Collect log events from Azure Event Hubs with Elastic Agent"
@@ -23,6 +23,7 @@ policy_templates:
     type: logs
     title: Collect Azure logs from Event Hub
     description: Collect Azure logs from Event Hub using the azure-eventhub input.
+    fips_compatible: false
     input: azure-eventhub
     template_path: input.yml.hbs
     vars:
@@ -33,12 +34,7 @@ policy_templates:
         required: true
         show_user: true
         description: >-
-          The event hub name that contains the logs to ingest.
-          Do not use the event hub namespace here. Elastic
-          recommends using one event hub for each integration.
-          Visit [Create an event hub](https://docs.elastic.co/integrations/azure#create-an-event-hub)
-          to learn more. Use event hub names up to 30 characters long
-          to avoid compatibility issues.
+          The event hub name that contains the logs to ingest. Do not use the event hub namespace here. Elastic recommends using one event hub for each integration. Visit [Create an event hub](https://docs.elastic.co/integrations/azure#create-an-event-hub) to learn more. Use event hub names up to 30 characters long to avoid compatibility issues.
       - name: consumer_group
         type: text
         title: Consumer Group
@@ -54,18 +50,15 @@ policy_templates:
         required: true
         show_user: true
         description: >-
-          The connection string required to communicate with Event Hubs.
-          See [Get an Event Hubs connection string](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-get-connection-string)
-          to learn more.
+          The connection string required to communicate with Event Hubs. See [Get an Event Hubs connection string](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-get-connection-string) to learn more.
       - name: storage_account
         type: text
         title: Storage Account
         multi: false
         required: true
         show_user: true
         description: >-
-          The name of the storage account where the consumer group's state/offsets
-          will be stored and updated.
+          The name of the storage account where the consumer group's state/offsets will be stored and updated.
       - name: storage_account_key
         type: password
         secret: true
@@ -74,24 +67,20 @@ policy_templates:
         required: true
         show_user: true
         description: >-
-          The storage account key, this key will be used to authorize access to
-          data in your storage account.
+          The storage account key, this key will be used to authorize access to data in your storage account.
       - name: data_stream.dataset
         type: text
         title: Dataset name
         description: >-
-          Dataset to write data to. Changing the dataset will send the data to a different index. 
-          You can't use `-` in the name of a dataset and only valid characters for
-          [Elasticsearch index names](https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-index_.html).
+          Dataset to write data to. Changing the dataset will send the data to a different index.  You can't use `-` in the name of a dataset and only valid characters for [Elasticsearch index names](https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-index_.html).
         default: azure_logs.generic
         required: true
         show_user: true
       - name: pipeline
         type: text
         title: Ingest Pipeline
         description: >-
-          The ingest pipeline ID to use for processing the data. If provided,
-          replaces the default pipeline for this integration.
+          The ingest pipeline ID to use for processing the data. If provided, replaces the default pipeline for this integration.
         required: false
         show_user: true
       - name: storage_account_container
@@ -100,15 +89,8 @@ policy_templates:
         multi: false
         required: false
         show_user: false
-        description:  >-
-          The storage account container where the integration stores the checkpoint
-          data for the event hub / consumer group. It is an advanced option to use with extreme care.
-          If you are using the [processor_version](https://www.elastic.co/guide/en/integrations/current/azure_logs.html#azure_logs-event-hub-processor-options) v1
-          (default option), you MUST use a dedicated storage account container for each event hub / consumer group pair.
-          For information about container name restrictions, please refer to the
-          [Container Names](https://docs.microsoft.com/en-us/rest/api/storageservices/naming-and-referencing-containers--blobs--and-metadata#container-names)
-          section in Microsoft's documentation.
-          If you don't specify a container name, the integration will automatically generate a default one for you.
+        description: >-
+          The storage account container where the integration stores the checkpoint data for the event hub / consumer group. It is an advanced option to use with extreme care. If you are using the [processor_version](https://www.elastic.co/guide/en/integrations/current/azure_logs.html#azure_logs-event-hub-processor-options) v1 (default option), you MUST use a dedicated storage account container for each event hub / consumer group pair. For information about container name restrictions, please refer to the [Container Names](https://docs.microsoft.com/en-us/rest/api/storageservices/naming-and-referencing-containers--blobs--and-metadata#container-names) section in Microsoft's documentation. If you don't specify a container name, the integration will automatically generate a default one for you.
       - name: resource_manager_endpoint
         type: text
         title: Resource Manager Endpoint
@@ -133,17 +115,14 @@ policy_templates:
         required: false
         show_user: false
         description: >
-          Processors are used to reduce the number of fields in the exported
-          event or to enhance the event with metadata. This runs in the agent
-          before the logs are parsed.
-          Check [Processors](https://www.elastic.co/guide/en/beats/filebeat/current/filtering-and-enhancing-data.html)
-          for details.
+          Processors are used to reduce the number of fields in the exported event or to enhance the event with metadata. This runs in the agent before the logs are parsed. Check [Processors](https://www.elastic.co/guide/en/beats/filebeat/current/filtering-and-enhancing-data.html) for details.
+
       - name: sanitize_newlines
         type: bool
         title: Sanitizes New Lines
         description: >
-          Removes new lines in logs to ensure proper formatting of JSON data and
-          avoid parsing issues during processing.
+          Removes new lines in logs to ensure proper formatting of JSON data and avoid parsing issues during processing.
+
         multi: false
         required: false
         show_user: false
@@ -153,9 +132,8 @@ policy_templates:
         show_user: false
         title: Sanitizes Single Quotes
         description: >
-          Replaces single quotes with double quotes (single quotes inside double
-          quotes are omitted) in logs to ensure proper formatting of JSON data
-          and avoid parsing issues during processing.
+          Replaces single quotes with double quotes (single quotes inside double quotes are omitted) in logs to ensure proper formatting of JSON data and avoid parsing issues during processing.
+
         type: bool
         multi: false
         default: false
@@ -166,15 +144,7 @@ policy_templates:
         required: false
         show_user: false
         default: v1
-        description: >-
-          The processor version that the integration should use.
-          Possible values are `v1` and `v2` (preview). 
-
-          The v2 event hub processor is in preview, so using the v1 processor
-          is recommended for typical use cases.
-
-          Default is `v1`.
-
+        description: "The processor version that the integration should use. Possible values are `v1` and `v2` (preview). \nThe v2 event hub processor is in preview, so using the v1 processor is recommended for typical use cases.\nDefault is `v1`."
       - name: processor_update_interval
         type: text
         title: Processor update interval
@@ -183,9 +153,8 @@ policy_templates:
         show_user: false
         default: 10s
         description: >-
-          (Processor v2 only) How often the processor should attempt to claim
-          partitions.
-
+          (Processor v2 only) How often the processor should attempt to claim partitions.
+
           Default is `10` seconds.
       - name: processor_start_position
         type: text
@@ -195,19 +164,15 @@ policy_templates:
         show_user: false
         default: earliest
         description: >-
-          (Processor v2 only) Controls from what position in the event hub
-          the processor should start processing messages for all partitions.
-
+          (Processor v2 only) Controls from what position in the event hub the processor should start processing messages for all partitions.
+
           Possible values are `earliest` and `latest`.
-
-          `earliest` starts processing messages from the last checkpoint, or the
-          beginning of the event hub if no checkpoint is available.
 
-          `latest` starts processing messages from the the latest event in the
-          event hub and continues to process new events as they arrive.
-
-          Default is `earliest`.
+          `earliest` starts processing messages from the last checkpoint, or the beginning of the event hub if no checkpoint is available.
+
+          `latest` starts processing messages from the the latest event in the event hub and continues to process new events as they arrive.
 
+          Default is `earliest`.
       - name: migrate_checkpoint
         type: bool
         title: Migrate checkpoint information
@@ -216,16 +181,11 @@ policy_templates:
         show_user: false
         default: false
         description: >-
-          (Processor v2 only) Flag to control if the processor should perform 
-          the checkpoint information migration from processor v1 to v2
-          at startup.
-
-          The checkpoint migration converts the checkpoint information
-          from the v1 format to the v2 format.
+          (Processor v2 only) Flag to control if the processor should perform  the checkpoint information migration from processor v1 to v2 at startup.
 
-          Default is `false`, which means the processor will not perform the
-          checkpoint migration.
+          The checkpoint migration converts the checkpoint information from the v1 format to the v2 format.
 
+          Default is `false`, which means the processor will not perform the checkpoint migration.
       - name: partition_receive_timeout
         type: text
         title: Partition receive timeout
@@ -234,14 +194,11 @@ policy_templates:
         show_user: false
         default: 5s
         description: >-
-          (Processor v2 only) Maximum time to wait before processing the
-          messages received from the event hub.
-
-          The partition consumer waits up to a "receive count" or a
-          "receive timeout", whichever comes first.
+          (Processor v2 only) Maximum time to wait before processing the messages received from the event hub.
 
-          Default is `5` seconds.
+          The partition consumer waits up to a "receive count" or a "receive timeout", whichever comes first.
 
+          Default is `5` seconds.
       - name: partition_receive_count
         type: text
         title: Partition receive count
@@ -250,14 +207,11 @@ policy_templates:
         show_user: false
         default: 100
         description: >-
-          (Processor v2 only) Maximum number of messages from the event hub
-          to wait for before processing them.
-
-          The partition consumer waits up to a "receive count" or a
-          "receive timeout", whichever comes first.
+          (Processor v2 only) Maximum number of messages from the event hub to wait for before processing them.
 
-          Default is `100` messages.
+          The partition consumer waits up to a "receive count" or a "receive timeout", whichever comes first.
 
+          Default is `100` messages.
 owner:
   github: elastic/obs-infraobs-integrations
   type: elastic