Merge pull request #266692 from MicrosoftDocs/main

2/20 11:00 AM IST Publish

Author: Saisang

articles/aks/csi-storage-drivers.md

@@ -2,7 +2,7 @@
 title: Container Storage Interface (CSI) drivers on Azure Kubernetes Service (AKS)
 description: Learn about and deploy the Container Storage Interface (CSI) drivers for Azure Disks and Azure Files in an Azure Kubernetes Service (AKS) cluster
 ms.topic: article
-ms.date: 05/31/2023
+ms.date: 02/16/2024
 
 ---
 
@@ -29,7 +29,7 @@ The CSI storage driver support on AKS allows you to natively use:
 ## Prerequisites
 
 - You need the Azure CLI version 2.42 or later installed and configured. Run `az --version` to find the version. If you need to install or upgrade, see [Install Azure CLI][install-azure-cli].
-- If the open-source CSI Blob storage driver is installed on your cluster, uninstall it before enabling the Azure Blob storage driver.
+- If the open-source CSI storage driver is installed on your cluster, uninstall it before enabling the Azure storage CSI driver.
 - To enforce the Azure Policy for AKS [policy definition][azure-policy-aks-definition] **Kubernetes clusters should use Container Storage Interface(CSI) driver StorageClass**, the Azure Policy add-on needs to be enabled on new and existing clusters. For an existing cluster, review the [Learn Azure Policy for Kubernetes][learn-azure-policy-kubernetes] to enable it.
 
 ## Disk encryption supported scenarios

articles/aks/howto-deploy-java-wls-app.md

@@ -143,6 +143,7 @@ The other values in the outputs are beyond the scope of this article, but are ex
    ```sql
    CREATE TABLE COFFEE (ID NUMERIC(19) NOT NULL, NAME VARCHAR(255) NULL, PRICE FLOAT(32) NULL, PRIMARY KEY (ID));
    CREATE TABLE SEQUENCE (SEQ_NAME VARCHAR(50) NOT NULL, SEQ_COUNT NUMERIC(28) NULL, PRIMARY KEY (SEQ_NAME));
+   INSERT INTO SEQUENCE VALUES ('SEQ_GEN',0);
    ```
 
    After a successful run, you should see the message **Query succeeded: Affected rows: 0**. If you don't see this message, troubleshoot and resolve the problem before proceeding.
@@ -583,9 +584,9 @@ In the previous steps, you created the auxiliary image including models and WDT.
 
    kubectl -n ${WLS_DOMAIN_NS} create secret generic \
        ${SECRET_NAME} \
-       --from-literal=password='${DB_PASSWORD}' \
-       --from-literal=url='${DB_CONNECTION_STRING}' \
-       --from-literal=user='${DB_USER}'
+       --from-literal=password="${DB_PASSWORD}" \
+       --from-literal=url="${DB_CONNECTION_STRING}" \
+       --from-literal=user="${DB_USER}"
 
    kubectl -n ${WLS_DOMAIN_NS} label secret \
        ${SECRET_NAME} \
@@ -674,6 +675,14 @@ Use the following steps to verify the functionality of the deployment by viewing
 
 1. Sign in with the username `weblogic` and the password you entered when deploying WLS from the Azure portal. Recall that this value is `wlsAksCluster2022`.
 
+1. In the **Domain Structure** box, select **Services**.
+
+1. Under the **Services**, select **Data Sources**.
+
+1. In the **Summary of JDBC Data Sources** panel, select **Monitoring**. Your screen should look similar to the following example. You find the state of data source is running on managed servers.
+
+   :::image type="content" source="media/howto-deploy-java-wls-app/datasource-state.png" alt-text="Screenshot of data source state." border="false":::
+
 1. In the **Domain Structure** box, select **Deployments**.
 
 1. In the **Deployments** table, there should be one row. The name should be the same value as the `Application` value in your *appmodel.yaml* file. Select the name.

articles/aks/media/howto-deploy-java-wls-app/datasource-state.png

@@ -3,7 +3,7 @@ title: Timer trigger for Azure Functions
 description: Understand how to use timer triggers in Azure Functions.
 ms.assetid: d2f013d1-f458-42ae-baf8-1810138118ac
 ms.topic: reference
