Merge pull request #219890 from MicrosoftDocs/main

Publish to Live, Wednesday 4AM PST, 11/30

Author: PMEds28

.openpublishing.redirection.json

@@ -16323,6 +16323,11 @@
             "redirect_url": "/azure/scheduler/migrate-from-scheduler-to-logic-apps",
             "redirect_document_id": ""
         },
+        {
+            "source_path_from_root": "/articles/search/search-how-to-index-power-query-data-sources.md",
+            "redirect_url": "/previous-versions/azure/search/search-how-to-index-power-query-data-sources",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/search/cognitive-search-quickstart-ocr.md",
             "redirect_url": "/azure/search/cognitive-search-quickstart-blob",

articles/applied-ai-services/form-recognizer/containers/form-recognizer-container-configuration.md

@@ -7,16 +7,18 @@ manager: nitinme
 ms.service: applied-ai-services
 ms.subservice: forms-recognizer
 ms.topic: how-to
-ms.date: 10/20/2022
+ms.date: 11/29/2022
 ms.author: lajanuar
-monikerRange: '>=form-recog-2.1.0'
+monikerRange: 'form-recog-2.1.0'
 recommendations: false
 ---
 # Configure Form Recognizer containers
 
+**This article applies to:** ![Form Recognizer v2.1 checkmark](../media/yes-icon.png) **Form Recognizer v2.1**.
+
 > [!IMPORTANT]
 >
-> Form Recognizer containers are in gated preview. To use them, you must submit an [online request](https://customervoice.microsoft.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbR7en2Ais5pxKtso_Pz4b1_xUNlpBU1lFSjJUMFhKNzVHUUVLN1NIOEZETiQlQCN0PWcu), and have it approved. For more information, See [**Request approval to run container**](form-recognizer-container-install-run.md#request-approval-to-run-the-container).
+> Form Recognizer containers are in gated release. To use them, you must submit an [online request](https://customervoice.microsoft.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbR7en2Ais5pxKtso_Pz4b1_xUNlpBU1lFSjJUMFhKNzVHUUVLN1NIOEZETiQlQCN0PWcu), and have it approved. For more information, See [**Request approval to run container**](form-recognizer-container-install-run.md#request-approval-to-run-the-container).
 
 With Azure Form Recognizer containers, you can build an application architecture that's optimized to take advantage of both robust cloud capabilities and edge locality. Containers provide a minimalist, isolated environment that can be easily deployed on-premises and in the cloud. In this article, you'll learn to configure the Form Recognizer container run-time environment by using the `docker compose` command arguments. Form Recognizer features are supported by six Form Recognizer feature containers—**Layout**, **Business Card**,**ID Document**,  **Receipt**, **Invoice**, **Custom**. These containers have both required and optional settings. For a few examples, see the [Example docker-compose.yml file](#example-docker-composeyml-file) section.
 
@@ -149,3 +151,5 @@ networks:
 
 > [!div class="nextstepaction"]
 > [Learn more about running multiple containers and the docker compose command](form-recognizer-container-install-run.md)
+
+* [Azure container instance recipe](../../../cognitive-services/containers/azure-container-instance-recipe.md)

articles/applied-ai-services/form-recognizer/containers/form-recognizer-container-image-tags.md

@@ -7,17 +7,19 @@ manager: nitinme
 ms.service: applied-ai-services
 ms.subservice: forms-recognizer
 ms.topic: reference
-ms.date: 10/20/2022
+ms.date: 11/29/2022
 ms.author: lajanuar
-monikerRange: '>=form-recog-2.1.0'
+monikerRange: 'form-recog-2.1.0'
 recommendations: false
 ---
 
 # Form Recognizer container image tags and release notes
 
+**This article applies to:** ![Form Recognizer v2.1 checkmark](../media/yes-icon.png) **Form Recognizer v2.1**.
+
 > [!IMPORTANT]
 >
-> * **Form Recognizer v2.1 containers** are in gated preview. To use them, you must submit an [online request](https://customervoice.microsoft.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbR7en2Ais5pxKtso_Pz4b1_xUNlpBU1lFSjJUMFhKNzVHUUVLN1NIOEZETiQlQCN0PWcu), and receive approval. 
+> * **Form Recognizer v2.1 containers** are in gated release. To use them, you must submit an [online request](https://customervoice.microsoft.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbR7en2Ais5pxKtso_Pz4b1_xUNlpBU1lFSjJUMFhKNzVHUUVLN1NIOEZETiQlQCN0PWcu), and receive approval.
 >
 > * The online request form requires that you provide a valid email address that belongs to the organization that owns the Azure subscription ID and that you have or have been granted access to that subscription.
 
@@ -49,17 +51,17 @@ The following tags are available for Form Recognizer:
 
 ### [Latest version](#tab/current)
 
-Release notes for `v2.1` (gated preview):
+Release notes for `v2.1`:
 
 | Container | Tags | Retrieve image |
 |------------|:------|------------|
-| **Layout**| &bullet; `latest` </br> &bullet; `2.1-preview`| `docker pull mcr.microsoft.com/azure-cognitive-services/form-recognizer/layout)`|
-| **Business Card** | &bullet; `latest` </br> &bullet; `2.1-preview` |`docker pull mcr.microsoft.com/azure-cognitive-services/form-recognizer/receipt` |
-| **ID Document** | &bullet; `latest` </br> &bullet; `2.1-preview`| `docker pull mcr.microsoft.com/azure-cognitive-services/form-recognizer/id-document`|
-| **Receipt**| &bullet; `latest` </br> &bullet; `2.1-preview`| `docker pull mcr.microsoft.com/azure-cognitive-services/form-recognizer/receipt` |
-| **Invoice**| &bullet; `latest` </br> &bullet; `2.1-preview`|`docker pull mcr.microsoft.com/azure-cognitive-services/form-recognizer/invoice` |
-| **Custom API** | &bullet; `latest` </br> &bullet; `2.1-preview`| `docker pull mcr.microsoft.com/azure-cognitive-services/form-recognizer/custom-api`|
-| **Custom Supervised**| &bullet; `latest` </br> &bullet; `2.1-preview`|`docker pull mcr.microsoft.com/azure-cognitive-services/form-recognizer/custom-supervised` |
+| **Layout**| &bullet; `latest` </br> &bullet; `2.1`| `docker pull mcr.microsoft.com/azure-cognitive-services/form-recognizer/layout)`|
+| **Business Card** | &bullet; `latest` </br> &bullet; `2.1` |`docker pull mcr.microsoft.com/azure-cognitive-services/form-recognizer/receipt` |
+| **ID Document** | &bullet; `latest` </br> &bullet; `2.1`| `docker pull mcr.microsoft.com/azure-cognitive-services/form-recognizer/id-document`|
+| **Receipt**| &bullet; `latest` </br> &bullet; `2.1`| `docker pull mcr.microsoft.com/azure-cognitive-services/form-recognizer/receipt` |
+| **Invoice**| &bullet; `latest` </br> &bullet; `2.1`|`docker pull mcr.microsoft.com/azure-cognitive-services/form-recognizer/invoice` |
+| **Custom API** | &bullet; `latest` </br> &bullet; `2.1`| `docker pull mcr.microsoft.com/azure-cognitive-services/form-recognizer/custom-api`|
+| **Custom Supervised**| &bullet; `latest` </br> &bullet; `2.1`|`docker pull mcr.microsoft.com/azure-cognitive-services/form-recognizer/custom-supervised` |
 
 ### [Previous versions](#tab/previous)
 
@@ -73,3 +75,5 @@ Release notes for `v2.1` (gated preview):
 > [!div class="nextstepaction"]
 > [Install and run Form Recognizer containers](form-recognizer-container-install-run.md)
 >
+
+* [Azure container instance recipe](../../../cognitive-services/containers/azure-container-instance-recipe.md)

articles/applied-ai-services/form-recognizer/containers/form-recognizer-container-install-run.md

@@ -7,17 +7,19 @@ manager: nitinme
 ms.service: applied-ai-services
 ms.subservice: forms-recognizer
 ms.topic: how-to
-ms.date: 10/20/2022
+ms.date: 11/29/2022
 ms.author: lajanuar
-monikerRange: '>=form-recog-2.1.0'
+monikerRange: 'form-recog-2.1.0'
 recommendations: false
 ---
 
-# Install and run Form Recognizer v2.1-preview containers
+# Install and run Form Recognizer v2.1 containers
+
+**This article applies to:** ![Form Recognizer v2.1 checkmark](../media/yes-icon.png) **Form Recognizer v2.1**.
 
 > [!IMPORTANT]
 >
-> * Form Recognizer containers are in gated preview. To use them, you must submit an [online request](https://aka.ms/csgate), and receive approval. For more information, *see* [**Request approval to run container**](#request-approval-to-run-the-container) below.
+> * Form Recognizer containers are in gated release. To use them, you must submit an [online request](https://aka.ms/csgate), and receive approval. For more information, *see* [**Request approval to run container**](#request-approval-to-run-the-container) below.
 >
 > * The online request form requires that you provide a valid email address that belongs to the organization that owns the Azure subscription ID and that you have or have been granted access to that subscription.
 
@@ -84,21 +86,21 @@ The following table lists the supporting container(s) for each Form Recognizer c
 
 | Container | Minimum | Recommended |
 |-----------|---------|-------------|
-| Read 3.2 | 8 cores, 16-GB memory | 8 cores, 24-GB memory|
-| Layout 2.1-preview | 8 cores, 16-GB memory | 8 cores, 24-GB memory |
-| Business Card 2.1-preview | 2 cores, 4-GB memory | 4 cores, 4-GB memory |
-| ID Document 2.1-preview | 1 core, 2-GB memory |2 cores, 2-GB memory |
-| Invoice 2.1-preview | 4 cores, 8-GB memory | 8 cores, 8-GB memory |
-| Receipt 2.1-preview |  4 cores, 8-GB memory | 8 cores, 8-GB memory  |
+| Read 3.2 | `8` cores, 16-GB memory | `8` cores, 24-GB memory|
+| Layout 2.1 | `8` cores, 16-GB memory | `8` cores, 24-GB memory |
+| Business Card 2.1 | `2` cores, 4-GB memory | `4` cores, 4-GB memory |
+| ID Document 2.1 | `1` core, 2-GB memory |`2` cores, 2-GB memory |
+| Invoice 2.1 | `4` cores, 8-GB memory | `8` cores, 8-GB memory |
+| Receipt 2.1 |  `4` cores, 8-GB memory | `8` cores, 8-GB memory  |
 
 ##### Custom containers
 
 The following host machine requirements are applicable to **train and analyze** requests:
 
 | Container | Minimum | Recommended |
 |-----------|---------|-------------|
-| Custom API| 0.5 cores, 0.5-GB memory| 1 cores, 1-GB memory |
-|Custom Supervised | 4 cores, 2-GB memory | 8 cores, 4-GB memory|
+| Custom API| 0.5 cores, 0.5-GB memory| `1` core, 1-GB memory |
+|Custom Supervised | `4` cores, 2-GB memory | `8` cores, 4-GB memory|
 
 * Each core must be at least 2.6 gigahertz (GHz) or faster.
 * Core and memory correspond to the `--cpus` and `--memory` settings, which are used as part of the `docker compose` or `docker run`  command.
@@ -324,7 +326,7 @@ In addition to the [prerequisites](#prerequisites) mentioned above, you'll need
 ####  • Create a folder to store the following files:
 
   1. [**.env**](#-create-an-environment-file)
-  1. [**nginx.conf**](#-create-a-nginx-file)
+  1. [**nginx.conf**](#-create-an-nginx-file)
   1. [**docker-compose.yml**](#-create-a-docker-compose-file)
 
 #### • Create a folder to store your input data
@@ -355,7 +357,7 @@ In addition to the [prerequisites](#prerequisites) mentioned above, you'll need
   NGINX_CONF_FILE="<file-path>"
   ```
 
-#### &bullet; Create a **nginx** file
+#### &bullet; Create an **nginx** file
 
   1. Name this file **nginx.conf**.
 
@@ -622,4 +624,6 @@ That's it! In this article, you learned concepts and workflows for downloading,
 
 ## Next steps
 
-* [Form Recognizer container configuration settings](form-recognizer-container-configuration.md) 
+* [Form Recognizer container configuration settings](form-recognizer-container-configuration.md)
+
+* [Azure container instance recipe](../../../cognitive-services/containers/azure-container-instance-recipe.md)

articles/applied-ai-services/form-recognizer/toc.yml

@@ -87,8 +87,6 @@ items:
     - name: Container image tags
       displayName: registry, mcr
       href: containers/form-recognizer-container-image-tags.md
-    - name: Use container instances
-      href: ../../cognitive-services/containers/azure-container-instance-recipe.md
   - name: Configure secure communications
     items:
     - name: Set up Virtual Networks
@@ -133,30 +131,30 @@ items:
   - name: Model overview
     displayName: get started, prebuilt, extraction, input
     href: concept-model-overview.md
-  - name: Form Recognizer Studio 
+  - name: Form Recognizer Studio
     href: concept-form-recognizer-studio.md
   - name: Read OCR model
     displayName: text
     href: concept-read.md
   - name: General document model
     displayName: key value pairs, selection marks, structured
     href: concept-general-document.md
-  - name: Layout model 
+  - name: Layout model
     displayName: tables, selection marks, structure, paragraph roles, text, headers, page numbers
     href: concept-layout.md
   - name: W-2 form model
     displayName: wages, taxes, salary, employees
     href: concept-w2.md
-  - name: Invoice model 
+  - name: Invoice model
     displayName: sales, vendors, VAT
     href: concept-invoice.md
-  - name: Receipt model 
+  - name: Receipt model
     displayName: sales, merchants
     href: concept-receipt.md
-  - name: ID document model 
+  - name: ID document model
     displayName: passport, visa, ID, social security, green card
     href: concept-id-document.md
-  - name: Business card model 
+  - name: Business card model
     displayName: https://westus.dev.cognitive.microsoft.com/docs/services/form-recognizer-api-2022-08-31/operations/AnalyzeDocument
     href: concept-business-card.md
   - name: Custom models
@@ -202,7 +200,7 @@ items:
     href: tutorial-azure-function.md
 - name: Reference
   items:
-    - name: REST API v3.0 
+    - name: REST API v3.0
       href: https://westus.dev.cognitive.microsoft.com/docs/services/form-recognizer-api-2022-08-31/operations/AnalyzeDocument
     - name: Error codes and messages v3.0
       href: v3-error-guide.md

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

@@ -27,10 +27,16 @@ Form Recognizer service is updated on an ongoing basis. Bookmark this page to st
 >[!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
+## November 2022
+
+* **Announcing the latest stable release of Azure Form Recognizer libraries**
+  * This release includes important changes and updates for .NET, Java, JavaScript, and Python SDKs. For more information, _see_ [**Azure SDK DevBlog**](https://devblogs.microsoft.com/azure-sdk/announcing-new-stable-release-of-azure-form-recognizer-libraries/).
+  * The most significant enhancements are the introduction of two new clients, the **`DocumentAnalysisClient`** and the **`DocumentModelAdministrationClient`**.
 
 ---
 
+## October 2022
+
 * **Form Recognizer versioned content**
   * Form Recognizer documentation has been updated to present a versioned experience. Now, you can choose to view content targeting the v3.0 GA experience or the v2.1 GA experience. The v3.0 experience is the default.
 

articles/attestation/overview.md

@@ -83,12 +83,15 @@ Azure Attestation is the preferred choice for attesting TEEs as it offers the fo
 
 3.	**Validate binding of Azure Attestation SGX quote with the key that signed the attestation token** – Relying party can verify if hash of the public key that signed the attestation token matches the report data field of the Azure Attestation SGX quote. See [code samples](https://github.com/Azure-Samples/microsoft-azure-attestation/blob/e7f296ee2ca1dd93b75acdc6bab0cc9a6a20c17c/sgx.attest.sample.oe.sdk/validatequotes.net/MaaQuoteValidator.cs#L78-L105)  for more information
 
-4.	**Validate if Azure Attestation code measurements match the Azure published values** -  The SGX quote embedded in attestation token signing certificates includes code measurements of Azure Attestation, like mrsigner. If relying party is interested to validate if the SGX quote belongs to Azure Attestation running inside Azure, mrsigner value can be retrieved from the SGX quote in attestation token signing certificate and compared with the value provided by Azure Attestation team. If you are interested to perform this validation, please submit a request on [Azure support](/support/) page. Azure Attestation team will reach out to you when Mrsigner is planned for rotation. 
+4.	**Validate if Azure Attestation code measurements match the Azure published values** -  The SGX quote embedded in attestation token signing certificates includes code measurements of Azure Attestation, like mrsigner. If relying party is interested to validate if the SGX quote belongs to Azure Attestation running inside Azure, mrsigner value can be retrieved from the SGX quote in attestation token signing certificate and compared with the value provided by Azure Attestation team. If you are interested to perform this validation, please submit a request on [Azure support page](https://azure.microsoft.com/support/options/). Azure Attestation team will reach out to you when we plan to rotate the Mrsigner. 
 
 Mrsigner of Azure Attestation is expected to change when code signing certificates are rotated. Azure Attestation team will follow the below rollout schedule for every mrsigner rotation:
-I.	Azure Attestation team will notify the upcoming MRSIGNER value with a 2 month grace period for making relevant code changes
-II.	After the 2-month grace period, Azure Attestation will start using the new MRSIGNER value
-III.	3 months post notification date, Azure Attestation will stop using the old MRSIGNER value
+
+i.	Azure Attestation team will notify the upcoming MRSIGNER value with a 2 month grace period for making relevant code changes
+
+ii.	After the 2-month grace period, Azure Attestation will start using the new MRSIGNER value
+
+iii.	3 months post notification date, Azure Attestation will stop using the old MRSIGNER value
 
 
 ## Business Continuity and Disaster Recovery (BCDR) support

articles/azure-monitor/agents/agents-overview.md

@@ -198,7 +198,7 @@ View [supported operating systems for Azure Arc Connected Machine agent](../../a
 | Oracle Linux 7                                              | X | X | X |
 | Oracle Linux 6                                              |   | X |   |
 | Oracle Linux 6.4+                                           |   | X | X |
-| Red Hat Enterprise Linux Server 8.6                         | X<sup>3</sup> |   |   |
+| Red Hat Enterprise Linux Server 8.6                         | X<sup>3</sup> | X |   |
 | Red Hat Enterprise Linux Server 8                           | X | X |   |
 | Red Hat Enterprise Linux Server 7                           | X | X | X |
 | Red Hat Enterprise Linux Server 6                           |   | X |   |