Merge pull request #195051 from MicrosoftDocs/repo_sync_working_branch

huypub · web-flow · commit c5a13507e8f6 · 2022-04-14T09:51:18.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/app-service/resources-kudu.md b/articles/app-service/resources-kudu.md
@@ -37,7 +37,7 @@ It also provides other features, such as:
 - Generates [custom deployment scripts](https://github.com/projectkudu/kudu/wiki/Custom-Deployment-Script).
 - Allows access with [REST API](https://github.com/projectkudu/kudu/wiki/REST-API).
 
-## RBAC permissions required to access Kudo
+## RBAC permissions required to access Kudu
 To access Kudu in the browser with Azure Active Directory authentication, you need to be a member of a built-in or custom role.
 
 - If using a built-in role, you must be a member of Website Contributor, Contributor, or Owner.
diff --git a/articles/azure-arc/data/toc.yml b/articles/azure-arc/data/toc.yml
@@ -169,7 +169,7 @@ items:
               href: using-extensions-in-postgresql-hyperscale-server-group.md
         - name: Migrate
           items:
-            - name: Migrate PostgreSQL data into a Postgres Hyperscale server group
+            - name: Migrate PostgreSQL data into a PostgreSQL Hyperscale server group
               href: migrate-postgresql-data-into-postgresql-hyperscale-server-group.md
             - name: Import the sample database AdventureWorks
               href: restore-adventureworks-sample-db-into-postgresql-hyperscale-server-group.md
diff --git a/articles/azure-resource-manager/bicep/deploy-github-actions.md b/articles/azure-resource-manager/bicep/deploy-github-actions.md
@@ -12,7 +12,7 @@ ms.custom: github-actions-azure
 
 [GitHub Actions](https://docs.github.com/en/actions) is a suite of features in GitHub to automate your software development workflows.
 
-In this quickstart, you use the [GitHub Action for Azure Resource Manager deployment](https://github.com/marketplace/actions/deploy-azure-resource-manager-arm-template) to automate deploying a Bicep file to Azure.
+In this quickstart, you use the [GitHub Actions for Azure Resource Manager deployment](https://github.com/marketplace/actions/deploy-azure-resource-manager-arm-template) to automate deploying a Bicep file to Azure.
 
 It provides a short introduction to GitHub actions and Bicep files. If you want more detailed steps on setting up the GitHub actions and project, see [Learning path: Deploy Azure resources by using Bicep and GitHub Actions](/learn/paths/bicep-github-actions).
 
@@ -32,7 +32,7 @@ az group create -n exampleRG -l westus
 
 ## Generate deployment credentials
 
-Your GitHub action runs under an identity. Use the [az ad sp create-for-rbac](/cli/azure/ad/sp#az-ad-sp-create-for-rbac) command to create a [service principal](../../active-directory/develop/app-objects-and-service-principals.md#service-principal-object) for the identity.
+Your GitHub Actions runs under an identity. Use the [az ad sp create-for-rbac](/cli/azure/ad/sp#az-ad-sp-create-for-rbac) command to create a [service principal](../../active-directory/develop/app-objects-and-service-principals.md#service-principal-object) for the identity.
 
 Replace the placeholder `myApp` with the name of your application. Replace `{subscription-id}` with your subscription ID.
 
diff --git a/articles/cognitive-services/language-service/question-answering/concepts/azure-resources.md b/articles/cognitive-services/language-service/question-answering/concepts/azure-resources.md
@@ -30,7 +30,7 @@ When you move into the development phase of the project, you should consider:
 Typically there are three parameters you need to consider:
 
 * **The throughput you need**:
-    * Question answering is a free feature, and the throughput is currently capped at 10 transactions per second for both management APIs and prediction APIs.
+    * The throughput for question answering is currently capped at 10 transactions per second for both management APIs and prediction APIs.
     * This should also influence your Azure **Cognitive Search** SKU selection, see more details [here](../../../../search/search-sku-tier.md). Additionally, you may need to adjust Cognitive Search [capacity](../../../../search/search-capacity-planning.md) with replicas.
 
 * **Size and the number of knowledge bases**: Choose the appropriate [Azure search SKU](https://azure.microsoft.com/pricing/details/search/) for your scenario. Typically, you decide the number of knowledge bases you need based on number of different subject domains. One subject domain (for a single language) should be in one knowledge base.
@@ -42,7 +42,7 @@ Typically there are three parameters you need to consider:
 
     For example, if your tier has 15 allowed indexes, you can publish 14 knowledge bases of the same language (one index per published knowledge base). The 15th index is used for all the knowledge bases for authoring and testing. If you choose to have knowledge bases in different languages, then you can only publish seven knowledge bases.
 
-* **Number of documents as sources**: question answering is a free feature, and there are no limits to the number of documents you can add as sources. 
+* **Number of documents as sources**: There are no limits to the number of documents you can add as sources in question answering.
 
 The following table gives you some high-level guidelines.
 
@@ -54,7 +54,7 @@ The following table gives you some high-level guidelines.
 
 ## Recommended settings
 
-Custom question answering is a free feature, and the throughput is currently capped at 10 transactions per second for both management APIs and prediction APIs. To target 10 transactions per second for your service, we recommend the S1 (one instance) SKU of Azure Cognitive Search.
+The throughput for question answering is currently capped at 10 transactions per second for both management APIs and prediction APIs. To target 10 transactions per second for your service, we recommend the S1 (one instance) SKU of Azure Cognitive Search.
 
 ## Keys in question answering
 
diff --git a/articles/cosmos-db/sql/how-to-time-to-live.md b/articles/cosmos-db/sql/how-to-time-to-live.md
@@ -199,7 +199,7 @@ async function createcontainerWithTTL(db: Database, containerDefinition: Contain
 
 In addition to setting a default time to live on a container, you can set a time to live for an item. Setting time to live at the item level will override the default TTL of the item in that container.
 
-* To set the TTL on an item, you need to provide a non-zero positive number, which indicates the period, in seconds, to expire the item after the last modified timestamp of the item `_ts`.
+* To set the TTL on an item, you need to provide a non-zero positive number, which indicates the period, in seconds, to expire the item after the last modified timestamp of the item `_ts`. You can provide a `-1` as well when the item should not expire.
 
 * If the item doesn't have a TTL field, then by default, the TTL set to the container will apply to the item.
 
@@ -563,4 +563,4 @@ container = database.createContainerIfNotExists(containerProperties, 400).block(
 
 Learn more about time to live in the following article:
 
-* [Time to live](time-to-live.md)
+* [Time to live](time-to-live.md)
diff --git a/articles/iot-hub/iot-hub-mqtt-support.md b/articles/iot-hub/iot-hub-mqtt-support.md
@@ -70,7 +70,7 @@ In order to ensure a client/IoT Hub connection stays alive, both the service and
 |Language  |Default keep-alive interval  |Configurable  |
 |---------|---------|---------|
 |Node.js     |   180 seconds      |     No    |
-|Java     |    230 seconds     |     No    |
+|Java     |    230 seconds     |     [Yes](https://github.com/Azure/azure-iot-sdk-java/blob/main/device/iot-device-client/src/main/java/com/microsoft/azure/sdk/iot/device/ClientOptions.java#L64)    |
 |C     | 240 seconds |  [Yes](https://github.com/Azure/azure-iot-sdk-c/blob/master/doc/Iothub_sdk_options.md#mqtt-transport)   |
 |C#     | 300 seconds |  [Yes](https://github.com/Azure/azure-iot-sdk-csharp/blob/main/iothub/device/src/Transport/Mqtt/MqttTransportSettings.cs#L89)   |
 |Python   | 60 seconds |  No   |
diff --git a/articles/sentinel/authentication-normalization-schema.md b/articles/sentinel/authentication-normalization-schema.md
@@ -62,12 +62,12 @@ The following filtering parameters are available:
 
 | Name     | Type      | Description |
 |----------|-----------|-------------|
-| **starttime** | datetime | Filter only DNS queries that ran at or after this time. |
-| **endtime** | datetime | Filter only DNS queries that finished running at or before this time. |
+| **starttime** | datetime | Filter only authentication events that ran at or after this time. |
+| **endtime** | datetime | Filter only authentication events that finished running at or before this time. |
 | **targetusername_has** | string | Filter only authentication events that has any of the listed user names. |
 
 
-For example, to filter only DNS queries from the last day to a specific user, use:
+For example, to filter only authentication events from the last day to a specific user, use:
 
 ```kql
 imAuthentication (targetusername_has = 'johndoe', starttime = ago(1d), endtime=now())
diff --git a/articles/spring-cloud/how-to-config-server.md b/articles/spring-cloud/how-to-config-server.md
@@ -174,7 +174,7 @@ Now that your configuration files are saved in a repository, you need to connect
 
    > [!CAUTION]
    > Some Git repository servers use a *personal-token* or an *access-token*, such as a password, for **Basic Authentication**. You can use that kind of token as a password in Azure Spring Cloud, because it will never expire. But for other Git repository servers, such as Bitbucket and Azure DevOps Server, the *access-token* expires in one or two hours. This means that the option isn't viable when you use those repository servers with Azure Spring Cloud.
-   > GitHub has removed support for password authentication, so you'll need to use a personal access token instead of password authentication for Github. For more information, see [Token authentication](https://github.blog/2020-12-15-token-authentication-requirements-for-git-operations/).
+   > GitHub has removed support for password authentication, so you'll need to use a personal access token instead of password authentication for GitHub. For more information, see [Token authentication](https://github.blog/2020-12-15-token-authentication-requirements-for-git-operations/).
 
    * **SSH**: In the **Default repository** section, in the **Uri** box, paste the repository URI, and then select the **Authentication** ("pencil" icon) button. In the **Edit Authentication** pane, in the **Authentication type** drop-down list, select **SSH**, and then enter your **Private key**. Optionally, specify your **Host key** and **Host key algorithm**. Be sure to include your public key in your Config Server repository. Select **OK**, and then select **Apply** to finish setting up your Config Server instance.
 
diff --git a/articles/synapse-analytics/whats-new-archive.md b/articles/synapse-analytics/whats-new-archive.md
@@ -41,7 +41,7 @@ Improvements to the Synapse Machine Learning library v0.9.5 (previously called M
 
 ### Synapse SQL
 
-* COPY schema discovery for complex data ingestion. To learn more, see the [blog post](https://techcommunity.microsoft.com/t5/azure-synapse-analytics-blog/azure-synapse-analytics-january-update-2022/ba-p/3071681#TOCREF_12) or [how Github leveraged this functionality in Introducing Automatic Schema Discovery with auto table creation for complex datatypes](https://techcommunity.microsoft.com/t5/azure-synapse-analytics-blog/introducing-automatic-schema-discovery-with-auto-table-creation/ba-p/3068927).
+* COPY schema discovery for complex data ingestion. To learn more, see the [blog post](https://techcommunity.microsoft.com/t5/azure-synapse-analytics-blog/azure-synapse-analytics-january-update-2022/ba-p/3071681#TOCREF_12) or [how GitHub leveraged this functionality in Introducing Automatic Schema Discovery with auto table creation for complex datatypes](https://techcommunity.microsoft.com/t5/azure-synapse-analytics-blog/introducing-automatic-schema-discovery-with-auto-table-creation/ba-p/3068927).
 
 * Serverless SQL pools now support the HASHBYTES function. HASHBYTES is a T-SQL function which hashes values. Learn how to use [hash values in distributing data using this article](/sql/t-sql/functions/hashbytes-transact-sql) or the [blog post](https://techcommunity.microsoft.com/t5/azure-synapse-analytics-blog/azure-synapse-analytics-january-update-2022/ba-p/3071681#TOCREF_13).
 
