Merge pull request #95441 from MicrosoftDocs/repo_sync_working_branch

huypub · web-flow · commit 60b0c4028d26 · 2019-11-11T09:34:54.000-08:00
Confirm merge from repo_sync_working_branch to master to sync with https://github.com/Microsoft/azure-docs (branch master)
diff --git a/articles/active-directory/develop/msal-net-initializing-client-applications.md b/articles/active-directory/develop/msal-net-initializing-client-applications.md
@@ -98,7 +98,7 @@ In the code snippets using application builders, a number of `.With` methods can
 
 The modifiers you can set on a public client or confidential client application builder are:
 
-|Parameter | Description|
+|Modifier | Description|
 |--------- | --------- |
 |`.WithAuthority()` 7 overrides | Sets the application default authority to an Azure AD authority, with the possibility of choosing the Azure Cloud, the audience, the tenant (tenant ID or domain name), or providing directly the authority URI.|
 |`.WithAdfsAuthority(string)` | Sets the application default authority to be an ADFS authority.|
@@ -117,15 +117,15 @@ The modifiers you can set on a public client or confidential client application
 
 The modifiers you can set on a public client application builder on Xamarin.iOS are:
 
-|Parameter | Description|
+|Modifier | Description|
 |--------- | --------- |
 |`.WithIosKeychainSecurityGroup()` | **Xamarin.iOS only**: Sets the iOS key chain security group (for the cache persistence).|
 
 ### Modifiers specific to confidential client applications
 
 The modifiers you can set on a confidential client application builder are:
 
-|Parameter | Description|
+|Modifier | Description|
 |--------- | --------- |
 |`.WithCertificate(X509Certificate2 certificate)` | Sets the certificate identifying the application with Azure AD.|
 |`.WithClientSecret(string clientSecret)` | Sets the client secret (app password) identifying the application with Azure AD.|
diff --git a/articles/active-directory/governance/entitlement-management-overview.md b/articles/active-directory/governance/entitlement-management-overview.md
@@ -23,7 +23,7 @@ ms.collection: M365-identity-device-management
 ---
 # What is Azure AD entitlement management?
 
-Azure Active Directory (Azure AD) entitlement management is a [identity governance](identity-governance-overview.md) feature that  enables organizations to manage identity and access lifecycle at scale, by automating access request workflows, access assignments, reviews, and expiration.
+Azure Active Directory (Azure AD) entitlement management is an [identity governance](identity-governance-overview.md) feature that  enables organizations to manage identity and access lifecycle at scale, by automating access request workflows, access assignments, reviews, and expiration.
 
 Employees in organizations need access to various groups, applications, and sites to perform their job. Managing this access is challenging, as requirements change - new applications are added or users need additional access rights.  This scenario gets more complicated when you collaborate with outside organizations - you may not know who in the other organization needs access to your organization's resources, and they won't know what applications, groups or sites your organization is using.
 
