Adhavan Elangovan

We would like to request the ability to remove or customize the Environment Maker role for users in the default environment of Power Platform.

Currently, all licensed users are automatically assigned the Environment Maker and Basic User roles in the default environment, which grants them permissions to create apps, flows, and Dataverse databases. This automatic assignment limits administrative control and makes it difficult to enforce governance policies, especially in large organizations.

Our specific concerns include:

• Inability to restrict Dataverse usage or disable the "Create Database" button.
• Lack of control over AI model creation and app development in the default environment.
• No option to customize or remove Environment Maker privileges in the default environment.

We understand this behavior is by design, but having the flexibility to manage these roles—even in the default environment—would greatly improve security, compliance, and governance.

Please consider adding functionality that allows administrators to:

• Opt out of automatic role assignment in the default environment.
• Customize or remove Environment Maker privileges.
• Restrict creation of Dataverse databases and AI models.

Thank you for considering this feature request.

Description:

With the recent update to the "Power Platform Request Licensed User" report, the columns for Dataverse Requests, Power App Requests, Caller Type, and Total Consumed Quantity have been removed. These columns were essential for monitoring usage, troubleshooting, and internal reporting. Their absence has impacted our ability to track and analyze platform consumption effectively.

Business Impact:

• Loss of visibility into Dataverse and Power Apps usage metrics.
• Difficulty in reconciling internal billing and usage reports.
• Increased manual effort to gather data that was previously available in the report.

Request:

Please consider reinstating the following columns in the report:

• Dataverse Requests
• Power App Requests
• Caller Type
• Total Consumed Quantity

Restoring these columns will help customers maintain continuity in reporting and ensure accurate tracking of Power Platform resource consumption.

Additional Context:

This change has affected multiple teams relying on these metrics for operational and billing purposes. If there are technical or business reasons for the removal, please provide documentation or alternative solutions.

Thank you for considering this request.

Currently, in Dynamics 365 (specifically on the Opportunity entity), the system UI sometimes displays the “Above/Under” hierarchical filter option for the Owning Business Unit field. Users are able to select the operator initially, but when the view is reopened or the filter is revalidated, the platform removes the condition and displays the warning:“Condition not executed because of missing relationship: businessunit.”

This creates confusion and disrupts analytical scenarios where business-unit hierarchies are important. Since Owning Business Unit is a system-managed field tied to the Owner’s business unit, it is not currently treated as a fully filterable hierarchical lookup — even though the UI suggests otherwise.

Why this needed:

• Organizations frequently use business unit hierarchies for reporting, territory management, and global visibility.
• Having the Above/Under operator consistently supported would enable richer filtering without workarounds.
• The current experience (UI showing options that later disappear) is unintuitive and feels incomplete to customers.
• Avoids the need to create custom BU lookup fields and maintain them through Power Automate or plugins.

Enable native, full support for applying Above/Under hierarchical filters on:

• Owning Business Unit
• Other system-managed business-unit-related fields

AND ensure the UI reflects only supported operators so the experience is consistent.

Expected benifits:

Better alignment between UI and backend capabilities

More intuitive and predictable filtering behavior

Richer reporting and user-controlled data segmentation

Reduced need for custom fields or automation-based workarounds

Currently, it is not possible to update the color of Business Process Flows (BPF) in Dynamics 365 Customer Engagement. We would like the ability to:

• Update the default colors of BPFs to align with corporate branding.
• Assign specific colors to individual BPFs so users can easily identify which business process they are in.

For example, the current default color is blue, but we want to change it to purple or other colors based on our branding and process differentiation.

This feature would greatly improve user experience and visual clarity when working with multiple business processes.

Problem Statement

Currently, the Finance and Operations – User License Consumption detailed report is available only through the Power Platform Admin Center (PPAC) and can be exported manually as a CSV file. There is no supported method to automate the export or directly integrate this data into Power BI.

For organizations that centrally manage licensing, governance, and compliance through Power BI, this creates a gap, as this critical report remains siloed outside the existing reporting ecosystem.

Business Requirement

Our organization maintains multiple Power BI reports to manage:

• License usage
• Azure AD / Entra ID security groups
• Role-based access and compliance
• Cost optimization and audits

