Merge pull request #253370 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: v-alje

articles/active-directory/governance/how-to-lifecycle-workflow-sync-attributes.md

@@ -31,10 +31,10 @@ The following table shows the scheduling (trigger) relevant attributes and the m
 > [!NOTE]
 > Manually setting the employeeLeaveDateTime for cloud-only users requires special permissions. For more information, see: [Configure the employeeLeaveDateTime property for a user](/graph/tutorial-lifecycle-workflows-set-employeeleavedatetime)
 
-This document explains how to set up synchronization from on-premises Microsoft Entra Connect cloud sync and Microsoft Entra Connect for the required attributes.
+This document explains how to set up synchronization from on-premises Microsoft Entra Connect cloud sync or Microsoft Entra Connect for the required attributes.
 
 >[!NOTE]
-> There's no corresponding EmployeeHireDate or EmployeeLeaveDateTime attribute in Active Directory. If you're importing from on-premises AD, you'll need to identify an attribute in AD that can be used. This attribute must be a string.
+> There's no corresponding EmployeeHireDate or EmployeeLeaveDateTime attribute in Active Directory. If you're synchronizing from on-premises AD, you'll need to identify an attribute in AD that can be used. This attribute must be a string.
 
 
 ## Understanding EmployeeHireDate and EmployeeLeaveDateTime formatting
@@ -173,7 +173,7 @@ To update this mapping, you'd do the following:
 1.  Add your source attribute(s) created as Type String, and select on the CheckBox for required.
     :::image type="content" source="media/how-to-lifecycle-workflow-sync-attributes/edit-attribute-list.png" alt-text="Screenshot of source api list.":::
     > [!NOTE]
-    > The number, and name, of source attributes added will depend on which attributes you are syncing.
+    > The number, and name, of source attributes added will depend on which attributes you are syncing from Active Directory.
 1.  Select Save. 
 
 1. From there you must map the HRM attributes to the added Active Directory attributes. To do this, Add New Mapping using an Expression. 

articles/azure-monitor/containers/container-insights-logging-v2.md

@@ -101,9 +101,29 @@ This applies to the scenario where you have already enabled container insights f
 >* The configuration change can take a few minutes to complete before it takes effect. All ama-logs pods in the cluster will restart. 
 >* The restart is a rolling restart for all ama-logs pods. It won't restart all of them at the same time.
 
-## Multi-line logging in Container Insights (preview)
+## Multi-line logging in Container Insights
 Azure Monitor container insights now supports multiline logging. With this feature enabled, previously split container logs are stitched together and sent as single entries to the ContainerLogV2 table. Customers are able see container log lines upto to 64 KB (up from the existing 16 KB limit). If the stitched log line is larger than 64 KB, it gets truncated due to Log Analytics limits. 
-Additionally, the feature also adds support for .NET and Go stack traces, which appear as single entries instead of being split into multiple entries in ContainerLogV2 table. 
+Additionally, the feature also adds support for .NET, Go, Python and Java stack traces, which appear as single entries instead of being split into multiple entries in ContainerLogV2 table.
+
+Below are two screenshots which demonstrate Multi-line logging at work for Go exception stack trace:
+
+Multi-line logging disabled scenario:
+
+![Screenshot that shows Multi-line logging disabled.](./media/container-insights-logging-v2/multi-line-disabled-go.png)
+
+Multi-line logging enabled scenario:
+
+[ ![Screenshot that shows Multi-line enabled.](./media/container-insights-logging-v2/multi-line-enabled-go.png) ](./media/container-insights-logging-v2/multi-line-enabled-go.png#lightbox)
+
+Similarly, below screenshots depict Multi-line logging enabled scenarios for Java and Python stack traces:
+
+For Java:
+
+[ ![Screenshot that shows Multi-line enabled for Java](./media/container-insights-logging-v2/multi-line-enabled-java.png) ](./media/container-insights-logging-v2/multi-line-enabled-java.png#lightbox)
+
+For Python:
+
+[ ![Screenshot that shows Multi-line enabled for Python](./media/container-insights-logging-v2/multi-line-enabled-python.png) ](./media/container-insights-logging-v2/multi-line-enabled-python.png#lightbox)
 
 ### Pre-requisites 
 
@@ -116,7 +136,7 @@ Multi-line logging is a preview feature and can be enabled by setting **enabled*
 [log_collection_settings.enable_multiline_logs]
 # fluent-bit based multiline log collection for go (stacktrace), dotnet (stacktrace)
 # if enabled will also stitch together container logs split by docker/cri due to size limits(16KB per log line)
-enabled = "true"
+  enabled = "true"
 ```
 
 ## Next steps

articles/azure-monitor/containers/media/container-insights-logging-v2/multi-line-disabled-go.png

@@ -162,7 +162,6 @@ This section shows you how to create a .NET Core console application to send eve
         {
             // if it is too large for the batch
             throw new Exception($"Event {i} is too large for the batch and cannot be sent.");
-            Console.ReadLine();
         }
     }
     

articles/azure-monitor/containers/media/container-insights-logging-v2/multi-line-enabled-go.png

@@ -19,7 +19,7 @@ With managed disks, you don't have to worry about managing storage accounts for
 
 ## How does this affect me?
 
-- As of September 30, 2023, new customers won't be able to create unmanaged disks.
+- As of January 30, 2024, new customers won't be able to create unmanaged disks.
 - On September 30, 2025, customers will no longer be able to start IaaS VMs by using unmanaged disks. Any VMs that are still running or allocated will be stopped and deallocated.
 
 ## What is being retired?