Dataverse Long Term Retention

Intercompany and Direct Delivery orders are significantly contributing to the growth of customer's database, leading to usage overruns beyond the threshold.

Currently, there is no functionality to archive or clean up these types of orders, which limits customer's ability to manage database size effectively.

To address this, a propose developing a feature that allows for the archiving or clean-up of Intercompany and Direct Delivery orders. This feature should include criteria for archiving orders, such as orders older than a certain date or orders that have been fully processed and closed alongside the Inventory archival and not being allowed for data archival with intercompany chain linked to sales orders.

Additionally, an automated process should be implemented to periodically archive orders based on the defined criteria, along with a manual archiving option for users. It is also essential to ensure that archived orders can be easily retrieved if necessary for auditing or reference purposes.

Furthermore, a clean-up function may be developed to remove unnecessary data from the database, reducing its size and improving performance.

Implementing this archiving and clean-up function will help manage database growth, improve system performance, and ensure compliance with data retention policies.

However, it is important to note that addressing this issue will require additional resources and an increase in system resource requirements.

The impact of this issue is particularly significant for retail operations, where efficient database management is crucial for smooth functioning.

Background & Challenge:

In the current data management landscape, many organizations leverage Azure Data Lake for data storage and analytics. However, they often encounter a significant challenge in the process of integrating data, particularly when using managed tables that are not customizable. A key issue is the absence of a "track changes" feature in these tables. This feature is crucial for synchronizing data via Microsoft tools like Power Apps - Synapse Linked are involved in the data pipeline. Without the ability to track changes by default, users must implement workarounds, leading to increased complexity, risk of data inconsistency, and potential delays in data availability. This limitation hinders the agility and effectiveness of data-driven decision-making processes.

Idea Description: AutoTrack

The proposed solution, "AutoTrack," is designed to address this gap by setting the "track changes" feature as a default option in dataverse managed and non-customizable tables. AutoTrack aims to streamline the data integration process, enhancing the efficiency and reliability of data synchronization between dataverse and Azure data lake.

Key Features:

• Default Change Tracking: Automatically enables tracking changes in managed tables, eliminating the need for manual setup and ensuring that any alteration in the data is captured seamlessly.
• Enhanced Integration with Power Apps - Synapse linked with Azure Data Lake: Optimizes the data flow from Power Apps to Azure Data Lake via Synapse link, ensuring real-time data availability and consistency.
• Data Lake Optimization: Improves the overall efficiency of Azure Data Lake by ensuring that only relevant, change-impacted data is processed and stored.
• Simplified Data Management: Reduces the complexity of data operations, making it easier for users to manage their data landscapes without deep technical expertise.
• Improved Data Quality and Consistency of table schemas: Ensures that data across the organization is up-to-date and consistent, facilitating accurate analytics and decision-making.

Impact:

AutoTrack will significantly reduce the technical barriers and complexities involved in data integration into Azure Data Lake. It offers customers more freedom and flexibility in managing their data, leading to enhanced data quality, better analytics, and more informed decision-making. This feature is particularly beneficial for organizations looking to leverage the full potential of their data in a cloud environment without the additional overhead of manual change tracking configurations.

Per document below, it's stated that SharePoint doesn't fully support ALM scenarios.

There are issues in correctly updating the references to SharePoint in the environment where the solution is imported. It means that SharePoint meta-data (for example, a new column has been added) or data source info (for example, a list pointed at) will be wrong. Refreshing Power Apps Studio in the target environment won't get additional metadata and the data source will always point to the data source for the source environment

Data source references based on environment variables aren't updated during solution import - Microsoft Dataverse | Microsoft Learn

Since it's not fully supported, this option should be removed and updated on the document to avoid confusion for the customer.

I have encountered a situation where two solutions are entangled in a circular dependency. To resolve this, we need all the dependent components of a solution within the circle to exist in order to untangle them. However, I have deleted all the dependent components in both solutions in lower environment, making it impossible to untangle the two solutions. I believe many people face the same problem. Therefore, I suggest implementing a function to address this circular dependency issue. Thank you!

When a Microsoft 365 account is created, automatically add a user to the Dynamics 365 environment in the same tenant without accessing an enviroment.

This feature will improve convenience for users.

Because the concept of device doesn’t exist for Dynamics CRM Online as far as I’m aware of, so a shared service account will take the role as a ‘device’ in this case and get assigned the device license.

And users will take turn access the Applications corresponding to the device licenses assigned to the service accounts. In the Licensing Guide, it does mention that “Device licenses may use shared logins (such as “Warehouse Computer” and a shared password) or individual logins (each user’s personal credentials), depending on the application and license.”

Currently, this is the default nature of the Device license for Dynamics CRM Online Platform.

However, this doesn't meet the requirement of some users since some companies don't allow to use Common Id (shared Id) under any circumstance. What is expected here is that each users will sign in with their own account and password instead of shared account and shared password. So, this design is flaw in this this type of scenario.

And since we don’t have any suggestion at this moment to bypass this mechanism for the device license, we hope Microsoft can adjust this design to support scenario like this.

This is a simple request: we would like to be able to archive purchase orders and related tables please.

Microsoft should add the features to restrict the access of the Dynamics 365 environment to a specific IP address. This is practical and to avoid any security risk.

I would like to propose a new feature for the Power Platform Admin Center that enables administrative users to export a comprehensive list of users within a selected environment, along with their:

• Security roles
• Associated licenses
• Environment access
• Other relevant user metadata (e.g., business unit, access mode, etc.)

This feature should include a customizable view, allowing administrators to:

• Select which columns they want to include (e.g., email, roles, license type, etc.)
• Apply filters to narrow down specific user groups
• Export the data into formats like CSV or Excel for audit or reporting purposes

Why this matters:

Today, gathering this type of information involves switching between multiple tools (Admin Center, Dynamics 365 settings, Azure AD, etc.), and often requires technical knowledge or custom scripts. Providing this functionality in a centralized, user-friendly interface would:

• Streamline administrative and audit tasks
• Improve security and compliance visibility
• Save time for administrators and IT teams
• Enhance governance, especially in large or multi-environment tenants

Suggested Features:

• Environment picker to scope the export
• Role-based filtering (e.g., show only users with “System Admin” role)
• Ability to sort and group by user attributes
• Export button with format options
• Scheduled export or API access (optional but very valuable for automation)

If you agree this feature would be helpful, please upvote and comment to show support!

Issue description: There is no way to export System Administrators across all environments.

Example:

Admins can only export/ retrieve users with assigned security roles in an individual environment. They would have to go through every organization and take action within its database.

Actions taken:

I've tried to perform several ways to retrieve users with assigned security roles, but there are no options to export users with appropriate roles within the environments they are member of.

Expectations:

==========

We should have an OOB workaround to export a user list which include their organization and appropriate security roles accordingly.