Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into rolyon-constrained-delegation-ga-release

Author: rolyon

articles/ai-services/document-intelligence/quickstarts/includes/python-sdk.md

@@ -6,7 +6,7 @@ author: laujan
 manager: nitinme
 ms.service: azure-ai-document-intelligence
 ms.topic: include
-ms.date: 12/18/2023
+ms.date: 01/29/2024
 ms.author: lajanuar
 ---
 <!-- markdownlint-disable MD025 -->
@@ -135,11 +135,30 @@ Extract text, selection marks, text styles, table structures, and bounding regio
 import os
 from azure.core.credentials import AzureKeyCredential
 from azure.ai.documentintelligence import DocumentIntelligenceClient
+from azure.ai.documentintelligence.models import AnalyzeResult
 
 # set `<your-endpoint>` and `<your-key>` variables with the values from the Azure portal
 endpoint = "<your-endpoint>"
 key = "<your-key>"
 
+# helper functions
+
+def get_words(page, line):
+    result = []
+    for word in page.words:
+        if _in_span(word, line.spans):
+            result.append(word)
+    return result
+
+
+def _in_span(word, spans):
+    for span in spans:
+        if word.span.offset >= span.offset and (
+            word.span.offset + word.span.length
+        ) <= (span.offset + span.length):
+            return True
+    return False
+
 
 def analyze_layout():
     # sample document
@@ -152,9 +171,10 @@ def analyze_layout():
     poller = document_intelligence_client.begin_analyze_document_from_url(
         "prebuilt-layout", formUrl
     )
-    result = poller.result()
 
-    if any([style.is_handwritten for style in result.styles]):
+    result: AnalyzeResult = poller.result()
+
+    if result.styles and any([style.is_handwritten for style in result.styles]):
         print("Document contains handwritten content")
     else:
         print("Document does not contain handwritten content")
@@ -165,49 +185,53 @@ def analyze_layout():
             f"Page has width: {page.width} and height: {page.height}, measured with unit: {page.unit}"
         )
 
-        for line_idx, line in enumerate(page.lines):
-            words = get_words(page, line)
-            print(
-                f"...Line # {line_idx} has word count {len(words)} and text '{line.content}' "
-                f"within bounding polygon '{line.polygon}'"
-            )
-
-            for word in words:
+        if page.lines:
+            for line_idx, line in enumerate(page.lines):
+                words = get_words(page, line)
                 print(
-                    f"......Word '{word.content}' has a confidence of {word.confidence}"
+                    f"...Line # {line_idx} has word count {len(words)} and text '{line.content}' "
+                    f"within bounding polygon '{line.polygon}'"
                 )
 
-        for selection_mark in page.selection_marks:
-            print(
-                f"Selection mark is '{selection_mark.state}' within bounding polygon "
-                f"'{selection_mark.polygon}' and has a confidence of {selection_mark.confidence}"
-            )
+                for word in words:
+                    print(
+                        f"......Word '{word.content}' has a confidence of {word.confidence}"
+                    )
 
-    for table_idx, table in enumerate(result.tables):
-        print(
-            f"Table # {table_idx} has {table.row_count} rows and "
-            f"{table.column_count} columns"
-        )
-        for region in table.bounding_regions:
-            print(
-                f"Table # {table_idx} location on page: {region.page_number} is {region.polygon}"
-            )
-        for cell in table.cells:
+        if page.selection_marks:
+            for selection_mark in page.selection_marks:
+                print(
+                    f"Selection mark is '{selection_mark.state}' within bounding polygon "
+                    f"'{selection_mark.polygon}' and has a confidence of {selection_mark.confidence}"
+                )
+
+    if result.tables:
+        for table_idx, table in enumerate(result.tables):
             print(
-                f"...Cell[{cell.row_index}][{cell.column_index}] has text '{cell.content}'"
+                f"Table # {table_idx} has {table.row_count} rows and "
+                f"{table.column_count} columns"
             )
-            for region in cell.bounding_regions:
+            if table.bounding_regions:
+                for region in table.bounding_regions:
+                    print(
+                        f"Table # {table_idx} location on page: {region.page_number} is {region.polygon}"
+                    )
+            for cell in table.cells:
                 print(
-                    f"...content on page {region.page_number} is within bounding polygon '{region.polygon}'"
+                    f"...Cell[{cell.row_index}][{cell.column_index}] has text '{cell.content}'"
                 )
+                if cell.bounding_regions:
+                    for region in cell.bounding_regions:
+                        print(
+                            f"...content on page {region.page_number} is within bounding polygon '{region.polygon}'"
+                        )
 
     print("----------------------------------------")
 
 
 if __name__ == "__main__":
     analyze_layout()
 
