Merge pull request #166965 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to master to sync with https://github.com/MicrosoftDocs/azure-docs (branch master)

Author: huypub

articles/cognitive-services/text-analytics/includes/entity-types/identification-entities.md

@@ -113,7 +113,7 @@ This category contains the following entity:
 
         IBAN codes for payment instruction information. Also returned with `domain=phi`.
 
-        To get this entity category, add `InternationlBankingAccountNumber` to the `pii-categories` parameter. `InternationlBankingAccountNumber` will be returned in the API response if detected.
+        To get this entity category, add `InternationalBankingAccountNumber` to the `pii-categories` parameter. `InternationalBankingAccountNumber` will be returned in the API response if detected.
       
     :::column-end:::
     :::column span="2":::

articles/frontdoor/front-door-http-headers-protocol.md

@@ -39,7 +39,7 @@ Front Door includes headers for an incoming request unless they're removed becau
 | X-Forwarded-For | *X-Forwarded-For: 127.0.0.1* </br> The X-Forwarded-For (XFF) HTTP header field often identifies the originating IP address of a client connecting to a web server through an HTTP proxy or load balancer. If there's an existing XFF header, then Front Door appends the client socket IP to it or adds the XFF header with the client socket IP. |
 | X-Forwarded-Host | *X-Forwarded-Host: contoso.azurefd.net* </br> The X-Forwarded-Host HTTP header field is a common method used to identify the original host requested by the client in the Host HTTP request header. This is because the host name from Front Door may differ for the backend server handling the request. Any previous value will be overridden by Front Door. |
 | X-Forwarded-Proto | *X-Forwarded-Proto: http* </br> The X-Forwarded-Proto HTTP header field is often used to identify the originating protocol of an HTTP request. Front Door based on configuration might communicate with the backend by using HTTPS. This is true even if the request to the reverse proxy is HTTP. Any previous value will be overridden by Front Door. |
-| X-FD-HealthProbe | X-FD-HealthProbe HTTP header field is used to identify the health probe from Front Door. If this header set to 1, the request is health probe. You can use when want to strict access from particular Front Door with X-Forwarded-Host header field. |
+| X-FD-HealthProbe | X-FD-HealthProbe HTTP header field is used to identify the health probe from Front Door. If this header is set to 1, the request is from the health probe. It can be used to restrict access from Front Door with a particular value for the X-Forwarded-Host header field. |
 | X-Azure-FDID | *X-Azure-FDID header: 437c82cd-360a-4a54-94c3-5ff707647783* </br> This field contains frontdoorID that can be used to identify which Front Door the incoming request is from. This field is populated by Front Door service. | 
 
 ## Front Door to client

articles/frontdoor/standard-premium/overview.md

@@ -23,7 +23,7 @@ With Azure Front Door Standard/Premium, you can transform your global consumer a
 
 Azure Front Door Standard/Premium works at Layer 7 (HTTP/HTTPS layer) using anycast protocol with split TCP and Microsoft's global network to improve global connectivity. Based on your customized routing method using rules set, you can ensure that Azure Front Door will route your client requests to the fastest and most available origin. An application origin is any Internet-facing service hosted inside or outside of Azure. Azure Front Door Standard/Premium provides a range of traffic-routing methods and origin health monitoring options to suit different application needs and automatic failover scenarios. Similar to Traffic Manager, Front Door is resilient to failures, including failures to an entire Azure region.
 
-Azure Front Door also protect your app at the edges with integrated Web Application Firewall protection, Bot Protection, and built-in layer 3/layer 4 distributed denial of service (DDoS) protection. It also secures your private back-ends with private link service. Azure Front Door gives you Microsoft’s best-in-practice security at global scale.  
+Azure Front Door also protects your app at the edges with integrated Web Application Firewall protection, Bot Protection, and built-in layer 3/layer 4 distributed denial of service (DDoS) protection. It also secures your private back-ends with private link service. Azure Front Door gives you Microsoft’s best-in-practice security at global scale.  
 
 >[!NOTE]
 > Azure provides a suite of fully managed load-balancing solutions for your scenarios.

articles/sentinel/sap-solution-deploy-alternate.md

@@ -253,7 +253,7 @@ x509pkicert = <SET_YOUR_X509_PKI_CERTIFICATE>
 appserver = <SET_YOUR_SAPCTRL_SERVER IP OR FQDN>
 instance = <SET_YOUR_SAP_INSTANCE NUMBER, example 10>
 abapseverity = <SET_ABAP_SEVERITY 0 = All logs ; 1 = Warning ; 2 = Error>
