Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into ip-upgrade

Author: halkazwini

articles/active-directory/saas-apps/linkedinsalesnavigator-provisioning-tutorial.md

@@ -65,12 +65,12 @@ The first step is to retrieve your LinkedIn access token. If you are an Enterpri
 4. Click **+ Add new SCIM configuration** and follow the procedure by filling in each field.
 
     > [!NOTE]
-    > When auto­assign licenses is not enabled, it means that only user data is synced.
+    > When auto-assign licenses is not enabled, it means that only user data is synced.
 
     ![Screenshot shows the LinkedIn Account Center Global Settings.](./media/linkedinsalesnavigator-provisioning-tutorial/linkedin_1.PNG)
 
     > [!NOTE]
-    > When auto­license assignment is enabled, you need to note the application instance and license type. Licenses are assigned on a first come, first serve basis until all the licenses are taken.
+    > When auto-license assignment is enabled, you need to note the application instance and license type. Licenses are assigned on a first come, first serve basis until all the licenses are taken.
 
     ![Screenshot shows the S C I M Setup page.](./media/linkedinsalesnavigator-provisioning-tutorial/linkedin_2.PNG)
 
@@ -94,7 +94,7 @@ The first step is to retrieve your LinkedIn access token. If you are an Enterpri
 
     * In the **Secret Token** field, enter the access token you generated in step 1 and click **Test Connection** .
 
-    * You should see a success notification on the upper­right side of
+    * You should see a success notification on the upper-right side of
     your portal.
 
 12. Enter the email address of a person or group who should receive provisioning error notifications in the **Notification Email** field, and check the checkbox below.

articles/api-management/how-to-deploy-self-hosted-gateway-kubernetes-opentelemetry.md

@@ -114,7 +114,7 @@ Now that we have the chart repository configured, we can deploy the OpenTelemetr
         protocol: TCP
     ```
 
-This allows us to use a standalone collector with the Prometheus exporter being exposed on port `8889`. To expose the Prometheus metrics, we are asking the Helm chart to configure a ´LoadBalancer` service.
+This allows us to use a standalone collector with the Prometheus exporter being exposed on port `8889`. To expose the Prometheus metrics, we are asking the Helm chart to configure a `LoadBalancer` service.
 
 > [!NOTE]
 > We are disabling the compact Jaeger port given it uses UDP and `LoadBalancer` service does not allow you to have multiple protocols at the same time.

articles/app-service/app-service-web-configure-tls-mutual-auth.md

@@ -27,11 +27,59 @@ To set up your app to require client certificates:
 
 1. Set **Client certificate mode** to **Require**. Click **Save** at the top of the page.
 
