Merge pull request #265670 from MicrosoftDocs/repo_sync_working_branch

Taojunshen · web-flow · commit 062805e57d8a · 2024-02-08T09:31:59.000-08:00
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
diff --git a/articles/advisor/advisor-reference-reliability-recommendations.md b/articles/advisor/advisor-reference-reliability-recommendations.md
@@ -645,12 +645,13 @@ In active-active configuration, both instances of the VPN gateway establish S2S
 
 Learn more about [Virtual network gateway - VNetGatewayActiveActive (Enable Active-Active gateways for redundancy)](https://aka.ms/aa_vpnha_learnmore).
 
+<!--
 ### Use HEAD health probes
 
 For health probes, it’s a good practice to use the HEAD method, which reduces the amount of traffic load on your origins.
 
 Learn more about [Front Door - Use HEAD health probes](https://aka.ms/afd-use-health-probes).
-
+-->
 ### Use managed TLS certificates
 
 Front Door management of your TLS certificates reduces your operational costs and helps you to avoid costly outages caused by forgetting to renew a certificate.
@@ -663,6 +664,12 @@ If you only have a single origin, Front Door always routes traffic to that origi
 
 Learn more about [Health probe best practices](https://aka.ms/afd-disable-health-probes).
 
+### Use the same domain name on Azure Front Door and your origin
+
+We recommend that you preserve the original HTTP host name when you use a reverse proxy in front of a web application. Having a different host name at the reverse proxy than the one that's provided to the back-end application server can lead to cookies or redirect URLs that don't work properly. For example, session state can get lost, authentication can fail, or back-end URLs can inadvertently be exposed to end users. You can avoid these problems by preserving the host name of the initial request so that the application server sees the same domain as the web browser.
+
+Learn more about [Use the same domain name on Azure Front Door and your origin](https://aka.ms/afd-same-domain-origin).
+
 ## SAP for Azure
 
 ### Enable the 'concurrent-fencing' parameter in Pacemaker cofiguration in ASCS HA setup in SAP workloads
diff --git a/articles/azure-signalr/signalr-tutorial-build-blazor-server-chat-app.md b/articles/azure-signalr/signalr-tutorial-build-blazor-server-chat-app.md
@@ -371,7 +371,7 @@ Beginning in Visual Studio 2019 version 16.2.0, Azure SignalR Service is built i
 
 ## Publish to Azure
 
-When you deploy the Blazor app to Azure App Service, we recommend that you use [Azure SignalR Service](/aspnet/core/signalr/scale#azure-signalr-service). Azure SingalR Service allows for scaling up a Blazor Server app to a large number of concurrent SignalR connections. In addition, the SignalR service's global reach and high-performance datacenters significantly aid in reducing latency due to geography.
+When you deploy the Blazor app to Azure App Service, we recommend that you use [Azure SignalR Service](/aspnet/core/signalr/scale#azure-signalr-service). Azure SignalR Service allows for scaling up a Blazor Server app to a large number of concurrent SignalR connections. In addition, the SignalR service's global reach and high-performance datacenters significantly aid in reducing latency due to geography.
 
 > [!IMPORTANT]
 > In a Blazor Server app, UI states are maintained on the server side, which means a sticky server session is required to preserve state. If there is a single app server, sticky sessions are ensured by design. However, if there are multiple app servers, there are chances that the client negotiation and connection may go to different servers which may lead to an inconsistent UI state management in a Blazor app. Hence, it is recommended to enable sticky server sessions as shown below in *appsettings.json*:
@@ -422,7 +422,7 @@ When you deploy the Blazor app to Azure App Service, we recommend that you use [
    dotnet add package Microsoft.Azure.SignalR --version 1.5.1
    ```
 
-1. Add a call to `AddAzureSingalR()` in `Startup.ConfigureServices()` as demonstrated below.
+1. Add a call to `AddAzureSignalR()` in `Startup.ConfigureServices()` as demonstrated below.
 
    ```cs
    public void ConfigureServices(IServiceCollection services)
diff --git a/articles/communication-services/samples/includes/call-automation-ai-javascript.md b/articles/communication-services/samples/includes/call-automation-ai-javascript.md
@@ -56,9 +56,9 @@ Open the `.env` file to configure the following settings
 1. `CONNECTION_STRING`: Azure Communication Service resource's connection string.
 2. `CALLBACK_URI`: Base url of the app. (For local development replace the dev tunnel url)
 3. `COGNITIVE_SERVICE_ENDPOINT`: Azure AI Service endpoint
-4. `AZURE_OPENAI_SERVICE_KEY`: Azure Open AI service key
-5. `AZURE_OPENAI_SERVICE_ENDPOINT`: Azure Open AI endpoint
-6. `AZURE_OPENAI_DEPLOYMENT_MODEL_NAME`: Azure Open AI deployment name
+4. `AZURE_OPENAI_SERVICE_KEY`: Azure OpenAI service key
+5. `AZURE_OPENAI_SERVICE_ENDPOINT`: Azure OpenAI endpoint
+6. `AZURE_OPENAI_DEPLOYMENT_MODEL_NAME`: Azure OpenAI deployment name
 6. `AGENT_PHONE_NUMBER`: Agent phone number to transfer the call to resolve queries
 
 
diff --git a/articles/frontdoor/standard-premium/how-to-enable-private-link-internal-load-balancer.md b/articles/frontdoor/standard-premium/how-to-enable-private-link-internal-load-balancer.md
@@ -33,7 +33,7 @@ In this section, you map the Private Link service to a private endpoint created
 1. Select **+ Add an origin** to add new origin. Select or enter the following settings to configure the internal load balancer origin. 
 
     > [!NOTE] 
-    > The hostname must be a valid domain name, IPv4 or IPv6. The hostname can be the private IP of the internal load balancer or a domain name. If you are using a domain name, you must have a DNS record that resolves to the private IP of the internal load balancer. 
+    > The hostname must be a valid domain name, IPv4 or IPv6. The hostname can be the private IP of the internal load balancer or a domain name. 
 
     :::image type="content" source="../media/how-to-enable-private-link-internal-load-balancer/private-endpoint-internal-load-balancer-ip.png" alt-text="Screenshot of enabling private link to an internal load balancer using an IP address.":::
 
diff --git a/articles/governance/policy/concepts/scope.md b/articles/governance/policy/concepts/scope.md
@@ -25,8 +25,8 @@ the definition location to target for assignment. The [resources covered by Azur
 
 If the definition location is a:
 
-- **Subscription** - Only resources within that subscription can be assigned the policy definition.
-- **Management group** - Only resources within child management groups and child subscriptions can
+- **Subscription** - The subscription where policy is defined and resources within that subscription can be assigned the policy definition.
+- **Management group** - The management group where the policy is defined and resources within child management groups and child subscriptions can
   be assigned the policy definition. If you plan to apply the policy definition to several
   subscriptions, the location must be a management group that contains each subscription.
 
diff --git a/articles/oracle/oracle-db/oracle-database-network-plan.md b/articles/oracle/oracle-db/oracle-database-network-plan.md
@@ -12,7 +12,7 @@ ms.date: 12/12/2023
 
 # Network planning for Oracle Database@Azure
 
-In this article, you learn about the topologies and constraints for Oracle Database@Azure. After you purchase the offer through Azure Marketplace and provision the Exadata infrastructure, you'll then need to create your virtual machine cluster that will host your Oracle Exadata Database. These Oracle database clusters are connected to your Azure virtual network via a virtual NIC from your delegated subnet (delegated to ``Oracle.Database/networkAattachement``).  
+In this article, you learn about the topologies and constraints for Oracle Database@Azure. After you purchase the offer through Azure Marketplace and provision the Exadata infrastructure, you'll then need to create your virtual machine cluster that will host your Oracle Exadata Database. These Oracle database clusters are connected to your Azure virtual network via a virtual NIC from your delegated subnet (delegated to ``Oracle.Database/networkAttachement``).  
 
 ## Supported topologies
 
diff --git a/articles/reliability/reliability-traffic-manager.md b/articles/reliability/reliability-traffic-manager.md
@@ -6,7 +6,7 @@ ms.author: anaharris
 ms.topic: overview
 ms.custom: subject-reliability, references-regions
 ms.service: traffic-manager
-ms.date: 02/02/2024
+ms.date: 02/06/2024
 ---
 
 
diff --git a/articles/role-based-access-control/conditions-troubleshoot.md b/articles/role-based-access-control/conditions-troubleshoot.md
@@ -48,11 +48,19 @@ When you try to add a role assignment with a condition, you get an error similar
 
 `The given role assignment condition is invalid.`
 
-**Cause**
+**Cause 1**
+
+The `conditionVersion` property is set to "1.0".
+
+**Solution 1**
+
+Set `conditionVersion` property to "2.0".
+
+**Cause 2**
 
 Your condition is not formatted correctly. 
 
-**Solution**
+**Solution 2**
 
 Fix any [condition format or syntax](conditions-format.md) issues. Alternatively, add the condition using the [visual editor in the Azure portal](conditions-role-assignments-portal.md).
 
diff --git a/articles/search/search-language-support.md b/articles/search/search-language-support.md
@@ -43,7 +43,7 @@ Non-string fields and non-searchable string fields don't undergo lexical analysi
 
 ## Add text translation
 
-This article assumes translated strings alreach exist. If that's not the case, you can attach Azure AI services to an [enrichment pipeline](cognitive-search-concept-intro.md), invoking text translation during indexing. Text translation takes a dependency on the indexer feature and Azure AI services, but all setup is done within Azure AI Search. 
+This article assumes translated strings already exist. If that's not the case, you can attach Azure AI services to an [enrichment pipeline](cognitive-search-concept-intro.md), invoking text translation during indexing. Text translation takes a dependency on the indexer feature and Azure AI services, but all setup is done within Azure AI Search. 
 
 To add text translation, follow these steps:
 
diff --git a/articles/service-fabric/service-fabric-how-to-specify-environment-variables.md b/articles/service-fabric/service-fabric-how-to-specify-environment-variables.md
@@ -53,6 +53,6 @@ environment:
 ```
 
 ## Next steps
-To learn more about some of the core concepts that are discussed in this article, see the [Manage applications for multiple environments articles](service-fabric-manage-multiple-environment-app-configuration.md).
+To learn more about some of the core concepts that are discussed in this article, see the [Manage applications for multiple environments](service-fabric-manage-multiple-environment-app-configuration.md).
 
 For information about other app management capabilities that are available in Visual Studio, see [Manage your Service Fabric applications in Visual Studio](service-fabric-manage-application-in-visual-studio.md).