-abaptz = <SET_ABAP_TZ for example GMT-3>
+abaptz = <SET_ABAP_TZ --Use ONLY GMT FORMAT-- example - For OS Timezone = NZST use abaptz = GMT+12>
 
 [File Extraction JAVA]
 javaosuser = <SET_YOUR_JAVAADM_LIKE_USER>
@@ -265,7 +265,7 @@ javax509pkicert = <SET_YOUR_X509_PKI_CERTIFICATE>
 javaappserver = <SET_YOUR_JAVA_SAPCTRL_SERVER IP ADDRESS OR FQDN>
 javainstance = <SET_YOUR_JAVA_SAP_INSTANCE for example 10>
 javaseverity = <SET_JAVA_SEVERITY  0 = All logs ; 1 = Warning ; 2 = Error>
-javatz = <SET_JAVA_TZ for example GMT-3>
+javatz = <SET_JAVA_TZ --Use ONLY GMT FORMAT-- example - For OS Timezone = NZST use javatz = GMT+12>
 ```
 
 ### Define the SAP logs that are sent to Azure Sentinel

articles/sentinel/sap-solution-log-reference.md

@@ -192,13 +192,13 @@ This article is intended for advanced SAP users.
 
 ## ABAP Gateway log
 
-- **Name in Azure Sentinel**: `GW_CL`
+- **Name in Azure Sentinel**: `ABAPOS_GW_CL`
 
 - **Related SAP documentation**: [SAP Help Portal](https://help.sap.com/viewer/62b4de4187cb43668d15dac48fc00732/7.5.7/en-US/48b2a710ca1c3079e10000000a42189b.html)
 
 - **Log purpose**: Monitors Gateway activities. Available by the SAP Control Web Service. This log is generated with data across all clients.
 
-### GW_CL log schema
+### ABAPOS_GW_CL log schema
 
 | Field        | Description      |
 | ------------ | ---------------- |
@@ -212,15 +212,15 @@ This article is intended for advanced SAP users.
 
 ## ABAP ICM log
 
-- **Name in Azure Sentinel**: `ICM_CL`
+- **Name in Azure Sentinel**: `ABAPOS_ICM_CL`
 
 - **Related SAP documentation**: [SAP Help Portal](https://help.sap.com/viewer/683d6a1797a34730a6e005d1e8de6f22/7.52.4/en-US/a10ec40d01e740b58d0a5231736c434e.html)
 
 - **Log purpose**: Records inbound and outbound requests and compiles statistics of the HTTP requests.
 
     Available by the SAP Control Web Service. This log is generated with data across all clients.
 
-### ICM_CL log schema
+### ABAPOS_ICM_CL log schema
 
 | Field        | Description      |
 | ------------ | ---------------- |
@@ -438,15 +438,15 @@ This article is intended for advanced SAP users.
 
 ## ABAP SysLog
 
-- **Name in Azure Sentinel**: `SysLog_CL`
+- **Name in Azure Sentinel**: `ABAPOS_Syslog_CL`
 
 - **Related SAP documentation**: [SAP Help Portal](https://help.sap.com/viewer/56bf1265a92e4b4d9a72448c579887af/7.5.7/en-US/c769bcbaf36611d3a6510000e835363f.html)
 
 - **Log purpose**: Records all SAP NetWeaver Application Server (SAP NetWeaver AS) ABAP system errors, warnings, user locks because of failed sign-in attempts from known users, and process messages.
 
     Available by the SAP Control Web Service. This log is generated with data across all clients.
 
-### SysLog_CL log schema
+### ABAPOS_Syslog_CL log schema
 
 
 | Field            | Description            |
@@ -522,15 +522,15 @@ This article is intended for advanced SAP users.
 
 ## ABAP WorkProcess log
 
-- **Name in Azure Sentinel**: `WP_CL`
+- **Name in Azure Sentinel**: `ABAPOS_WP_CL`
 
 - **Related SAP documentation**: [SAP Help Portal](https://help.sap.com/viewer/d0739d980ecf42ae9f3b4c19e21a4b6e/7.3.15/en-US/46fb763b6d4c5515e10000000a1553f6.html)
 
 - **Log purpose**: Combines all work process logs. (default: `dev_*`).
 
     Available by the SAP Control Web Service. This log is generated with data across all clients.
 
-### WP_CL log schema
+### ABAPOS_WP_CL log schema
 
 
 | Field        | Description         |