Merge pull request #198343 from MicrosoftDocs/main

5/16 AM Publishing

Author: v-alje

articles/azure-netapp-files/cross-region-replication-display-health-status.md

@@ -12,7 +12,7 @@ ms.service: azure-netapp-files
 ms.workload: storage
 ms.tgt_pltfrm: na
 ms.topic: how-to
-ms.date: 01/28/2022
+ms.date: 05/16/2022
 ms.author: anfdocs
 ---
 # Display health and monitor status of replication relationship 
@@ -58,9 +58,9 @@ Follow the following steps to create [alert rules in Azure Monitor](../azure-mon
 5.	From the Condition tab, select **Add condition**. From there, find a signal called “**is volume replication healthy**”.
 6.	There you'll see **Condition of the relationship, 1 or 0** and the **Configure Signal Logic** window is displayed.
 7.	To check if the replication is _unhealthy_: 
-    * Set **Operator** to `Less than or equal to`.
+    * Set **Operator** to `Less than`.
     * Set **Aggregation type** to `Average`. 
-    * Set **Threshold** value to `0`.
+    * Set **Threshold** value to `1`.
     * Set **Unit** to `Count`.
 8.	To check if the replication is _healthy_: 
     * Set **Operator** to `Greater than or equal to`.

articles/cognitive-services/Speech-Service/rest-speech-to-text-short.md

@@ -8,7 +8,7 @@ manager: nitinme
 ms.service: cognitive-services
 ms.subservice: speech-service
 ms.topic: reference
-ms.date: 01/24/2022
+ms.date: 05/16/2022
 ms.author: eur
 ms.devlang: csharp
 ms.custom: devx-track-csharp
@@ -22,6 +22,7 @@ Before you use the speech-to-text REST API for short audio, consider the followi
 
 * Requests that use the REST API for short audio and transmit audio directly can contain no more than 60 seconds of audio.
 * The REST API for short audio returns only final results. It doesn't provide partial results.
+* [Speech translation](speech-translation.md) is not supported via REST API for short audio. You need to use [Speech SDK](speech-sdk.md).
 
 > [!TIP]
 > For Azure Government and Azure China endpoints, see [this article about sovereign clouds](sovereign-clouds.md).

articles/cosmos-db/configure-custom-partitioning.md

@@ -101,7 +101,7 @@ df = spark.read\
     .option("spark.cosmos.asns.basePath", "/mnt/CosmosDBPartitionedStore/") \
     .load()
 
-df_filtered = df.filter("readDate='2020-11-27 00:00:00.000'")
+df_filtered = df.filter("readDate='2020-11-01 00:00:00.000'")
 display(df_filtered.limit(10))
 ```
 
@@ -115,7 +115,7 @@ val df = spark.read.
             option("spark.cosmos.asns.partition.keys", "readDate String").
             option("spark.cosmos.asns.basePath", "/mnt/CosmosDBPartitionedStore/").
             load()
-val df_filtered = df.filter("readDate='2020-11-27 00:00:00.000'")
+val df_filtered = df.filter("readDate='2020-11-01 00:00:00.000'")
 display(df_filtered.limit(10))
 ```
 ---

articles/databox/data-box-disk-faq.yml

@@ -8,7 +8,7 @@ metadata:
   ms.service: databox
   ms.subservice: disk
   ms.topic: faq
-  ms.date: 04/07/2022
+  ms.date: 05/06/2022
   ms.author: alkohli
   ms.custom: references_regions
 title: "Azure Data Box Disk: Frequently Asked Questions"
@@ -84,11 +84,11 @@ sections:
         answer: |
           No. Data Box Disk does not store any customer data outside of the service region. The customer has full ownership of their data and can save the data to a specified location based on the storage account they select during the order creation.  
           
-          In addition to the customer data, there is Data Box Disk data that includes metadata and monitoring logs. In all the regions (except Brazil South and Southeast Asia), Data Box Disk data is stored and replicated in a [paired region](../availability-zones/cross-region-replication-azure.md) via a Geo-redundant Storage account to protect against data loss.  
+          In addition to the customer data, there is Data Box Disk data that includes metadata and monitoring logs. In all the regions (except Brazil South, Southeast Asia, and East Asia), Data Box Disk data is stored and replicated in a [paired region](../availability-zones/cross-region-replication-azure.md) via a Geo-redundant Storage account to protect against data loss.  
           
-          Due to [data residency requirements](https://azure.microsoft.com/global-infrastructure/data-residency/#more-information) in Brazil South and Southeast Asia, Data Box Disk data is stored in a Zone-redundant Storage (ZRS) account so that it is contained in a single region. For Southeast Asia, all the Data Box Disk data is stored in Singapore and for Brazil South, the data is stored in Brazil. 
+          Due to [data residency requirements](https://azure.microsoft.com/global-infrastructure/data-residency/#more-information) in Brazil South, Southeast Asia, and East Asia, Data Box Disk data is stored in a Zone-redundant Storage (ZRS) account so that it is contained in a single region. For Southeast Asia, all the Data Box Disk data is stored in Singapore. For Brazil South, the data is stored in Brazil. For East Asia, the data is stored in Hong Kong.
           
-          If there is a service outage in Brazil South and Southeast Asia, the customers can create new orders from another region. The new orders will be served from the region in which they are created and the customers are responsible for the to and fro shipment of the Data Box Disk.
+          If there is a service outage in Brazil South, Southeast Asia, or East Asia, the customers can create new orders from another region. The new orders will be served from the region in which they are created and the customers are responsible for the to and fro shipment of the Data Box Disk.
       
       - question: |
           Does my Data Box Disk region have to be in the same Azure region as my destination storage account?

articles/databox/data-box-faq.yml

@@ -8,7 +8,7 @@ metadata:
   ms.service: databox
   ms.subservice: pod
   ms.topic: faq
-  ms.date: 04/13/2022
+  ms.date: 05/06/2022
   ms.author: alkohli
   ms.custom: references_regions
 
@@ -61,11 +61,11 @@ sections:
 
           No. Data Box does not store any customer data outside of the service region. The customer has full ownership of their data. They can save the data to a specified location based on the storage account they select during the order creation.
 
-          In addition to the customer data, there is Data Box data that includes security artifacts related to the device, monitoring logs for the device and the service, and service-related metadata. In all regions (except Brazil South and Southeast Asia), Data Box data is stored and replicated in the paired region via a Geo-redundant Storage account to protect against data loss.
+          In addition to the customer data, there is Data Box data that includes security artifacts related to the device, monitoring logs for the device and the service, and service-related metadata. In all regions (except Brazil South, Southeast Asia, and East Asia), Data Box data is stored and replicated in the paired region via a Geo-redundant Storage account to protect against data loss.
 
-          Due to [data residency requirements](https://azure.microsoft.com/global-infrastructure/data-residency/#more-information) in Brazil South and Southeast Asia, Data Box data is stored in a Zone-redundant Storage (ZRS) account so that it is contained in a single region. For Southeast Asia, all the Data Box data is stored in Singapore and for Brazil South, the data is stored in Brazil.
+          Due to [data residency requirements](https://azure.microsoft.com/global-infrastructure/data-residency/#more-information) in Brazil South, Southeast Asia, and East Asia, Data Box data is stored in a Zone-redundant Storage (ZRS) account so that it is contained in a single region. For Southeast Asia, all the Data Box data is stored in Singapore. For Brazil South, the data is stored in Brazil. For East Asia, the data is stored in Hong Kong.
 
-          If there is a service outage in Brazil South or Southeast Asia, the customers can create new orders from another region. The new orders will be served from the region in which they are created and the customers are responsible for the to and fro shipment of the Data Box device.
+          If there is a service outage in Brazil South, Southeast Asia, or East Asia, the customers can create new orders from another region. The new orders will be served from the region in which they are created and the customers are responsible for the to and fro shipment of the Data Box device.
 
           ### Does my Data Box region have to be in the same Azure region as my destination storage account?
 

articles/databox/data-box-overview.md

@@ -8,8 +8,9 @@ author: alkohli
 ms.service: databox
 ms.subservice: pod
 ms.topic: overview
-ms.date: 04/06/2022
+ms.date: 05/06/2022
 ms.author: alkohli
+ms.custom: references_regions
 #Customer intent: As an IT admin, I need to understand what Data Box is and how it works so I can use it to import on-premises data into Azure or export data from Azure.
 ---
 # What is Azure Data Box?
@@ -161,7 +162,7 @@ In the extreme event of any Azure region being affected by a disaster, the Data
 
 For regions paired with a region within the same country or commerce boundary, no action is required. Microsoft is responsible for recovery, which could take up to 72 hours.
 
-For regions that don’t have a paired region within the same geographic or commerce boundary, the customer will be notified to create a new Data Box order from a different, available region and copy their data to Azure in the new region. New orders would be required for the Brazil South and Southeast Asia regions.
+For regions that don’t have a paired region within the same geographic or commerce boundary, the customer will be notified to create a new Data Box order from a different, available region and copy their data to Azure in the new region. New orders would be required for the Brazil South, Southeast Asia, and East Asia regions.
 
 For more information, see [Business continuity and disaster recovery (BCDR): Azure Paired Regions](../best-practices-availability-paired-regions.md).
 

articles/search/search-get-started-arm.md

@@ -8,7 +8,7 @@ ms.author: heidist
 ms.service: cognitive-search
 ms.topic: quickstart
 ms.custom: subject-armqs, mode-arm
-ms.date: 12/07/2021
+ms.date: 05/16/2022
 ---
 
 # Quickstart: Deploy Cognitive Search using an Azure Resource Manager template
@@ -17,6 +17,8 @@ This article walks you through the process for using an Azure Resource Manager (
 
 [!INCLUDE [About Azure Resource Manager](../../includes/resource-manager-quickstart-introduction.md)]
 
+Only those properties included in the template are used in the deployment. If more customization is required, such as [setting up network security](search-security-overview.md#network-security), you can [update service configuration](/cli/azure/search/service?view=azure-cli-latest#az-search-service-update) after the service is deployed.
+
 If your environment meets the prerequisites and you're familiar with using ARM templates, select the **Deploy to Azure** button. The template will open in the Azure portal.
 
 [![Deploy to Azure](../media/template-deployments/deploy-to-azure.svg)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2Fazure%2Fazure-quickstart-templates%2Fmaster%2Fquickstarts%2Fmicrosoft.search%2Fazure-search-create%2Fazuredeploy.json)

articles/search/search-get-started-bicep.md

@@ -7,7 +7,7 @@ ms.author: v-eschaffer
 ms.service: cognitive-search
 ms.topic: quickstart
 ms.custom: subject-armqs, mode-arm
-ms.date: 03/18/2022
+ms.date: 05/16/2022
 ---
 
 # Quickstart: Deploy Cognitive Search using Bicep
@@ -24,6 +24,8 @@ If you don't have an Azure subscription, create a [free account](https://azure.m
 
 The Bicep file used in this quickstart is from [Azure Quickstart Templates](https://azure.microsoft.com/resources/templates/azure-search-create/).
 
+Only those properties included in the template are used in the deployment. If more customization is required, such as [setting up network security](search-security-overview.md#network-security), you can [update service configuration](/cli/azure/search/service?view=azure-cli-latest#az-search-service-update) after the service is deployed.
+
 :::code language="bicep" source="~/quickstart-templates/quickstarts/microsoft.search/azure-search-create/main.bicep":::
 
 The Azure resource defined in this Bicep file:

articles/spatial-anchors/how-tos/create-locate-anchors-unity.md

@@ -295,11 +295,21 @@ Learn more about the [AnchorLocatedDelegate](/dotnet/api/microsoft.azure.spatial
 
 Learn more about the [DeleteAnchorAsync](/dotnet/api/microsoft.azure.spatialanchors.cloudspatialanchorsession.deleteanchorasync) method.
 
+### Delete anchor after locating (recommended)
 ```csharp
     await this.cloudSession.DeleteAnchorAsync(cloudAnchor);
     // Perform any processing you may want when delete finishes
 ```
 
+### Delete anchor without locating
+If you are unable to locate an anchor but would still like to delete it you can use the ``GetAnchorPropertiesAsync`` API which takes an anchorId as input to get the ``CloudSpatialAnchor`` object. You can then pass this object into ``DeleteAnchorAsync`` to delete it. 
+```csharp
+var anchor = await cloudSession.GetAnchorPropertiesAsync(@"anchorId");
+await this.cloudSession.DeleteAnchorAsync(anchor);
+```
+    
+
+
 [!INCLUDE [Stopping](../../../includes/spatial-anchors-create-locate-anchors-stopping.md)]
 
 Learn more about the [Stop](/dotnet/api/microsoft.azure.spatialanchors.cloudspatialanchorsession.stop) method.

articles/storage/file-sync/file-sync-planning.md

@@ -80,7 +80,7 @@ Future versions of Windows Server will be added as they are released.
 > We recommend keeping all servers that you use with Azure File Sync up to date with the latest updates from Windows Update. 
 
 ### Minimum system resources
-Azure File Sync requires a server, either physical or virtual, with at least one CPU and a minimum of 2 GiB of memory.
+Azure File Sync requires a server, either physical or virtual, with at least one CPU, minimum of 2 GiB of memory and a locally attached volume formatted with the NTFS file system.
 
 > [!Important]  
 > If the server is running in a virtual machine with dynamic memory enabled, the VM should be configured with a minimum of 2048 MiB of memory.
@@ -112,8 +112,6 @@ In the following table, we have provided both the size of the namespace as well
 > 
 > Typical churn is 0.5% of the namespace changing per day. For higher levels of churn, consider adding more CPU. 
 
-- A locally attached volume formatted with the NTFS file system.
-
 ### Evaluation cmdlet
 Before deploying Azure File Sync, you should evaluate whether it is compatible with your system using the Azure File Sync evaluation cmdlet. This cmdlet checks for potential issues with your file system and dataset, such as unsupported characters or an unsupported operating system version. Its checks cover most but not all of the features mentioned below; we recommend you read through the rest of this section carefully to ensure your deployment goes smoothly.