A key business requirement is to centralize all license‑related reporting within Power BI, including the Finance and Operations user license consumption data that is currently available only in PPAC.

Specifically, we require:

• A supported, automated mechanism to access Finance and Operations user license consumption data
• Ability to refresh this data on a scheduled basis (for example, daily)
• Native or supported integration with Power BI (API, data connector, or Dataverse/Export to Data Lake option)

Current Limitation

• The report can only be exported manually by an administrator
• No API, connector, or scheduling capability exists today
• Manual downloads do not scale and are not suitable for enterprise reporting or audit automation

This limitation introduces:

• Operational overhead
• Risk of outdated or inconsistent reporting
• Fragmentation of license governance data

Proposed Solution / Ask

Provide one or more of the following supported capabilities:

• A Power Platform or Graph API to retrieve Finance and Operations license consumption data
• A native Power BI connector for Finance and Operations licensing data
• Ability to export this dataset to Azure Data Lake / Dataverse for reporting
• Built‑in scheduled export capability from PPAC

Business Value

• Centralized and consistent license governance reporting
• Reduced manual effort and administrative overhead
• Improved compliance, audit readiness, and cost optimization
• Better alignment with enterprise BI and FinOps practices

Impact

This enhancement would benefit:

• Large enterprises managing multiple Finance and Operations environments
• Organizations with strict compliance and audit requirements
• Customers using Power BI as a single source of truth for licensing and governance insights

We have multiple users accessing the same model‑driven app forms that include embedded Power BI reports. These users operate Dynamics 365 in different languages, which are configured through Dynamics personalization and user language settings.

Currently, embedded Power BI reports displayed within Dynamics 365 model‑driven apps determine their language based on the browser language or Power BI service locale, rather than the Dynamics 365 UI language selected by the user. As a result, users viewing the same form see Power BI content in different or unexpected languages, leading to inconsistent user experience and additional operational overhead.

Business Requirement:

We would like embedded Power BI reports to automatically align with the Dynamics 365 UI language selected by the user, instead of relying on browser language settings. This would ensure:

• Consistent multilingual user experience across Dynamics UI and embedded analytics
• Reduced dependency on browser configuration
• Better usability for global organizations with multilingual users
• Improved alignment between Dynamics personalization settings and embedded Power BI behavior

Requested Enhancement:

Provide a supported mechanism (such as a configuration option, parameter, or integration improvement) that allows embedded Power BI reports in model‑driven apps to inherit the user’s Dynamics 365 UI language.

This enhancement would significantly improve usability for organizations operating across multiple regions and languages while using embedded analytics in Dynamics 365.

Idea Type:

Feature Enhancement

Description:

Currently, Dynamics 365 email templates support only a limited set of predefined web‑safe fonts. There is no supported option to add or use corporate fonts that are mandated by customer branding or internal style guides.

We request an enhancement to allow custom fonts (for example, Aptos) to be made available in Dynamics 365 email templates, either by:

• Allowing administrators to upload approved corporate fonts (TTF/OTF), or
• Allowing selection of Microsoft-standard fonts already used across M365 (such as Aptos)

This capability would help organizations maintain consistent branding across all customer communications sent from Dynamics 365.

Business Justification / Impact:

the font Aptos is defined as the official standard font in the corporate branding and internal style guide. Since Aptos is not available in Dynamics 365 email templates today, users are forced to:

• Use non-compliant fallback fonts, or
• Rely on workarounds such as images or external tools, which reduces accessibility and maintainability.

This creates brand inconsistency and additional effort for business users who rely on Dynamics 365 for customer communications.

Who Would Benefit:

• Enterprises with strict corporate branding requirements
• Sales and Customer Service teams using Dynamics 365 email templates
• Organizations standardizing on Microsoft 365 fonts (e.g., Aptos)

Proposed Outcome / Value:

• Improved brand consistency across Dynamics 365 and Microsoft 365
• Reduced reliance on unsupported workarounds
• Better alignment between Dynamics 365 and modern Microsoft styling standards

Additional Notes:

Other Microsoft products (e.g., Microsoft 365 apps) already support Aptos as a standard font. Extending similar support to Dynamics 365 email templates would improve ecosystem consistency.