Merge pull request #250312 from MicrosoftDocs/repo_sync_working_branch

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

Author: Taojunshen

articles/advisor/advisor-reference-reliability-recommendations.md

@@ -496,6 +496,13 @@ We identified the below thread resulted in an unhandled exception for your App a
 
 Learn more about [App service - AppServiceProactiveCrashMonitoring (Application code should be fixed as worker process crashed due to Unhandled Exception)](https://azure.github.io/AppService/2020/08/11/Crash-Monitoring-Feature-in-Azure-App-Service.html).
 
+### Consider changing your App Service configuration to 64-bit
+
+We identified your application is running in 32-bit and the memory is reaching the 2GB limit. 
+Consider switching to 64-bit processes so you can take advantage of the additional memory available in your Web Worker role. This action triggers a web app restart, so schedule accordingly.
+
+Learn more about [App service 32-bit limitations](/troubleshoot/azure/app-service/web-apps-performance-faqs#i-see-the-message-worker-process-requested-recycle-due-to-percent-memory-limit-how-do-i-address-this-issue).
+
 ## Next steps
 
 Learn more about [Reliability - Microsoft Azure Well Architected Framework](/azure/architecture/framework/resiliency/overview)

articles/ai-services/openai/concepts/use-your-data.md

@@ -191,7 +191,8 @@ For example, if you're creating a chatbot where the data consists of transcripti
 
 This system message can help improve the quality of the response by specifying the domain (in this case finance) and mentioning that the data consists of call transcriptions. It helps set the necessary context for the model to respond appropriately. 
 
-> [!NOTE] 
+> [!NOTE]
+> The system message is used to modify how GPT assistant responds to a user question based on retrieved documentation. It does not affect the retrieval process. If you'd like to provide instructions for the retrieval process, it is better to include them in the questions.
 > The system message is only guidance. The model might not adhere to every instruction specified because it has been primed with certain behaviors such as objectivity, and avoiding controversial statements. Unexpected behavior may occur if the system message contradicts with these behaviors. 
 
 ### Maximum response 
@@ -291,6 +292,8 @@ You can also use the available standalone web app to interact with your model us
 
 ![A screenshot of the web app interface.](../media/use-your-data/web-app.png)
 
+##### Web app customization
+
 You can also customize the app's frontend and backend logic. For example, you could change the icon that appears in the center of the app by updating `/frontend/src/assets/Azure.svg` and then redeploying the app [using the Azure CLI](https://github.com/microsoft/sample-app-aoai-chatGPT#deploy-with-the-azure-cli).  See the source code for the web app, and more information [on GitHub](https://github.com/microsoft/sample-app-aoai-chatGPT).
 
 When customizing the app, we recommend:
@@ -303,12 +306,11 @@ When customizing the app, we recommend:
 
 - Pulling changes from the `main` branch for the web app's source code frequently to ensure you have the latest bug fixes and improvements.
 
-#### Important considerations
+##### Important considerations
 
 - Publishing creates an Azure App Service in your subscription. It may incur costs depending on the 
 
 [pricing plan](https://azure.microsoft.com/pricing/details/app-service/windows/) you select. When you're done with your app, you can delete it from the Azure portal.
-- You can customize the frontend and backend logic of the web app.
 - By default, the app will only be accessible to you. To add authentication (for example, restrict access to the app to members of your Azure tenant):
 
     1. Go to the [Azure portal](https://portal.azure.com/#home) and search for the app name you specified during publishing. Select the web app, and go to the **Authentication** tab on the left navigation menu. Then select **Add an identity provider**. 
@@ -340,7 +342,7 @@ Deleting your web app does not delete your Cosmos DB instance automatically. To
 
 ### Using the API
 
-Consider setting the following parameters even if they are optional for using the API.
+After you upload your data through Azure OpenAI studio, you can make a call against Azure OpenAI models through APIs. Consider setting the following parameters even if they are optional for using the API.
 
 
 

articles/ai-services/openai/how-to/function-calling.md

@@ -64,8 +64,8 @@ functions= [
                     "description": "A comma separated list of features (i.e. beachfront, free wifi, etc.)"
                 }
             },
-            "required": ["location"],
-        },
+            "required": ["location"]
+        }
     }
 ]  
 

articles/aks/ingress-basic.md

@@ -75,9 +75,9 @@ To control image versions, you'll want to import them into your own Azure Contai
 REGISTRY_NAME=<REGISTRY_NAME>
 SOURCE_REGISTRY=registry.k8s.io
 CONTROLLER_IMAGE=ingress-nginx/controller
