Merge branch 'main' into Branch-CI4011

Author: AmandaAZ

support/azure/virtual-machines/linux/linux-vm-sshconnectionissue-perms.md

@@ -1,9 +1,9 @@
 ---
 title: SSH connection to Azure Linux VM fails due to permission and ownership issues 
 description: Resolves an issue in which the SSH service fails because the /var/empty/sshd, /var/lib/empty, or /var/run/sshd directory doesn't exist, or it isn't owned by the root user, or it's group-writable or world-writable.
-ms.date: 04/15/2024
-author: saimsh-msft
-ms.reviewer: divargas, adelgadohell
+ms.date: 03/13/2025
+author: pagienge
+ms.reviewer: divargas, adelgadohell, saimsh
 ms.service: azure-virtual-machines
 ms.custom: sap:Cannot connect to my VM, linux-related-content
 ms.collection: linux
@@ -13,15 +13,13 @@ ms.collection: linux
 
 **Applies to:** :heavy_check_mark: Linux VMs
 
-[!INCLUDE [CentOS End Of Life](../../../includes/centos-end-of-life-note.md)]
-
 This article provides solutions to an issue in which connecting to a Linux virtual machine (VM) via Secure Shell (SSH) fails because the _/var/empty/sshd_ directory in RHEL, the _/var/lib/empty_ directory in SUSE, or the _/var/run/sshd_ directory in Ubuntu, doesn't exist, or it isn't owned by the root user, or it's group-writable or world-writable.
 
 ## Symptoms
 
 When you connect to a Linux virtual machine (VM) via SSH, the connection fails. You may receive the following error message about the affected directory, depending on your Linux distribution.
 
-### [RHEL/CentOS](#tab/rhelsymp)
+### [RHEL](#tab/rhelsymp)
 
 ```bash
 sudo tail /var/log/messages
@@ -75,7 +73,7 @@ Here are two methods to repair the VM offline:
 2. Sign in to the VM by using a local administrative account and its corresponding credential or password.
 3. Run the following commands to resolve the permission and ownership issue:
 
-   ### [RHEL/CentOS](#tab/rhelts1)
+   ### [RHEL](#tab/rhelts1)
 
    ```bash
    sudo mkdir -p /var/empty/sshd
@@ -111,7 +109,7 @@ In the Azure portal, open the **Properties** window of the VM to check the agent
 1. Go to the Azure portal, locate your VM settings, and then select **Run Command** under **Operations**.
 2. Execute the following shell script by selecting **RunShellScript** > **Run**:
 
-   ### [RHEL/CentOS](#tab/rhelts2)
+   ### [RHEL](#tab/rhelts2)
 
    ```bash
    #!/bin/bash
@@ -155,12 +153,12 @@ If you can connect to the VM via SSH, and you want to analyze the details of the
 
 Here are two methods to repair the VM offline:
 
-- [Use Azure Linux Auto Repair (ALAR).](#offlinetroubleshooting-repairvm)
+- [Use az vm repair](#offlinetroubleshooting-repairvm)
 - [Use the manual method.](#offlinetroubleshooting-manualvm)
 
-### <a id="offlinetroubleshooting-repairvm"></a>Use Azure Linux Auto Repair (ALAR)
+### <a id="offlinetroubleshooting-repairvm"></a>Use az vm repair
 
-Azure Linux Auto Repair (ALAR) scripts are a part of the VM repair extension described in [Repair a Linux VM by using the Azure Virtual Machine repair commands](repair-linux-vm-using-azure-virtual-machine-repair-commands.md).
+The `az vm repair`, part of the vm-repair extension for the Azure CLI, is described in [Repair a Linux VM by using the Azure Virtual Machine repair commands](repair-linux-vm-using-azure-virtual-machine-repair-commands.md).
 
 Follow these steps to automate the manual offline process:
 
@@ -177,7 +175,7 @@ Follow these steps to automate the manual offline process:
 
 3. Run the following commands to resolve the permission and ownership issues:
 
-   ### [RHEL/CentOS](#tab/rhelts3)
+   ### [RHEL](#tab/rhelts3)
 
    ```bash
    mkdir -p /var/empty/sshd
