Merge pull request #99558 from MicrosoftDocs/master

12/20 AM Publish

Author: huypub

articles/active-directory/manage-apps/methods-for-assigning-users-and-groups.md

@@ -30,10 +30,11 @@ This article shows you how to assign users or groups to an application in Azure
 
 The availability of group-based assignment is determined by your license agreement. Group-based assignment is supported for Security groups only. Nested group memberships and O365 groups are not currently supported.
 
-## Prerequisites
-Before you can assign users and groups to an application, you must require user assignment. To require user assignment:
+## Configure the application to require assignment
 
-1. Log in to the Azure portal with an administrator account.
+An application can be configured to require assignment before it can be accessed. To require assignment:
+
+1. Log in to the Azure portal with an administrator account, or as an owner of the app under **Enterprise apps**.
 2. Click on the **All services** item in the main menu.
 3. Choose the directory you are using for the application.
 4. Click on the **Enterprise applications** tab.

articles/advisor/advisor-cost-recommendations.md

@@ -16,7 +16,7 @@ Advisor helps you optimize and reduce your overall Azure spend by identifying id
 
 ## Optimize virtual machine spend by resizing or shutting down underutilized instances 
 
-Although certain application scenarios can result in low utilization by design, you can often save money by managing the size and number of your virtual machines. Advisor advanced evaluation models considers a virtual machines for shut-down when P95th of the max of max value of CPU utilization is less than 3% and network utilization is less than 2% over a 7 day period. Virtual machines are considered for right size when it is possible to fit the current load in a smaller SKU (within the same SKU family) or a smaller number # of instance such that the current load doesn’t go over 80% utilization when non-user facing workloads and not above 40% when user-facing workload. Here, the type of workload is determined by analyzing the CPU utilization characteristics of the workload.
+Although certain application scenarios can result in low utilization by design, you can often save money by managing the size and number of your virtual machines. Advisor advanced evaluation models considers virtual machines for shut-down when P95th of the max of max value of CPU utilization is less than 3% and network utilization is less than 2% over a 7 day period. Virtual machines are considered for right size when it is possible to fit the current load in a smaller SKU (within the same SKU family) or a smaller number # of instance such that the current load doesn’t go over 80% utilization when non-user facing workloads and not above 40% when user-facing workload. Here, the type of workload is determined by analyzing the CPU utilization characteristics of the workload.
 
 The recommended actions are shut-down or resize, specific to resource being recommended for. Advisor shows you the estimated cost savings for either recommended actions - resize or shut-down. Also, for resize recommended action, Advisor provides current and target SKU information. 
 
@@ -45,13 +45,15 @@ Advisor identifies public IP addresses that are not currently associated to Azur
 Azure Advisor will detect Azure Data Factory pipelines that repeatedly fail and recommend that you resolve the issues or delete the failing pipelines if they are no longer needed. You will be billed for these pipelines even if though they are not serving you while they are failing. 
 
 ## Use Standard Snapshots for Managed Disks