-CONTROLLER_TAG=v1.2.1
+CONTROLLER_TAG=v1.8.1
 PATCH_IMAGE=ingress-nginx/kube-webhook-certgen
-PATCH_TAG=v1.1.1
+PATCH_TAG=v2023040
 DEFAULTBACKEND_IMAGE=defaultbackend-amd64
 DEFAULTBACKEND_TAG=1.5
 
@@ -95,9 +95,9 @@ $RegistryName = "<REGISTRY_NAME>"
 $ResourceGroup = (Get-AzContainerRegistry | Where-Object {$_.name -eq $RegistryName} ).ResourceGroupName
 $SourceRegistry = "registry.k8s.io"
 $ControllerImage = "ingress-nginx/controller"
-$ControllerTag = "v1.2.1"
+$ControllerTag = "v1.8.1"
 $PatchImage = "ingress-nginx/kube-webhook-certgen"
-$PatchTag = "v1.1.1"
+$PatchTag = "v20230407"
 $DefaultBackendImage = "defaultbackend-amd64"
 $DefaultBackendTag = "1.5"
 
@@ -133,7 +133,7 @@ ACR_URL=<REGISTRY_URL>
 
 # Use Helm to deploy an NGINX ingress controller
 helm install ingress-nginx ingress-nginx/ingress-nginx \
-    --version 4.1.3 \
+    --version 4.7.1 \
     --namespace ingress-basic \
     --create-namespace \
     --set controller.replicaCount=2 \
@@ -208,7 +208,7 @@ ACR_URL=<REGISTRY_URL>
 
 # Use Helm to deploy an NGINX ingress controller
 helm install ingress-nginx ingress-nginx/ingress-nginx \
-    --version 4.1.3 \
+    --version 4.7.1 \
     --namespace ingress-basic \
     --create-namespace \
     --set controller.replicaCount=2 \

articles/aks/load-balancer-standard.md

@@ -455,6 +455,8 @@ The following annotations are supported for Kubernetes services with type `LoadB
 | `service.beta.kubernetes.io/azure-load-balancer-resource-group`   | Name of the resource group            | Specify the resource group of load balancer public IPs that aren't in the same resource group as the cluster infrastructure (node resource group).
 | `service.beta.kubernetes.io/azure-allowed-service-tags`           | List of allowed service tags          | Specify a list of allowed [service tags][service-tags] separated by commas.
 | `service.beta.kubernetes.io/azure-load-balancer-tcp-idle-timeout` | TCP idle timeouts in minutes          | Specify the time in minutes for TCP connection idle timeouts to occur on the load balancer. The default and minimum value is 4. The maximum value is 30. The value must be an integer.
+| `service.beta.kubernetes.io/azure-load-balancer-ipv4`             | IPv4 address                          | Specify the IPv4 address to assign to the load balancer.
+| `service.beta.kubernetes.io/azure-load-balancer-ipv6`             | IPv6 address                          | Specify the IPv6 address to assign to the load balancer.
 
 > [!NOTE]
 > `service.beta.kubernetes.io/azure-load-balancer-disable-tcp-reset` was deprecated in Kubernetes 1.18 and removed in 1.20.

articles/api-management/api-management-howto-mutual-certificates-for-clients.md

@@ -72,6 +72,9 @@ Configure the policy to validate one or more attributes including certificate is
 
 You can also create policy expressions with the [`context` variable](api-management-policy-expressions.md#ContextVariables) to check client certificates. Examples in the following sections show expressions using the `context.Request.Certificate` property and other `context` properties.
 
+> [!NOTE]
+> Mutual certificate authentication might not function correctly when the API Management gateway endpoint is exposed through the Application Gateway. This is because Application Gateway functions as a Layer 7 load balancer, establishing a distinct SSL connection with the backend API Management service. Consequently, the certificate attached by the client in the initial HTTP request will not be forwarded to APIM. However, as a workaround, you can transmit the certificate using the server variables option. For detailed instructions, refer to [Mutual Authentication Server Variables](../application-gateway/rewrite-http-headers-url.md#mutual-authentication-server-variables).
+
 > [!IMPORTANT]
 > * Starting May 2021, the `context.Request.Certificate` property only requests the certificate when the API Management instance's [`hostnameConfiguration`](/rest/api/apimanagement/current-ga/api-management-service/create-or-update#hostnameconfiguration) sets the `negotiateClientCertificate` property to True. By default, `negotiateClientCertificate` is set to False.
 > * If TLS renegotiation is disabled in your client, you may see TLS errors when requesting the certificate using the `context.Request.Certificate` property. If this occurs, enable TLS renegotiation settings in the client. 

articles/container-apps/tutorial-ci-cd-runners-jobs.md

@@ -823,24 +823,24 @@ az containerapp job create -n "$JOB_NAME" -g "$RESOURCE_GROUP" --environment "$E
 
 # [PowerShell](#tab/powershell)
 ```powershell
