When a known issue is found in the Lifecycle Services (LCS) Issue search tool with an "open" status and no available hotfix, it signifies that Microsoft is aware of the bug but has not yet released a fix. The official and recommended procedure is to submit a support ticket. This action formally registers that your organization is impacted by the issue. Submitting a ticket helps Microsoft gauge the widespread impact of the bug, which can influence the priority of developing and releasing a hotfix. It also opens a direct line of communication with Microsoft Support for potential workarounds and status updates.

A. Update to the latest platform version.

This is not the correct first step because the issue explicitly states no hotfix is attached, meaning a fix is likely not included in the latest version.

C. Pause updates.

Pausing updates is a preventative measure to delay future updates. It does not address an existing bug and would prevent the automatic application of the fix once it is released.

1. Microsoft Learn. (2023). Issue search in Lifecycle Services (LCS). In the "Search for issues and view the results" section, the documentation states, "If you're affected by an issue, we recommend that you submit a support ticket to the Microsoft Support team." This directly supports logging a ticket as the recommended action when an issue is found.

Source: Microsoft Docs, https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/lifecycle-services/issue-search-lcs

2. Microsoft Learn. (2023). Get support for finance and operations apps or Lifecycle Services (LCS). This document outlines the official process for obtaining support. The "Submit a support request" section details how to report an issue to Microsoft to get it investigated and resolved, which is the situation described in the question.

Source: Microsoft Docs, https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/lifecycle-services/lcs-support

3. Microsoft Learn. (2023). Pause service updates through Lifecycle Services (LCS). This document explains that pausing updates is intended to provide a window to "validate customizations and business processes" before a mandatory update. It is a feature for managing the update cadence, not for resolving existing product bugs.

Source: Microsoft Docs, https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/lifecycle-services/pause-service-updates