Merge pull request #273671 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/ai-services/content-safety/concepts/jailbreak-detection.md

@@ -71,7 +71,7 @@ Currently, the Prompt Shields API supports the English language. While our API d
 
 ### Text length limitations
 
-The maximum character limit for Prompt Shields is 10,000 characters per API call, between both the user prompts and documents combines. If your input (either user prompts or documents) exceeds these character limitations, you'll encounter an error.
+The maximum character limit for Prompt Shields allows for a user prompt of up to 10,000 characters, while the document array is restricted to a maximum of 5 documents with a combined total not exceeding 10,000 characters.
 
 ### TPS limitations
 

articles/ai-services/content-safety/how-to/use-blocklist.md

@@ -258,14 +258,18 @@ curl --location --request POST '<endpoint>/contentsafety/text/blocklists/<your_l
 > You can add multiple blocklistItems in one API call. Make the request body a JSON array of data groups:
 >
 > ```json
-> [{
->    "description": "string",
->    "text": "bleed"
-> },
 > {
->    "description": "string",
->    "text": "blood"
-> }]
+>    "blocklistItems": [
+>        {
+>            "description": "string",
+>            "text": "bleed"
+>        },
+>        {
+>            "description": "string",
+>            "text": "blood"
+>        }
+>    ]
+>}
 > ```
 
 

articles/aks/concepts-clusters-workloads.md

@@ -40,7 +40,7 @@ The control plane includes the following core Kubernetes components:
 | Component | Description |  
 | ----------------- | ------------- |  
 | *kube-apiserver* | The API server exposes the underlying Kubernetes APIs and provides the interaction for management tools, such as `kubectl` or the Kubernetes dashboard. |  
-| *etcd* | etcd is a highly available key vault store within Kubernetes that helps maintain the state of your Kubernetes cluster and configuration. |  
+| *etcd* | etcd is a highly available key-value store within Kubernetes that helps maintain the state of your Kubernetes cluster and configuration. |  
 | *kube-scheduler* | When you create or scale applications, the scheduler determines what nodes can run the workload and starts the identified nodes. |  
 | *kube-controller-manager* | The controller manager oversees a number of smaller controllers that perform actions such as replicating pods and handling node operations. |  
 

articles/aks/upgrade-aks-cluster.md

@@ -244,10 +244,10 @@ At times, you may have a long running workload on a certain pod and it can't be
 
     ```azurecli-interactive
     # Set drain timeout for a new node pool
-    az aks nodepool add -n mynodepool -g MyResourceGroup --cluster-name MyManagedCluster   --drainTimeoutInMinutes 100
+    az aks nodepool add -n mynodepool -g MyResourceGroup --cluster-name MyManagedCluster  --drain-timeout 100
 
     # Update drain timeout for an existing node pool
-    az aks nodepool update -n mynodepool -g MyResourceGroup --cluster-name MyManagedCluster --drainTimeoutInMinutes 45
+    az aks nodepool update -n mynodepool -g MyResourceGroup --cluster-name MyManagedCluster --drain-timeout 45
     ```
 
 #### Set node soak time value

articles/aks/what-is-aks.md

@@ -9,7 +9,7 @@ ms.date: 04/17/2024
 
 # What is Azure Kubernetes Service (AKS)?
 
-Azure Kubernetes Service (AKS) is a managed Kubernetes service that you can use to deploy and manage containerized applications. You don't need container orchestration expertise to use AKS. AKS reduces the complexity and operational overhead of managing Kubernetes by offloading much of that responsibility to Azure. AKS is an ideal platform for deploying and managing containerized applications that require high availability, scalability, and portability, and for deploying applications to multiple regions, using open-source tools, and integrating with existing DevOps tools.
+Azure Kubernetes Service (AKS) is a managed Kubernetes service that you can use to deploy and manage containerized applications. You need minimal container orchestration expertise to use AKS. AKS reduces the complexity and operational overhead of managing Kubernetes by offloading much of that responsibility to Azure. AKS is an ideal platform for deploying and managing containerized applications that require high availability, scalability, and portability, and for deploying applications to multiple regions, using open-source tools, and integrating with existing DevOps tools.
 
 This article is intended for platform administrators or developers who are looking for a scalable, automated, managed Kubernetes solution.
 

