-
Break Down of RelevanceSearch (Dataverse Search) table
It would be nice to have an option to break down the storage consumption of the RelevanceSearch table (known as Dataverse Search). This way it can be determined which entities/columns selected are consuming the most space and be able to take informed decisions on which ones to disable, to effectively and efficiently free up storage space, when required.
-
Dataverse for Teams environment Notifications Modification
We would like to have the ability to limit, change or update the contacts/users that receive notifications on Dataverse for Teams deletion actions. Some end users/Team owners receive these notifications, that may have used an app to test its functionality and may not be aware of Dataverse or what it is used for.
So, having the ability to change/modify the notifications that are sent out or limit them to Admins only would make it easier to manage user expectations or concerns regarding these notification emails.
-
Additional Info/Details on Dataverse for Teams, within Teams for end users
It would be useful to have a notice/warning when end users are deploying an app/solution that would subsequently create a Dataverse for Teams environment. This way end users' awareness of the environment increases, and notifications sent out for an environment they may have provisioned based on an app/solution they were testing/using in Teams, are a lot clearer for users when they receive the notifications.
This can be when the app/solutions are being installed/used, or even on the notification emails sent for Dataverse for Teams environments.
Overview documentation on what the Dataverse for Teams environments are, and how to manage them if they are Team owners.
Like these articles:
About the Microsoft Dataverse for Teams environment - Power Platform | Microsoft Learn
Automatic cleanup of inactive environments - Power Platform | Microsoft Learn