Merge pull request #273043 from MicrosoftDocs/main

Publish to live, Tuesday 4 AM PST, 4/23

Author: ttorble

articles/aks/concepts-network.md

@@ -98,7 +98,7 @@ For more information, see [Configure Azure CNI for an AKS cluster][aks-configure
 
 [Azure CNI Powered by Cilium][azure-cni-powered-by-cilium] uses [Cilium](https://cilium.io) to provide high-performance networking, observability, and network policy enforcement. It integrates natively with [Azure CNI Overlay][azure-cni-overlay] for scalable IP address management (IPAM).
 
-Additionally, Cilium enforces network policies by default, without requiring a separate network policy engine. Azure CNI Powered by Cilium can scale beyond [Azure Network Policy Manager's limits of 250 nodes / 20-K pod][use-network-policies] by using ePBF programs and a more efficient API object structure.
+Additionally, Cilium enforces network policies by default, without requiring a separate network policy engine. Azure CNI Powered by Cilium can scale beyond [Azure Network Policy Manager's limits of 250 nodes / 20-K pod][use-network-policies] by using eBPF programs and a more efficient API object structure.
 
 Azure CNI Powered by Cilium is the recommended option for clusters that require network policy enforcement.
 

articles/automation/troubleshoot/managed-identity.md

@@ -3,14 +3,29 @@ title: Troubleshoot Azure Automation managed identity issues
 description: This article tells how to troubleshoot and resolve issues when using a managed identity with an Automation account.
 services: automation
 ms.subservice:
-ms.date: 10/26/2021
+ms.date: 04/22/2024
 ms.topic: troubleshooting
 ---
 
 # Troubleshoot Azure Automation managed identity issues
 
 This article discusses solutions to problems that you might encounter when you use a managed identity with your Automation account. For general information about using managed identity with Automation accounts, see [Azure Automation account authentication overview](../automation-security-overview.md#managed-identities).
 
+
+## Scenario: Runbook with system assigned managed identity fails with 400 error message
+
+### Issue
+
+Runbook with system assigned managed identity fails with the error as `unable to acquire for tenant organizations with error ManagedIdentityCredential authentication failed. Managed System Identity not found! Status 400 (Bad Request)`
+
+
+### Cause
+You haven't assigned permissions after creating the system-assigned managed identity. 
+
+### Resolution
+Ensure to assign the appropriate permissions for system-assigned managed identity. [Using a system-assigned managed identity for an Azure Automation account](../enable-managed-identity-for-automation.md)
+
+
 ## Scenario: Managed Identity in a Runbook cannot authenticate against Azure
 
 ### Issue

articles/hdinsight-aks/flink/media/use-flink-delta-connector/app-mode-jar.png

@@ -3,7 +3,7 @@ title: How to use Apache Flink® on HDInsight on AKS with Flink/Delta connector
 description: Learn how to use Flink/Delta Connector.
 ms.service: hdinsight-aks
 ms.topic: how-to
-ms.date: 04/10/2024
+ms.date: 04/22/2024
 ---
 
 # How to use Flink/Delta Connector
@@ -316,19 +316,26 @@ public class DeltaSourceExample {
     </build>
 </project>
 ```
+
 ## Package the jar and submit it to Flink cluster to run
 
-### Submit the jar on WebSSH pod
+1. Upload the jar to ABFS.
+    :::image type="content" source="./media/use-flink-delta-connector/app-mode-jar.png" alt-text="Screenshot showing App mode jar files." lightbox="./media/use-flink-delta-connector/app-mode-jar.png":::
+
+1. Pass the job jar information in AppMode cluster.
+
+    :::image type="content" source="./media/use-flink-delta-connector/cluster-configuration.png" alt-text="Screenshot showing cluster configuration." lightbox="./media/use-flink-delta-connector/cluster-configuration.png":::
+
+1. Enable `hadoop.classpath.enable`.
 
-:::image type="content" source="./media/use-flink-delta-connector/webssh-pod.png" alt-text="Screenshot showing how to submit the jar on WebSSH pod." lightbox="./media/use-flink-delta-connector/webssh-pod.png":::
+1. Submit the cluster, you should be able to see the job in Flink UI.
 
-### Check Job on Flink UI
+    :::image type="content" source="./media/use-flink-delta-connector/flink-dashboard.png" alt-text="Screenshot showing Flink dashboard." lightbox="./media/use-flink-delta-connector/flink-dashboard.png":::
 
-:::image type="content" source="./media/use-flink-delta-connector/check-job-on-flink-ui.png" alt-text="Screenshot showing how to check the job on Flink UI." lightbox="./media/use-flink-delta-connector/check-job-on-flink-ui.png":::
+1. Find Results in ADLS.
 
-### Check the delta output on Azure portal
+    :::image type="content" source="./media/use-flink-delta-connector/output.png" alt-text="Screenshot showing the output." lightbox="./media/use-flink-delta-connector/output.png":::
 
-:::image type="content" source="./media/use-flink-delta-connector/delta-output.png" alt-text="Screenshot showing the delta output." lightbox="./media/use-flink-delta-connector/delta-output.png":::
 
 ## Power BI integration