@@ -210,11 +208,11 @@ Follow these steps to automate the manual offline process:
 
 ### <a id="offlinetroubleshooting-manualvm"></a>Use the manual method
 
-If both the serial console and ALAR approach don't apply to you or fail, the repair has to be performed manually. Follow the steps below to manually attach the OS disk to a recovery VM and swap the OS disk back to the original VM:
+If both the serial console and `az vm repair` approach don't apply to you or fail, the repair has to be performed manually. Follow the steps below to manually attach the OS disk to a recovery VM and swap the OS disk back to the original VM:
 
 - [Attach the OS disk to a recovery VM using the Azure portal.](troubleshoot-recovery-disks-portal-linux.md)
 - [Attach the OS disk to a recovery VM using Azure CLI.](troubleshoot-recovery-disks-linux.md)
 
-Once the OS disk is successfully attached to the recovery VM, follow the detailed [chroot instructions](chroot-environment-linux.md) to mount and chroot to the filesystems of the attached OS disk. Then, follow step 3 in the [Use Azure Linux Auto Repair (ALAR)](#offlinetroubleshooting-repairvm) section to resolve the permission and ownership issues.
+Once the OS disk is successfully attached to the recovery VM, follow the detailed [chroot instructions](chroot-environment-linux.md) to mount and chroot to the filesystems of the attached OS disk. Then, follow step 3 in the [Use az vm repair](#offlinetroubleshooting-repairvm) section to resolve the permission and ownership issues.
 
 [!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]

support/dynamics-365/supply-chain/toc.yml

@@ -352,6 +352,8 @@
       href: warehousing/shipment-confirmed-no-posting.md
     - name: Slotting templates don't consider on-hand inventory for batch-above items
       href: warehousing/slotting-templates-inventory-batch-above.md
+    - name: '"The size of the request xml exceeds the maximum allowed value" in the mobile app'
+      href: warehousing/request-xml-size-exceeds-maximum-allowed-value.md
     - name: The last closed work line must be a put
       href: warehousing/the-last-closed-work-link-must-be-a-put-error.md
     - name: The weight fields on load lines don't match the weight fields on the load

support/dynamics-365/supply-chain/warehousing/request-xml-size-exceeds-maximum-allowed-value.md

@@ -0,0 +1,37 @@
+---
+title: Size of Request XML Exceeds Maximum Allowed Value Error
+description: Resolves the size of the request xml exceeds the maximum allowed value error in the Warehouse Management mobile app.
+ms.date: 03/13/2025
+# ms.search.form:
+audience: Application User
+ms.reviewer: kamaybac, ivanma
+ms.search.region: Global
+ms.author: ivanma
+ms.search.validFrom: 2025-03-03
+ms.dyn365.ops.version: 10.0.39
+ms.custom: sap:Warehouse management
+---
+# "The size of the request xml exceeds the maximum allowed value" error in the Warehouse management mobile app
+
+This article provides a resolution for "The size of the request xml exceeds the maximum allowed value" error that occurs in the [Warehouse Management mobile app](/dynamics365/supply-chain/warehousing/install-configure-warehouse-management-app).
+
+## Symptoms
+
+When you open a [Display open work list](/dynamics365/supply-chain/warehousing/configure-mobile-devices-warehouse#configure-menu-items-for-activities-and-inquiries) mobile device flow in the Warehouse Management mobile app, you might receive the following error message:
+
+> The size of the request xml exceeds the maximum allowed value.
+
+## Cause
+
+The Warehouse Management mobile app communicates with the Dynamics 365 Supply Chain Management service through an XML file. The system has a built-in limit on the size of this XML file. If there are many warehouse work items to be displayed in the Warehouse Management mobile app, the XML file size might exceed this limit.
+
+## Resolution
+
+To resolve this issue, follow these steps to reduce the number of warehouse work items shown in the Warehouse Management mobile app:
+
+1. Open the **Mobile device menu items** form by navigating to **Warehouse management** > **Setup** > **Mobile device** > **Mobile device menu items**.
+1. Find the impacted menu item.
+1. Select the **Edit query** button in the Action Pane.
+1. Edit the query to reduce the number of displayed warehouse work items.
+
+For more information about editing the queries, see [User-configurable queries in Warehouse management](/dynamics365/supply-chain/warehousing/user-configurable-queries-in-warehouse-management).

support/entra/entra-id/app-integration/enable-msal4j-logging-spring-boot-webapp.md

@@ -0,0 +1,89 @@
+---
+title: Enable MSAL4J Logging in a Spring Boot Web Application in Microsoft Entra ID
+description: Discusses how to enable MSAL4J logging in a Spring Boot web application in Microsoft Entra.
+ms.date: 03/10/2025
+ms.author: bachoang
+ms.service: entra-id
+ms.custom: sap:Microsoft Entra App Integration and Development
+---
+
+# Enable MSAL4J logging in a Spring Boot web application
+
+This article provides step-by-step instructions to enable [Microsoft Authentication Library for Java](https://github.com/AzureAD/microsoft-authentication-library-for-java) (MSAL4J) logging by using the [Logback framework](https://logback.qos.ch/) in a Spring Boot web application.
+
+## Code sample
+
+The complete code sample and configuration guide for this implementation are available on [GitHub](https://github.com/bachoang/MSAL4J_SpringBoot_Logging/tree/main/msal-b2c-web-sample).
+
+## Enable MSAL4J logging
+
+1. Add the following dependency to your Pom.xml file to include the Logback framework:
+
+    ```xml
+    <dependency>
+        <groupid>ch.qos.logback</groupid>
+        <artifactid>logback-classic</artifactid>
+        <version>1.2.3</version>
+    </dependency>
+    ```
+
+2. In your app project, create a file in the **src/main/resources** folder, and name the file **Logback.xml**. Then, add the following content:
+
+    ```xml
+    <?xml version="1.0" encoding="UTF-8"?>
+    <configuration>
+        <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
+            <encoder>
+                <pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n</pattern>
+            </encoder>
+        </appender>
+        <root level="debug">
+            <appender-ref ref="STDOUT" />
+        </root>
+    </configuration>
+    ```
+
+    This Appender configuration logs messages to the console. You can adjust the logging level to `error`, `warn`, `info`, or `verbose` based on your preference. For more information, see [LogBack: Appenders](https://logback.qos.ch/manual/appenders.html).
+3. Set the **logging.config** property to the location of the **Logback.xml** file before the main method:
+
+    ```java
+    @SpringBootApplication
+    public class MsalB2CWebSampleApplication {
+    
+    	static { System.setProperty("logging.config", "C:\\Users\\<your path>\\src\\main\\resources\\logback.xml");}
+    	public static void main(String[] args) {
+    		// Console.log("main");
+    		// System.console().printf("hello");
+    		// System.out.printf("Hello %s!%n", "World");
+    		System.out.printf("%s%n", "Hello World");
+    		SpringApplication.run(MsalB2CWebSampleApplication.class, args);
+    	}
+    }
+    ```
+
+## Configuration for running the code sample
+
+### Enable HTTPs support
+
+This code sample is set up to run on the local server (localhost) by using the HTTPS protocol. Follow the steps in [Configure the sample to use your Azure AD B2C tenant](https://github.com/bachoang/MSAL4J_SpringBoot_Logging/tree/main/msal-b2c-web-sample#step-2--configure-the-sample-to-use-your-azure-ad-b2c-tenant) to generate a self-signed certificate. Put the **keystore.p12** file in the resources folder.
+
+### App registration configuration
+
+To configure app registration in Azure AD B2C, follow these steps: 
+
+1. Create two app registrations in your Azure AD B2C tenant: One for the web application and the other for the web API.
+2. Expose the required scope in the web API. For more information, see [Configure web API app scopes](/azure/active-directory-b2c/configure-authentication-sample-web-app-with-api?tabs=visual-studio#step-22-configure-web-api-app-scopes).
+3. Configure the web API scope in the **API Permissions** blade for the web application.
+4. Grant admin consent to all configured permissions in the web application.
+
+For more information, see [Configure authentication in a sample web app that calls a web API by using Azure AD B2C](/azure/active-directory-b2c/configure-authentication-sample-web-app-with-api).
+
+Example configuration:
+
+ :::image type="content" source="media/enable-msal4j-logging-spring-boot-webapp/app-reg.png" alt-text="Diagram that shows configured app registration." border="true" lightbox="media/enable-msal4j-logging-spring-boot-webapp/app-reg.png":::
+
+## Logging output example
+
+If the app is configured correctly, the logging output should resemble the following output.
+
+ :::image type="content" source="media/enable-msal4j-logging-spring-boot-webapp/log-sample.png" alt-text="Diagram that shows logging output." border="true" lightbox="media/enable-msal4j-logging-spring-boot-webapp/log-sample.png":::

support/entra/entra-id/app-integration/media/enable-msal4j-logging-spring-boot-webapp/app-reg.png

@@ -57,6 +57,8 @@
         href: app-integration/troubleshoot-wif10201-no-validkey-securitytoken-mvc.md
       - name: Package Inspector for MSAL Android Native
         href: app-integration/package-inspector-msal-android-native.md
+      - name: Enable MSAL4J logging in a Spring Boot web application
+        href: app-integration/enable-msal4j-logging-spring-boot-webapp.md
 
 
   - name: Troubleshoot adding apps

support/entra/entra-id/app-integration/media/enable-msal4j-logging-spring-boot-webapp/log-sample.png

@@ -2,7 +2,7 @@
 title: Error code occurs when running an attended or unattended desktop flow
 description: Provides mitigation steps for the error codes that occur when running attended or unattended desktop flows.
 ms.reviewer: cefriant, kenseongtan, guco, johndund, alarnaud
-ms.date: 02/11/2025
+ms.date: 03/13/2025
 ms.custom: sap:Desktop flows\Unattended flow runtime errors
 ---
 # Error code occurs when running an attended or unattended desktop flow
@@ -66,3 +66,4 @@ _Original KB number:_   4555406
 |AccountLockedOut|400|Unattended|This error occurs when an internal system policy has prevented an account from creating a session on the machine because of too many sign-in attempts or password change attempts for the account. It's related to an on-premises configuration, not Power Automate licenses. Check that password rotation policies don't interfere with your scheduled runs, causing many incorrect sign-in attempts. If this error occurs regularly, work with your IT administrator to review sign-in attempt logs and account lockout policies.|
 |LogonTypeNotGranted|400|Unattended|For more information, see [troubleshooting documentation for logon type not granted](logon-type-has-not-been-granted.md).|
 |UnallowedTenantForConnectWithSignIn|403|Attended|This error occurs when using a [connect with sign-in](/power-automate/desktop-flows/desktop-flow-connections#connect-with-sign-in-for-attended-runs) connection on an Active Directory (AD) domain-joined machine without adding your tenant to the allowlist. </br> For more information, see ["UnallowedTenantForConnectWithSignIn" error in a Power Automate desktop flow](troubleshoot-unallowed-tenant-for-connect-with-sign-in.md).|
+|MachineNotFound|404|Attended</br>Unattended|This error can occur when the machine is unregistered during a run or if the Dataverse organization has been migrated to a different region. Verify that:</br>- Your machine is still registered by [viewing its status](/power-automate/desktop-flows/manage-machines#view-list-of-machines) in the machine runtime application or the Power Automate portal.</br>- Your [desktop flow connection](/power-automate/desktop-flows/desktop-flow-connections) isn't broken in the Power Automate portal.</br>- [Scripting actions](/power-automate/desktop-flows/actions-reference/scripting) in your flow don't register your machine while the flow is running.|