Merge pull request #215073 from MicrosoftDocs/repo_sync_working_branch

huypub · web-flow · commit dcb1191e26ca · 2022-10-19T14:40:51.000-07:00
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
diff --git a/articles/active-directory-b2c/threat-management.md b/articles/active-directory-b2c/threat-management.md
@@ -55,7 +55,7 @@ The smart lockout feature uses many factors to determine when an account should
 - Passwords such as 12456! and 1234567! (or newAccount1234 and newaccount1234) are so similar that the algorithm interprets them as human error and counts them as a single try.
 - Larger variations in pattern, such as 12456! and ABCD2!, are counted as separate tries.
 
-When testing the smart lockout feature, use a distinctive pattern for each password you enter. Consider using password generation web apps, such as `https://passwordsgenerator.net/`.
+When testing the smart lockout feature, use a distinctive pattern for each password you enter. Consider using password generation web apps, such as `https://password-generator.net/`.
 
 When the smart lockout threshold is reached, you'll see the following message while the account is locked: **Your account is temporarily locked to prevent unauthorized use. Try again later**. The error messages can be [localized](localization-string-ids.md#sign-up-or-sign-in-error-messages).
 
diff --git a/articles/active-directory/develop/userinfo.md b/articles/active-directory/develop/userinfo.md
@@ -17,13 +17,13 @@ ms.custom: aaddev
 
 # Microsoft identity platform UserInfo endpoint
 
