-
Read audit logs retention policy and tagging option
It would be useful to tag D365 related read logs while exporting them (automatically) to O365 security and compliance center. Also possibility to retain those logs for longer than just 90 days would be beneficial.
-
Allow for creation of form fields that are not mapped to a lead or contact record / RTM
We still would like to have the option to use custom fields not tied to contact (nor lead) related to form itself and often to the event. Please reconsider this!
This was originally here in the idea called: "Non-mapped form fields" and now we are getting more and more comments that we still need it despite your documentation of "no need". Please reconsider!
-
Automating sharing of Projects related to Customer Voice
We would like to use Power Automate flow to share every newly created project to certain user (or service account).
Unfortunately currently with the Customer Voice connector in Power Automate you cannot share projects. There are only two actions that can be done with the Customer Voice connector and those are "Create an invitation" and "Send a survey"
By sharing the project automatically with the "backup-user" or service account we ensure Projects don't get orphaned if the original Project Owner leaves the organization and hasn't shared the Project manually from the Customer Voice UI.
-
Copilot for Customer Voice
We should have similar functionality creating surveys like we have now in Forms using Draft with Copilot -feature
"Describe what form you'd like to create, including its context, purpose,. inteded audience and any specific requirements to be considered.
And then some example prompts like "Draft an in-take form for a fitness center to collect..."
-
Sharing Copilot Agent
You know, there is a simple share button that users can use to give others access to the Copilot Agent. Easy thing and IT loves the simplicity (/sarcasm).
We’ve heard numerous concerns regarding sharing these Copilot Agents. Many organizations haven’t had enough time to understand what they are and how to govern them. So, my colleague took a long journey and went through all the options and did practical testing with several different type of user accounts in our Lab tenant.
We were surprised how many bits and pieces there was and it took several days go through all of them.
- Sharing the Copilot Studio Agent Builder agent in BizChat is simple and straightforward, but the agent's capabilities and sharing controls are limited.
- Sharing Copilot Studio extension for M365 Copilot has more capabilities, and different controls and settings are available.
Our urgent ask for Microsoft is a tool to monitor all different types of agents. We want to see what our users have created, how much they are used, and where the agents are connected.
Credits for this idea goes to my colleague Mikko K!
-
Make Copilot for Sales available in Outlook Mobile
It would be beneficial to have Copilot for Sales functionality available in Outlook Mobile like it's in new Outlook and Outlook OWA.
-
Support for Entra ID security groups in Customer Insights Data
Like in the CIJ side and also other CE apps / Power Platform environments it would be super useful from the security and governance perspective if CID could support Entra ID security groups and not just individual users from Entra ID.
-
Using Customer Insights Data Segments as part of the segment definition on Customer Insights Journeys side
All the created CID segments are nicely visible in CIJ RTM side but you cannot use them as basis for other segments. When you have some external data on CID side and you create a segment there, it would be really useful to be able to use that segment of accounts (for example) connected to actual contacts and then leverage that in journeys.
With the current setup you take all your data into CID side and create segments there (where the segment builder is far from user-friendly compared to CIJ segment builder experience).