+### [Azure CLI](#tab/azurecli)
 To do the same with Azure CLI, run the following command in the [Cloud Shell](https://shell.azure.com):
 
 ```azurecli-interactive
 az webapp update --set clientCertEnabled=true --name <app-name> --resource-group <group-name>
 ```
+### [Bicep](#tab/bicep)
+
+For Bicep, modify the properties `clientCertEnabled`, `clientCertMode`, and `clientCertExclusionPaths`. A sampe Bicep snippet is provided for you:
+
+```bicep
+resource appService 'Microsoft.Web/sites@2020-06-01' = {
+  name: webSiteName
+  location: location
+  kind: 'app'
+  properties: {
+    serverFarmId: appServicePlan.id
+    siteConfig: {
+      linuxFxVersion: linuxFxVersion
+    }
+    clientCertEnabled: true
+    clientCertMode: 'Required'
+    clientCertExclusionPaths: '/sample1;/sample2'
+  }
+}
+```
+
+### [ARM](#tab/arm)
+
+For ARM templates, modify the properties `clientCertEnabled`, `clientCertMode`, and `clientCertExclusionPaths`. A sampe ARM template snippet is provided for you:
+
+```ARM
+{
+    "type": "Microsoft.Web/sites",
+    "apiVersion": "2020-06-01",
+    "name": "[parameters('webAppName')]",
+    "location": "[parameters('location')]",
+    "dependsOn": [
+        "[resourceId('Microsoft.Web/serverfarms', variables('appServicePlanPortalName'))]"
+    ],
+    "properties": {
+        "serverFarmId": "[resourceId('Microsoft.Web/serverfarms', variables('appServicePlanPortalName'))]",
+        "siteConfig": {
+            "linuxFxVersion": "[parameters('linuxFxVersion')]"
+        },
+        "clientCertEnabled": true,
+        "clientCertMode": "Required",
+        "clientCertExclusionPaths": "/sample1;/sample2"
+    }
+}
+```
+
+---
 
 ## Exclude paths from requiring authentication
 

articles/app-service/tutorial-java-tomcat-connect-managed-identity-postgresql-database.md

@@ -4,8 +4,8 @@ description: Secure Azure Database for PostgreSQL connectivity with managed iden
 ms.devlang: java
 ms.topic: tutorial
 ms.date: 09/26/2022
-author: shizn
-ms.author: xshi
+author: KarlErickson
+ms.author: karler
 ---
 
 # Tutorial: Connect to a PostgreSQL Database from Java Tomcat App Service without secrets using a managed identity
@@ -25,7 +25,7 @@ ms.author: xshi
 * [Git](https://git-scm.com/)
 * [Java JDK](/azure/developer/java/fundamentals/java-support-on-azure)
 * [Maven](https://maven.apache.org)
-* [Azure CLI](/cli/azure/overview). This quickstart requires that you are running the latest [edge build of Azure CLI](https://github.com/Azure/azure-cli/blob/dev/doc/try_new_features_before_release.md). [Download and install the edge builds](https://github.com/Azure/azure-cli#edge-builds) for your platform.
+* [Azure CLI](/cli/azure/install-azure-cli) version 2.41.0 or higher.
 
 ## Clone the sample app and prepare the repo
 

articles/applied-ai-services/form-recognizer/v3-migration-guide.md

@@ -19,6 +19,20 @@ recommendations: false
 >
 > Form Recognizer REST API v3.0 introduces breaking changes in the REST API request and analyze response JSON.
 
+## Migrating from a v3.0 preview API version
+
+Preview APIs are periodically deprecated. If you're using a preview API version, plan on updating your application to target the GA API version once available. To migrate from the 2021-09-30-preview or the 2022-01-30-preview API versions to the 2022-08-31 (GA) API version using the SDK, update to the [current version of the language specific SDK](sdk-overview.md).
+
+The 2022-08-31 API has a few updates from the preview API versions:
+* Field rename:  boundingBox to polygon to support non-quadrilateral polygon regions.
+* Field deleted: entities removed from the result of the general document model.
+* Field rename: documentLanguage.languageCode to locale
+* Added support for HEIF format
+* Added paragraph detection, with role classification for layout and general document models
+* Added support for parsed address fields.
+
+## Migrating from v2.1
+
 Form Recognizer v3.0  introduces several new features and capabilities:
 
 * [Form Recognizer REST API](quickstarts/get-started-sdks-rest-api.md?view=form-recog-3.0.0&preserve-view=true) has been redesigned for better usability.
@@ -92,7 +106,7 @@ Base64 encoding is also supported in Form Recognizer v3.0:
 }
 ```
 
-### Additional supported parameters
+### Additionally supported parameters
 
 Parameters that continue to be supported:
 
@@ -372,4 +386,5 @@ In this migration guide, you've learned how to upgrade your existing Form Recogn
 
 * [Review the new REST API](https://westus.dev.cognitive.microsoft.com/docs/services/form-recognizer-api-2022-08-31/operations/AnalyzeDocument)
 * [What is Form Recognizer?](overview.md)
-* [Form Recognizer quickstart](/azure/applied-ai-services/form-recognizer/how-to-guides/v2-1-sdk-rest-api)
+* [Form Recognizer quickstart](./quickstarts/try-sdk-rest-api.md)
+

articles/applied-ai-services/form-recognizer/whats-new.md

@@ -11,6 +11,7 @@ ms.date: 10/20/2022
 ms.author: lajanuar
 monikerRange: '>=form-recog-2.1.0'
 recommendations: false
+ms.custom: references_regions
 ---
 <!-- markdownlint-disable MD024 -->
 <!-- markdownlint-disable MD036 -->
@@ -23,12 +24,22 @@ recommendations: false
 
 Form Recognizer service is updated on an ongoing basis. Bookmark this page to stay up to date with release notes, feature enhancements, and documentation updates.
 
+>[!NOTE]
+> With the release of the 2022-08-31 GA API, the associated preview APIs are being deprecated. If you are using the 2021-09-30-preview or the 2022-01-30-preview API versions, please update your applications to target the 2022-08-31 API version. There are a few minor changes involved, for more information, _see_ the [migration guide](v3-migration-guide.md).
+
 ## October 2022
 
 With the latest preview release, Form Recognizer's Read (OCR), Layout, and Custom template models support 134 new languages. These language additions include Greek, Latvian, Serbian, Thai, Ukrainian, and Vietnamese, along with several Latin and Cyrillic languages. Form Recognizer now has a total of 299 supported languages across the most recent GA and new preview versions. Refer to the [supported languages](language-support.md) page to see all supported languages.
 
 Use the REST API parameter `api-version=2022-06-30-preview` when using the API or the corresponding SDK to support the new languages in your applications.
 
+### Region expansion for training custom neural models 
+
+Training custom neural models now supported in added regions.
+* East US
+* East US2
+* US Gov Arizona
+
 ## September 2022
 
 ### Region expansion for training custom neural models
@@ -565,7 +576,7 @@ The updated Layout API table feature adds header recognition with column headers
 
 * Client defaults to the latest supported service version, currently v2.1. You can specify version 2.0  in the **FormRecognizerClientOptions** object's **Version** property.
 
-* **StartRecognizeIdentityDocuments**. Renamed methods and method parameters using **Identity** to replace _Id_ keyword for all related identity documents recognition API functionalities.
+* **StartRecognizeIdentityDocuments**. Renamed methods and method parameters using **Identity** to replace _ID_ keyword for all related identity documents recognition API functionalities.
 
 * **FormReadingOrder**. *ReadingOrder* renamed to **FormReadingOrder**.
 
@@ -653,7 +664,7 @@ The updated Layout API table feature adds header recognition with column headers
 
 #### **Breaking changes (May)**
 
-* **begin_recognize_identity_documents** and **begin_recognize_identity_documents_from_url**. Renamed methods and method parameters using **Identity** to replace _Id_ keyword.
+* **begin_recognize_identity_documents** and **begin_recognize_identity_documents_from_url**. Renamed methods and method parameters using **Identity** to replace _ID_ keyword.
 
 * **FieldValueType**. Renamed value type *country* to **countryRegion**.  Removed value type *gender*.