-Part of the OpenID Connect (OIDC) standard, the [UserInfo endpoint](https://openid.net/specs/openid-connect-core-1_0.html#UserInfo) is returns information about an authenticated user. In the Microsoft identity platform, the UserInfo endpoint is hosted by Microsoft Graph at https://graph.microsoft.com/oidc/userinfo. 
+As part of the OpenID Connect (OIDC) standard, the [UserInfo endpoint](https://openid.net/specs/openid-connect-core-1_0.html#UserInfo) returns information about an authenticated user. In the Microsoft identity platform, the UserInfo endpoint is hosted by Microsoft Graph at https://graph.microsoft.com/oidc/userinfo. 
 
 ## Find the .well-known configuration endpoint
 
 You can find the UserInfo endpoint programmatically by reading the `userinfo_endpoint` field of the OpenID configuration document at `https://login.microsoftonline.com/common/v2.0/.well-known/openid-configuration`. We don't recommend hard-coding the UserInfo endpoint in your applications. Instead, use the OIDC configuration document to find the endpoint at runtime.
 
-The UserInfo endpoint is typically called automatically by [OIDC-compliant libraries](https://openid.net/developers/certified/) to get information about the user.From the [list of claims identified in the OIDC standard](https://openid.net/specs/openid-connect-core-1_0.html#StandardClaims), the Microsoft identity platform produces the name claims, subject claim, and email when available and consented to. 
+The UserInfo endpoint is typically called automatically by [OIDC-compliant libraries](https://openid.net/developers/certified/) to get information about the user. From the [list of claims identified in the OIDC standard](https://openid.net/specs/openid-connect-core-1_0.html#StandardClaims), the Microsoft identity platform produces the name claims, subject claim, and email when available and consented to. 
 
 ## Consider using an ID token instead
 
@@ -33,7 +33,7 @@ If you require more details about the user like manager or job title, call the [
 
 ## Calling the UserInfo endpoint
 
-UserInfo is a standard OAuth bearer token API hosted by Microsoft Graph. Call the UserInfo endpoint as you would any Microsoft Graph API by using the access token your application received when it requested access to Microsoft Graph. The UserInfo endpoint returns a JSON response containing claims about the user.
+UserInfo is a standard OAuth bearer token API hosted by Microsoft Graph. Call the UserInfo endpoint as you would call any Microsoft Graph API by using the access token your application received when it requested access to Microsoft Graph. The UserInfo endpoint returns a JSON response containing claims about the user.
 
 ### Permissions
 
@@ -69,11 +69,11 @@ Authorization: Bearer eyJ0eXAiOiJKV1QiLCJub25jZSI6Il…
 ```jsonc
 {
     "sub": "OLu859SGc2Sr9ZsqbkG-QbeLgJlb41KcdiPoLYNpSFA",
-    "name": "Mikah Ollenburg", // names all require the “profile” scope.
+    "name": "Mikah Ollenburg", // all names require the “profile” scope.
     "family_name": " Ollenburg",
     "given_name": "Mikah",
     "picture": "https://graph.microsoft.com/v1.0/me/photo/$value",
-    "email": "mikoll@contoso.com" //requires the “email” scope.
+    "email": "mikoll@contoso.com" // requires the “email” scope.
 }
 ```
 
diff --git a/articles/active-directory/verifiable-credentials/decentralized-identifier-overview.md b/articles/active-directory/verifiable-credentials/decentralized-identifier-overview.md
@@ -8,7 +8,7 @@ editor:
 ms.service: decentralized-identity
 ms.subservice: verifiable-credentials
 ms.topic: overview
-ms.date: 06/02/2022
+ms.date: 08/20/2022
 ms.author: barclayn
 ms.reviewer: 
 ---
diff --git a/articles/active-directory/verifiable-credentials/how-to-dnsbind.md b/articles/active-directory/verifiable-credentials/how-to-dnsbind.md
@@ -17,6 +17,7 @@ ms.author: barclayn
 
 [!INCLUDE [Verifiable Credentials announcement](../../../includes/verifiable-credentials-brand.md)]
 
+
 ## Prerequisites
 
 To link your DID to your domain, you need to have completed the following.
diff --git a/articles/active-directory/verifiable-credentials/how-to-opt-out.md b/articles/active-directory/verifiable-credentials/how-to-opt-out.md
@@ -24,6 +24,7 @@ In this article:
 - What happens to your data?
 - Effect on existing verifiable credentials.
 
+
 ## Prerequisites
 
 - Complete verifiable credentials onboarding.
diff --git a/articles/active-directory/verifiable-credentials/how-to-register-didwebsite.md b/articles/active-directory/verifiable-credentials/how-to-register-didwebsite.md
@@ -17,6 +17,7 @@ ms.author: barclayn
 
 [!INCLUDE [Verifiable Credentials announcement](../../../includes/verifiable-credentials-brand.md)]
 
+
 ## Prerequisites
 
 - Complete verifiable credentials onboarding with Web as the selected trust system.
diff --git a/articles/active-directory/verifiable-credentials/how-to-use-quickstart-idtoken.md b/articles/active-directory/verifiable-credentials/how-to-use-quickstart-idtoken.md
@@ -17,6 +17,7 @@ ms.author: barclayn
 
 [!INCLUDE [Verifiable Credentials announcement](../../../includes/verifiable-credentials-brand.md)]
 
+
 A [rules definition](rules-and-display-definitions-model.md#rulesmodel-type) that uses the [idTokens attestation](rules-and-display-definitions-model.md#idtokenattestation-type) produces an issuance flow where you're required to do an interactive sign-in to an OpenID Connect (OIDC) identity provider in Microsoft Authenticator. Claims in the ID token that the identity provider returns can be used to populate the issued verifiable credential. The claims mapping section in the rules definition specifies which claims are used. 
 
 ## Create a custom credential with the idTokens attestation type
diff --git a/articles/active-directory/verifiable-credentials/how-to-use-quickstart-selfissued.md b/articles/active-directory/verifiable-credentials/how-to-use-quickstart-selfissued.md
@@ -17,6 +17,7 @@ ms.author: barclayn
 
 [!INCLUDE [Verifiable Credentials announcement](../../../includes/verifiable-credentials-brand.md)]
 
+
 A [rules definition](rules-and-display-definitions-model.md#rulesmodel-type) that uses the [selfIssued attestation](rules-and-display-definitions-model.md#selfissuedattestation-type) type produces an issuance flow where you're required to manually enter values for the claims in Microsoft Authenticator.  
 
 ## Create a custom credential with the selfIssued attestation type
diff --git a/articles/active-directory/verifiable-credentials/how-use-vcnetwork.md b/articles/active-directory/verifiable-credentials/how-use-vcnetwork.md
@@ -17,6 +17,7 @@ ms.author: barclayn
 
 [!INCLUDE [Verifiable Credentials announcement](../../../includes/verifiable-credentials-brand.md)]
 
+
 ## Prerequisites
 
 To use the Entra Verified ID Network, you need to have completed the following.
diff --git a/articles/active-directory/verifiable-credentials/introduction-to-verifiable-credentials-architecture.md b/articles/active-directory/verifiable-credentials/introduction-to-verifiable-credentials-architecture.md
@@ -15,6 +15,7 @@ ms.author: barclayn
 
 [!INCLUDE [Verifiable Credentials announcement](../../../includes/verifiable-credentials-brand.md)]
 
+
 It’s important to plan your verifiable credential solution so that in addition to issuing and or validating credentials, you have a complete view of the architectural and business impacts of your solution. If you haven’t reviewed them already, we recommend you review  [Introduction to Microsoft Entra Verified ID](decentralized-identifier-overview.md) and the [FAQs](verifiable-credentials-faq.md), and then complete the [Getting Started](get-started-verifiable-credentials.md) tutorial. 
 
 This architectural overview introduces the capabilities and components of the Microsoft Entra Verified ID service. For more detailed information on issuance and validation, see 
diff --git a/articles/active-directory/verifiable-credentials/plan-issuance-solution.md b/articles/active-directory/verifiable-credentials/plan-issuance-solution.md
@@ -16,6 +16,7 @@ ms.custom: references_regions
 
 [!INCLUDE [Verifiable Credentials announcement](../../../includes/verifiable-credentials-brand.md)]
 
+
 It’s important to plan your issuance solution so that in addition to issuing credentials, you have a complete view of the architectural and business impacts of your solution. If you haven’t done so, we recommend you view the [Microsoft Entra Verified ID architecture overview](introduction-to-verifiable-credentials-architecture.md) for foundational information.
 
 ## Scope of guidance
diff --git a/articles/active-directory/verifiable-credentials/plan-verification-solution.md b/articles/active-directory/verifiable-credentials/plan-verification-solution.md
@@ -16,6 +16,7 @@ ms.custom: references_regions
 
 [!INCLUDE [Verifiable Credentials announcement](../../../includes/verifiable-credentials-brand.md)]
 
+
 Microsoft’s Microsoft Entra Verified ID (Azure AD VC) service enables you to trust proofs of user identity without expanding your trust boundary. With Azure AD VC, you create accounts or federate with another identity provider. When a solution implements a verification exchange using verifiable credentials, it enables applications to request credentials that aren't bound to a specific domain. This approach makes it easier to request and verify credentials at scale.
 
 If you haven’t already, we suggest you review the [Microsoft Entra Verified ID architecture overview](introduction-to-verifiable-credentials-architecture.md). You may also want to review [Plan your Microsoft Entra Verified ID issuance solution](plan-issuance-solution.md).
diff --git a/articles/active-directory/verifiable-credentials/verifiable-credentials-faq.md b/articles/active-directory/verifiable-credentials/verifiable-credentials-faq.md
@@ -21,6 +21,7 @@ This page contains commonly asked questions about Verifiable Credentials and Dec
 - [Conceptual questions about decentralized identity](#conceptual-questions)
 - [Questions about using Verifiable Credentials preview](#using-the-preview)
 
+
 ## The basics
 
 ### What is a DID? 
diff --git a/articles/aks/integrations.md b/articles/aks/integrations.md
@@ -13,7 +13,7 @@ Azure Kubernetes Service (AKS) provides additional, supported functionality for
 
 ## Add-ons
 
-Add-ons are a fully supported way to provide extra capabilities for your AKS cluster. Add-ons' installation, configuration, and lifecycle is managed by AKS. Use `az aks addon` to install an add-on or manage the add-ons for your cluster.
+Add-ons are a fully supported way to provide extra capabilities for your AKS cluster. Add-ons' installation, configuration, and lifecycle is managed by AKS. Use `az aks enable-addons` to install an add-on or manage the add-ons for your cluster.
 
 The following rules are used by AKS for applying updates to installed add-ons:
 
@@ -123,4 +123,4 @@ The below table shows a few examples of open-source and third-party integrations
 [azure/k8s-artifact-substitute]: https://github.com/Azure/k8s-artifact-substitute
 [azure/aks-create-action]: https://github.com/Azure/aks-create-action
 [azure/aks-github-runner]: https://github.com/Azure/aks-github-runner
-[github-actions-aks]: kubernetes-action.md
+[github-actions-aks]: kubernetes-action.md
diff --git a/articles/azure-monitor/logs/search-jobs.md b/articles/azure-monitor/logs/search-jobs.md
@@ -16,7 +16,7 @@ Search jobs are asynchronous queries that fetch records into a new search table
 
 ## When to use search jobs
 
-Use a search job when the log query timeout of 10 minutes isn't sufficient to search through large volumes of data or if your running a slow query.
+Use a search job when the log query timeout of 10 minutes isn't sufficient to search through large volumes of data or if you're running a slow query.
 
 Search jobs also let you retrieve records from [Archived Logs](data-retention-archive.md) and [Basic Logs](basic-logs-configure.md) tables into a new log table you can use for queries. In this way, running a search job can be an alternative to:
 
diff --git a/articles/cognitive-services/language-service/text-analytics-for-health/how-to/call-api.md b/articles/cognitive-services/language-service/text-analytics-for-health/how-to/call-api.md
@@ -38,6 +38,7 @@ By default, Text Analytics for health will use the latest available AI model on
 
 | Supported Versions | latest version |
 |--|--|
+| `2022-08-15-preview` | `2022-08-15-preview`   |
 | `2022-03-01` | `2022-03-01`   |
 | `2021-05-15` | `2021-05-15`   |
 
@@ -61,7 +62,7 @@ The [Text Analytics for health container](use-containers.md) uses separate model
 
 ### Input languages
 
-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).
+The Text Analytics for health supports English in addition to multiple languages that are currently in preview. You can use the hosted API or deploy the API in a container, as detailed [under Text Analytics for health languages support](../language-support.md).
 
 ## Submitting data
 
@@ -75,6 +76,17 @@ Analysis is performed upon receipt of the request. If you send a request using t
 [!INCLUDE [asynchronous-result-availability](../../includes/async-result-availability.md)]
 
 
+## Submitting a Fast Healthcare Interoperability Resources (FHIR) request
+
+To receive your result using the **FHIR** structure, you must send the FHIR version in the API request body. You can also send the **document type** as a parameter to the FHIR API request body. If the request does not specify a document type, the value is set to none.
+
+| Parameter Name  | Type |  Value |
+|--|--|--|
+| fhirVersion |  string  | `4.0.1` |
+| documentType | string | `ClinicalTrial`, `Consult`, `DischargeSummary`,  `HistoryAndPhysical`, `Imaging`, `None`, `Pathology`, `ProcedureNote`, `ProgressNote`|
+
+
+
 ## Getting results from the feature
 
 Depending on your API request, and the data you submit to the Text Analytics for health, you will get:
diff --git a/articles/cognitive-services/language-service/text-analytics-for-health/language-support.md b/articles/cognitive-services/language-service/text-analytics-for-health/language-support.md
@@ -19,7 +19,40 @@ Use this article to learn which natural languages are supported by Text Analytic
 
 ## Hosted API Service
 
-The hosted API service supports English language, model version 03-01-2022.
+The hosted API service supports English language, model version 03-01-2022. Additional languages, English, Spanish, French, German Italian, Portuguese and Hebrew are supported with model version 2022-08-15-preview.
+
+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”
+```
+```json
+json
+
+{
+    "analysisInput": {
+        "documents": [
+            {
+                "text": "El médico prescrió 200 mg de ibuprofeno.",
+                "language": "es",
+                "id": "1"
+            }
+        ]
+    },
+    "tasks": [
+        {
+            "taskName": "analyze 1",
+            "kind": "Healthcare",
+        }
+    ]
+}
+```
 
 ## Docker container
 
diff --git a/articles/cognitive-services/language-service/text-analytics-for-health/quickstart.md b/articles/cognitive-services/language-service/text-analytics-for-health/quickstart.md
@@ -19,7 +19,7 @@ zone_pivot_groups: programming-languages-text-analytics
 # Quickstart: Using Text Analytics for health client library and REST API
 
 > [!IMPORTANT]
-> Fast Healthcare Interoperability Resources (FHIR) structuring is available for preview using the Language REST API. The client libraries are not currently supported.
+> Fast Healthcare Interoperability Resources (FHIR) structuring is available for preview using the Language REST API. The client libraries are not currently supported. [Learn more](./how-to/call-api.md) on how to use FHIR structuring in your API call.
 
 ::: zone pivot="programming-language-csharp"
 
diff --git a/articles/cognitive-services/language-service/whats-new.md b/articles/cognitive-services/language-service/whats-new.md
@@ -28,7 +28,8 @@ Azure Cognitive Service for Language is updated on an ongoing basis. To stay up-
 * Expanded language support for:
     * [Sentiment analysis](./sentiment-opinion-mining/language-support.md)
     * [Key phrase extraction](./key-phrase-extraction/language-support.md)
-    * [Named entity recognition](./key-phrase-extraction/language-support.md)
+    * [Named entity recognition](./named-entity-recognition/language-support.md)
+    * [Text Analytics for health](./text-analytics-for-health/language-support.md)
 * [Multi-region deployment](./concepts/custom-features/multi-region-deployment.md) and [project asset versioning](./concepts/custom-features/project-versioning.md) for: 
     * [Conversational language understanding](./conversational-language-understanding/overview.md)
     * [Orchestration workflow](./orchestration-workflow/overview.md)
@@ -40,7 +41,8 @@ Azure Cognitive Service for Language is updated on an ongoing basis. To stay up-
     * [Conversational language understanding](./conversational-language-understanding/service-limits.md#regional-availability)
     * [Orchestration workflow](./orchestration-workflow/service-limits.md#regional-availability)
     * [Custom text classification](./custom-text-classification/service-limits.md#regional-availability) 
-    * [Custom named entity recognition](./custom-named-entity-recognition/service-limits.md#regional-availability)
+    * [Custom named entity recognition](./custom-named-entity-recognition/service-limits.md#regional-availability) 
+* Document type as an input supported for [Text Analytics for health](./text-analytics-for-health/how-to/call-api.md) FHIR requests 
 
 ## September 2022
 
diff --git a/articles/cosmos-db/nosql/query/getting-started.md b/articles/cosmos-db/nosql/query/getting-started.md
@@ -23,6 +23,7 @@ Here are some examples of how to do **Point reads** with each SDK:
 - [Java SDK](/java/api/com.azure.cosmos.cosmoscontainer.readitem#com-azure-cosmos-cosmoscontainer-(t)readitem(java-lang-string-com-azure-cosmos-models-partitionkey-com-azure-cosmos-models-cosmositemrequestoptions-java-lang-class(t)))
 - [Node.js SDK](/javascript/api/@azure/cosmos/item#@azure-cosmos-item-read)
 - [Python SDK](/python/api/azure-cosmos/azure.cosmos.containerproxy#azure-cosmos-containerproxy-read-item)
+- [Go SDK](https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/data/azcosmos#ContainerClient.ReadItem)
 
 **SQL queries** - You can query data by writing queries using the Structured Query Language (SQL) as a JSON query language. Queries always cost at least 2.3 request units and, in general, will have a higher and more variable latency than point reads. Queries can return many items.
 
@@ -34,6 +35,7 @@ Here are some examples of how to do **SQL queries** with each SDK:
 - [Java SDK](../samples-java.md#query-examples)
 - [Node.js SDK](../samples-nodejs.md#item-examples)
 - [Python SDK](../samples-python.md#item-examples)
+- [Go SDK](../samples-go.md#item-examples)
 
 The remainder of this doc shows how to get started writing SQL queries in Azure Cosmos DB. SQL queries can be run through either the SDK or Azure portal.
 
diff --git a/articles/iot-edge/how-to-provision-devices-at-scale-linux-symmetric.md b/articles/iot-edge/how-to-provision-devices-at-scale-linux-symmetric.md
@@ -132,7 +132,7 @@ Have the following information ready:
 
 1. Update the values of `id_scope`, `registration_id`, and `symmetric_key` with your DPS and device information.
 
-   The symmetric key parameter can accept a value of an inline key, a file URI, or a PKCS#11 URI. Uncomment just one symmetric key line, based on which format you're using.
+   The symmetric key parameter can accept a value of an inline key, a file URI, or a PKCS#11 URI. Uncomment just one symmetric key line, based on which format you're using. When using an inline key, use a base64-encoded key like the example. When using a file URI, your file should contain the raw bytes of the key.
 
    If you use any PKCS#11 URIs, find the **PKCS#11** section in the config file and provide information about your PKCS#11 configuration.
 
diff --git a/articles/machine-learning/tutorial-train-deploy-image-classification-model-vscode.md b/articles/machine-learning/tutorial-train-deploy-image-classification-model-vscode.md
@@ -61,7 +61,7 @@ The first thing you have to do to build an application in Azure Machine Learning
     $schema: https://azuremlschemas.azureedge.net/latest/workspace.schema.json
     name: TeamWorkspace
     location: WestUS2
-    friendly_name: team-ml-workspace
+    display_name: team-ml-workspace
     description: A workspace for training machine learning models
     tags:
       purpose: training
@@ -114,13 +114,11 @@ Like workspaces and compute targets, training jobs are defined using resource te
 
 ```yml
 $schema: https://azuremlschemas.azureedge.net/latest/commandJob.schema.json
-code: 
-    local_path: src
+code: src
 command: >
     python train.py
-environment: azureml:AzureML-TensorFlow2.4-Cuda11-OpenMpi4.1.0-py36:1
-compute:
-    target: azureml:gpu-cluster
+environment: azureml:AzureML-tensorflow-2.4-ubuntu18.04-py37-cuda11-gpu:48
+compute: azureml:gpu-cluster
 experiment_name: tensorflow-mnist-example
 description: Train a basic neural network with TensorFlow on the MNIST dataset.
 ```
diff --git a/articles/postgresql/flexible-server/concepts-pgbouncer.md b/articles/postgresql/flexible-server/concepts-pgbouncer.md
@@ -45,7 +45,7 @@ For more details on the PgBouncer configurations, please see [pgbouncer.ini](htt
 
 ## Monitoring PgBouncer statistics 
 
-PgBouncer also provides an **internal* database that you can connect to called `pgbouncer`. Once connected to the database you can execute `SHOW` commands that provide information on the current state of pgbouncer.
+PgBouncer also provides an **internal** database that you can connect to called `pgbouncer`. Once connected to the database you can execute `SHOW` commands that provide information on the current state of pgbouncer.
 
 Steps to connect to `pgbouncer` database
 1. Set `pgBouncer.stats_users` parameter to the name of an existing user (ex. "myUser"), and apply the changes.
diff --git a/articles/sentinel/sap/sap-solution-log-reference.md b/articles/sentinel/sap/sap-solution-log-reference.md
diff --git a/articles/sentinel/sap/sap-solution-security-content.md b/articles/sentinel/sap/sap-solution-security-content.md
diff --git a/articles/service-fabric/service-fabric-resource-governance.md b/articles/service-fabric/service-fabric-resource-governance.md
diff --git a/articles/storage/common/infrastructure-encryption-enable.md b/articles/storage/common/infrastructure-encryption-enable.md
diff --git a/articles/storage/common/media/infrastructure-encryption-enable/create-account-infrastructure-encryption-portal.png b/articles/storage/common/media/infrastructure-encryption-enable/create-account-infrastructure-encryption-portal.png
diff --git a/articles/web-application-firewall/ag/application-gateway-crs-rulegroups-rules.md b/articles/web-application-firewall/ag/application-gateway-crs-rulegroups-rules.md
diff --git a/includes/vpn-gateway-connect-vm.md b/includes/vpn-gateway-connect-vm.md