diff --git a/articles/active-directory/hybrid/reference-connect-version-history.md b/articles/active-directory/hybrid/reference-connect-version-history.md
@@ -38,9 +38,18 @@ Download| [Download Azure AD Connect](https://go.microsoft.com/fwlink/?LinkId=61
 While we go through this process, the version number of the release will be shown with an "X" in the minor release number position, as in "1.3.X.0" - this indicates that the release notes in this document are valid for all versions beginning with "1.3.". As soon as we have finalized the release process the release version number will be updated to the most recently released version and the release status will be updated to "Released for download and auto upgrade".
 Not all releases of Azure AD Connect will be made available for auto upgrade. The release status will indicate whether a release is made available for auto upgrade or for download only. If auto upgrade was enabled on your Azure AD Connect server then that server will automatically upgrade to the latest version of Azure AD Connect that is released for auto upgrade. Note that not all Azure AD Connect configurations are eligible for auto upgrade. Please follow this link to read more about [auto upgrade](https://docs.microsoft.com/azure/active-directory/hybrid/how-to-connect-install-automatic-upgrade)
 
-## 1.4.25.0
+## 1.4.32.0
+### Release status
+08/11/2019: Released for download. Not available for auto-upgrade
+
+>[!IMPORTANT]
+>Due to an internal schema change in this release of Azure AD Connect, if you manage ADFS trust relationship configuration settings using MSOnline PowerShell then you must update your MSOnline PowerShell module to version 1.1.183.57 or higher
+### Fixed issues
 
+This version fixes an issue with existing Hybrid Azure AD joined devices. This release contains a new device sync rule that corrects this issue.
+Note that this rule change may cause deletion of obsolete devices from Azure AD. This is not a cause for concern, as these device objects are not used by Azure AD during Conditional Access authorization. For some customers, the number of devices that will be deleted through this rule change can exceed the deletion threshold. If you see the deletion of device objects in Azure AD exceeding the Export Deletion Threshold, it is advised to allow the deletions to go through. [How to allow deletes to flow when they exceed the deletion threshold](https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-sync-feature-prevent-accidental-deletes)
 
+## 1.4.25.0
 
 ### Release status
 9/28/2019: Released for auto-upgrade to select tenants. Not available for download.
diff --git a/articles/aks/kubernetes-walkthrough.md b/articles/aks/kubernetes-walkthrough.md
@@ -29,7 +29,7 @@ If you don't have an Azure subscription, create a [free account](https://azure.m
 
 If you choose to install and use the CLI locally, this quickstart requires that you are running the Azure CLI version 2.0.64 or later. Run `az --version` to find the version. If you need to install or upgrade, see [Install Azure CLI][azure-cli-install].
 
-> [!Note]
+> [!NOTE]
 > If running the commands in this quickstart locally (instead of Azure Cloud Shell), ensure you run the commands as administrator.
 
 ## Create a resource group
@@ -61,7 +61,7 @@ The following example output shows the resource group created successfully:
 
 Use the [az aks create][az-aks-create] command to create an AKS cluster. The following example creates a cluster named *myAKSCluster* with one node. Azure Monitor for containers is also enabled using the *--enable-addons monitoring* parameter.  This will take several minutes to complete.
 
-> [NOTE]
+> [!NOTE]
 > When creating an AKS cluster a second resouce group is automatically created to store the AKS resources. For more information see [Why are two resource groups created with AKS?](https://docs.microsoft.com/azure/aks/faq#why-are-two-resource-groups-created-with-aks)
 
 ```azurecli-interactive
diff --git a/articles/aks/servicemesh-consul-about.md b/articles/aks/servicemesh-consul-about.md
@@ -32,7 +32,7 @@ The following architecture diagram demonstrates how the various components withi
 
 ## Selection criteria
 
-It's important to understand and consider the following areas when evaluating Linkerd for your workloads:
+It's important to understand and consider the following areas when evaluating Consul for your workloads:
 
 - [Consul Principles](#consul-principles)
 - [Capabilities](#capabilities)
@@ -107,4 +107,4 @@ You can also further explore Consul features and architecture:
 [prometheus]: https://prometheus.io/
 
 <!-- LINKS - internal -->
-[consul-install]: ./servicemesh-consul-install.md
+[consul-install]: ./servicemesh-consul-install.md
diff --git a/articles/app-service/networking-features.md b/articles/app-service/networking-features.md
@@ -87,7 +87,7 @@ You can learn how to set an address on your app with the tutorial on [Configurin
 
 ### Access Restrictions 
 
-The Access Restrictions capability lets you filter **inbound** requests based on the origination IP address. The filtering action takes place on the front-end roles that are upstream from the worker rolls where your apps are running. Since the front-end roles are upstream from the workers, the Access Restrictions capability can be regarded as network level protection for your apps. The feature allows you to build a list of allow and deny address blocks that are evaluated in priority order. It is similar to the Network Security Group (NSG) feature that exists in Azure Networking.  You can use this feature in an ASE or in the multi-tenant service. When used with an ILB ASE, you can restrict access from private address blocks.
+The Access Restrictions capability lets you filter **inbound** requests based on the origination IP address. The filtering action takes place on the front-end roles that are upstream from the worker roles where your apps are running. Since the front-end roles are upstream from the workers, the Access Restrictions capability can be regarded as network level protection for your apps. The feature allows you to build a list of allow and deny address blocks that are evaluated in priority order. It is similar to the Network Security Group (NSG) feature that exists in Azure Networking.  You can use this feature in an ASE or in the multi-tenant service. When used with an ILB ASE, you can restrict access from private address blocks.
 
 ![Access Restrictions](media/networking-features/access-restrictions.png)
 
diff --git a/articles/cognitive-services/Speech-Service/includes/quickstarts/quickstart-list.md b/articles/cognitive-services/Speech-Service/includes/quickstarts/quickstart-list.md
@@ -1,7 +1,7 @@
 - [Quickstart: Recognize speech from a microphone](~/articles/cognitive-services/speech-service/quickstarts/speech-to-text-from-microphone.md)
 - [Quickstart: Recognize speech from a file](~/articles/cognitive-services/speech-service/quickstarts/speech-to-text-from-file.md)
-- [Quickstart: Recognize speech from an Azure Blog](~/articles/cognitive-services/speech-service/quickstarts/from-blob.md)
+- [Quickstart: Recognize speech from an Azure Blob](~/articles/cognitive-services/speech-service/quickstarts/from-blob.md)
 - [Quickstart: Translate speech-to-text](~/articles/cognitive-services/speech-service/quickstarts/translate-speech-to-text.md)
 - [Quickstart: Synthesize text to an audio device](~/articles/cognitive-services/speech-service/quickstarts/text-to-speech.md)
 - [Quickstart: Synthesize text to a file](~/articles/cognitive-services/speech-service/quickstarts/text-to-speech-audio-file.md)
-- [Quickstart: Recognize Intents](~/articles/cognitive-services/speech-service/quickstarts/intent-recognition.md)
+- [Quickstart: Recognize Intents](~/articles/cognitive-services/speech-service/quickstarts/intent-recognition.md)
diff --git a/articles/cognitive-services/Speech-Service/long-audio-api.md b/articles/cognitive-services/Speech-Service/long-audio-api.md
@@ -21,6 +21,9 @@ Additional benefits of the Long Audio API:
 * Synthesized speech returned by the service uses neural voices, which ensures high-fidelity audio outputs.
 * Since real-time responses aren't supported, there's no need to deploy a voice endpoint.
 
+> [!NOTE]
+> The Long Audio API now supports only [Custom Neural Voice](https://docs.microsoft.com/azure/cognitive-services/speech-service/how-to-custom-voice#custom-neural-voices).
+
 ## Workflow
 
 Typically, when using the Long Audio API, you'll submit a text file or files to be synthesized, poll for the status, then if the status is successful, you can download the audio output.
diff --git a/articles/cosmos-db/set-throughput.md b/articles/cosmos-db/set-throughput.md
@@ -23,7 +23,7 @@ The throughput provisioned on an Azure Cosmos container is exclusively reserved
 
 Setting provisioned throughput on a container is the most frequently used option. You can elastically scale throughput for a container by provisioning any amount of throughput by using [Request Units (RUs)](request-units.md). 
 
-Assuming a good partition key that distributes the logical partitions evenly among the physical partitions, the throughput is also distributed evenly across all the logical partitions of the container. You cannot selectively specify the throughput for logical partitions. Because one or more logical partitions of a container are hosted by a physical partition, the physical partitions belong exclusively to the container and support the throughput provisioned on the container. 
+The throughput provisioned for a container is evenly distributed among its physical partitions, and assuming a good partition key that distributes the logical partitions evenly among the physical partitions, the throughput is also distributed evenly across all the logical partitions of the container. You cannot selectively specify the throughput for logical partitions. Because one or more logical partitions of a container are hosted by a physical partition, the physical partitions belong exclusively to the container and support the throughput provisioned on the container. 
 
 If the workload running on a logical partition consumes more than the throughput that was allocated to that logical partition, your operations get rate-limited. When rate-limiting occurs, you can either increase the provisioned throughput for the entire container or retry the operations. For more information on partitioning, see [Logical partitions](partition-data.md).
 
diff --git a/articles/sentinel/connect-cloud-app-security.md b/articles/sentinel/connect-cloud-app-security.md
@@ -26,7 +26,7 @@ You can stream logs from [Cloud App Security](https://docs.microsoft.com/cloud-a
 ## Prerequisites
 
 - User with global administrator or security administrator permissions
-- To stream Cloud Discovery logs into Azure Sentinel, [enable Azure Sentinel as your SIEM in Microsoft Cloud App Security](aka.ms.https://aka.ms/AzureSentinelMCAS).
+- To stream Cloud Discovery logs into Azure Sentinel, [enable Azure Sentinel as your SIEM in Microsoft Cloud App Security](https://aka.ms/AzureSentinelMCAS).
 
 > [!IMPORTANT]
 > Ingestion of Cloud Discovery logs is currently in public preview.
diff --git a/articles/site-recovery/hyper-v-azure-common-questions.md b/articles/site-recovery/hyper-v-azure-common-questions.md
@@ -142,16 +142,16 @@ You can replicate any app or workload running a Hyper-V VM that complies with [r
 
 ### Can I replicate to Azure with a site-to-site VPN?
 
-Site Recovery replicates data from on-premises to Azure storage over a public endpoint, or using ExpressRoute public peering. Replication over a site-to-site VPN network isn't supported.
+Site Recovery replicates data from on-premises to Azure storage over a public endpoint, or using ExpressRoute Microsoft peering. Replication over a site-to-site VPN network isn't supported.
 
 ### Can I replicate to Azure with ExpressRoute?
 
-Yes, ExpressRoute can be used to replicate VMs to Azure. Site Recovery replicates data to an Azure Storage Account over a public endpoint, and you need to set up [public peering](../expressroute/expressroute-circuit-peerings.md#publicpeering) for Site Recovery replication. After VMs fail over to an Azure virtual network, you can access them using [private peering](../expressroute/expressroute-circuit-peerings.md#privatepeering).
+Yes, ExpressRoute can be used to replicate VMs to Azure. Site Recovery replicates data to an Azure Storage Account over a public endpoint, and you need to set up [Microsoft peering](../expressroute/expressroute-circuit-peerings.md#microsoftpeering) for Site Recovery replication. After VMs fail over to an Azure virtual network, you can access them using [private peering](../expressroute/expressroute-circuit-peerings.md#privatepeering).
 
 
 ### Why can't I replicate over VPN?
 
-When you replicate to Azure, replication traffic reaches the public endpoints of an Azure Storage account. Thus you can only replicate over the public internet with ExpressRoute (public peering), and VPN doesn't work. 
+When you replicate to Azure, replication traffic reaches the public endpoints of an Azure Storage account. Thus you can only replicate over the public internet with ExpressRoute (Microsoft peering), and VPN doesn't work. 
 
 ### What are the replicated VM requirements?
 
diff --git a/articles/storage/blobs/TOC.yml b/articles/storage/blobs/TOC.yml
@@ -449,7 +449,7 @@
       - name: Storage Resource Provider
         href: /java/api/overview/azure/storage/management
     - name: JavaScript (version 12.x)
-      href: /javascript/api/@azure/storage-blob/?view=azure-node-preview
+      href: /javascript/api/@azure/storage-blob/
     - name: Python (version 12.x)
       href: /python/api/azure-storage-blob/
     - name: REST
diff --git a/articles/storage/blobs/storage-quickstart-blobs-nodejs.md b/articles/storage/blobs/storage-quickstart-blobs-nodejs.md
@@ -347,7 +347,7 @@ In this quickstart, you learned how to upload, download, and list blobs using Ja
 To see Blob storage sample apps, continue to:
 
 > [!div class="nextstepaction"]
-> [Azure Blob storage SDK v12 JavaScript samples](https://github.com/Azure/azure-sdk-for-js/tree/master/sdk/storage/azure-storage-blob/samples)
+> [Azure Blob storage SDK v12 JavaScript samples](https://github.com/Azure/azure-sdk-for-js/tree/master/sdk/storage/storage-blob/samples)
 
 * To learn more, see the [Azure SDK for JavaScript](https://github.com/Azure/azure-sdk-for-js/blob/master/sdk/storage/storage-blob/README.md).
 * For tutorials, samples, quick starts and other documentation, visit [Azure SDK for JavaScript documentation](/azure/javascript/).
diff --git a/articles/storage/queues/TOC.yml b/articles/storage/queues/TOC.yml
@@ -214,9 +214,9 @@
       href: /java/api/com.microsoft.azure.storage.queue
     - name: Storage Resource Provider
       href: /java/api/overview/azure/storage/management
-  - name: JavaScript (version 10.x)
+  - name: JavaScript (version 12.x)
     href: /javascript/api/@azure/storage-queue
-  - name: Python (version 2.x)
+  - name: Python (version 12.x)
     href: /python/api/azure-storage-queue/?view=azure-python
   - name: REST
     items:
diff --git a/articles/stream-analytics/stream-analytics-parallelization.md b/articles/stream-analytics/stream-analytics-parallelization.md
@@ -54,7 +54,7 @@ An *embarrassingly parallel* job is the most scalable scenario we have in Azure
 
 1. If your query logic depends on the same key being processed by the same query instance, you must make sure that the events go to the same partition of your input. For Event Hubs or IoT Hub, this means that the event data must have the **PartitionKey** value set. Alternatively, you can use partitioned senders. For blob storage, this means that the events are sent to the same partition folder. If your query logic does not require the same key to be processed by the same query instance, you can ignore this requirement. An example of this logic would be a simple select-project-filter query.  
 
-2. Once the data is laid out on the input side, you must make sure that your query is partitioned. This requires you to use **PARTITION BY** in all the steps. Multiple steps are allowed, but they all must be partitioned by the same key. Under compatibility level 1.0 and 1.1, the partitioning key must be set to **PartitionId** in order for the job to be fully parallel. For jobs with compatility level 1.2 and higher, custom column can be specified as Partition Key in the input settings and the job will be paralellized automoatically even without PARTITION BY clause.
+2. Once the data is laid out on the input side, you must make sure that your query is partitioned. This requires you to use **PARTITION BY** in all the steps. Multiple steps are allowed, but they all must be partitioned by the same key. Under compatibility level 1.0 and 1.1, the partitioning key must be set to **PartitionId** in order for the job to be fully parallel. For jobs with compatility level 1.2 and higher, custom column can be specified as Partition Key in the input settings and the job will be paralellized automatically even without PARTITION BY clause. For event hub output the property "Partition key column" must be set to use "PartitionId".
 
 3. Most of our output can take advantage of partitioning, however if you use an output type that doesn't support partitioning your job won't be fully parallel. Refer to the [output section](#outputs) for more details.
 
@@ -71,7 +71,7 @@ The following sections discuss some example scenarios that are embarrassingly pa
 ### Simple query
 
 * Input: Event hub with 8 partitions
-* Output: Event hub with 8 partitions
+* Output: Event hub with 8 partitions ("Partition key column" must be set to use "PartitionId")
 
 Query:
 
@@ -138,7 +138,7 @@ The preceding examples show some Stream Analytics jobs that conform to (or don't
 
 ### Compatibility level 1.2 - Multi-step query with different PARTITION BY values 
 * Input: Event hub with 8 partitions
-* Output: Event hub with 8 partitions
+* Output: Event hub with 8 partitions ("Partition key column" must be set to use "TollBoothId")
 
 Query:
 