-az containerapp job create -n "$JOB_NAME" -g "$RESOURCE_GROUP" --environment "$ENVIRONMENT" \
-    --trigger-type Event \
-    --replica-timeout 1800 \
-    --replica-retry-limit 1 \
-    --replica-completion-count 1 \
-    --parallelism 1 \
-    --image "$CONTAINER_REGISTRY_NAME.azurecr.io/$CONTAINER_IMAGE_NAME" \
-    --min-executions 0 \
-    --max-executions 10 \
-    --polling-interval 30 \
-    --scale-rule-name "azure-pipelines" \
-    --scale-rule-type "azure-pipelines" \
-    --scale-rule-metadata "poolName=container-apps" "targetPipelinesQueueLength=1" \
-    --scale-rule-auth "personalAccessToken=personal-access-token" "organizationURL=organization-url" \
-    --cpu "2.0" \
-    --memory "4Gi" \
-    --secrets "personal-access-token=$AZP_TOKEN" "organization-url=$ORGANIZATION_URL" \
-    --env-vars "AZP_TOKEN=secretref:personal-access-token" "AZP_URL=secretref:organization-url" "AZP_POOL=$AZP_POOL" \
+az containerapp job create -n "$JOB_NAME" -g "$RESOURCE_GROUP" --environment "$ENVIRONMENT" `
+    --trigger-type Event `
+    --replica-timeout 1800 `
+    --replica-retry-limit 1 `
+    --replica-completion-count 1 `
+    --parallelism 1 `
+    --image "$CONTAINER_REGISTRY_NAME.azurecr.io/$CONTAINER_IMAGE_NAME" `
+    --min-executions 0 `
+    --max-executions 10 `
+    --polling-interval 30 `
+    --scale-rule-name "azure-pipelines" `
+    --scale-rule-type "azure-pipelines" `
+    --scale-rule-metadata "poolName=container-apps" "targetPipelinesQueueLength=1" `
+    --scale-rule-auth "personalAccessToken=personal-access-token" "organizationURL=organization-url" `
+    --cpu "2.0" `
+    --memory "4Gi" `
+    --secrets "personal-access-token=$AZP_TOKEN" "organization-url=$ORGANIZATION_URL" `
+    --env-vars "AZP_TOKEN=secretref:personal-access-token" "AZP_URL=secretref:organization-url" "AZP_POOL=$AZP_POOL" `
     --registry-server "$CONTAINER_REGISTRY_NAME.azurecr.io"
 ```
 

articles/mysql/flexible-server/concepts-high-availability.md

@@ -184,7 +184,8 @@ Data-in Replication isn't supported for HA servers. But Data-in Replication for
     1. Enable HA.
 
 - **To reduce downtime, can I fail over to the standby server during server restarts or while scaling up or down?** </br>
-Currently, when you do a scale up or scale down operation, the standby and primary are scaled at the same time. So failing over doesn't help. Allowing scaling up of the standby first, followed by failover, and then scaling up of the primary is on our roadmap but isn't supported yet.</br>
+Currently, Azure MySQL Flexible Server has utlized Planned Failover to optmize the HA operations including scaling up/down, and planned maintenance to help reduce the downtime.
+When such operations started, it would operate on the original standby instance first, followed by triggering a planned failover operation, and then operate on the original primary instance. </br>
 
 - **Can we change the availability mode (Zone-redundant HA/same-zone) of server** </br>
 If you create the server with Zone-redundant HA mode enabled then you can change from Zone-redundant HA to same-zone and vice versa. To change the availability mode, you can set **High Availability** to **Disabled** on the **High Availability** pane, and then set it back to **Zone Redundant or same-zone** and choose **High Availability Mode**.</br>  

articles/static-web-apps/getting-started.md

@@ -153,7 +153,7 @@ If you don't already have the [Azure Static Web Apps extension for Visual Studio
 
 If you're not going to continue to use this application, you can delete the Azure Static Web Apps instance through the extension.
 
-In the Visual Studio Code Explorer window, return to the _Resources_ section and under _Static Web Apps_, right-click **my-first-static-web-app** and select **Delete**.
+In the Visual Studio Code Azure window, return to the _Resources_ section and under _Static Web Apps_, right-click **my-first-static-web-app** and select **Delete**.
 
 ## Next steps