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

Author: fauhse

articles/cosmos-db/continuous-backup-restore-resource-model.md

@@ -14,7 +14,7 @@ ms.reviewer: mjbrown
 
 [!INCLUDE[NoSQL, MongoDB, Gremlin, Table](includes/appliesto-nosql-mongodb-gremlin-table.md)]
 
-This article explains the resource model for the Azure Cosmos DB point-in-time restore feature. It explains the parameters that support the continuous backup and resources that can be restored. This feature is supported in Azure Cosmos DB API for SQL and the Azure Cosmos DB API for MongoDB. Currently, this feature is in preview for Azure Cosmos DB API for Gremlin and Table accounts.
+This article explains the resource model for the Azure Cosmos DB point-in-time restore feature. It explains the parameters that support the continuous backup and resources that can be restored. This feature is supported in Azure Cosmos DB API for SQL, Azure Cosmos DB API for Gremlin, Table API and the Azure Cosmos DB API for MongoDB.  
 
 ## Database account's resource model
 
@@ -25,7 +25,7 @@ The database account's resource model is updated with a few extra properties to
 A new property in the account level backup policy named ``Type`` under the ``backuppolicy`` parameter enables continuous backup and point-in-time restore. This mode is referred to as **continuous backup**. You can set this mode when creating the account or while [migrating an account from periodic to continuous mode](migrate-continuous-backup.md). After continuous mode is enabled, all the containers and databases created within this account will have point-in-time restore and continuous backup enabled by default. The continuous backup tier can be set to ``Continuous7Days`` or ``Continuous30Days``. By default, if no tier is provided, ``Continuous30Days`` is applied on the account.
 
 > [!NOTE]
-> Currently the point-in-time restore feature is available for Azure Cosmos DB for MongoDB and API for NoSQL accounts. It is also available for API for Table and API for Gremlin in preview. After you create an account with continuous mode you can't switch it to a periodic mode. The ``Continuous7Days`` tier is in preview.
+> Currently the point-in-time restore feature is available for Azure Cosmos DB for NoSQL, API for MongoDB, Table and Gremlin accounts. After you create an account with continuous mode you can't switch it to a periodic mode. The ``Continuous7Days`` tier is in preview.
 
 ### CreateMode
 

articles/cosmos-db/get-latest-restore-timestamp.md

@@ -6,7 +6,7 @@ ms.author: govindk
 ms.service: cosmos-db
 ms.subservice: nosql
 ms.custom: ignite-2022, devx-track-azurecli, devx-track-azurepowershell
-ms.date: 04/08/2022
+ms.date: 03/31/2023
 ms.topic: how-to
 ms.reviewer: mjbrown
 ---
@@ -16,7 +16,7 @@ ms.reviewer: mjbrown
 
 This article describes how to get the [latest restorable timestamp](latest-restore-timestamp-continuous-backup.md) for accounts with continuous backup mode. It explains how to get the latest restorable time using Azure PowerShell and Azure CLI, and provides the request and response format for the PowerShell and CLI commands. 
 
-This feature is supported for Azure Cosmos DB API for NoSQL containers and Azure Cosmos DB API for MongoDB collections. This feature is in preview for API for Table tables and API for Gremlin graphs. 
+This feature is supported for Azure Cosmos DB API for NoSQL containers, API for MongoDB , Table API and API for Gremlin graphs.
 
 ## SQL container
 

articles/service-bus-messaging/monitor-service-bus-reference.md

@@ -53,6 +53,9 @@ The following two types of errors are classified as **user errors**:
 > [!IMPORTANT]
 > Values for messages, active, dead-lettered, scheduled, completed, and abandoned messages are point-in-time values. Incoming messages that were consumed immediately after that point-in-time may not be reflected in these metrics. 
 
