Merge pull request #194186 from MicrosoftDocs/main

Merge Main to Live, 4 AM

Author: PMEds28

.openpublishing.redirection.json

@@ -39058,6 +39058,11 @@
       "redirect_url": "/azure/cognitive-services/Speech-Service/speech-devices",
       "redirect_document_id": false
     },
+    {
+      "source_path_from_root": "/articles/cognitive-services/Speech-Service/index-conversation-scenarios.yml",
+      "redirect_url": "/azure/cognitive-services/Speech-Service/call-center-transcription.md",
+      "redirect_document_id": false
+    },
     {
       "source_path_from_root": "/articles/cognitive-services/Speech-Service/keyword-recognition-region-support.md",
       "redirect_url": "/azure/cognitive-services/Speech-Service/regions",

articles/active-directory/conditional-access/concept-condition-filters-for-devices.md

@@ -4,7 +4,7 @@ description: Use filter for devices in Conditional Access to enhance security po
 ms.service: active-directory
 ms.subservice: conditional-access
 ms.topic: conceptual
-ms.date: 02/28/2022
+ms.date: 04/05/2022
 ms.author: joflore
 author: MicrosoftGuyJFlo
 manager: karenhoran
@@ -135,11 +135,11 @@ The filter for devices condition in Conditional Access evaluates policy based on
 | Include/exclude mode with positive operators (Equals, StartsWith, EndsWith, Contains, In) and use of any attributes | Unregistered device | No |
 | Include/exclude mode with positive operators (Equals, StartsWith, EndsWith, Contains, In) and use of attributes excluding extensionAttributes1-15 | Registered device | Yes, if criteria are met |
 | Include/exclude mode with positive operators (Equals, StartsWith, EndsWith, Contains, In) and use of attributes including extensionAttributes1-15 | Registered device managed by Intune | Yes, if criteria are met |
-| Include/exclude mode with positive operators (Equals, StartsWith, EndsWith, Contains, In) and use of attributes including extensionAttributes1-15 | Registered device not managed by Intune | Yes, if criteria are met and if device is compliant or Hybrid Azure AD joined |
+| Include/exclude mode with positive operators (Equals, StartsWith, EndsWith, Contains, In) and use of attributes including extensionAttributes1-15 | Registered device not managed by Intune | Yes, if criteria are met. When extensionAttributes1-15 are used, the policy will apply if device is compliant or Hybrid Azure AD joined |
 | Include/exclude mode with negative operators (NotEquals, NotStartsWith, NotEndsWith, NotContains, NotIn) and use of any attributes | Unregistered device | Yes |
 | Include/exclude mode with negative operators (NotEquals, NotStartsWith, NotEndsWith, NotContains, NotIn) and use of any attributes excluding extensionAttributes1-15 | Registered device | Yes, if criteria are met |
 | Include/exclude mode with negative operators (NotEquals, NotStartsWith, NotEndsWith, NotContains, NotIn) and use of any attributes including extensionAttributes1-15 | Registered device managed by Intune | Yes, if criteria are met |
-| Include/exclude mode with negative operators (NotEquals, NotStartsWith, NotEndsWith, NotContains, NotIn) and use of any attributes including extensionAttributes1-15 | Registered device not managed by Intune | Yes, if criteria are met and if device is compliant or Hybrid Azure AD joined |
+| Include/exclude mode with negative operators (NotEquals, NotStartsWith, NotEndsWith, NotContains, NotIn) and use of any attributes including extensionAttributes1-15 | Registered device not managed by Intune | Yes, if criteria are met. When extensionAttributes1-15 are used, the policy will apply if device is compliant or Hybrid Azure AD joined |
 
 ## Next steps
 

articles/active-directory/conditional-access/concept-conditional-access-conditions.md

@@ -6,7 +6,7 @@ services: active-directory
 ms.service: active-directory
 ms.subservice: conditional-access
 ms.topic: conceptual
-ms.date: 03/10/2022
+ms.date: 04/05/2022
 
 ms.author: joflore
 author: MicrosoftGuyJFlo
@@ -43,7 +43,7 @@ Azure AD Conditional Access supports the following device platforms:
 - iOS
 - Windows
 - macOS
-- Linux (Preview)
+- Linux
 
 If you block legacy authentication using the **Other clients** condition, you can also set the device platform condition.
 
@@ -189,7 +189,7 @@ By selecting **Other clients**, you can specify a condition that affects apps th
 ## Device state (preview)
 
 > [!CAUTION]
-> **This preview feature has being deprecated.** Customers should use **Filter for devices** condition in Conditional Access to satisfy scenarios, previously achieved using device state (preview) condition.
+> **This preview feature has been deprecated.** Customers should use **Filter for devices** condition in Conditional Access to satisfy scenarios, previously achieved using device state (preview) condition.
 
 The device state condition was used to exclude devices that are hybrid Azure AD joined and/or devices marked as compliant with a Microsoft Intune compliance policy from an organization's Conditional Access policies.
 

articles/active-directory/saas-apps/meta-networks-connector-provisioning-tutorial.md

@@ -149,10 +149,10 @@ This section guides you through the steps to configure the Azure AD provisioning
     |Attribute|Type|Supported for filtering|Required by Meta Networks Connector|
     |---|---|---|---|
     |userName|String|✓|✓
+	|active|Boolean||
+	|phonenumbers[type eq "work"].value|String||
     |name.givenName|String||✓
     |name.familyName|String||✓
-    |active|Boolean||
-    |phonenumbers[type eq "work"].value|String||
 
 	> [!NOTE]
 	> phonenumbers value should be in E164 format. For example +16175551212
@@ -189,8 +189,10 @@ Once you've configured provisioning, use the following resources to monitor your
 
 * Use the [provisioning logs](../reports-monitoring/concept-provisioning-logs.md) to determine which users have been provisioned successfully or unsuccessfully
 * Check the [progress bar](../app-provisioning/application-provisioning-when-will-provisioning-finish-specific-user.md) to see the status of the provisioning cycle and how close it is to completion
-* If the provisioning configuration seems to be in an unhealthy state, the application will go into quarantine. Learn more about quarantine states [here](../app-provisioning/application-provisioning-quarantine-status.md).  
+* If the provisioning configuration seems to be in an unhealthy state, the application will go into quarantine. Learn more about quarantine states [here](../app-provisioning/application-provisioning-quarantine-status.md).
 
+## Change Log
+04/06/2022 - Added support for **phoneNumbers[type eq "work"].value**. Removed support for **emails[type eq "work"].value** and **manager** . **name.givenName** and **name.familyName** made required attributes.
 
 ## More resources
 

articles/api-management/get-started-create-service-instance-cli.md

@@ -4,15 +4,15 @@ description: Create a new Azure API Management service instance by using the Azu
 author: dlepow
 ms.service: api-management
 ms.topic: quickstart
-ms.custom: mode-api, devx-track-azurecli
-ms.date: 09/10/2020
+ms.custom: mode-api, devx-track-azurecli, devdivchpfy22
+ms.date: 03/29/2022
 ms.author: danlep 
 ms.devlang: azurecli
 ---
 
 # Quickstart: Create a new Azure API Management service instance by using the Azure CLI
 
-Azure API Management (APIM) helps organizations publish APIs to external, partner, and internal developers to unlock the potential of their data and services. API Management provides the core competencies to ensure a successful API program through developer engagement, business insights, analytics, security, and protection. APIM enables you to create and manage modern API gateways for existing backend services hosted anywhere. For more information, see the [Overview](api-management-key-concepts.md).
+Azure API Management (APIM) helps organizations publish APIs to external, partner, and internal developers to unlock the potential of their data and services. API Management provides the core competencies to ensure a successful API program through developer engagement, business insights, analytics, security, and protection. APIM lets you create and manage modern API gateways for existing backend services hosted anywhere. For more information about APIM, see the [Overview](api-management-key-concepts.md).
 
 This quickstart describes the steps for creating a new API Management instance using [az apim](/cli/azure/apim) commands in the Azure CLI.
 
@@ -24,7 +24,7 @@ This quickstart describes the steps for creating a new API Management instance u
 
 ## Create a resource group
 
-Azure API Management instances, like all Azure resources, must be deployed into a resource group. Resource groups allow you to organize and manage related Azure resources.
+Azure API Management instances, like all Azure resources, must be deployed into a resource group. Resource groups let you organize and manage related Azure resources.
 
 First, create a resource group named *myResourceGroup* in the Central US location with the following [az group create](/cli/azure/group#az-group-create) command:
 
@@ -34,9 +34,9 @@ az group create --name myResourceGroup --location centralus
 
 ## Create a new service
 
-Now that you have a resource group, you can create an API Management service instance. Create one by using the [az apim create](/cli/azure/apim#az-apim-create) command and provide a service name and publisher details. The service name must be unique within Azure. 
+Now that you have a resource group, you can create an API Management service instance. Create one by using the [az apim create](/cli/azure/apim#az-apim-create) command and provide a service name and publisher details. The service name must be unique within Azure.
 
-In the following example, *myapim* is used for the service name. Update the name to a unique value. Also update the name of the API publisher's organization and the email address to receive notifications. 
+In the following example, *myapim* is used for the service name. Update the name to a unique value. Also update the name of the API publisher's organization and the email address to receive notifications.
 
 ```azurecli-interactive
 az apim create --name myapim --resource-group myResourceGroup \
@@ -75,7 +75,7 @@ When your API Management service instance is online, you're ready to use it. Sta
 
 ## Clean up resources
 
-When no longer needed, you can use the [az group delete](/cli/azure/group#az-group-delete) command to remove the resource group and the API Management service instance.
+You can use the [az group delete](/cli/azure/group#az-group-delete) command to remove the resource group and the API Management service instance when they aren't needed.
 
 ```azurecli-interactive
 az group delete --name myResourceGroup

articles/api-management/powershell-create-service-instance.md

@@ -6,14 +6,14 @@ documentationcenter: ''
 author: dlepow
 ms.service: api-management
 ms.topic: quickstart
-ms.custom: mvc, devx-track-azurepowershell, mode-api
-ms.date: 09/14/2020
+ms.custom: mvc, devx-track-azurepowershell, mode-api, devdivchpfy22
+ms.date: 03/30/2022
 ms.author: danlep
 ---
 
 # Quickstart: Create a new Azure API Management service instance by using PowerShell
 
-Azure API Management (APIM) helps organizations publish APIs to external, partner, and internal developers to unlock the potential of their data and services. API Management provides the core competencies to ensure a successful API program through developer engagement, business insights, analytics, security, and protection. APIM  enables you to create and manage modern API gateways for existing backend services hosted anywhere. For more information, see the [Overview](api-management-key-concepts.md).
+Azure API Management (APIM) helps organizations publish APIs to external, partner, and internal developers to unlock the potential of their data and services. API Management provides the core competencies to ensure a successful API program through developer engagement, business insights, analytics, security, and protection. APIM lets you create and manage modern API gateways for existing backend services hosted anywhere. For more information, see the [Overview](api-management-key-concepts.md).
 
 This quickstart describes the steps for creating a new API Management instance by using Azure PowerShell cmdlets.
 
@@ -39,19 +39,19 @@ New-AzResourceGroup -Name myResourceGroup -Location WestUS
 
 Now that you have a resource group, you can create an API Management service instance. Create one by using [New-AzApiManagement](/powershell/module/az.apimanagement/new-azapimanagement) and provide a service name and publisher details. The service name must be unique within Azure.
 
-In the following example, *myapim* is used for the service name. Update the name to a unique value. Also update the organization name of the API publisher and the admin email address to receive notifications.
+In the following example, *myapim* is used for the service name. Update the name to a unique value. Also, update the organization name of the API publisher and the admin email address to receive notifications.
 
 By default, the command creates the instance in the Developer tier, an economical option to evaluate Azure API Management. This tier isn't for production use. For more information about scaling the API Management tiers, see [upgrade and scale](upgrade-and-scale.md).
 
 > [!NOTE]
-> This is a long-running operation. It can take between 30 and 40 minutes to create and activate an API Management service in this tier.
+> This is a long-running action. It can take between 30 and 40 minutes to create and activate an API Management service in this tier.
 
 ```azurepowershell-interactive
 New-AzApiManagement -Name "myapim" -ResourceGroupName "myResourceGroup" `
   -Location "West US" -Organization "Contoso" -AdminEmail "[email protected]" 
 ```
 
-When the command returns, run [Get-AzApiManagement](/powershell/module/az.apimanagement/get-azapimanagement) to view the properties of the Azure API Management service. After activation, the provisioning status is Succeeded and the service instance has several associated URLs. For example:
+When the command returns, run [Get-AzApiManagement](/powershell/module/az.apimanagement/get-azapimanagement) to view the properties of the Azure API Management service. After activation, the setting up status is Succeeded and the service instance has several associated URLs. For example:
 
 ```azurepowershell-interactive
 Get-AzApiManagement -Name "myapim" -ResourceGroupName "myResourceGroup" 

articles/app-service/configure-language-nodejs.md

@@ -28,7 +28,7 @@ az webapp config appsettings list --name <app-name> --resource-group <resource-g
 To show all supported Node.js versions, navigate to `https://<sitename>.scm.azurewebsites.net/api/diagnostics/runtime` or run the following command in the [Cloud Shell](https://shell.azure.com):
 
 ```azurecli-interactive
-az webapp list-runtimes --os windows | grep node
+az webapp list-runtimes --os windows | grep NODE
 ```
 
 ::: zone-end

articles/azure-fluid-relay/TOC.yml

@@ -40,6 +40,8 @@
       href: how-tos/test-automation.md
     - name: 'How to: Delete a Fluid container'
       href: how-tos/container-deletion.md
+    - name: 'How to: Validate a User Created a Document'
+      href: how-tos/validate-document-creator.md
 - name: Reference
   items:
     - name: API documentation

articles/azure-fluid-relay/how-tos/azure-function-token-provider.md

@@ -45,7 +45,7 @@ const key = "myTenantKey";
 const httpTrigger: AzureFunction = async function (context: Context, req: HttpRequest): Promise<void> {
     // tenantId, documentId, userId and userName are required parameters
     const tenantId = (req.query.tenantId || (req.body && req.body.tenantId)) as string;
-    const documentId = (req.query.documentId || (req.body && req.body.documentId)) as string;
+    const documentId = (req.query.documentId || (req.body && req.body.documentId)) as string | undefined;
     const userId = (req.query.userId || (req.body && req.body.userId)) as string;
     const userName = (req.query.userName || (req.body && req.body.userName)) as string;
     const scopes = (req.query.scopes || (req.body && req.body.scopes)) as ScopeType[];
@@ -66,14 +66,6 @@ const httpTrigger: AzureFunction = async function (context: Context, req: HttpRe
         return;
     }
 
-    if (!documentId) {
-        context.res = {
-            status: 400,
-            body: "No documentId provided in query params"
-        };
-        return;
-    }
-
     let user = { name: userName, id: userId };
 
     // Will generate the token and returned by an ITokenProvider implementation to use with the AzureClient.
@@ -159,3 +151,4 @@ export class AzureFunctionTokenProvider implements ITokenProvider {
 
 - [Add custom data to an auth token](connect-fluid-azure-service.md#adding-custom-data-to-tokens)
 - [How to: Deploy Fluid applications using Azure Static Web Apps](deploy-fluid-static-web-apps.md)
+- [How to: Validate a User Created a Document](validate-document-creator.md)