Merge pull request #9183 from MicrosoftDocs/main

Auto push to live 2025-06-24 10:02:15

Author: Deland-Han

support/azure/automation/runbooks/runbook-job-suspended.md

@@ -0,0 +1,65 @@
+---
+title: Runbook Jobs Get Suspended in Azure Automation
+description: Provides solutions to an issue where runbook jobs are suspended in Azure Automation.
+ms.date: 06/24/2025
+ms.reviewer: adoyle, v-weizhu
+ms.service: azure-automation
+ms.custom: sap:Runbook not working as expected
+---
+# Runbook jobs are suspended in Azure Automation
+
+This article provides solutions to an issue where runbook jobs are suspended in Azure Automation.
+
+> [!NOTE]
+> Azure Automation enables recovery of runbooks deleted in the last 29 days. You can restore the deleted runbook by running a PowerShell script as a job in your Automation account. For more information, see [Restore a deleted runbook](/azure/automation/manage-runbooks#restore-deleted-runbook).
+
+## Symptoms
+
+Runbook jobs might be suspended after three failed start attempts.
+
+## Cause 1: Exceeding memory or network socket limits in an Azure sandbox
+
+- Memory limits
+
+    A job might fail if it uses more than 400 MB of memory.
+- Network socket limits
+
+    An Azure sandbox is limited to 1,000 concurrent network sockets.
+
+For more information, see [Azure Automation limits](/azure/azure-resource-manager/management/azure-subscription-service-limits#azure-automation-limits).
+
+Here are some suggestions for working within memory limits:
+
+- Split the workload among multiple runbooks.
+- Reduce the amount of data processed in memory.
+- Avoid writing unnecessary output from your runbooks.
+- Consider the number of checkpoints written in your PowerShell workflow runbooks.
+
+Here are some actions that can reduce the memory footprint of your runbook during runtime:
+
+- Use the `clear` method, such as `$myVar.clear`, to clear variables.
+- Use the `[GC]::Collect` command to run the garbage collection immediately.
+
+## Cause 2: Module incompatibility
+
+Module dependencies might be incorrect. In this case, your runbook typically returns a "Command not found" or "Cannot bind parameter" error message.
+
+To resolve this issue, [update Azure PowerShell modules in Azure Automation](/azure/automation/automation-update-azure-modules).
+
+## Cause 3: Not authenticated with Microsoft Entra ID in an Azure sandbox
+
+Azure Automation runbooks that attempt to call executables or subprocesses within an Azure sandbox environment can't use Microsoft Authentication Library (MSAL) to authenticate with Microsoft Entra ID.
+
+To resolve this issue, use a managed identity for the Automation account. When you authenticate this runbook with Microsoft Entra ID by using a managed identity, ensure the following things:
+
+- The Microsoft Graph PowerShell module is available in your Automation account.
+- The managed identity is granted the permissions required to execute the runbook automation tasks.
+
+If your runbook can't call an executable or subprocess in an Azure sandbox, run the runbook on a [hybrid worker](/azure/automation/automation-hrw-run-runbooks). Hybrid workers aren't constrained by the memory and network limits of Azure sandboxes.
+
+## References
+
+- [Understand how Azure Resource Manager throttles requests](/azure/azure-resource-manager/management/request-limits-and-throttling)
+- [Troubleshooting API throttling errors](../../virtual-machines/windows/troubleshooting-throttling-errors.md)
+
+[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]

support/azure/automation/toc.yml

@@ -2,6 +2,8 @@
   href: welcome-automation.yml
 - name: Runbook not working as expected
   items:
+  - name: Runbook jobs get suspended
+    href: runbooks/runbook-job-suspended.md
   - name: Troubleshoot runbook execution issues when using PowerShell
     href: runbooks/powershell-job-script-cmdlets-not-working.md
 

support/azure/automation/welcome-automation.yml

@@ -21,6 +21,8 @@ landingContent:
   - title: Runbook not working as expected
     linkLists:
       - linkListType: how-to-guide
-        links:                                                               
+        links:       
+          - text: Runbook jobs get suspended
+            url: runbooks/runbook-job-suspended.md                                                        
           - text: Troubleshoot runbook execution issues when using PowerShell
             url: runbooks/powershell-job-script-cmdlets-not-working.md

support/azure/azure-functions/toc.yml

@@ -1,19 +1,19 @@
 items:
 - name: Welcome
   href: welcome-azure-functions.yml
-- name: Code Deployment
+- name: Application Code Deployment
   items:
     - name: Application issues post deployment
       href: deployment/functions-deploying-runtime-issues-post-deployment.md
-- name: Configuration and Management
+- name: Configuring and Managing Function Apps
   items:
     - name: Migration of runtime/language version
       href: config-mgmt/functions-configuring-updateversion.md
-- name: Creation or Deletion
+- name: Creating or Deleting Function Apps
   items:
     - name: General troubleshooting
       href: creation-deletion/functions-create-or-delete-faq.md
-- name: Monitoring
+- name: Monitoring using Application Insights, Metrics and Alerts
   items:
     - name: Application Insights logs missing or incorrect
       href: monitoring/functions-monitoring-appinsightslogs.md

support/azure/azure-functions/welcome-azure-functions.yml

@@ -9,35 +9,35 @@ metadata:
   ms.topic: landing-page # Required
   author: HaiyingYu  #Required; your GitHub user alias, with correct capitalization.
   ms.author: haiyingyu #Required; microsoft alias of author; optional team alias.
-  ms.date: 04/30/2025
+  ms.date: 06/24/2025
 
 # linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new
 
 landingContent:
 
   # Card
-  - title: Code Deployment
+  - title: Application Code Deployment
     linkLists:
       - linkListType: how-to-guide
         links:
           - text: Application issues post deployment
             url: deployment/functions-deploying-runtime-issues-post-deployment.md
 
-  - title: Configuration and Management
+  - title: Configuring and Managing Function Apps
     linkLists:
       - linkListType: how-to-guide
         links:
           - text: Migration of runtime/language version
             url: config-mgmt/functions-configuring-updateversion.md
 
-  - title: Creation or Deletion
+  - title: Creating or Deleting Function Apps
     linkLists:
       - linkListType: how-to-guide
         links:
           - text: General troubleshooting
             url: creation-deletion/functions-create-or-delete-faq.md
 
-  - title: Monitoring
+  - title: Monitoring using Application Insights, Metrics and Alerts
     linkLists:
       - linkListType: how-to-guide
         links:

support/dynamics-365/supply-chain/procurement/cannot-change-accounting-date.md

@@ -0,0 +1,46 @@
+---
+title: Can't Change Accounting Date or Do a Budget Check
+description: Works around an issue where you can't change the accounting date on a purchase order in Microsoft Dynamics 365 Supply Chain Management.
+ms.reviewer: shubhamshr, ashuaggarwal
+ms.date: 06/24/2025
+ms.custom: sap:Purchase order procurement and sourcing\Issues with purchase orders
+---
+# Can't change the accounting date or perform a budget check on a purchase order
+
+This article provides workarounds for an issue where you can't change the accounting date on a purchase order (PO) due to unjournalized reversing distributions and a closed fiscal period in Dynamics 365 Supply Chain Management.
+
+## Symptoms
+
+When you try to change the accounting date on a PO, you receive the following error message:
+
+> You cannot change the date because reversing distributions that have not yet been journalized still exist. Confirm the current changes before you change the accounting date.
+
+Additionally, the budget check can't be performed because the fiscal period associated with the accounting date isn't within an open fiscal calendar period.
+
+## Cause
+
+This issue occurs because the accounting date on the PO falls within a closed fiscal period. As a result, the accounting distribution can't be reset.
+
+## Workaround
+
+To resolve this issue, use one of the following workarounds:
+
+### Option 1: Cancel and re-create the purchase order
+
+1. [Cancel the PO](/dynamics365/supply-chain/procurement/purchase-order-approval-confirmation#canceling-purchase-orders).
+2. Create a new purchase order with the correct accounting date.
+
+### Option 2: Temporarily open the fiscal period
+
+1. Navigate to **General ledger** > **Calendars** > **Ledger calendars**.
+
+2. Open the relevant fiscal period (for example, 2023 Period 9).
+
+3. Make the necessary changes to the purchase order, such as changing the accounting date or performing a budget check.
+
+4. [Confirm the PO](/dynamics365/supply-chain/procurement/purchase-order-approval-confirmation#confirming-purchase-orders).
+
+5. Set the status of the fiscal period back to **On hold** once the changes are complete.
+
+> [!NOTE]
+> Changing the ledger calendar period is a viable workaround when the accounting date falls in a closed fiscal period. For more information on modifying ledger calendar assignments, see [Change or reassign a ledger calendar](/dynamics365/finance/general-ledger/change-mdfy-clndr-to-ledger).

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

@@ -132,6 +132,8 @@
       href: procurement/vendor-rebate-not-cumulated.md
     - name: A product receipt voucher number is consumed even when not generating a voucher
       href: procurement/voucher-number-consumed.md
+    - name: Can't change accounting date or do a budget check
+      href: procurement/cannot-change-accounting-date.md
     - name: Can't cancel a purchase order within a closed period
       href: procurement/unable-to-cancel-po.md  
     - name: Can't delete a purchase order line after it's confirmed