Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into feedbackUpdate

Author: roygara

articles/azure-monitor/app/java-in-process-agent.md

@@ -2,7 +2,7 @@
 title: Azure Monitor Application Insights Java
 description: Application performance monitoring for Java applications running in any environment without requiring code modification. The article also discusses distributed tracing and the application map.
 ms.topic: conceptual
-ms.date: 12/14/2022
+ms.date: 01/18/2023
 ms.devlang: java
 ms.custom: devx-track-java, ignite-2022
 ms.reviewer: mmcc
@@ -32,7 +32,7 @@ This section shows you how to download the auto-instrumentation jar file.
 
 #### Download the jar file
 
-Download the [applicationinsights-agent-3.4.7.jar](https://github.com/microsoft/ApplicationInsights-Java/releases/download/3.4.7/applicationinsights-agent-3.4.7.jar) file.
+Download the [applicationinsights-agent-3.4.8.jar](https://github.com/microsoft/ApplicationInsights-Java/releases/download/3.4.8/applicationinsights-agent-3.4.8.jar) file.
 
 > [!WARNING]
 >
@@ -63,7 +63,7 @@ Download the [applicationinsights-agent-3.4.7.jar](https://github.com/microsoft/
 
 #### Point the JVM to the jar file
 
-Add `-javaagent:"path/to/applicationinsights-agent-3.4.7.jar"` to your application's JVM args.
+Add `-javaagent:"path/to/applicationinsights-agent-3.4.8.jar"` to your application's JVM args.
 
 > [!TIP]
 > For help with configuring your application's JVM args, see [Tips for updating your JVM args](./java-standalone-arguments.md).
@@ -80,7 +80,7 @@ If you develop a Spring Boot application, you can replace the JVM argument by a
         APPLICATIONINSIGHTS_CONNECTION_STRING=<Copy connection string from Application Insights Resource Overview>
         ```
 
-   - Create a configuration file named `applicationinsights.json`. Place it in the same directory as `applicationinsights-agent-3.4.7.jar` with the following content:
+   - Create a configuration file named `applicationinsights.json`. Place it in the same directory as `applicationinsights-agent-3.4.8.jar` with the following content:
 
         ```json
         {

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

@@ -2,7 +2,7 @@
 title: Configure Azure Monitor Application Insights for Spring Boot
 description: How to configure Azure Monitor Application Insights for Spring Boot applications
 ms.topic: conceptual
-ms.date: 12/14/2022
+ms.date: 01/18/2023
 ms.devlang: java
 ms.custom: devx-track-java
 ---
@@ -13,24 +13,24 @@ There are two options for enabling Application Insights Java with Spring Boot: J
 
 ## Enabling with JVM argument 
 
-Add the JVM arg `-javaagent:"path/to/applicationinsights-agent-3.4.7.jar"` somewhere before `-jar`, for example:
+Add the JVM arg `-javaagent:"path/to/applicationinsights-agent-3.4.8.jar"` somewhere before `-jar`, for example:
 
 ```
-java -javaagent:"path/to/applicationinsights-agent-3.4.7.jar" -jar <myapp.jar>
+java -javaagent:"path/to/applicationinsights-agent-3.4.8.jar" -jar <myapp.jar>
 ```
 
 ### Spring Boot via Docker entry point
 
-If you're using the *exec* form, add the parameter `-javaagent:"path/to/applicationinsights-agent-3.4.7.jar"` to the parameter list somewhere before the `"-jar"` parameter, for example:
+If you're using the *exec* form, add the parameter `-javaagent:"path/to/applicationinsights-agent-3.4.8.jar"` to the parameter list somewhere before the `"-jar"` parameter, for example:
 
 ```
-ENTRYPOINT ["java", "-javaagent:path/to/applicationinsights-agent-3.4.7.jar", "-jar", "<myapp.jar>"]
+ENTRYPOINT ["java", "-javaagent:path/to/applicationinsights-agent-3.4.8.jar", "-jar", "<myapp.jar>"]
 ```
 
-If you're using the *shell* form, add the JVM arg `-javaagent:"path/to/applicationinsights-agent-3.4.7.jar"` somewhere before `-jar`, for example:
+If you're using the *shell* form, add the JVM arg `-javaagent:"path/to/applicationinsights-agent-3.4.8.jar"` somewhere before `-jar`, for example:
 
 ```
-ENTRYPOINT java -javaagent:"path/to/applicationinsights-agent-3.4.7.jar" -jar <myapp.jar>
+ENTRYPOINT java -javaagent:"path/to/applicationinsights-agent-3.4.8.jar" -jar <myapp.jar>
 ```
 
 ### Configuration

articles/azure-monitor/app/java-standalone-arguments.md

@@ -2,7 +2,7 @@
 title: Add the JVM arg - Application Insights for Java
 description: Learn how to add the JVM arg that enables Application Insights for Java.
 ms.topic: conceptual
-ms.date: 12/14/2022
+ms.date: 01/18/2023
 ms.devlang: java
 ms.custom: devx-track-java
 ms.reviewer: mmcc
@@ -34,18 +34,18 @@ If you're using a third-party container image that you can't modify, mount the A
 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:
 
 ```
-JAVA_OPTS="$JAVA_OPTS -javaagent:path/to/applicationinsights-agent-3.4.7.jar"
+JAVA_OPTS="$JAVA_OPTS -javaagent:path/to/applicationinsights-agent-3.4.8.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:
 
 ```
-CATALINA_OPTS="$CATALINA_OPTS -javaagent:path/to/applicationinsights-agent-3.4.7.jar"
+CATALINA_OPTS="$CATALINA_OPTS -javaagent:path/to/applicationinsights-agent-3.4.8.jar"
 ```
 
-If the file `<tomcat>/bin/setenv.sh` already exists, modify that file and add `-javaagent:path/to/applicationinsights-agent-3.4.7.jar` to `CATALINA_OPTS`.
+If the file `<tomcat>/bin/setenv.sh` already exists, modify that file and add `-javaagent:path/to/applicationinsights-agent-3.4.8.jar` to `CATALINA_OPTS`.
 
 ## Tomcat 8 (Windows)
 
@@ -54,35 +54,35 @@ 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:
 
 ```
-set CATALINA_OPTS=%CATALINA_OPTS% -javaagent:path/to/applicationinsights-agent-3.4.7.jar
+set CATALINA_OPTS=%CATALINA_OPTS% -javaagent:path/to/applicationinsights-agent-3.4.8.jar
 ```
 
 Quotes aren't necessary, but if you want to include them, the proper placement is:
 
 ```
-set "CATALINA_OPTS=%CATALINA_OPTS% -javaagent:path/to/applicationinsights-agent-3.4.7.jar"
+set "CATALINA_OPTS=%CATALINA_OPTS% -javaagent:path/to/applicationinsights-agent-3.4.8.jar"
 ```
 
-If the file `<tomcat>/bin/setenv.bat` already exists, modify that file and add `-javaagent:path/to/applicationinsights-agent-3.4.7.jar` to `CATALINA_OPTS`.
+If the file `<tomcat>/bin/setenv.bat` already exists, modify that file and add `-javaagent:path/to/applicationinsights-agent-3.4.8.jar` to `CATALINA_OPTS`.
 
 ### Run Tomcat as a Windows service
 
-Locate the file `<tomcat>/bin/tomcat8w.exe`. Run that executable and add `-javaagent:path/to/applicationinsights-agent-3.4.7.jar` to the `Java Options` under the `Java` tab.
+Locate the file `<tomcat>/bin/tomcat8w.exe`. Run that executable and add `-javaagent:path/to/applicationinsights-agent-3.4.8.jar` to the `Java Options` under the `Java` tab.
 
 ## JBoss EAP 7
 
 ### Standalone server
 
-Add `-javaagent:path/to/applicationinsights-agent-3.4.7.jar` to the existing `JAVA_OPTS` environment variable in the file `JBOSS_HOME/bin/standalone.conf` (Linux) or `JBOSS_HOME/bin/standalone.conf.bat` (Windows):
+Add `-javaagent:path/to/applicationinsights-agent-3.4.8.jar` to the existing `JAVA_OPTS` environment variable in the file `JBOSS_HOME/bin/standalone.conf` (Linux) or `JBOSS_HOME/bin/standalone.conf.bat` (Windows):
 
 ```java    ...
-    JAVA_OPTS="-javaagent:path/to/applicationinsights-agent-3.4.7.jar -Xms1303m -Xmx1303m ..."
+    JAVA_OPTS="-javaagent:path/to/applicationinsights-agent-3.4.8.jar -Xms1303m -Xmx1303m ..."
     ...
 ```
 
 ### Domain server
 
-Add `-javaagent:path/to/applicationinsights-agent-3.4.7.jar` to the existing `jvm-options` in `JBOSS_HOME/domain/configuration/host.xml`:
+Add `-javaagent:path/to/applicationinsights-agent-3.4.8.jar` to the existing `jvm-options` in `JBOSS_HOME/domain/configuration/host.xml`:
 
 ```xml
 ...
@@ -92,7 +92,7 @@ Add `-javaagent:path/to/applicationinsights-agent-3.4.7.jar` to the existing `jv
         <jvm-options>
             <option value="-server"/>
             <!--Add Java agent jar file here-->
-            <option value="-javaagent:path/to/applicationinsights-agent-3.4.7.jar"/>
+            <option value="-javaagent:path/to/applicationinsights-agent-3.4.8.jar"/>
             <option value="-XX:MetaspaceSize=96m"/>
             <option value="-XX:MaxMetaspaceSize=256m"/>
         </jvm-options>
@@ -131,19 +131,19 @@ Add these lines to `start.ini`:
 
 ```
 --exec
--javaagent:path/to/applicationinsights-agent-3.4.7.jar
+-javaagent:path/to/applicationinsights-agent-3.4.8.jar
 ```
 
 ## Payara 5
 
-Add `-javaagent:path/to/applicationinsights-agent-3.4.7.jar` to the existing `jvm-options` in `glassfish/domains/domain1/config/domain.xml`:
+Add `-javaagent:path/to/applicationinsights-agent-3.4.8.jar` to the existing `jvm-options` in `glassfish/domains/domain1/config/domain.xml`:
 
 ```xml
 ...
 <java-config ...>
     <!--Edit the JVM options here-->
     <jvm-options>
-        -javaagent:path/to/applicationinsights-agent-3.4.7.jar>
+        -javaagent:path/to/applicationinsights-agent-3.4.8.jar>
     </jvm-options>
         ...
 </java-config>
@@ -162,7 +162,7 @@ Add `-javaagent:path/to/applicationinsights-agent-3.4.7.jar` to the existing `jv
 1. In `Generic JVM arguments`, add the following JVM argument:
     
     ```
-    -javaagent:path/to/applicationinsights-agent-3.4.7.jar
+    -javaagent:path/to/applicationinsights-agent-3.4.8.jar
     ```
 
 1. Save and restart the application server.
@@ -172,7 +172,7 @@ Add `-javaagent:path/to/applicationinsights-agent-3.4.7.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:
 
 ```
--javaagent:path/to/applicationinsights-agent-3.4.7.jar
+-javaagent:path/to/applicationinsights-agent-3.4.8.jar
 ```
 
 ## Others

articles/azure-monitor/app/java-standalone-config.md

@@ -2,7 +2,7 @@
 title: Configuration options - Azure Monitor Application Insights for Java
 description: This article shows you how to configure Azure Monitor Application Insights for Java.
 ms.topic: conceptual
-ms.date: 12/14/2022
+ms.date: 01/18/2023
 ms.devlang: java
 ms.custom: devx-track-java
 ms.reviewer: mmcc
@@ -31,14 +31,14 @@ You'll find more information and configuration options in the following sections
 
 ## Configuration file path
 
-By default, Application Insights Java 3.x expects the configuration file to be named `applicationinsights.json`, and to be located in the same directory as `applicationinsights-agent-3.4.7.jar`.
+By default, Application Insights Java 3.x expects the configuration file to be named `applicationinsights.json`, and to be located in the same directory as `applicationinsights-agent-3.4.8.jar`.
 
 You can specify your own configuration file path by using one of these two options:
 
 * `APPLICATIONINSIGHTS_CONFIGURATION_FILE` environment variable
 * `applicationinsights.configuration.file` Java system property
 
-If you specify a relative path, it will be resolved relative to the directory where `applicationinsights-agent-3.4.7.jar` is located.
+If you specify a relative path, it will be resolved relative to the directory where `applicationinsights-agent-3.4.8.jar` is located.
 
 Alternatively, instead of using a configuration file, you can specify the entire _content_ of the JSON configuration via the environment variable `APPLICATIONINSIGHTS_CONFIGURATION_CONTENT`.
 
@@ -61,7 +61,7 @@ Or you can set the connection string by using the Java system property `applicat
 
 You can also set the connection string by specifying a file to load the connection string from.
 
-If you specify a relative path, it's resolved relative to the directory where `applicationinsights-agent-3.4.7.jar` is located.
+If you specify a relative path, it's resolved relative to the directory where `applicationinsights-agent-3.4.8.jar` is located.
 
 ```json
 {
@@ -323,6 +323,34 @@ Cloud role name overrides allow you to override the [default cloud role name](#c
 }
 ```
 
+## Connection string configured at runtime
+
+Starting from version 3.4.8, if you need the ability to configure the connection string at runtime,
+add this property to your json configuration:
+
+```json
+{
+  "connectionStringConfiguredAtRuntime": true
+}
+```
+
+and add `applicationinsights-core` to your application:
+
+```xml
+<dependency>
+  <groupId>com.microsoft.azure</groupId>
+  <artifactId>applicationinsights-core</artifactId>
+  <version>3.4.8</version>
+</dependency>
+```
+
+and use the static `configure(String)` method in the class
+`com.microsoft.applicationinsights.connectionstring.ConnectionString`.
+
+> [!NOTE]
+> Any telemetry that is captured prior to configuring the connection string will be dropped,
+> so it is best to configure it as early as possible in your application startup.
+
 ## Autocollect InProc dependencies (preview)
 
 Starting from version 3.2.0, if you want to capture controller "InProc" dependencies, use the following configuration:
@@ -754,7 +782,7 @@ In the preceding configuration example:
 
 * `level` can be one of `OFF`, `ERROR`, `WARN`, `INFO`, `DEBUG`, or `TRACE`.
 * `path` can be an absolute or relative path. Relative paths are resolved against the directory where
-`applicationinsights-agent-3.4.7.jar` is located.
+`applicationinsights-agent-3.4.8.jar` is located.
 
 Starting from version 3.0.2, you can also set the self-diagnostics `level` by using the environment variable
 `APPLICATIONINSIGHTS_SELF_DIAGNOSTICS_LEVEL`. It then takes precedence over the self-diagnostics level specified in the JSON configuration.

articles/azure-monitor/app/java-standalone-upgrade-from-2x.md

@@ -2,7 +2,7 @@
 title: Upgrading from 2.x - Azure Monitor Application Insights Java
 description: Upgrading from Azure Monitor Application Insights Java 2.x
 ms.topic: conceptual
-ms.date: 12/14/2022
+ms.date: 01/18/2023
 ms.devlang: java
 ms.custom: devx-track-java
 ms.reviewer: mmcc
@@ -32,7 +32,7 @@ auto-instrumentation which is provided by the 3.x Java agent.
 Add the 3.x Java agent to your JVM command-line args, for example
 
 ```
--javaagent:path/to/applicationinsights-agent-3.4.7.jar
+-javaagent:path/to/applicationinsights-agent-3.4.8.jar
 ```
 
 If you were using the Application Insights 2.x Java agent, just replace your existing `-javaagent:...` with the above.

articles/communication-services/quickstarts/voice-video-calling/get-started-volume-indicator.md

@@ -0,0 +1,45 @@
+---
+title: Quickstart - Add volume indicator to your Web calling app
+titleSuffix: An Azure Communication Services quickstart
+description: In this quickstart, you'll learn how to check call volume within your Web app when using Azure Communication Services.
+author: sloanster
+
+ms.author: micahvivion
+ms.date: 1/18/2023
+ms.topic: quickstart
+ms.service: azure-communication-services
+ms.subservice: calling
+ms.custom: mode-other
+---
+
+# Accessing call volume level
+As a developer you can have control over checking microphone volume in JavaScript. This quickstart shows examples of how to accomplish this within the ACS WebJS.
+
+## Prerequisites
+[!INCLUDE [Public Preview](../../includes/public-preview-include-document.md)]
+
+>[!IMPORTANT]
+> The quick start examples here are available starting on the public preview version [1.9.1-beta.1](https://www.npmjs.com/package/@azure/communication-calling/v/1.9.1-beta.1) of the calling Web SDK. Make sure to use that SDK version or newer when trying this quickstart.
+
+## Checking the audio stream volume
+As a developer it can be nice to have the ability to check and display to end users the current microphone volume. ACS calling API exposes this information using `getVolume`. The `getVolume` value is a number ranging from 0 to 100 (with 0 noting zero audio detected, 100 as the max level detectable). This value iss sampled every 200 ms to get near real time value of volume.
+
+### Example usage
+Sample code to get volume of selected microphone. This example shows how to generate the volume level by accessing `getVolume`.
+
+```javascript
+//Get the vaolume of the local audio source
+const volumeIndicator = await new SDK.LocalAudioStream(deviceManager.selectedMicrophone).getVolume();
+volumeIndicator.on('levelChanged', ()=>{
+    console.log(`Volume is ${volumeIndicator.level}`)
+})
+
+//Get the volume level of the remote incoming audio source
+const remoteAudioStream = call.remoteAudioStreams[0];
+const volumeIndicator = await remoteAudioStream.getVolume();
+volumeIndicator.on('levelChanged', ()=>{
+    console.log(`Volume is ${volumeIndicator.level}`)
+})
+
+```
+

articles/load-balancer/TOC.yml

@@ -232,6 +232,8 @@
       href: move-across-regions-internal-load-balancer-powershell.md
   - name: IPv6
     items:
+    - name: Configure DHCPv6 for Linux VMs
+      href: load-balancer-ipv6-for-linux.md
     - name: Public Load Balancer
       items:
       - name: Standard Public Load Balancer with IPv6 - PowerShell