Add/modify limitations

Author: karenzone

deploy-manage/security/fips-ingest.md

@@ -32,7 +32,7 @@ The default configurations provided in the binaries are FIPS compatible. Be sure
 
 ### TLS [ingest-limitations-tls]
 
-Only FIPS 140-2 compliant TLS protocols, ciphers, and curve types can be used. 
+Only FIPS 140-2 compliant TLS protocols, ciphers, and curve types are allowed to be used as listed below.
 * The supported TLS versions are `TLS v1.2` and `TLS v1.3`. 
 * The supported cipher suites are:
   * `TLS v1.2`: `ECDHE-RSA-AES-128-GCM-SHA256`, `ECDHE-RSA-AES-256-GCM-SHA384`, `ECDHE-ECDSA-AES-128-GCM-SHA256`, `ECDHE-ECDSA-AES-256-GCM-SHA384`
@@ -61,8 +61,10 @@ This impacts [Filebeat](beats://reference/filebeat/configuration-kerberos.md), [
 * The [Translate GUID processor](beats://reference/filebeat/processor-translate-guid.md) is not supported.
 * The [Fingerprint processor](beats://reference/filebeat/fingerprint.md) does not support the md5 and sha1 method. 
 * The [Community ID Network Flowhash processor](beats://reference/filebeat/community-id.md) is not supported. 
-* The [Azure module](beats://reference/filebeat/filebeat-module-azure.md) including the [Azure eventhub input](beats://reference/filebeat/filebeat-input-azure-eventhub.md) and the [Office 365 module (Beta)](beats://reference/filebeat/filebeat-module-o365.md) is currently not supported. The [Add Cloud Metadata processor](beats://reference/filebeat/add-cloud-metadata.md) does not support the Azure Virtual Machine provider currently. 
+* The [Azure module](beats://reference/filebeat/filebeat-module-azure.md) including the [Azure eventhub input](beats://reference/filebeat/filebeat-input-azure-eventhub.md) and the [Azure Blob Storage Input](https://www.elastic.co/docs/reference/beats/filebeat/filebeat-input-azure-blob-storage) are not currently supported. The [Add Cloud Metadata processor](beats://reference/filebeat/add-cloud-metadata.md) does not support the Azure Virtual Machine provider currently. 
+* The [Office 365 module (Beta)](beats://reference/filebeat/filebeat-module-o365.md) and the [Office 365 input (Deprecated)](https://www.elastic.co/docs/reference/beats/filebeat/filebeat-input-o365audit) are not supported. 
 * The [GCP Pub/Sub input](beats://reference/filebeat/filebeat-input-gcp-pubsub.md) is not supported for now. 
+* The [Entity Analytics input](https://www.elastic.co/docs/reference/beats/filebeat/filebeat-input-entity-analytics) is not supported. 
 
 ### Metricbeat [ingest-metricbeat-limitations]
 
@@ -71,6 +73,7 @@ This impacts [Filebeat](beats://reference/filebeat/configuration-kerberos.md), [
 * The [Fingerprint processor](beats://reference/metricbeat/fingerprint.md) does not support the md5 and sha1 method. 
 * The [Community ID Network Flowhash processor](beats://reference/metricbeat/community-id.md) is not supported. 
 * The [Azure module](beats://reference/metricbeat/metricbeat-module-azure.md) is currently not supported. The [Add Cloud Metadata processor](beats://reference/metricbeat/add-cloud-metadata.md) does not support the Azure Virtual Machine provider currently. 
+* The [Google Cloud Platform module](https://www.elastic.co/docs/reference/beats/metricbeat/metricbeat-module-gcp) is currently not supported. 
 * The [Beta KVM module](beats://reference/metricbeat/metricbeat-module-kvm.md) is not yet supported.
 * The [Mongo DB module](beats://reference/metricbeat/metricbeat-module-mongodb.md) is not supported. 
 * The [MySQL](beats://reference/metricbeat/metricbeat-module-mysql.md), [PostgreSQL](beats://reference/metricbeat/metricbeat-module-postgresql.md), [MSSQL](beats://reference/metricbeat/metricbeat-module-mssql.md) and [SQL](beats://reference/metricbeat/metricbeat-module-sql.md) modules are not supported. 
@@ -79,8 +82,7 @@ This impacts [Filebeat](beats://reference/filebeat/configuration-kerberos.md), [
 ### Elastic Agent and Fleet Server [ingest-limitations-agent]
 
 When you use {{agent}} and {{fleet-server}}, these limitations apply:
-* The [Prometheus Receiver](https://www.elastic.co/docs/reference/integrations/prometheus) is not supported. 
-* Running {{agent}} in [OpenTelemetry mode](https://github.com/elastic/elastic-agent/blob/main/internal/pkg/otel/README.md) is not yet supported. 
+* Running {{agent}} in [OpenTelemetry mode](https://github.com/elastic/elastic-agent/blob/main/internal/pkg/otel/README.md) is not yet supported. This includes all receivers, such as Filebeat Receiver, Metricbeat Receiver, [Prometheus Receiver](https://www.elastic.co/docs/reference/integrations/prometheus).
 * Some Elastic Integrations are not FIPS compatible, as they depend on functionality that is not yet supported for FIPS configuration. In general, when using {{agent}} and {{fleet-server}}, the same restrictions listed previously for {{metricbeat}} and {{filebeat}} modules, inputs, and processors apply.
 
   These Elastic Integrations have components that are **not** FIPS compatible, and **cannot** be used in FIPS environments, even if combined with other ingest tools that offer FIPS mode.