Dynamics 365 Sales

Currently, the functionality to change a component to another component is not implemented. If the relevant section is excluded from export, adding this feature would improve user convenience.

After reviewing the behavior of the “Remove Format” button in the Dynamics 365 rich text editor, we have confirmed that its current design removes only inline-level formatting (such as "span", bold/italic, and inline font-size or font-family), while styles applied directly to block-level elements like "p" tags are not removed.

As a result, when font-family or related styles remain on "p" tags and the email is opened in Outlook, Outlook evaluates fonts on a paragraph-by-paragraph basis. This can cause inconsistent font rendering between paragraphs, even when the content is the same language (for example, Japanese).

While this behavior is understood to be by design, from a user perspective it can be confusing, as using “Remove Format” does not fully normalize the visual appearance.

It would be very helpful to have:

・An option to fully remove font-related information inside "p" tags when “Remove Format” is applied

This would help prevent font inconsistencies when composing emails.

Currently, the model-driven app's bulk edit screen does not provide the functionality to hide or lock specific fields.

We believe that adding this feature would enhance user convenience and further improve operational efficiency.

In Dynamics 365's standard charting functionality, the order of the horizontal axis sometimes does not match the order of the data (the order on the grid or a meaningful order in business context).

Currently, this chart is not designed to match the column order, and the standard functionality does not provide a way to arbitrarily control the order.

However, if the order of important metrics, such as sales data, changes unintentionally, there is a concern that users may misinterpret data trends, potentially impacting decision-making.

Therefore, we would like you to consider providing the following flexible sorting functions for the horizontal axis of the chart:

• Option to match the sorting order of the grid or view

• Sort specification based on any column or condition

• Explicit control of ascending/descending order

These added features will improve the consistency of data visualization, allowing users to understand and analyze information more accurately. As a result, we expect this to lead to improved quality of business decisions and an enhanced user experience.

Currently, when you download a Dataverse data import template, even if your environment contains more than 500 items (fields), not all items will be displayed in the template.

This functionality is not currently provided as a standard feature; therefore, creating a template that includes all fields requires the use of external tools.

Adding a feature to display all items (more than 500 fields) in the data import template will allow users to work without relying on external tools, thus improving user convenience.

Currently, Azure Functions does not provide a standard capability to detect changes in Microsoft Dataverse tables directly, especially in scenarios where polling or outbound-only communication is required.

In many enterprise environments, strict network security policies prohibit inbound communication, making it difficult to adopt event-driven architectures such as Webhooks or Business Events (Dataverse → Azure Functions). As a result, users are unable to implement change detection scenarios using Azure Functions when inbound connectivity is restricted.

If Azure Functions (or Dataverse) could support a standard mechanism for detecting changes via outbound communication (for example, polling with change tracking or a lightweight delta API optimized for Functions), it would significantly improve usability in restricted network environments.

This enhancement would enable:

• Implementation of change detection in environments where inbound communication is not allowed
• Greater flexibility in designing secure, outbound-only integrations
• Simplification of architectures that currently require additional services (e.g., Logic Apps, Power Automate) as intermediaries
• Broader adoption of Azure Functions for enterprise integration scenarios with Dataverse

Currently, users must rely on workarounds or alternative services, which increases complexity and operational overhead. Providing this capability as a standard feature would greatly enhance developer experience and expand supported architecture patterns.

Starting from May 1, the use of model-driven apps embedded in Teams will be restricted/controlled.

As a result, we would like to request the addition of a feature that enables our internal admin users to identify which users are accessing model-driven apps from Teams.

At present, it is not possible to determine this based on available logs or configuration settings, so it will be necessary to consider how to provide effective notifications to admin users.

This request is being posted as a requirement specific to model-driven apps, but in the future, extending this capability to other services (such as canvas apps) and allowing the origin/source information to be identified would also be very effective for internal communication. It would help prevent unexpected interruption/stop of business operations.

In the following Docs that introduce new features in Dynamics 365 Sales, the business value and feature overviews are described in detail. 

However, the prerequisites and setup guidance required to actually try these features are not clearly presented or easy to find.

Docs URL : https://learn.microsoft.com/en-us/copilot/release-plan/2025wave2/copilot-sales/engage-prospects-faster-sales-agent-enriched-leads

Although there are references to other Docs in the Related content section, these typically focus on how to use the features after they have already been configured. 

As a result, users who want to confirm prerequisites, enablement requirements, or configuration steps must independently search for the relevant information across multiple documents.

Additionally, in the Japanese version of the Docs, the document titles listed under Related content are displayed as plain text rather than hyperlinks, which prevents users from navigating directly to the relevant pages.

Docs URL : https://learn.microsoft.com/ja-jp/copilot/release-plan/2025wave2/copilot-sales/engage-prospects-faster-sales-agent-enriched-leads

Because of this, users who want to try new features need to move back and forth between the feature introduction pages and Docs from other areas, such as Copilot or Sales Agent, which significantly increases the effort required to find the necessary information.

If the new feature introduction pages clearly included links to documentation that explains the prerequisites and setup steps, it would significantly improve usability.

For these reasons, I hope that the Dynamics 365 new feature introduction Docs can be improved overall to make them more user-friendly and easier to navigate.

Currently, when clicking the “Email a link” button in Dynamics 365, there is no standard functionality that automatically launches Outlook on the Web.

As a result, when using Outlook on the Web, users must manually copy the record URL from Dynamics 365 and paste it into a new email message in Outlook on the Web.

Therefore, we would like to request the implementation of a feature that enables users to utilize the “Email a link” button in Dynamics 365 when using Outlook on the Web as well.

Implementing this functionality would allow Dynamics 365 information to be used more efficiently in daily operations and would significantly improve overall user convenience.

We have multiple users accessing the same model‑driven app forms that include embedded Power BI reports. These users operate Dynamics 365 in different languages, which are configured through Dynamics personalization and user language settings.

Currently, embedded Power BI reports displayed within Dynamics 365 model‑driven apps determine their language based on the browser language or Power BI service locale, rather than the Dynamics 365 UI language selected by the user. As a result, users viewing the same form see Power BI content in different or unexpected languages, leading to inconsistent user experience and additional operational overhead.

Business Requirement:

We would like embedded Power BI reports to automatically align with the Dynamics 365 UI language selected by the user, instead of relying on browser language settings. This would ensure:

• Consistent multilingual user experience across Dynamics UI and embedded analytics
• Reduced dependency on browser configuration
• Better usability for global organizations with multilingual users
• Improved alignment between Dynamics personalization settings and embedded Power BI behavior

Requested Enhancement:

Provide a supported mechanism (such as a configuration option, parameter, or integration improvement) that allows embedded Power BI reports in model‑driven apps to inherit the user’s Dynamics 365 UI language.

This enhancement would significantly improve usability for organizations operating across multiple regions and languages while using embedded analytics in Dynamics 365.