Merge branch 'main' into Branch-CI3606

Author: v-phoebh

.openpublishing.redirection.json

@@ -12880,6 +12880,22 @@
       "source_path": "support/power-platform/dataverse/d365-app-outlook/error-when-installing-crm-2016-outlook.md",
       "redirect_url": "/previous-versions/troubleshoot/dynamics/crm/error-when-installing-crm-2016-outlook"
     },
+    {
+      "source_path": "support/power-platform/dataverse/d365-app-outlook/something-went-wrong-during-sign-in.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/something-went-wrong-during-sign"
+    },
+    {
+      "source_path": "support/power-platform/dataverse/d365-app-outlook/you-do-not-have-required-role-privilege.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/you-do-not-have-the-required-role-or-privilege-to-complete-this-action-error"
+    }, 
+    {
+      "source_path": "support/power-platform/dataverse/d365-app-outlook/we-cannot-load-this-app.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/error-when-opening-365-app-outlook"
+    },   
+    {
+      "source_path": "support/power-platform/dataverse/d365-app-outlook/error-incomingemailrejected-install-dynamics-365-app-outlook.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/error-install-dynamics-365-app-outlook"
+    },
     {
       "source_path": "support/power-platform/dataverse/d365-app-outlook/current-user-role-not-have-required-permissions.md",
       "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/privilege-error-occurs-when-using-dynamics-365-app-for-outlook"

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/asset-management/conversion-of-maintenance-schedule-to-workorder-is-failing.md

@@ -0,0 +1,42 @@
+---
+title: Conversion of Maintenance Schedule to Work Orders Fails
+description: Solves the errors that prevent you from creating work orders based on maintenance schedule in Microsoft Dynamics 365 Supply Chain Management.
+author: sorenbacker2
+ms.author: sorenba
+ms.date: 03/14/2025
+ms.custom: sap:Asset management\Issues with asset management
+---
+# Can't create work orders based on your maintenance schedule
+
+This article provides the setup steps to ensure the conversion of maintenance schedule lines to work orders doesn't fail due to errors related to number sequence setup in Microsoft Dynamics 365 Supply Chain Management.
+
+## Symptoms
+
+When you try to create work orders for the selected schedule items selected using the [Open maintenance schedule lines](/dynamics365/supply-chain/asset-management/preventive-and-reactive-maintenance/creating-work-orders#create-work-orders-based-on-your-maintenance-schedule) in **Asset Management**, you receive the following error message after selecting **OK** in the **Create work orders** dialog.
+
+> Number sequence \<Number sequence> has been exceeded.  
+> Number selection is canceled.
+
+## Cause
+
+This issue is caused by the setup of a number sequence. Specifically, the actual number sequence exceeds the configured range of the work order number sequence.
+
+## Resolution
+
+To resolve the issue and ensure the successful conversion of maintenance schedule lines to work orders, follow these steps to properly set up the number sequence:
+
+1. Go to **Asset management module** > **Setup** > **Asset management parameters**.
+2. Select the **Number sequences** FastTab.
+3. Select **Work order** in the **Reference** column, and then select the corresponding link in the **Number sequence code** column.
+
+4. Go to the **Segments** FastTab. Find the line where the **Segment** column equals *Alphanumeric*. Ensure the corresponding field in the **Value** column has enough hash tags to match the desired length of the variable numeric part of the work order number sequence.
+
+5. Go to the **General** FastTab. In the **Number allocation** field group, ensure that the **Largest** number matches (but is included in) the length of the variable numeric part of the work order number sequence set earlier. In other words, if the alphanumeric value from step 4 equals *######*, the largest number can be set as *999999*. Also, ensure that the number in the **Next** field is included in the range of the number sequence mentioned in steps 4 and 5.
+
+6. Select **Save** to save the changes to the number sequence.
+
+By configuring the work order number sequence correctly, the conversion of maintenance schedule lines to work orders can proceed without being blocked by an error.
+
+## More information
+
+[Set up number sequences on an individual basis](/dynamics365/fin-ops-core/fin-ops/organization-administration/tasks/set-up-number-sequences-individual-basis)

support/dynamics-365/supply-chain/procurement/purchase-requisitions-cannot-released.md

@@ -0,0 +1,52 @@
+---
+title: Purchase Requisitions Can't Be Released
+description: Works around an issue where PRs created before the current fiscal year can't be released in Dynamics 365 Finance and Dynamics 365 Supply Chain Management.
+author: Shubhs93
+ms.author: shubhamshr
+ms.reviewer: shubhamshr
+ms.search.form: PurchTable, PurchTablePart, PurchRFQTable
+audience: Application User
+ms.search.region: Global
+ms.custom: sap:Purchase order procurement and sourcing\Issues with purchase orders
+ms.date: 03/14/2025
+---
+
+# Purchase requisitions created before the current fiscal year can't be released
+
+This article provides workarounds for an issue where purchase requisitions created before the current fiscal year can't be released in Dynamics 365 Finance and Dynamics 365 Supply Chain Management.
+
+## Symptoms
+
+When you try to convert a purchase requisition (PR) submitted at the end of one fiscal year and approved in a new fiscal year into a purchase order (PO) in Dynamics 365 Finance and Dynamics 365 Supply Chain Management, you might receive the following error message:
+
+> Purchase requisition line was pre-encumbered in a fiscal year that is different from the accounting date of the purchase order. Hence, purchase order cannot be created.
+
+## Cause 1: Pre-encumbrance issue
+
+When a PR is [approved](/dynamics365/supply-chain/procurement/purchase-requisitions-overview#purchase-requisition-header-and-line-status-relationships), it creates [a pre-encumbrance to reserve budget funds](/dynamics365/supply-chain/procurement/purchase-requisitions-overview#consolidating-purchase-requisition-lines). If the requisition was submitted in the previous fiscal year, the pre-encumbrance is tied to that year's budget. The system detects a mismatch when converting the PR into a PO in the new fiscal year because the pre-encumbrance belongs to the old fiscal year, but the PO is created in the new fiscal year.
+
+## Cause 2: No PR rollover functionality
+
+Dynamics 365 doesn't support PR rollovers across fiscal years. If a PR remains open at year-end, it can't be carried over automatically into the new fiscal year. This restriction ensures that budgets and financial commitments remain aligned with fiscal year policies.
+
+## Workaround
+
+The best practice is to either cancel open PRs at year-end or convert them into POs before the fiscal year closes. This ensures smooth procurement processing without encountering fiscal year mismatches. Since Dynamics 365 doesn't support PR rollovers, organizations should proactively manage requisitions as part of their year-end closing procedures.
+
+- Method 1: Cancel open PRs at year-end
+   1. Identify all open PRs before the fiscal year-end closing.
+   1. Cancel any unapproved or pending PRs that haven't been converted into POs.
+   1. Create new PRs in the new fiscal year, ensuring they align with the correct budget year.
+
+  This method avoids the issue by ensuring that new requisitions are processed within the correct fiscal period.
+
+- Method 2: Convert PRs into POs before fiscal year-end and roll over POs
+   1. Convert open PRs into POs before the fiscal year closes.
+   1. If a PO needs to be received or invoiced in the new fiscal year, use the rollover functionality of POs.
+
+   This method ensures that financial commitments are properly managed across fiscal years.
+
+## More information
+
+- [Select purchase orders and run the purchase order year-end process](/previous-versions/dynamicsax-2012/appuser-itpro/process-purchase-orders-at-year-end#select-purchase-orders-and-run-the-purchase-order-year-end-process)
+- [Purchase order year-end close](/dynamics365/finance/budgeting/purchase-order-year-end-process)

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

@@ -6,6 +6,8 @@
       href: asset-management/asset-id-not-editable-when-number-sequence-is-manual.md
     - name: Changing work order lifecycle state doesn't generate fault cause or fault remedy error
       href: asset-management/change-lifecycle-state-doesnt-create-fault.md
+    - name: Can't create work orders based on your maintenance schedule
+      href: asset-management/conversion-of-maintenance-schedule-to-workorder-is-failing.md  
 - name: Inventory costing and closing
   items:
     - name: An update conflict occurs when the inventory valuation method is either standard cost or moving average
@@ -146,6 +148,8 @@
       href: procurement/object-reference-not-set.md
     - name: Imported purchase orders show incorrect line numbers
       href: procurement/line-number-increments.md
+    - name: Purchase requisitions created before the current fiscal year can't be released
+      href: procurement/purchase-requisitions-cannot-released.md
     - name: Purchase order line data discrepancies
       href: procurement/purchase-order-line-data-issues.md
     - name: Purchase orders don't reflect the language settings of the legal entity
@@ -352,6 +356,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).