-ms.date: 03/06/2023
+ms.date: 02/19/2024
 ms.devlang: csharp
 # ms.devlang: csharp, java, javascript, powershell, python
 ms.custom: devx-track-csharp, devx-track-python, devx-track-extended-java, devx-track-js
@@ -99,7 +99,7 @@ import azure.functions as func
 app = func.FunctionApp()
 
 @app.function_name(name="mytimer")
-@app.schedule(schedule="0 */5 * * * *", 
+@app.timer_trigger(schedule="0 */5 * * * *", 
               arg_name="mytimer",
               run_on_startup=True) 
 def test_function(mytimer: func.TimerRequest) -> None:

articles/azure-functions/functions-bindings-timer.md

@@ -5,7 +5,7 @@ ms.topic: conceptual
 ms.date: 11/01/2023
 ---
 
-# Data collection in Azure Monitor
+# Data collection in Azure Monitor 
 Azure Monitor has a [common data platform](../data-platform.md) that consolidates data from a variety of sources. Currently, different sources of data for Azure Monitor use different methods to deliver their data, and each typically require different types of configuration. Get a description of the most common data sources at [Sources of monitoring data for Azure Monitor](../data-sources.md).
 
 Azure Monitor is implementing a new [ETL](/azure/architecture/data-guide/relational-data/etl)-like data collection pipeline that improves on legacy data collection methods. This process uses a common data ingestion pipeline for all data sources and provides a standard method of configuration that's more manageable and scalable than current methods. Specific advantages of the new data collection include the following:
@@ -31,6 +31,10 @@ See [Data collection transformations in Azure Monitor](data-collection-transform
 The following sections describe the data collection scenarios that are currently supported using DCR and the new data ingestion pipeline.
 
 ### Azure Monitor agent
+
+>[!IMPORTANT]
+>The Log Analytics agent is on a **deprecation path** and won't be supported after **August 31, 2024**. Any new data centers brought online after January 1 2024 will not support the Log Analytics agent. If you use the Log Analytics agent to ingest data to Azure Monitor, [migrate to the new Azure Monitor agent](../agents/azure-monitor-agent-migration.md) prior to that date.
+>
 The diagram below shows data collection for the [Azure Monitor agent](../agents/azure-monitor-agent-overview.md) running on a virtual machine. In this scenario, the DCR specifies events and performance data to collect from the agent machine, a transformation to filter and modify the data after its collected, and a Log Analytics workspace to send the transformed data. To implement this scenario, you create an association between the DCR and the agent. One agent can be associated with multiple DCRs, and one DCR can be associated with multiple agents.
 
 :::image type="content" source="media/data-collection-transformations/transformation-azure-monitor-agent.png" lightbox="media/data-collection-transformations/transformation-azure-monitor-agent.png" alt-text="Diagram showing data collection for Azure Monitor agent." border="false":::

articles/azure-monitor/essentials/data-collection.md

@@ -269,7 +269,7 @@ Tables related to Application Insights resources also keep data for 90 days at n
 
 ## Pricing model
 
-The charge for maintaining archived logs is calculated based on the volume of data you archive, in GB, and the number or days for which you archive the data.
+The charge for maintaining archived logs is calculated based on the volume of data you archive, in GB, and the number or days for which you archive the data. Log data that has `_IsBillable == false` is not subject to retention or archive charges. 
 
 For more information, see [Azure Monitor pricing](https://azure.microsoft.com/pricing/details/monitor/).
 

articles/azure-monitor/logs/data-retention-archive.md

@@ -149,7 +149,10 @@ Azure VMware Solution monitors the following conditions on the host:
 
 ## Backup and restore
 
-Azure VMware Solution private cloud vCenter Server, NSX-T Data Center, and HCX Manager (if enabled) configurations are on a daily backup schedule. Backups are kept for three days. If you need to restore from a backup, open a [support request](https://rc.portal.azure.com/#create/Microsoft.Support) in the Azure portal to request restoration.
+Azure VMware Solution private cloud vCenter Server, NSX-T Data Center, and HCX Manager (if enabled) configurations are on a daily backup schedule. Open a [support request](https://rc.portal.azure.com/#create/Microsoft.Support) in the Azure portal to request restoration.
+
+> [!NOTE]
+> Restorations are intended for catastrophic situations only.
 
 Azure VMware Solution continuously monitors the health of both the physical underlay and the VMware Solution components. When Azure VMware Solution detects a failure, it takes action to repair the failed components.
 

articles/azure-vmware/concepts-private-clouds-clusters.md

@@ -7,15 +7,15 @@ manager: chpalm
 services: azure-communication-services
 
 ms.author: chpalm
-ms.date: 06/30/2021
+ms.date: 02/24/2024
 ms.topic: conceptual
 ms.service: azure-communication-services
 ms.subservice: calling
 ms.custom: devx-track-js
 ---
 # Calling SDK overview
 
-Azure Communication Services allows end-user browsers, apps, and services to drive voice and video communication. This page focuses on Calling client SDK, which can be embedded in websites and native applications. This page provides detailed descriptions of Calling client features such as platform and browser support information. Services programmatically manage and access calls using the [Call Automation APIs](../call-automation/call-automation.md). The [Rooms API](../rooms/room-concept.md) is an optional Azure Communication Services API that adds additional features to a voice or video call, such as roles and permissions.
+Azure Communication Services allows end-user browsers, apps, and services to drive voice and video communication. This page focuses on Calling client SDK, which can be embedded in websites and native applications. This page provides detailed descriptions of Calling client features such as platform and browser support information. Services programmatically manages and access calls using the [Call Automation APIs](../call-automation/call-automation.md). The [Rooms API](../rooms/room-concept.md) is an optional Azure Communication Services API that adds additional features to a voice or video call, such as roles and permissions.
 
 [!INCLUDE [Survey Request](../../includes/survey-request.md)]
 
@@ -166,7 +166,15 @@ The Azure Communication Services Calling SDK supports the following streaming co
 | **Maximum # of incoming remote streams that can be rendered simultaneously** | 9 videos + 1 screen sharing on desktop browsers*, 4 videos + 1 screen sharing on web mobile browsers | 9 videos + 1 screen sharing |
 
 \* Starting from Azure Communication Services Web Calling SDK version [1.16.3](https://github.com/Azure/Communication/blob/master/releasenotes/acs-javascript-calling-library-release-notes.md#1163-stable-2023-08-24)
-While the Calling SDK does not enforce these limits, your users might experience performance degradation if they're exceeded. Use the API of [Optimal Video Count](../../how-tos/calling-sdk/manage-video.md?pivots=platform-web#remote-video-quality) to determine how many current incoming video streams your web environment can support.
+While the Calling SDK doesn't enforce these limits, your users might experience performance degradation if they're exceeded. Use the API of [Optimal Video Count](../../how-tos/calling-sdk/manage-video.md?pivots=platform-web#remote-video-quality) to determine how many current incoming video streams your web environment can support.
+
+## Supported video resolutions
+The Azure Communicaton Services Calling SDK support the following video resolutions:
+
+| Maximum video resolution        | WebJS | iOS   | Android | Windows |
+| ------------- | ----- | ----- | ------- | ------- |
+| **Receiving video** | 1080P | 1080P | 1080P   | 1080P   |
+| **Sending video**    | 720P  | 720P  | 720P    | 1080P   |
 
 ## Calling SDK timeouts
 

articles/communication-services/concepts/voice-video-calling/calling-sdk-features.md

@@ -7,7 +7,7 @@ manager: chpalm
 services: azure-communication-services
 
 ms.author: nmurav
-ms.date: 09/12/2023
+ms.date: 02/19/2024
 ms.topic: conceptual
 ms.service: azure-communication-services
 ms.subservice: calling
@@ -24,7 +24,7 @@ The quality of real-time media over IP is significantly affected by the quality
 
 * **Latency**. The time it takes to get an IP packet from point A to point B on the network. This network propagation delay is determined by the physical distance between the two points and any other overhead incurred by the devices that your traffic flows through. Latency is measured as one-way or round-trip time (RTT).
 * **Packet loss**. A percentage of packets that are lost in a specific window of time. Packet loss directly affects audio quality—from small, individual lost packets having almost no impact to back-to-back burst losses that cause complete audio cut-out.
-* **Inter-packet arrival jitter, also known as jitter**. The average change in delay between successive packets. Communication Services can adapt to some levels of jitter through buffering. It's only when the jitter exceeds the buffering that a participant will notice its effects.
+* **Inter-packet arrival jitter, also known as jitter**. The average change in delay between successive packets. Communication Services can adapt to some levels of jitter through buffering. It's only when the jitter exceeds the buffering that a participant notices its effects.
 
 ## Network bandwidth
 
@@ -39,7 +39,8 @@ The following bandwidth requirements are for the JavaScript SDKs.
 |500 Kbps|Peer-to-peer quality video calling 360 pixels at 30 FPS|
 |1.2 Mbps|Peer-to-peer HD-quality video calling with resolution of HD 720 pixels at 30 FPS|
 |500 Kbps|Group video calling 360 pixels at 30 FPS|
-|1.2 Mbps|HD group video calling with resolution of HD 720 pixels at 30 FPS| 
+|1.2 Mbps|HD group video calling with resolution of HD 720 pixels at 30 FPS|
+|1.5 Mbps|Peer-to-peer HD-quality video calling with resolution of HD 1080 pixels at 30 FPS |
 
 The following bandwidth requirements are for the native Windows, Android, and iOS SDKs.
 
@@ -55,15 +56,15 @@ The following bandwidth requirements are for the native Windows, Android, and iO
 
 ## Firewall configuration
 
-Communication Services connections require internet connectivity to specific ports and IP addresses to deliver high-quality multimedia experiences. Without access to these ports and IP addresses, Communication Services will not work properly. The list of IP ranges and allow listed domains that need to be enabled are:
+Communication Services connections require internet connectivity to specific ports and IP addresses to deliver high-quality multimedia experiences. Without access to these ports and IP addresses, Communication Services won't work properly. The list of IP ranges and allow listed domains that need to be enabled are:
 
 | Category | IP ranges or FQDN | Ports | 
 | :-- | :-- | :-- |
 | Media traffic | Range of Azure public cloud IP addresses 20.202.0.0/16 The range provided above is the range of IP addresses on either Media processor or Azure Communication Services TURN service. | UDP 3478 through 3481, TCP ports 443 |
 | Signaling, telemetry, registration| *.skype.com, *.microsoft.com, *.azure.net, *.azure.com, *.office.com| TCP 443, 80 |
 
 
-The endpoints below should be reachable for U.S. Government GCC High customers only
+The endpoints below should be reachable for U.S. Government GCC High customers only.
 
 | Category | IP ranges or FQDN | Ports | 
 | :-- | :-- | :-- |

articles/communication-services/concepts/voice-video-calling/network-requirements.md

@@ -1,14 +1,15 @@
 ---
 title: Azure Communication Services Simulcast
 titleSuffix: An Azure Communication Services concept document
-description: Overview of Simulcast - how sending multiple video quality streams helps overall call quality
-author: chriswhilar
-manager: [email protected]
+description: Overview of Simulcast - how sending multiple video quality streams helps overall call quality.
+author: sloanster
+manager: chpalm
 services: azure-communication-services
 
-ms.author: chwhilar
-ms.date: 11/21/2022
+ms.author: micahvivion
+ms.date: 02/19/2024
 ms.topic: conceptual
+ms.subservice: calling
 ms.service: azure-communication-services
 ---
 # What is Simulcast?
@@ -26,8 +27,9 @@ Simulcast streaming from a web endpoint supports a maximum two video qualities.
 
 ## Available video resolutions
 When streaming with simulcast, there are no set resolutions for high or low quality simulcast video streams. Instead, based on many different variables, either a single or multiple video steams are delivered. If every subscriber to video is requesting and capable of receiving maximum resolution what publisher can provide, only that maximum resolution will be sent. The following resolutions are supported:
+- 1080P
 - 720p
 - 540p
 - 360p
 - 240p
-- 180p
+- 180p