Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into lb-rules-freshness

Author: asudbring

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

@@ -39,7 +39,7 @@ December 2022
 
   * **Custom model labeling**:
 
-    * **Batch OCR**. You can opt to run batch OCR in the setup wizard for custom model on all documents in your blob storage.
+    * **Run Layout API automatically**. You can opt to run the Layout API for all documents automatically in your blob storage during the setup process for custom model.
 
     * **Search**. The Studio now includes search functionality to locate words within a document. This improvement allows for easier navigation while labeling.
 

articles/azure-arc/data/includes/azure-arc-data-preview-release.md

@@ -6,11 +6,10 @@ ms.topic: include
 ms.date: 12/7/2022
 ---
 
-<!---
 
 At this time, a test or preview build is not available for the next release.
 
--->
+<!---
 December 2022 preview release is now available.
 
 |Component|Value|
@@ -28,3 +27,4 @@ New for this release:
 - Arc-enabled PostgreSQL server
   - Switch to Ubuntu based images
 
+--->

articles/azure-arc/data/release-notes.md

@@ -17,6 +17,29 @@ ms.custom: references_regions, devx-track-azurecli, event-tier1-build-2022
 
 This article highlights capabilities, features, and enhancements recently released or improved for Azure Arc-enabled data services.
 
+## December 13, 2022
+
+### Image tag
+
+`v1.14.0_2022-12-13`
+
+For complete release version information, see [Version log](version-log.md#december-13-2022).
+
+New for this release:
+
+- Arc data controller.
+    Added defaults on HA supervisor pod to support resource quotas.
+
+- Arc-enabled PostgreSQL server
+  - Switch to Ubuntu based images.
+ 
+- Arc-enabled SQL Server
+  - Database as a resource compatibility for SQL Server 2014 and SQL Server 2016. See [View databases](/sql/sql-server/azure-arc/view-databases).
+
+- Bug fixes and optimizations in the following areas:
+  - Arc enabling SQL Server onboarding.
+  - Fixed confusing error messages when DBMail is configured.
+
 ## November 8, 2022
 
 ### Image tag

articles/azure-arc/data/version-log.md

@@ -17,6 +17,17 @@ ms.topic: conceptual
 
 This article identifies the component versions with each release of Azure Arc-enabled data services.
 
+## December 13, 2022
+
+|Component|Value|
+|-----------|-----------|
+|Container images tag |`v1.14.0_2022-12-13`|
+|CRD names and version|`datacontrollers.arcdata.microsoft.com`: v1beta1, v1 through v6<br/>`exporttasks.tasks.arcdata.microsoft.com`: v1beta1, v1, v2<br/>`kafkas.arcdata.microsoft.com`: v1beta1, v1beta2<br/>`monitors.arcdata.microsoft.com`: v1beta1, v1, v2<br/>`sqlmanagedinstances.sql.arcdata.microsoft.com`: v1beta1, v1 through v7<br/>`postgresqls.arcdata.microsoft.com`: v1beta1, v1beta2, v1beta3<br/>`sqlmanagedinstancerestoretasks.tasks.sql.arcdata.microsoft.com`: v1beta1, v1<br/>`failovergroups.sql.arcdata.microsoft.com`: v1beta1, v1beta2, v1 through v2<br/>`activedirectoryconnectors.arcdata.microsoft.com`: v1beta1, v1beta2, v1<br/>`sqlmanagedinstancereprovisionreplicatask.tasks.sql.arcdata.microsoft.com`: v1beta1<br/>`telemetrycollectors.arcdata.microsoft.com`: v1beta1, v1beta2, v1beta3 *use to be otelcollectors*<br/>`telemetryrouters.arcdata.microsoft.com`: v1beta1, v1beta2, v1beta3, v1beta4<br/>`sqlmanagedinstancemonitoringprofiles.arcdata.microsoft.com`: v1beta1, v1beta2<br/>|
+|Azure Resource Manager (ARM) API version|2022-06-15-preview|
+|`arcdata` Azure CLI extension version|1.4.9 ([Download](https://aka.ms/az-cli-arcdata-ext))|
+|Arc-enabled Kubernetes helm chart extension version|1.14.0|
+|Azure Arc Extension for Azure Data Studio<br/>`arc`<br/>`azcli`|*No Changes*<br/>1.7.0 ([Download](https://aka.ms/ads-arcdata-ext))</br>1.7.0 ([Download](https://aka.ms/ads-azcli-ext))|
+
 ## November 8, 2022
 
 

articles/azure-monitor/logs/logs-dedicated-clusters.md

@@ -69,7 +69,8 @@ You can have up to five active clusters per subscription per region. If the clus
 > - A list of initial workspace to be linked to cluster is identified
 > - You have permissions to subscription intended for the cluster and any workspace to be linked
 
-**CLI**
+#### [CLI](#tab/cli)
+
 ```azurecli
 az account set --subscription "cluster-subscription-id"
 
@@ -80,7 +81,7 @@ $clusterResourceId = az monitor log-analytics cluster list --resource-group "res
 az resource wait --created --ids $clusterResourceId --include-response-body true
 ```
 
-**PowerShell**
+#### [PowerShell](#tab/powershell)
 
 ```powershell
 Select-AzSubscription "cluster-subscription-id"
@@ -91,7 +92,7 @@ New-AzOperationalInsightsCluster -ResourceGroupName "resource-group-name" -Clust
 Get-Job -Command "New-AzOperationalInsightsCluster*" | Format-List -Property *
 ```
 
-**REST API**
+#### [REST API](#tab/restapi)
 
 *Call* 
 
@@ -119,27 +120,29 @@ Content-type: application/json
 
 Should be 202 (Accepted) and a header.
 
+---
+
 ### Check cluster provisioning status
 
 The provisioning of the Log Analytics cluster takes a while to complete. Use one of the following methods to check the *ProvisioningState* property. The value is *ProvisioningAccount* while provisioning and *Succeeded* when completed.
 
-**CLI**
+#### [CLI](#tab/cli)
 
 ```azurecli
 az account set --subscription "cluster-subscription-id"
 
 az monitor log-analytics cluster show --resource-group "resource-group-name" --name "cluster-name"
 ```
 
-**PowerShell**
+#### [PowerShell](#tab/powershell)
 
 ```powershell
 Select-AzSubscription "cluster-subscription-id"
 
 Get-AzOperationalInsightsCluster -ResourceGroupName "resource-group-name" -ClusterName "cluster-name"
 ```
 
-**REST API**
+#### [REST API](#tab/restapi)
 
 Send a GET request on the cluster resource and look at the *provisioningState* value. The value is *ProvisioningAccount* while provisioning and *Succeeded* when completed.
 
@@ -208,7 +211,8 @@ Linking a workspace can be performed only after the completion of the Log Analyt
 
 Use the following commands to link a workspace to a cluster:
 
-**CLI**
+#### [CLI](#tab/cli)
+
 ```azurecli
 # Find cluster resource ID
 az account set --subscription "cluster-subscription-id"
@@ -223,7 +227,7 @@ $workspaceResourceId = az monitor log-analytics workspace list --resource-group
 az resource wait --deleted --ids $workspaceResourceId --include-response-body true
 ```
 
-**PowerShell**
+#### [PowerShell](#tab/powershell)
 
 ```powershell
 Select-AzSubscription "cluster-subscription-id"
@@ -240,7 +244,7 @@ Set-AzOperationalInsightsLinkedService -ResourceGroupName "resource-group-name"
 Get-Job -Command "Set-AzOperationalInsightsLinkedService" | Format-List -Property *
 ```
 
-**REST API**
+#### [REST API](#tab/restapi)
 
 Use the following REST call to link to a cluster:
 
@@ -268,22 +272,23 @@ Content-type: application/json
 
 When a cluster is configured with customer-managed keys, data ingested to the workspaces after the link operation completion is stored encrypted with your managed key. The workspace link operation can take up to 90 minutes to complete and you can check the state by sending Get request to workspace and observe if *clusterResourceId* property is present in the response under *features*.
 
-**CLI**
+#### [CLI](#tab/cli)
+
 ```azurecli
 az account set --subscription "workspace-subscription-id"
 
 az monitor log-analytics workspace show --resource-group "resource-group-name" --workspace-name "workspace-name"
 ```
 
-**PowerShell**
+#### [PowerShell](#tab/powershell)
 
 ```powershell
 Select-AzSubscription "workspace-subscription-id"
 
 Get-AzOperationalInsightsWorkspace -ResourceGroupName "resource-group-name" -Name "workspace-name"
 ```
 
-**REST API**
+#### [REST API](#tab/restapi)
 
 *Call*
 
@@ -346,23 +351,23 @@ After you create your cluster resource and it's fully provisioned, you can edit
 
 ## Get all clusters in resource group
 
-**CLI**
+#### [CLI](#tab/cli)
 
 ```azurecli
 az account set --subscription "cluster-subscription-id"
 
 az monitor log-analytics cluster list --resource-group "resource-group-name"
 ```
 
-**PowerShell**
+#### [PowerShell](#tab/powershell)
 
 ```powershell
 Select-AzSubscription "cluster-subscription-id"
 
 Get-AzOperationalInsightsCluster -ResourceGroupName "resource-group-name"
 ```
 
-**REST API**
+#### [REST API](#tab/restapi)
 
 *Call*
 
@@ -414,22 +419,22 @@ Authorization: Bearer <token>
 
 ## Get all clusters in subscription
 
-**CLI**
+#### [CLI](#tab/cli)
 
 ```azurecli
 az account set --subscription "cluster-subscription-id"
 
 az monitor log-analytics cluster list
 ```
 
-**PowerShell**
+#### [PowerShell](#tab/powershell)
 
 ```powershell
 Select-AzSubscription "cluster-subscription-id"
 
 Get-AzOperationalInsightsCluster
 ```
-**REST API**
+#### [REST API](#tab/restapi)
 
 *Call*
 
@@ -449,23 +454,23 @@ The same as for 'clusters in a resource group', but in subscription scope.
 
 When the data volume to your linked workspaces change over time and you want to update the Commitment Tier level appropriately. The tier is specified in units of GB and can have values of 500, 1000, 2000 or 5000 GB/day. Note that you don't have to provide the full REST request body but should include the sku.
 
-**CLI**
+#### [CLI](#tab/cli)
 
 ```azurecli
 az account set --subscription "cluster-subscription-id"
 
 az monitor log-analytics cluster update --resource-group "resource-group-name" --name "cluster-name"  --sku-capacity 500
 ```
 
-### PowerShell
+#### [PowerShell](#tab/powershell)
 
 ```powershell
 Select-AzSubscription "cluster-subscription-id"
 
 Update-AzOperationalInsightsCluster -ResourceGroupName "resource-group-name" -ClusterName "cluster-name" -SkuCapacity 500
 ```
 
-### REST API
+#### [REST API](#tab/restapi)
 
 *Call*
 
@@ -487,19 +492,23 @@ Content-type: application/json
 
 ### Update billingType in cluster
 
-### PowerShell
+The *billingType* property determines the billing attribution for the cluster and its data:
+- *Cluster* (default) -- billing is attributed to the Cluster resource
+- *Workspaces* -- billing is attributed to linked workspaces proportionally. When data volume from all linked workspaces is below Commitment Tier level, the bill for the remaining volume is attributed to the cluster
+
+#### [CLI](#tab/cli)
+
+N/A
+
+#### [PowerShell](#tab/powershell)
 
 ```powershell
 Select-AzSubscription "cluster-subscription-id"
 
 Update-AzOperationalInsightsCluster -ResourceGroupName "resource-group-name" -ClusterName "cluster-name" -BillingType "Workspaces"
 ```
 
-The *billingType* property determines the billing attribution for the cluster and its data:
-- *Cluster* (default) -- billing is attributed to the Cluster resource
-- *Workspaces* -- billing is attributed to linked workspaces proportionally. When data volume from all linked workspaces is below Commitment Tier level, the bill for the remaining volume is attributed to the cluster
-
-**REST**
+#### [REST API](#tab/restapi)
 
 *Call*
 
@@ -516,24 +525,26 @@ Content-type: application/json
 }
 ```
 
+---
+
 ### Unlink a workspace from cluster
 
 You can unlink a workspace from a cluster at any time. The workspace pricing tier is changed to per-GB, data ingested to cluster before the unlink operation remains in the cluster, and new data to workspace get ingested to Log Analytics. You can query data as usual and the service performs cross-cluster queries seamlessly. If cluster was configured with Customer-managed key (CMK), data remains encrypted with your key and accessible, while your key and permissions to Key Vault remain.  
 
-> [!NOT] 
+> [!NOTE] 
 > There is a limit of two link operations for a specific workspace within a month to prevent data distribution across clusters. Contact support if you reach limit.
 
 Use the following commands to unlink a workspace from cluster:
 
-**CLI**
+#### [CLI](#tab/cli)
 
 ```azurecli
 az account set --subscription "workspace-subscription-id"
 
 az monitor log-analytics workspace linked-service delete --resource-group "resource-group-name" --workspace-name "workspace-name" --name cluster
 ```
 
-**PowerShell**
+#### [PowerShell](#tab/powershell)
 
 ```powershell
 Select-AzSubscription "workspace-subscription-id"
@@ -542,6 +553,10 @@ Select-AzSubscription "workspace-subscription-id"
 Remove-AzOperationalInsightsLinkedService -ResourceGroupName "resource-group-name" -WorkspaceName {workspace-name} -LinkedServiceName cluster
 ```
 
+#### [REST API](#tab/restapi)
+
+N/A
+
 ---
 
 
@@ -560,22 +575,23 @@ If you delete your cluster while workspaces are linked, Workspaces get automatic
 
 Use the following commands to delete a cluster:
 
-**CLI**
+#### [CLI](#tab/cli)
+
 ```azurecli
 az account set --subscription "cluster-subscription-id"
 
 az monitor log-analytics cluster delete --resource-group "resource-group-name" --name $clusterName
 ```
 
-**PowerShell**
+#### [PowerShell](#tab/powershell)
 
 ```powershell
 Select-AzSubscription "cluster-subscription-id"
 
 Remove-AzOperationalInsightsCluster -ResourceGroupName "resource-group-name" -ClusterName "cluster-name"
 ```
 
-**REST API**
+#### [REST API](#tab/restapi)
 
 Use the following REST call to delete a cluster:
 

articles/azure-video-indexer/includes/limited-access-account-types.md

@@ -5,15 +5,15 @@ services: azure-video-indexer
 manager: femila
 ms.service: azure-video-indexer
 ms.topic: include 
-ms.date: 10/14/2022
+ms.date: 12/13/2022
 ms.author: juliako
 ---
 
 This section talks about limited access features in Azure Video Indexer.
 
 |When did I create the account?|Trial account (free)|	Paid account <br/>(classic or ARM-based)|
 |---|---|---|
-|Existing VI accounts <br/><br/>created before June 21, 2022|Able to access face identification, customization and celebrities recognition till June 2023. <br/><br/>**Recommended**: Move to a paid account and afterward fill in the [intake form](https://aka.ms/facerecognition) and based on the eligibility criteria we will enable the features also after the grace period. |Able to access face identification, customization and celebrities recognition till June 2023\*.<br/><br/>**Recommended**: fill in the [intake form](https://aka.ms/facerecognition) and based on the eligibility criteria we will enable the features also after the grace period. <br/><br/>We proactively sent emails to these customers + AEs.|
+|Existing VI accounts <br/><br/>created before June 21, 2022|Able to access face identification, customization and celebrities recognition till June 2023. <br/><br/>**Recommended**: Move to a paid account and afterward fill in the [intake form](https://aka.ms/facerecognition) and based on the eligibility criteria we will enable the features also after the grace period. |Able to access face identification, customization and celebrities recognition till June 2023\*.<br/><br/>**Recommended**: fill in the [intake form](https://aka.ms/facerecognition) and based on the eligibility criteria we will enable the features also after the grace period.|
 |New VI accounts <br/><br/>created after June 21, 2022	|Not able the access face identification, customization and celebrities recognition as of today. <br/><br/>**Recommended**: Move to a paid account and afterward fill in the [intake form](https://aka.ms/facerecognition). Based on the eligibility criteria we will enable the features (after max 10 days).|Azure Video Indexer disables the access face identification, customization and celebrities recognition as of today by default, but gives the option to enable it. <br/><br/>**Recommended**: Fill in the [intake form](https://aka.ms/facerecognition) and based on the eligibility criteria we will enable the features (after max 10 days).|
 
 \*In Brazil South we also disabled the face detection.

articles/frontdoor/scenario-storage-blobs.md

@@ -101,6 +101,8 @@ To use Private Link in this solution, you must deploy the premium tier of Front
 
 To deploy this scenario by using Bicep or JSON ARM templates, [see this quickstart](https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.cdn/front-door-premium-storage-blobs-private-link).
 
+To deploy this scenario by using Terraform, [see this quickstart](https://github.com/Azure/terraform/tree/master/quickstart/101-front-door-premium-storage-blobs-private-link).
+
 ## Next steps
 
 Learn how to [create a Front Door profile](create-front-door-portal.md).