Shin N

Currently, the Email Engagement feature only tracks email interactions when the primary recipient is an activity party such as a Contact, Account, or Lead. However, internal users (User entity) added in the CC field are not tracked, which limits visibility into internal collaboration and communication.

This idea proposes enhancing Email Engagement to support tracking when internal users are included in the CC field. Since customers often use the CC field to share emails with internal stakeholders, enabling tracking for the User entity in CC would ensure more comprehensive engagement analytics and better alignment with real-world email usage patterns.

The D365 App for Outlook does not support tracking an externally organized, recurring meeting at this time being and have to use workaround to archive the outcome.

Work around: You have to open the meeting from the Calendar first, then track from the meeting.

Target outcome: Automatically tracking incoming meeting invites.

It is currently not able to change the session name for entity-based sessions. The default name is the value of the record, which can get confusing when there are a lot of sessions from different entities are opened, we are unable to differentiate which session is from which entity. 

Targeted Result

Provide an option in Copilot Studio to remove, archive, or hide unused managed agents (such as Sales Qualification agents) so that the agent list and dashboard view are cleaner and easier to manage.

Actual Result

Currently, unused or managed Sales Qualification agents cannot be removed or hidden. As a result, all agents remain visible in the Copilot Studio view, which causes the interface to become cluttered, especially in environments with multiple agents.

Justification / Business Impact

As the number of agents grows, the Copilot Studio dashboard becomes increasingly difficult to navigate. Allowing users to hide or archive unused agents would:

• Improve overall usability and readability of the dashboard
• Reduce visual clutter in environments with many agents
• Help administrators and makers focus on actively used agents
• Improve day‑to‑day management efficiency

This enhancement would significantly improve the Copilot Studio management experience without impacting existing agent functionality.

Problem Statement

==============================

In the current experience, the Subgrid ribbon includes a “See All Records” button, which is very useful in many scenarios. However, some customers have business or security requirements where users should not be able to view all associated records.

At this time, there is no supported customization option to hide or control the visibility of this button, which limits flexibility in meeting different business needs.

Current Behavior

==============================

• The “See All Records” button is always visible on the subgrid ribbon.
• There is no configuration or customization option to hide or restrict this button based on role, form, or business requirement.
• Some users are able to see more associated records than intended.

Expected Behavior

==============================

Administrators should have the ability to customize or hide the “See All Records” button on subgrids.

This could be controlled via:

• Security roles
• Form configuration
• Command bar / ribbon customization

This would allow organizations to better align the UI with their business, security, and data compliance requirements.

Business Impact

==============================

• Improves control over data visibility
• Helps meet security and compliance requirements
• Reduces user confusion by limiting access to unnecessary or restricted records
• Increases flexibility and adoption for organizations with strict business rules

Idea Description

Customer Voice currently tracks survey response consumption only at the tenant-wide level, with no built-in capability to break down usage across projects or business units.

This creates challenges for organizations managing multiple projects under the same tenant, where each project belongs to different environments and is owned by different departments with separate budgets.

Scenario

We have multiple Customer Voice projects within the same tenant, each tied to different environments and Business Units. Although survey responses are consumed at the tenant level, costs need to be tracked and allocated per project and department.

We need visibility into survey response usage:

1. Across projects (e.g., Project A vs Project B)
2. Within a project by Business Units (e.g., BU A vs BU B)

Impact

• Lack of transparency for cost allocation and budgeting
• Difficulty tracking usage across departments
• Reliance on manual or unsupported workarounds

Suggested Enhancement

Introduce built-in reporting to provide survey response usage breakdown by:

• Project
• Survey
• Business Unit / owner