Merge pull request #210405 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: huypub

articles/azure-monitor/app/javascript.md

@@ -193,7 +193,7 @@ Most configuration fields are named so that they can default to false. All field
 | samplingPercentage | Percentage of events that will be sent. Default is 100, meaning all events are sent. Set this option if you want to preserve your data cap for large-scale applications. | numeric<br/>100 |
 | autoTrackPageVisitTime | If true, on a pageview, the _previous_ instrumented page's view time is tracked and sent as telemetry and a new timer is started for the current pageview. It's sent as a custom metric named `PageVisitTime` in `milliseconds` and is calculated via the Date [now()](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/now) function (if available) and falls back to (new Date()).[getTime()](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/getTime) if now() is unavailable (Internet Explorer 8 or less). Default is false. | boolean<br/>false |
 | disableAjaxTracking | If true, Ajax calls aren't autocollected. | boolean<br/> false |
-| disableFetchTracking | If true, Fetch requests aren't autocollected.|boolean<br/>true |
+| disableFetchTracking | If true, Fetch requests aren't autocollected.|boolean<br/>false |
 | overridePageViewDuration | If true, default behavior of trackPageView is changed to record end of page view duration interval when trackPageView is called. If false and no custom duration is provided to trackPageView, the page view performance is calculated by using the navigation timing API. |boolean<br/>
 | maxAjaxCallsPerView | Default 500 controls how many Ajax calls will be monitored per page view. Set to -1 to monitor all (unlimited) Ajax calls on the page. | numeric<br/> 500 |
 | disableDataLossAnalysis | If false, internal telemetry sender buffers will be checked at startup for items not yet sent. | boolean<br/> true |

articles/azure-monitor/essentials/resource-manager-diagnostic-settings.md

@@ -588,7 +588,7 @@ param eventHubAuthorizationRuleId string
 @description('The name of the event hub.')
 param eventHubName string
 