+> [!NOTE]
+> When a client tries to get the info about a queue or topic, the Service Bus service returns some static information like name, last updated time, created time, requires session or not etc., and some dynamic information like message counts. If the request gets throttled, the service returns the static information and empty dynamic information. That's why message counts are shown as 0 when the namespace is being throttled. This behavior is by design. 
+
 ### Connection metrics
 
 | Metric Name |  Exportable via diagnostic settings | Unit | Aggregation type |  Description | Dimensions | 
@@ -87,7 +90,7 @@ Azure Service Bus supports the following dimensions for metrics in Azure Monitor
 
 |Dimension name|Description|
 | ------------------- | ----------------- |
-|Entity Name| Service Bus supports messaging entities under the namespace. With the 'Incoming Requests' metric, the Entity Name dimension will see a value of '-NamespaceOnlyMetric-' in addition to all your queues and topics. This represents request which were made at the namespace level. Examples include a  request to list all queues/topics under the namespace or requests to entities which failed authentication or authorization.|
+|Entity Name| Service Bus supports messaging entities under the namespace. With the 'Incoming Requests' metric, the Entity Name dimension will have a value of '-NamespaceOnlyMetric-' in addition to all your queues and topics. This represents the request, which was made at the namespace level. Examples include a  request to list all queues/topics under the namespace or requests to entities that failed authentication or authorization.|
 
 ## Resource logs
 This section lists the types of resource logs you can collect for Azure Service Bus.

articles/virtual-desktop/whats-new.md

@@ -3,7 +3,7 @@ title: What's new in Azure Virtual Desktop? - Azure
 description: New features and product updates for Azure Virtual Desktop.
 author: Heidilohr
 ms.topic: overview
-ms.date: 03/07/2023
+ms.date: 04/11/2023
 ms.author: helohr
 ms.reviewer: thhickli; darank
 manager: femila
@@ -20,6 +20,30 @@ Azure Virtual Desktop updates regularly. This article is where you'll find out a
 
 Make sure to check back here often to keep up with new updates.
 
+## March 2023
+
+Here's what changed in March 2023:
+
+### Redesigned connection bar for the Windows Desktop client
+
+The latest version of the Windows Desktop client includes a redesigned connection bar. For more information, see [Updates for version 1.2.4155](whats-new-client-windows.md#updates-for-version-124157). 
+
+### Shutdown session host status
+
+The Shutdown session host status is now available in the Azure Virtual Desktop portal and the most recent API version. For more information, see [Session host statuses and health checks](troubleshoot-statuses-checks.md#session-host-statuses).
+
+### Windows 10 and 11 22H2 images now visible in the image drop-down menu
+
+Windows 10 and 11 22H2 Enterprise and Enterprise multi-session images are now visible in the image dropdown when creating a new host pool or adding a VM in a host pool from the Azure Virtual Desktop portal.
+
+### Uniform Resource Identifier Schemes in public preview
+
+Uniform Resource Identifier (URI) schemes with the Remote Desktop client for Azure Virtual Desktop is now in public preview. This new feature lets you subscribe to a workspace or connect to a particular desktop or Remote App using URI schemes. URI schemes also provide fast and efficient end-user connection to Azure Virtual Desktop resources. For more information, see [our blog post](https://techcommunity.microsoft.com/t5/azure-virtual-desktop-blog/announcing-the-public-preview-of-uniform-resource-identifier/ba-p/3763075). 
+
+### Azure Virtual Desktop Insights at Scale now generally available
+
+Azure Virtual Desktop Insights at Scale is now generally available. This feature gives you the ability to review performance and diagnostic information in multiple host pools at the same time in a single view. If you're an existing Azure Virtual Desktop Insights user, you get this feature without having to do any extra configuration or setup. For more information, see [our blog post](https://techcommunity.microsoft.com/t5/azure-virtual-desktop-blog/announcing-the-general-availability-of-azure-virtual-desktop/ba-p/3738624). 
+
 ## February 2023
 
 Here's what changed in February 2023: