Merge branch 'docs-1209-update-image-tagging-in-metrics-and-observability' of github.com:SumoLogic/sumologic-documentation into docs-1209-update-image-tagging-in-metrics-and-observability

Author: jpipkin1

docs/cloud-soar/overview.md

@@ -7,7 +7,7 @@ sidebar_label: Overview
 import useBaseUrl from '@docusaurus/useBaseUrl';
 import StaticIpAddresses from '../reuse/static-ips-automation-service.md';
 
-Cloud SOAR automates triage, investigation, and remediation of threats for security professionals. The open integrations framework allows you to connect to many third-party applications. The platform provides full incident response lifecycle management with machine learning and threat hunting, accelerating mean time to respond (MTTR).
+Cloud SOAR automates triage, investigation, and remediation of threats for security professionals. Its open integrations framework allows you to connect to many third-party applications. The platform provides full incident response lifecycle management with machine learning and threat hunting, accelerating mean time to respond (MTTR).
 
 ## Why Cloud SOAR?
 

docs/observability/aws/deploy-use-aws-observability/before-you-deploy.md

@@ -36,9 +36,10 @@ If you are already collecting AWS metrics, logs, and/or events, we recommend tha
   :::note
   For the AWS Observability Solution, you must use the default scope when generating the Access ID and Key; custom scopes are not supported.
   :::
+* **[Disabled allowlist](https://www.sumologic.com/help/docs/manage/security/create-allowlist-ip-cidr-addresses/) for login and APIs**. During the installation/upgrade of the AWSO solution, the allowlist for login and APIs must remain disabled because the solution creates Lambda functions that uses AWS-managed public network infrastructure. When this Lambda makes outbound calls (such as to Sumo Logic APIs), the traffic is routed through AWS public IP address ranges, which are dynamic and cannot be fixed or predicted.
+* The AWS Observability solution comes with [pre-packaged alerts](https://www.sumologic.com/help/docs/observability/aws/deploy-use-aws-observability/configure-alerts/) in the form of Sumo Logic Monitors. To understand more about their capabilities, please visit the [Monitors page](https://www.sumologic.com/help/docs/alerts/monitors/).
 * **AWS credentials**. To deploy the solution, you will need to log onto the AWS Console. For the CloudFormation template deployment option, your AWS role must have the permissions described by this [JSON file](https://sumologic-appdev-aws-sam-apps.s3.amazonaws.com/AWSObservabilityCFTemplatePermissions.json). As necessary, you may add JSON text to an existing or a new policy associated with an AWS IAM role as described in the [AWS documentation](https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-create-and-attach-iam-policy.html). For Terraform deployment options, see the \*.tmpl files in this folder [aws-observability-terraform/source-module/templates/](https://github.com/SumoLogic/sumologic-solution-templates/tree/master/aws-observability-terraform/source-module/templates).
 * Set up the [AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-install.html) and configure the AWS CLI as described in the [AWS documentation](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-configure.html) if you would like to use an AWS profile for Terraform script based deployment.
-* The AWS Observability solution comes with pre-packaged alerts in the form of Sumo Logic Monitors. To understand more about their capabilities please visit the Monitors page.
 * For AWS services exporting to CloudWatch Logs, make sure logs are exported to log groups:
   * RDS - Enable publishing of logs to CloudWatch by following instructions in [Collect Amazon RDS CloudTrail logs](/docs/integrations/amazon-aws/rds/#collect-amazon-rds-cloudwatch-logs).
   * API Gateway - Enable Access Logs for each respective API by following instructions in Step 3 of [Collect access logs for AWS API Gateway](/docs/integrations/amazon-aws/api-gateway/#collect-access-logs-for-aws-api-gateway). Make sure you have the following prefix `/aws/apigateway/<apiid>/<stagename>` while creating the log group.

docs/platform-services/automation-service/app-central/integrations/microsoft-ews-graph.md

@@ -7,8 +7,8 @@ import useBaseUrl from '@docusaurus/useBaseUrl';
 
 <img src={useBaseUrl('/img/platform-services/automation-service/app-central/logos/microsoft-ews.png')} alt="microsoft-ews" width="100"/>
 
-***Version: 1.1  
-Updated: Oct 31, 2025***
+***Version: 1.2  
+Updated: Nov 21, 2025***
 
 Perform actions on Microsoft EWS mailboxes and accounts using Graph API. 
 
@@ -137,4 +137,7 @@ Email Gateway
 ## Change Log
 
 * September 10, 2025 - First upload
-* October 31, 2025 - Fixed issue in the **Download Mail As EML action**.
+* October 31, 2025 (v1.1) - Fixed issue in the **Download Mail As EML** action.
+* November 21, 2025 (v1.2)
+  + Fixed issue in the **Search Emails Extended** action.
+  + Converted `has_attachments` and `is_unread` from text fields to list fields with true/false options.