Merge pull request #196876 from MicrosoftDocs/main

Merge main to live, 4 AM

Author: ttorble

articles/active-directory/develop/test-setup-environment.md

@@ -10,7 +10,7 @@ ms.service: active-directory
 ms.subservice: develop
 ms.topic: how-to
 ms.workload: identity
-ms.date: 09/28/2021
+ms.date: 05/02/2022
 ms.author: arcrowe
 ms.reviewer: 
 ms.custom: aaddev
@@ -45,7 +45,7 @@ If you can't safely constrain your test app in your production tenant, you can c
 If you don't already have a dedicated test tenant, you can create one for free using the Microsoft 365 Developer Program or manually create one yourself. 
 
 #### Join the Microsoft 365 Developer Program (recommended) 
-The [Microsoft 365 Developer Program](https://developer.microsoft.com/microsoft-365/dev-program) is free and can have test user accounts and sample data packs automatically added to the tenant.
+The [Microsoft 365 Developer Program](/office/developer-program/microsoft-365-developer-program) is free and can have test user accounts and sample data packs automatically added to the tenant.
 1. Click on the **Join now** button on the screen.
 2. Sign in with a new Microsoft Account or use an existing (work) account you already have.
 3. On the sign-up page select your region, enter a company name and accept the terms and conditions of the program before you click **Next**.

articles/active-directory/reports-monitoring/reference-basic-info-sign-in-logs.md

@@ -13,7 +13,7 @@ ms.topic: reference
 ms.tgt_pltfrm: na
 ms.workload: identity
 ms.subservice: report-monitor
-ms.date: 12/17/2021
+ms.date: 05/02/2022
 ms.author: markvi
 ms.reviewer: besiler
 
@@ -88,12 +88,12 @@ The type of a user. Examples include `member`, `guest`, or `external`.
 
 This attribute describes the type of cross-tenant access used by the actor to access the resource. Possible values are: 
 
-- `none`
-- `b2bCollaboration`
-- `b2bDirectConnect`
-- `microsoftSupport`
-- `serviceProvider`
-- `unknownFutureValue` 
+- `none` - A sign-in event that did not cross an Azure AD tenant's boundaries.
+- `b2bCollaboration`- A cross tenant sign-in performed by a guest user using B2B Collaboration.
+- `b2bDirectConnect` - A cross tenant sign-in performed by a B2B.
+- `microsoftSupport`- A cross tenant sign-in performed by a Microsoft support agent in a Microsoft customer tenant.
+- `serviceProvider` - A cross-tenant sign-in performed by a Cloud Service Provider (CSP) or similar admin on behalf of that CSP's customer in a tenant
+- `unknownFutureValue` - A sentinel value used by MS Graph to help clients handle changes in enum lists. For more information, see [Best practices for working with Microsoft Graph](https://docs.microsoft.com/graph/best-practices-concept).
 
 If the sign-in did not the pass the boundaries of a tenant, the value is `none`.
 

articles/api-management/TOC.yml

@@ -44,7 +44,7 @@ You can move an app to another App Service plan, as long as the source plan and
 > [!NOTE]
 > Azure deploys each new App Service plan into a deployment unit, internally called a webspace. Each region can have many webspaces, but your app can only move between plans that are created in the same webspace. An App Service Environment is an isolated webspace, so apps can be moved between plans in the same App Service Environment, but not between plans in different App Service Environments.
 >
-> You can’t specify the webspace you want when creating a plan, but it’s possible to ensure that a plan is created in the same webspace as an existing plan. In brief, all plans created with the same resource group and region combination are deployed into the same webspace. For example, if you created a plan in resource group A and region B, then any plan you subsequently create in resource group A and region B is deployed into the same webspace. Note that plans can’t move webspaces after they’re created, so you can’t move a plan into “the same webspace” as another plan by moving it to another resource group.
+> You can’t specify the webspace you want when creating a plan, but it’s possible to ensure that a plan is created in the same webspace as an existing plan. In brief, all plans created with the same resource group, region combination and operating system are deployed into the same webspace. For example, if you created a plan in resource group A and region B, then any plan you subsequently create in resource group A and region B is deployed into the same webspace. Note that plans can’t move webspaces after they’re created, so you can’t move a plan into “the same webspace” as another plan by moving it to another resource group.
 > 
 
 1. In the [Azure portal](https://portal.azure.com), search for and select **App services** and select the app that you want to move.

articles/app-service/app-service-plan-manage.md

@@ -15,7 +15,7 @@ ms.custom: seodec18
 Once the certificate is added to your App Service app or [function app](../azure-functions/index.yml), you can [secure a custom DNS name with it](configure-ssl-bindings.md) or [use it in your application code](configure-ssl-certificate-in-code.md).
 
 > [!NOTE]
-> A certificate uploaded into an app is stored in a deployment unit that is bound to the app service plan's resource group and region combination (internally called a *webspace*). This makes the certificate accessible to other apps in the same resource group and region combination. 
+> A certificate uploaded into an app is stored in a deployment unit that is bound to the app service plan's resource group, region and operating system combination (internally called a *webspace*). This makes the certificate accessible to other apps in the same resource group and region combination. 
 
 The following table lists the options you have for adding certificates in App Service:
 

articles/app-service/configure-ssl-certificate.md

@@ -13,7 +13,7 @@ ms.author: lajanuar
 
 # Language support for Form Recognizer
 
- This table lists the written languages supported by each Form Recognizer service.
+This article covers the supported languages for text and field **extraction (by feature)** and **[detection (Read only)](#detected-languages-read-api)**. Both groups are mutually exclusive.
 
 <!-- markdownlint-disable MD001 -->
 <!-- markdownlint-disable MD024 -->
@@ -29,7 +29,7 @@ The following lists include the currently GA languages in for the v2.1 version a
 
 To use the preview languages, refer to the [v3.0 REST API migration guide](/rest/api/media/#changes-to-the-rest-api-endpoints) to understand the differences from the v2.1 GA API and explore the [v3.0 preview SDK quickstarts](quickstarts/try-v3-python-sdk.md).
 
-### Handwritten languages (preview and GA)
+### Handwritten text (preview and GA)
 
 The following table lists the supported languages for extracting handwritten texts.
 
@@ -41,7 +41,7 @@ The following table lists the supported languages for extracting handwritten tex
 |German (preview) |`de`|Spanish (preview) |`es`|
 |Italian (preview) |`it`|
 
-### Print languages (preview)
+### Print text (preview)
 
 This section lists the supported languages for extracting printed texts in the latest preview.
 
@@ -94,7 +94,7 @@ This section lists the supported languages for extracting printed texts in the l
 |Kurukh (Devanagari) | `kru`|Welsh | `cy`
 |Kyrgyz (Cyrillic)  | `ky`
 
-### Print languages (GA)
+### Print text (GA)
 
 This section lists the supported languages for extracting printed texts in the latest GA version.
 
@@ -178,14 +178,14 @@ Language| Locale code |
 
 ## Detected languages: Read API
 
-The [Read API](concept-read.md) supports language detection for the following languages:
+The [Read API](concept-read.md) supports detecting the following languages in your documents. This list may include languages not currently supported for text extraction.
 
 > [!NOTE]
 > **Language detection**
 >
-> Form Recognizer read model can _detect_ a wide range of languages, variants, dialects, and some regional/cultural languages and return a language code.
->
-> This section lists the languages that can be detected using the Read API. To determine if text can also be _extracted_ for a given language, see [handwritten](#handwritten-languages-preview-and-ga), [print preview](#print-languages-preview), and [print GA](#print-languages-ga) language extraction lists (above).
+> Form Recognizer read model can _detect_ possible presence of languages and returns language codes for detected languages. To determine if text can also be 
+> extracted for a given language, see previous sections.
+
 
 | Language            | Code |
 |---------------------|---------------|

articles/applied-ai-services/form-recognizer/language-support.md

@@ -10,7 +10,7 @@ metadata:
   description: Learn how to deploy resources to complex and distributed environments across on-premises, edge and multicloud. Azure Arc enables deployment of Azure services anywhere and extends Azure management to any infrastructure.
   ms.service: azure-arc
   ms.topic: hub-page
-  ms.date: 10/25/2021
+  ms.date: 05/02/2022
   ms.custom: e2e-hybrid
 
 # highlightedContent section (optional)
@@ -81,7 +81,7 @@ conceptualContent:
           text: Apply configurations on clusters using GitOps
         - url: ./kubernetes/tutorial-arc-enabled-open-service-mesh.md
           itemType: tutorial
-          text: Azure Arc-enabled Open Service Mesh (Preview)
+          text: Azure Arc-enabled Open Service Mesh
       # footerLink (optional)
       footerLink:
         url: ./kubernetes/index.yml