articles/azure-arc/vmware-vsphere/enable-guest-management-at-scale.md

@@ -25,7 +25,7 @@ Ensure the following before you install Arc agents at scale for VMware VMs:
 - The user account must have permissions listed in Azure Arc VMware Administrator role.
 - All the target machines are:
     - Powered on and the resource bridge has network connectivity to the host running the VM.
-    - Running a [supported operating system](../servers/prerequisites.md#supported-operating-systems).c
+    - Running a [supported operating system](../servers/prerequisites.md#supported-operating-systems).
     - VMware tools are installed on the machines. If VMware tools aren't installed, enable guest management operation is grayed out in the portal.  
         >[!Note]
         >You can use the [out-of-band method](./enable-guest-management-at-scale.md#approach-d-install-arc-agents-at-scale-using-out-of-band-approach) to install Arc agents if VMware tools aren't installed.  

articles/azure-monitor/app/java-get-started-supplemental.md

@@ -33,13 +33,13 @@ For more information, see [Use Application Insights Java In-Process Agent in Azu
 
 If you're using the *exec* form, add the parameter `-javaagent:"path/to/applicationinsights-agent-3.5.2.jar"` to the parameter list somewhere before the `"-jar"` parameter, for example:
 
-```
+```dockerfile
 ENTRYPOINT ["java", "-javaagent:path/to/applicationinsights-agent-3.5.2.jar", "-jar", "<myapp.jar>"]
 ```
 
 If you're using the *shell* form, add the Java Virtual Machine (JVM) arg `-javaagent:"path/to/applicationinsights-agent-3.5.2.jar"` somewhere before `-jar`, for example:
 
-```
+```dockerfile
 ENTRYPOINT java -javaagent:"path/to/applicationinsights-agent-3.5.2.jar" -jar <myapp.jar>
 ```
 
@@ -48,7 +48,7 @@ ENTRYPOINT java -javaagent:"path/to/applicationinsights-agent-3.5.2.jar" -jar <m
 
 A Dockerfile example:
 
-```
+```dockerfile
 FROM ...
 
 COPY target/*.jar app.jar
@@ -83,15 +83,15 @@ For information on setting up the Application Insights Java agent, see [Enabling
 
 If you installed Tomcat via `apt-get` or `yum`, you should have a file `/etc/tomcat8/tomcat8.conf`. Add this line to the end of that file:
 
-```
+```console
 JAVA_OPTS="$JAVA_OPTS -javaagent:path/to/applicationinsights-agent-3.5.2.jar"
 ```
 
 #### Tomcat installed via download and unzip
 
 If you installed Tomcat via download and unzip from [https://tomcat.apache.org](https://tomcat.apache.org), you should have a file `<tomcat>/bin/catalina.sh`. Create a new file in the same directory named `<tomcat>/bin/setenv.sh` with the following content:
 
-```
+```console
 CATALINA_OPTS="$CATALINA_OPTS -javaagent:path/to/applicationinsights-agent-3.5.2.jar"
 ```
 
@@ -103,13 +103,13 @@ If the file `<tomcat>/bin/setenv.sh` already exists, modify that file and add `-
 
 Locate the file `<tomcat>/bin/catalina.bat`. Create a new file in the same directory named `<tomcat>/bin/setenv.bat` with the following content:
 
-```
+```console
 set CATALINA_OPTS=%CATALINA_OPTS% -javaagent:path/to/applicationinsights-agent-3.5.2.jar
 ```
 
 Quotes aren't necessary, but if you want to include them, the proper placement is:
 
-```
+```console
 set "CATALINA_OPTS=%CATALINA_OPTS% -javaagent:path/to/applicationinsights-agent-3.5.2.jar"
 ```
 
@@ -181,7 +181,7 @@ The specified `applicationinsights.agent.id` value must be unique. You use the v
 
 Add these lines to `start.ini`:
 
-```
+```console
 --exec
 -javaagent:path/to/applicationinsights-agent-3.5.2.jar
 ```
@@ -209,7 +209,7 @@ Add `-javaagent:path/to/applicationinsights-agent-3.5.2.jar` to the existing `jv
 
 1. In `Generic JVM arguments`, add the following JVM argument.
 
-    ```
+    ```console
     -javaagent:path/to/applicationinsights-agent-3.5.2.jar
     ```
 
@@ -219,10 +219,10 @@ Add `-javaagent:path/to/applicationinsights-agent-3.5.2.jar` to the existing `jv
 
 Create a new file `jvm.options` in the server directory (for example, `<openliberty>/usr/servers/defaultServer`), and add this line:
 
-```
+```console
 -javaagent:path/to/applicationinsights-agent-3.5.2.jar
 ```
 
 ### Others
 
-See your application server documentation on how to add JVM args.
+See your application server documentation on how to add JVM args.

articles/azure-monitor/app/java-jmx-metrics-configuration.md

@@ -14,7 +14,7 @@ Application Insights Java 3.x collects some of the Java Management Extensions (J
 
 ## How do I collect extra JMX metrics?
 
-JMX metrics collection can be configured by adding a ```"jmxMetrics"``` section to the applicationinsights.json file. Enter a name for the metric as you want it to appear in Azure portal in application insights resource. Object name and attribute are required for each of the metrics you want collected.
+JMX metrics collection can be configured by adding a ```"jmxMetrics"``` section to the applicationinsights.json file. Enter a name for the metric as you want it to appear in Azure portal in application insights resource. Object name and attribute are required for each of the metrics you want collected. You may use `*` in object names for glob-style wildcard ([details](/azure/azure-monitor/app/java-standalone-config#java-management-extensions-metrics)).
 
 ## How do I know what metrics are available to configure?
 

articles/azure-monitor/app/java-spring-boot.md

@@ -18,7 +18,7 @@ There are two options for enabling Application Insights Java with Spring Boot: J
 
 Add the JVM arg `-javaagent:"path/to/applicationinsights-agent-3.5.2.jar"` somewhere before `-jar`, for example:
 
-```
+```console
 java -javaagent:"path/to/applicationinsights-agent-3.5.2.jar" -jar <myapp.jar>
 ```
 

articles/event-grid/event-schema.md

@@ -101,7 +101,7 @@ For custom topics, the event publisher determines the data object. The top-level
 
 When publishing events to custom topics, create subjects for your events that make it easy for subscribers to know whether they're interested in the event. Subscribers use the subject to filter and route events. Consider providing the path for where the event happened, so subscribers can filter by segments of that path. The path enables subscribers to narrowly or broadly filter events. For example, if you provide a three segment path like `/A/B/C` in the subject, subscribers can filter by the first segment `/A` to get a broad set of events. Those subscribers get events with subjects like `/A/B/C` or `/A/D/E`. Other subscribers can filter by `/A/B` to get a narrower set of events.
 
-Sometimes your subject needs more detail about what happened. For example, the **Storage Accounts** publisher provides the subject `/blobServices/default/containers/<container-name>/blobs/<file>` when a file is added to a container. A subscriber could filter by the path `/blobServices/default/containers/testcontainer` to get all events for that container but not other containers in the storage account. A subscriber could also filter or route by the suffix `.txt` to only work with text files.
+Sometimes your subject needs more detail about what happened. For example, the **Storage Accounts** publisher provides the subject `/blobServices/default/containers/<container-name>/blobs/<file>` when a file is added to a container. A subscriber could filter by the path `/blobServices/default/containers/<container-name>/` to get all events for that container but not other containers in the storage account. A subscriber could also filter or route by the suffix `.txt` to only work with text files.
 
 ## CloudEvents
 CloudEvents is the recommended event format to use. Azure Event Grid continues investing in features related to at least [CloudEvents JSON](https://github.com/cloudevents/spec/blob/v1.0.2/cloudevents/formats/json-format.md) format. Given the fact that some event sources like Azure services use the Event Grid format, the following table is provided to help you understand the transformation supported when using CloudEvents and Event Grid formats as an input schema in topics and as an output schema in event subscriptions. An Event Grid output schema can't be used when using CloudEvents as an input schema because CloudEvents supports [extension attributes](https://github.com/cloudevents/spec/blob/v1.0.2/cloudevents/primer.md#cloudevent-attribute-extensions) that aren't supported by the Event Grid schema.