-
 ```
 
 **Run the application**

articles/azure-monitor/app/convert-classic-resource.md

@@ -329,6 +329,12 @@ No. There's no impact to [Live Metrics](live-stream.md#live-metrics-monitor-and-
 
 To continue with automated exports, you will need to migrate to [diagnostic settings](/previous-versions/azure/azure-monitor/app/continuous-export-diagnostic-setting) before migrating to workspace-based resource.  The diagnostic setting will carry over in the migration to workspace-based Application Insights.
 
+### How do I ensure a successful migration of my App Insights resource using Terraform?
+
+If you are using Terraform to manage your Azure resources, it is important to use the latest version of the Terraform azurerm provider before attempting to upgrade your App Insights resource. Using an older version of the provider, such as version 3.12, may result in the deletion of the classic component before creating the replacement workspace-based Application Insights resource. This can cause the loss of previous data and require updating the configurations in your monitored apps with new connection string and instrumentation key values.
+
+To avoid this issue, make sure to use the latest version of the Terraform [azurerm provider](https://registry.terraform.io/providers/hashicorp/azurerm/latest), version 3.89 or higher, which performs the proper migration steps by issuing the appropriate ARM call to upgrade the App Insights classic resource to a workspace-based resource while preserving all the old data and connection string/instrumentation key values.
+
 ## Troubleshooting
 
 This section offers troubleshooting tips for common issues.

articles/azure-vmware/azure-vmware-solution-known-issues.md

@@ -4,7 +4,7 @@ description: This article provides details about the known issues of Azure VMwar
 ms.topic: reference
 ms.custom: "engagement-fy23"
 ms.service: azure-vmware
-ms.date: 11/28/2023
+ms.date: 1/29/2024
 ---
 
 # Known issues: Azure VMware Solution
@@ -23,6 +23,7 @@ Refer to the table to find details about resolution dates or possible workaround
 | When I build a VMware HCX Service Mesh with the Enterprise license, the Replication Assisted vMotion Migration option isn't available. | 2023  | The default VMware HCX Compute Profile doesn't have the Replication Assisted vMotion Migration option enabled. From the Azure VMware Solution vSphere Client, select the VMware HCX option and edit the default Compute Profile to enable Replication Assisted vMotion Migration. | 2023 |
 | [VMSA-2023-023](https://www.vmware.com/security/advisories/VMSA-2023-0023.html) VMware vCenter Server Out-of-Bounds Write Vulnerability (CVE-2023-34048) publicized in October 2023 | October 2023  | Microsoft is currently working with its security teams and partners to evaluate the risk to Azure VMware Solution and its customers. Initial investigations show that controls in place within Azure VMware Solution reduce the risk of CVE-2023-03048. However Microsoft is working on a plan to roll out security fixes soon to completely remediate the security vulnerability. | October 2023 |
 | The AV64 SKU currently supports RAID-1 FTT1, RAID-5 FTT1, and RAID-1 FTT2 vSAN storage policies. For more information, see [AV64 supported RAID configuration](introduction.md#av64-supported-raid-configuration) | Nov 2023 | Use AV36, AV36P, or AV52 SKUs when RAID-6 FTT2 or RAID-1 FTT3 storage policies are needed. | N/A |
+| VMware HCX version 4.8.0 Network Extension (NE) Appliance VMs running in High Availability (HA) mode may experience intermittent Standby to Active failover. For more information, see [HCX - NE appliances in HA mode experience intermittent failover (96352)](https://kb.vmware.com/s/article/96352) | Jan 2024 | Avoid upgrading to VMware HCX 4.8.0 if you are using NE appliances in a HA configuration. | N/A |
 
 In this article, you learned about the current known issues with the Azure VMware Solution.
 

articles/confidential-computing/choose-confidential-containers-offerings.md

@@ -2,7 +2,8 @@
 title: Choose container offerings for confidential computing
 description: How to choose the right confidential container offerings to meet your security, isolation and developer needs.
 author: angarg05
-ms.service: container-service
+ms.service: virtual-machines
+ms.subservice: confidential-computing
 ms.topic: conceptual
 ms.date: 11/01/2021
 ms.author: ananyagarg

articles/container-registry/container-registry-tasks-overview.md

@@ -16,7 +16,8 @@ Containers provide new levels of virtualization, isolating application and devel
 
 **ACR Tasks** is a suite of features within Azure Container Registry. It provides cloud-based container image building for [platforms](#image-platforms) including Linux, Windows, and ARM, and can automate [OS and framework patching](#automate-os-and-framework-patching) for your Docker containers. ACR Tasks not only extends your "inner-loop" development cycle to the cloud with on-demand container image builds, but also enables automated builds triggered by source code updates, updates to a container's base image, or timers. For example, with base image update triggers, you can automate your OS and application framework patching workflow, maintaining secure environments while adhering to the principles of immutable containers.
 
-ACR is temporarily pausing ACR Tasks runs from Azure free credits. This may affect existing Tasks runs. If you encounter problems, open a [support case](../azure-portal/supportability/how-to-create-azure-support-request.md) for our team to provide additional guidance. We'll remove this note when this pause is lifted.
+>[! IMPORTANT]
+> ACR is temporarily pausing ACR Tasks runs from Azure free credits. This may affect existing Tasks runs. If you encounter problems, open a [support case](../azure-portal/supportability/how-to-create-azure-support-request.md) for our team to provide additional guidance. Please note that existing customers will not be affected by this pause. We will update our documentation notice here whenever the pause is lifted.
 
 ## Task scenarios