-resource vault 'Microsoft.KeyVault/managedHSMs@2021-11-01-preview' existing = {
+resource vault 'Microsoft.KeyVault/vaults@2021-11-01-preview' existing = {
   name: vaultName
 }
 
@@ -664,7 +664,7 @@ resource setting 'Microsoft.Insights/diagnosticSettings@2021-05-01-preview' = {
     {
       "type": "Microsoft.Insights/diagnosticSettings",
       "apiVersion": "2021-05-01-preview",
-      "scope": "[format('Microsoft.KeyVault/managedHSMs/{0}', parameters('vaultName'))]",
+      "scope": "[format('Microsoft.KeyVault/vaults/{0}', parameters('vaultName'))]",
       "name": "[parameters('settingName')]",
       "properties": {
         "workspaceId": "[parameters('workspaceId')]",

articles/azure-vmware/ecosystem-os-vms.md

@@ -8,9 +8,9 @@ ms.date: 04/11/2022
 
 # Operating system support for Azure VMware Solution virtual machines
 
-Azure VMware Solution supports a wide range of operating systems to be used in the guest virtual machines. Being based on VMware vSphere, currently 6.7 version, all operating systems currently supported by vSphere can be used by any Azure VMware Solution customer for their workloads.
+Azure VMware Solution supports a wide range of operating systems to be used in the guest virtual machines. Being based on VMware vSphere, currently 7.0 version, all operating systems currently supported by vSphere can be used by any Azure VMware Solution customer for their workloads.
 
-Check the list of operating systems and configurations supported in the [VMware Compatibility Guide](https://www.vmware.com/resources/compatibility/search.php?deviceCategory=software), create a query for ESXi 6.7 Update 3 and select all operating systems and vendors.
+Check the list of operating systems and configurations supported in the [VMware Compatibility Guide](https://www.vmware.com/resources/compatibility/search.php?deviceCategory=software), create a query for ESXi 7.0 Update 3 and select all operating systems and vendors.
 
 Additionally to the supported operating systems by VMware for vSphere, we have worked with Red Hat, SUSE and Canonical to extend the support model currently in place for Azure Virtual Machines to the workloads running on Azure VMware Solution, given that it is a first-party Azure service. You can check the following sites of vendors for more information about the benefits of running their operating system on Azure.
 

articles/azure-vmware/enable-vmware-cds-with-azure.md

@@ -32,12 +32,12 @@ To provide access to vNET based Azure resources, each tenant can have their own
 As shown in the diagram above, organization 01 has two organization virtual datacenters: VDC1 and VDC2. The virtual datacenter of each organization has its own Azure vNETs connected with their respective organization VDC Edge gateway through IPSEC VPN.
 Providers provide public IP addresses to the organization VDC Edge gateway for IPSEC VPN configuration. An ORG VDC Edge gateway firewall blocks all traffic by default, specific allow rules needs to be added on organization Edge gateway firewall.
 
-Organization VDCs can be part of a single organization and still provide isolation between them. For example, JSVM1 hosted in organization VDC1 cannot ping Azure VM JSVM2 for tenant2.
+Organization VDCs can be part of a single organization and still provide isolation between them. For example, VM1 hosted in organization VDC1 cannot ping Azure VM JSVM2 for tenant2.
 
 ### Prerequisites  
 - Organization VDC is configured with an Edge gateway and has Public IPs assigned to it to establish IPSEC VPN by provider.
 - Tenants have created a routed Organization VDC network in tenant’s virtual datacenter.
-- Test JSVM1 and JSVM2 are created in the Organization VDC1 and VDC2 respectively. Both VMs are connected to the routed orgVDC network in their respective VDCs.
+- Test VM1 and VM2 are created in the Organization VDC1 and VDC2 respectively. Both VMs are connected to the routed orgVDC network in their respective VDCs.
 - Have a dedicated [Azure vNET](tutorial-configure-networking.md#create-a-vnet-manually) configured for each tenant. For this example, we created Tenant1-vNet and Tenant2-vNet for tenant1 and tenant2 respectively.
 - Create an [Azure Virtual network gateway](tutorial-configure-networking.md#create-a-virtual-network-gateway) for vNETs created earlier.
 - Deploy Azure VMs JSVM1 and JSVM2 for tenant1 and tenant2 for test purposes.

articles/cognitive-services/language-service/text-analytics-for-health/how-to/call-api.md

@@ -8,7 +8,7 @@ manager: nitinme
 ms.service: cognitive-services
 ms.subservice: language-service
 ms.topic: how-to
-ms.date: 03/01/2022
+ms.date: 09/05/2022
 ms.author: aahi
 ms.custom: language-service-health, ignite-fall-2021
 ---
@@ -38,15 +38,20 @@ By default, Text Analytics for health will use the latest available AI model on
 
 | Supported Versions | latest version |
 |--|--|
+| `2022-03-01` | `2022-03-01`   |
 | `2021-05-15` | `2021-05-15`   |
 
+
 ### Text Analytics for health container
 
 The [Text Analytics for health container](use-containers.md) uses separate model versioning than the REST API and client libraries. Only one model version is available per container image.
 
 | Endpoint                        | Container Image Tag                     | Model version |
 |---------------------------------|-----------------------------------------|---------------|
-| `/entities/health`              | `3.0.016230002-onprem-amd64` (latest)            | `2021-05-15`  |
+| `/entities/health`              | `3.0.59413252-onprem-amd64` (latest)            | `2022-03-01`  |
+| `/entities/health`              | `3.0.59413252-latin-onprem-amd64` (latin)            | `2022-08-15-preview`  |
+| `/entities/health`              | `3.0.59413252-semitic-onprem-amd64` (semitic)            | `2022-08-15-preview`  |
+| `/entities/health`              | `3.0.016230002-onprem-amd64`            | `2021-05-15`  |
 | `/entities/health`              | `3.0.015370001-onprem-amd64`            | `2021-03-01`  |
 | `/entities/health`              | `1.1.013530001-amd64-preview`           | `2020-09-03`  |
 | `/entities/health`              | `1.1.013150001-amd64-preview`           | `2020-07-24`  |
@@ -56,7 +61,7 @@ The [Text Analytics for health container](use-containers.md) uses separate model
 
 ### Input languages
 
-Currently the Text Analytics for health only [supports](../language-support.md) the English language. 
+Currently the Text Analytics for health hosted API only [supports](../language-support.md) the English language. Additional languages are currently in preview when deploying the API in a container, as detailed [under Text Analytics for health languages support](../language-support.md).
 
 ## Submitting data
 

articles/cognitive-services/language-service/text-analytics-for-health/how-to/use-containers.md

@@ -8,7 +8,7 @@ manager: nitinme
 ms.service: cognitive-services
 ms.subservice: language-service
 ms.topic: how-to
-ms.date: 04/20/2022
+ms.date: 09/05/2022
 ms.author: aahi
 ms.custom: language-service-health, ignite-fall-2021, devx-track-azurecli 
 ms.devlang: azurecli
@@ -46,13 +46,12 @@ CPU core and memory correspond to the `--cpus` and `--memory` settings, which ar
 
 ## Get the container image with `docker pull`
 
-Use the [`docker pull`](https://docs.docker.com/engine/reference/commandline/pull/) command to download this container image from the Microsoft public container registry.
+Use the [`docker pull`](https://docs.docker.com/engine/reference/commandline/pull/) command to download this container image from the Microsoft public container registry. You can find the featured tags on the  [dockerhub page](https://hub.docker.com/_/microsoft-azure-cognitive-services-textanalytics-healthcare)  
 
 ```
-docker pull mcr.microsoft.com/azure-cognitive-services/textanalytics/healthcare:latest
+docker pull mcr.microsoft.com/azure-cognitive-services/textanalytics/healthcare:<tag-name>
 ```
 
-
 [!INCLUDE [Tip for using docker list](../../../../../includes/cognitive-services-containers-docker-list-tip.md)]
 
 ## Run the container with `docker run`
@@ -84,7 +83,7 @@ To run the container in your own environment after downloading the container ima
 
 ```bash
 docker run --rm -it -p 5000:5000 --cpus 6 --memory 12g \
-mcr.microsoft.com/azure-cognitive-services/textanalytics/healthcare:latest \
+mcr.microsoft.com/azure-cognitive-services/textanalytics/healthcare:<tag-name> \
 Eula=accept \
 rai_terms=accept \
 Billing={ENDPOINT_URI} \

articles/cognitive-services/language-service/text-analytics-for-health/language-support.md

@@ -8,32 +8,91 @@ manager: nitinme
 ms.service: cognitive-services
 ms.subservice: language-service
 ms.topic: conceptual
-ms.date: 11/02/2021
+ms.date: 9/5/2022
 ms.author: aahi
 ms.custom: language-service-health, ignite-fall-2021
 ---
 
 # Language support for Text Analytics for health
 
-> [!NOTE]
-> * The container uses different model versions than the API endpoints and SDK.
-> * Languages are added as new model versions are released. The current [model versions](how-to/call-api.md#specify-the-text-analytics-for-health-model) for Text Analytics for health are:
->    * API and SDK: `2021-05-15`
->    * Container: `2021-03-01`
-
 Use this article to learn which natural languages are supported by Text Analytics for health and its Docker container. 
 
-## REST API and client library
+## Hosted API Service
 
-| Language | Language code | Starting with v3 model version: | Notes |
-|:---------|:-------------:|:-----------------------------------------:|:-----:|
-| English  |     `en`      |                API endpoint and client library: 2019-10-01                 |       |
+The hosted API service supports English language, model version 03-01-2022.
 
 ## Docker container
 
-| Language | Language code | Starting with v3 model version: | Notes |
-|:---------|:-------------:|:-----------------------------------------:|:-----:|
-| English  |     `en`      |                Container: 2020-04-16                |       |
+The docker container supports English language, model version 03-01-2022. 
+Additional languages are also supported when using a docker container to deploy the API: Spanish, French, German Italian, Portuguese and Hebrew. This functionality is currently in preview, model version 2022-08-15-preview.
+Full details for deploying the service in a container can be found [here](../text-analytics-for-health/how-to/use-containers.md).
+
+In order to download the new container images from the Microsoft public container registry, use the [docker pull](https://docs.docker.com/engine/reference/commandline/pull/) command, as follows :
+
+For English, Spanish, Italian, French, German and Portuguese:
+
+```
+docker pull mcr.microsoft.com/azure-cognitive-services/textanalytics/latin
+```
+
+For Hebrew:
+
+```
+docker pull mcr.microsoft.com/azure-cognitive-services/textanalytics/semitic
+```
+
+
+When structuring the API request, the relevant language tags must be added for these languages: 
+
+```
+English – “en”
+Spanish – “es”
+French  - “fr”
+German – “de”
+Italian – “it”
+Portuguese – “pt”
+Hebrew – “he”
+```
+
+The following json is an example of a JSON file attached to the Language request's POST body, for a Spanish document:
+
+```json
+json
+
+{
+    "analysisInput": {
+        "documents": [
+            {
+                "text": "El médico prescrió 200 mg de ibuprofeno.",
+                "language": "es",
+                "id": "1"
+            }
+        ]
+    },
+    "tasks": [
+        {
+            "taskName": "analyze 1",
+            "kind": "Healthcare",
+            "parameters": {
+                "fhirVersion": "4.0.1"
+            }
+        }
+    ]
+}
+```
+## Details of the supported model versions for each language:
+
+
+| Language code       | model version: |  Featured Tag | Specific Tag |
+|:--------------------|:-------------:|:-------------------:|:------------------:|
+| en                  |  2022-03-01   |      latest         |   3.0.59413252-onprem-amd64    | 
+| en,es,it,fr,de,pt   |  2022-08-15-preview  |      latin         |   3.0.59413252-latin-onprem-amd64   | 
+| he                  |  2022-08-15-preview   |      semitic         |   3.0.59413252-semitic-onprem-amd64   | 
+
+
+
+
+
 
 ## See also
 

articles/postgresql/flexible-server/overview.md

@@ -98,7 +98,7 @@ One advantage of running your workload in Azure is global reach. The flexible se
 | Brazil South | :heavy_check_mark: (v3 only) | :x: | :x: |
 | Canada Central | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | 
 | Canada East | :heavy_check_mark: | :x: | :heavy_check_mark: |
-| Central India | :heavy_check_mark: | :heavy_check_mark: ** | :heavy_check_mark: |
+| Central India | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
 | Central US | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
 | China East 3 | :heavy_check_mark: | :x: | :x:|
 | China North 3 | :heavy_check_mark: | :x: | :x:|

articles/virtual-machine-scale-sets/virtual-machine-scale-sets-use-availability-zones.md

@@ -43,7 +43,7 @@ When you deploy a scale set, you also have the option to deploy with a single [p
 
 ### Zone balancing
 
-Finally, for scale sets deployed across multiple zones, you also have the option of choosing "best effort zone balance" or "strict zone balance". A scale set is considered "balanced" if each zone the same number of VMs or +\\- 1 VM in all other zones for the scale set. For example:
+Finally, for scale sets deployed across multiple zones, you also have the option of choosing "best effort zone balance" or "strict zone balance". A scale set is considered "balanced" if each zone has the same number of VMs +\\- 1 VM as all other zones for the scale set. For example:
 
 - A scale set with 2 VMs in zone 1, 3 VMs in zone 2, and 3 VMs in zone 3 is considered balanced. There is only one zone with a different VM count and it is only 1 less than the other zones.
 - A scale set with 1 VM in zone 1, 3 VMs in zone 2, and 3 VMs in zone 3 is considered unbalanced. Zone 1 has 2 fewer VMs than zones 2 and 3.