Alex Pham (Tek Experts)

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!

Customers often face business requirements involving large-scale data migration and batch deletion, especially when dealing with substantial datasets (e.g., 10 to 20 million records). Configuring SSIS (SQL Server Integration Services) for such purging tasks can be complex and time-consuming. To simplify this process, adding a straightforward button to clear the table would significantly streamline operations and reduce the overhead of manual configuration.

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!

We recently encountered a case where a customer noticed that certain Customer Copilot features had been re-enabled in their Dynamics 365 environment—without any prior notification or indication of who made the change. Upon investigation, we discovered that D365 currently lacks audit logging or tracking capabilities for these types of configuration changes.

While it’s possible that system updates or automated processes may re-enable features, customers need full transparency and traceability for all changes—especially those that could impact data access, user experience, or compliance.

Problem

There is no built-in mechanism to:

• Identify who enabled or modified a feature (user, service principal, or system process)
• Determine when the change occurred
• Understand what was changed and the before/after values

Suggested Solution

Introduce comprehensive audit logging for all feature enablement and configuration changes in Dynamics 365. This should include:

• Who made the change (user/service principal/system)
• When the change occurred
• What feature or setting was modified
• Previous and new values of the setting

Additionally:

• Make this audit data accessible via Advanced Find, Power Platform Admin Center, or Audit History
• Optionally, allow customers to configure notifications for changes to sensitive or critical feature flags