-To save 60% of cost, we recommend storing your snapshots in Standard Storage, regardless of the storage type of the parent disk. This is the default option for Managed Disks snapshots. Azure Advisor will identify snapshots that are stored Premium Storage and recommend migrating your snapshot from Premium to Standard Storage. [Learn more about Managed Disk pricing](https://aka.ms/aa_manageddisksnapshot_learnmore)
+To save 60% of cost, we recommend storing your snapshots in Standard Storage, regardless of the storage type of the parent disk. This option is the default option for Managed Disks snapshots. Azure Advisor will identify snapshots that are stored Premium Storage and recommend migrating your snapshot from Premium to Standard Storage. [Learn more about Managed Disk pricing](https://aka.ms/aa_manageddisksnapshot_learnmore)
 
 ## How to access Cost recommendations in Azure Advisor
 
-1. Sign in to the [Azure portal](https://portal.azure.com), and then open [Advisor](https://aka.ms/azureadvisordashboard).
+1. Sign in to the [Azure portal](https://portal.azure.com).
 
-2.	On the Advisor dashboard, click the **Cost** tab.
+1. Search for and select [**Advisor**](https://aka.ms/azureadvisordashboard) from any page.
+
+1. On the **Advisor** dashboard, select the **Cost** tab.
 
 ## Next steps
 

articles/api-management/api-management-role-based-access-control.md

@@ -24,17 +24,17 @@ Azure API Management relies on Azure Role-Based Access Control (RBAC) to enable
 
 ## Built-in roles
 
-API Management currently provides three built-in roles and will add two more roles in the near future. These roles can be assigned at different scopes, including subscription, resource group, and individual API Management instance. For instance, if you assign the "Azure API Management Service Reader" role to a user at the resource-group level, then the user has read access to all API Management instances inside the resource group. 
+API Management currently provides three built-in roles and will add two more roles in the near future. These roles can be assigned at different scopes, including subscription, resource group, and individual API Management instance. For instance, if you assign the "API Management Service Reader" role to a user at the resource-group level, then the user has read access to all API Management instances inside the resource group. 
 
 The following table provides brief descriptions of the built-in roles. You can assign these roles by using the Azure portal or other tools, including Azure [PowerShell](https://docs.microsoft.com/azure/role-based-access-control/role-assignments-powershell), [Azure CLI](https://docs.microsoft.com/azure/role-based-access-control/role-assignments-cli), and [REST API](https://docs.microsoft.com/azure/role-based-access-control/role-assignments-rest). For details about how to assign built-in roles, see [Use role assignments to manage access to your Azure subscription resources](https://docs.microsoft.com/azure/role-based-access-control/role-assignments-portal).
 
 | Role          | Read access<sup>[1]</sup> | Write access<sup>[2]</sup> | Service creation, deletion, scaling, VPN, and custom domain configuration | Access to the legacy publisher portal | Description
 | ------------- | ---- | ---- | ---- | ---- | ---- 
-| Azure API Management Service Contributor | ✓ | ✓ | ✓ | ✓ | Super user. Has full CRUD access to API Management services and entities (for example, APIs and policies). Has access to the legacy publisher portal. |
-| Azure API Management Service Reader | ✓ | | || Has read-only access to API Management services and entities. |
-| Azure API Management Service Operator | ✓ | | ✓ | | Can manage API Management services, but not entities.|
-| Azure API Management Service Editor<sup>*</sup> | ✓ | ✓ | |  | Can manage API Management entities, but not services.|
-| Azure API Management Content Manager<sup>*</sup> | ✓ | | | ✓ | Can manage the developer portal. Read-only access to services and entities.|
+| API Management Service Contributor | ✓ | ✓ | ✓ | ✓ | Super user. Has full CRUD access to API Management services and entities (for example, APIs and policies). Has access to the legacy publisher portal. |
+| API Management Service Reader | ✓ | | || Has read-only access to API Management services and entities. |
+| API Management Service Operator | ✓ | | ✓ | | Can manage API Management services, but not entities.|
+| API Management Service Editor<sup>*</sup> | ✓ | ✓ | |  | Can manage API Management entities, but not services.|
+| API Management Content Manager<sup>*</sup> | ✓ | | | ✓ | Can manage the developer portal. Read-only access to services and entities.|
 
 <sup>[1] Read access to API Management services and entities (for example, APIs and policies).</sup>
 
@@ -49,7 +49,7 @@ If none of the built-in roles meet your specific needs, custom roles can be crea
 > [!NOTE]
 > To be able to see an API Management instance in the Azure portal, a custom role must include the ```Microsoft.ApiManagement/service/read``` action.
 
-When you create a custom role, it's easier to start with one of the built-in roles. Edit the attributes to add **Actions**, **NotActions**, or **AssignableScopes**, and then save the changes as a new role. The following example begins with the "Azure API Management Service Reader" role and creates a custom role called "Calculator API Editor." You can assign the custom role to a specific API. Consequently, this role only has access to that API. 
+When you create a custom role, it's easier to start with one of the built-in roles. Edit the attributes to add **Actions**, **NotActions**, or **AssignableScopes**, and then save the changes as a new role. The following example begins with the "API Management Service Reader" role and creates a custom role called "Calculator API Editor." You can assign the custom role to a specific API. Consequently, this role only has access to that API. 
 
 ```powershell
 $role = Get-AzRoleDefinition "API Management Service Reader Role"
@@ -79,4 +79,4 @@ To learn more about Role-Based Access Control in Azure, see the following articl
   * [Get started with access management in the Azure portal](../role-based-access-control/overview.md)
   * [Use role assignments to manage access to your Azure subscription resources](../role-based-access-control/role-assignments-portal.md)
   * [Custom roles in Azure RBAC](../role-based-access-control/custom-roles.md)
-  * [Azure Resource Manager resource provider operations](../role-based-access-control/resource-provider-operations.md#microsoftapimanagement)
+  * [Azure Resource Manager resource provider operations](../role-based-access-control/resource-provider-operations.md#microsoftapimanagement)

articles/azure-functions/functions-versions.md

@@ -111,7 +111,7 @@ The version of the Functions runtime used by published apps in Azure is dictated
 
 ### Locally developed application versions
 
-You can make the following updates function apps locally change targeted versions.
+You can make the following updates to function apps to locally change the targeted versions.
 
 #### Visual Studio runtime versions
 

articles/cognitive-services/Speech-Service/batch-transcription.md

@@ -78,29 +78,26 @@ Configuration parameters are provided as JSON:
 }
 ```
 
-> [!NOTE]
-> The Batch Transcription API uses a REST service for requesting transcriptions, their status, and associated results. You can use the API from any language. The next section describes how the API is used.
-
 ### Configuration properties
 
 Use these optional properties to configure transcription:
 
 | Parameter | Description |
-|-----------|-------------|
-| `ProfanityFilterMode` | Specifies how to handle profanity in recognition results. Accepted values are `None`, which disables profanity filtering; `Masked`, which replaces profanity with asterisks; `Removed`, which removes all profanity from the result; `Tags`, which adds "profanity" tags. The default setting is `Masked`. |
-| `PunctuationMode` | Specifies how to handle punctuation in recognition results. Accepted values are `None`, which disables punctuation; `Dictated`, which implies explicit punctuation; `Automatic`, which lets the decoder deal with punctuation; `DictatedAndAutomatic`, which implies dictated punctuation marks or automatic (the default value). |
-| `AddWordLevelTimestamps` | Specifies if word level timestamps should be added to the output. Accepted values are `True`, which enables word level timestamps; `False`, to disable it (the default value). |
-| `AddSentiment` | Specifies sentiment should be added to the utterance. Accepted values are `True`, which enables sentiment per utterance; `False`, to disable it (the default value).|
-| `AddDiarization` | Specifies that diarization analysis should be carried out on the input that is expected to be mono channel containing two voices. Accepted values are `True`, which enables diarization; `False`, to disable it (the default value). It also requires `AddWordLevelTimestamps` to be set to true.|
-| `TranscriptionResultsContainerUrl` | An optional SAS token to a writeable container in Azure. The result will be stored in this container. |
+|-----------|------------|
+|`ProfanityFilterMode`|Specifies how to handle profanity in recognition results
+||**`Masked`** - Default. Replaces profanity with asterisks<br>`None` - Disables profanity filtering<br>`Removed` - Removes all profanity from the result<br>`Tags` - Adds profanity tags
+|`PunctuationMode`|Specifies to handle punctuation in recognition results
+||`Automatic` - The service inserts punctuation<br>`Dictated` - Dictated (spoken) punctuation<br>**`DictatedAndAutomatic`** - Default. Dictated and automatic punctuation<br>`None` - Disables punctuation
+|`AddWordLevelTimestamps`|Specifies if word level timestamps should be added to the output
+||`True` - Enables word level timestamps<br>**`False`** - Default. Disable word level timestamps
+|`AddSentiment`|Specifies if sentiment analysis is added to the utterance
+||`True` - Enables sentiment per utterance<br>**`False`** - Default. Disable sentiment
+|`AddDiarization`|Specifies if diarization analysis is carried out. If `true`, the input is expected to be mono channel audio containing a maximum of two voices. `AddWordLevelTimestamps` needs to be set to `true`
+||`True` - Enables diarization<br>**`False`** - Default. Disable diarization
+|`TranscriptionResultsContainerUrl`|Optional SAS token to a writeable container in Azure. The result will be stored in this container
 
 ### Storage
 
-Lexical` | The lexical form of the recognized text: the actual words recognized. |
-| `ITN` | The inverse-text-normalized ("canonical") form of the recognized text, with phone numbers, numbers, abbreviations ("doctor smith" to "dr smith"), and other transformations applied. |
-| `MaskedITN` | The ITN form with profanity masking applied, if requested. |
-| `Display` | The display form of the recognized text, with punctuation and capitalization added. This parameter is the same as `DisplayText` provided when format is set to `simple`. |
-
 Batch transcription supports [Azure Blob storage](https://docs.microsoft.com/azure/storage/blobs/storage-blobs-overview) for reading audio and writing transcriptions to storage.
 
 ## The batch transcription result
@@ -117,14 +114,10 @@ For mono input audio, one transcription result file is being created. For stereo
       "CombinedResults": [
         {
           "ChannelNumber": null                             'always null'
-          "Lexical": string                                 'the actual words recognized'
-          "ITN": string                                     'inverse-text-normalized form
-                                                             of the recognized text, with phone numbers,
-                                                             abbreviations ("doctor smith" to "dr smith"),
-                                                             and other transformations applied'
-          "MaskedITN": string                               'The ITN form with profanity masking applied'
-          "Display": string                                 'The display form of the recognized text
-                                                             with punctuation and capitalization added'
+          "Lexical": string
+          "ITN": string
+          "MaskedITN": string
+          "Display": string
         }
       ]
       SegmentResults:[                                     'for each individual segment'
@@ -148,7 +141,7 @@ For mono input audio, one transcription result file is being created. For stereo
               "MaskedITN": string
               "Display": string
               "Sentiment":
-                {                                          'this is ommitted if sentiment is
+                {                                          'this is omitted if sentiment is
                                                             not requested'
                   "Negative": number                        'between 0 and 1'
                   "Neutral": number                         'between 0 and 1'
@@ -172,6 +165,15 @@ For mono input audio, one transcription result file is being created. For stereo
 }
 ```
 
+The result contains these forms:
+
+|Form|Content|
+|-|-|
+|`Lexical`|The actual words recognized.
+|`ITN`|Inverse-text-normalized form of the recognized text. Abbreviations ("doctor smith" to "dr smith"), phone numbers, and other transformations are applied.
+|`MaskedITN`|The ITN form with profanity masking applied.
+|`Display`|The display form of the recognized text. This includes added punctuation and capitalization.
+
 ## Speaker separation (Diarization)
 
 Diarization is the process of separating speakers in a piece of audio. Our Batch pipeline supports diarization and is capable of recognizing two speakers on mono channel recordings. The feature is not available on stereo recordings.

articles/cosmos-db/how-to-use-stored-procedures-triggers-udfs.md

@@ -139,7 +139,7 @@ The following example shows how to register a stored procedure by using the Java
 ```javascript
 const container = client.database("myDatabase").container("myContainer");
 const sprocId = "spCreateToDoItem";
-await container.storedProcedures.create({
+await container.scripts.storedProcedures.create({
     id: sprocId,
     body: require(`../js/${sprocId}`)
 });
@@ -156,7 +156,7 @@ const newItem = [{
 }];
 const container = client.database("myDatabase").container("myContainer");
 const sprocId = "spCreateToDoItem";
-const {body: result} = await container.storedProcedure(sprocId).execute(newItem, {partitionKey: newItem[0].category});
+const {body: result} = await container.scripts.storedProcedure(sprocId).execute(newItem, {partitionKey: newItem[0].category});
 ```
 
 ### Stored procedures - Python SDK

articles/cosmos-db/sql-query-order-by.md

@@ -45,6 +45,9 @@ ORDER BY <sort_specification>
 ## Remarks  
 
    The ORDER BY clause requires that the indexing policy include an index for the fields being sorted. The Azure Cosmos DB query runtime supports sorting against a property name and not against computed properties. Azure Cosmos DB supports multiple ORDER BY properties. In order to run a query with multiple ORDER BY properties, you should define a [composite index](index-policy.md#composite-indexes) on the fields being sorted.
+   
+> [!Note] 
+> When using the .NET SDK 3.4.0 or above, if the properties being sorted against might be undefined for some documents then you need to explicitly create an index on those properties. The default indexing policy will not allow for the retrieval of the documents where the sort property is undefined.
 
 ## Examples
 

articles/data-factory/concepts-data-flow-overview.md

@@ -7,7 +7,7 @@ ms.reviewer: daperlov
 ms.service: data-factory
 ms.topic: conceptual
 ms.custom: seo-lt-2019
-ms.date: 10/7/2019
+ms.date: 12/19/2019
 ---
 
 # What are mapping data flows?
@@ -56,6 +56,8 @@ If you execute data flows in a pipeline in parallel, ADF will spin-up separate A
 
 Of these three options, this option will likely execute in the shortest amount of time. However, each parallel data flow will execute at the same time on separate clusters, so the ordering of events is non-deterministic.
 
+If you are executing your data flow activities in parallel inside your pipelines, it is recommended to not use TTL. This is because parallel executions of data flows simultaneously using the same Azure Integration Runtime will result in multiple warm pool instances for your data factory.
+
 ##### Overload single data flow
 
 If you put all of your logic inside a single data flow, ADF will all execute in that same job execution context on a single Spark cluster instance.