Power Platform Governance and Administration

In Power Platform Admin Center, when opening an environment, we can see the dashboard of environment details, including Security Group (SG) associated to environment. The SG of environment shows either SG name (if a SG is chosen) or None (if we choose Not assigned). We suggest the choice “Not assigned” and status “None” should be in the same term. In some cases, "Not assigned" implies that we haven't made a choice and therefore the default behavior prevails for that environment. When I choose "None", I am actively telling that I don't want to set a security group. With that reason, we should merge those 2 terms to avoid confusion.

Customer Scenario: We are deploying custom connector action via a Solution. When deployed manually as managed solution, actions are reflected in the target environment Dynamics_CFT_Test. When we used GIT pipeline with force overwrite = true, it didn't reflect. We found the deployment was done successfully from Solution history. It upgraded to newer version and uninstalled older one. Any upgrade/ update/ Import was not failed irrespective of GIT/Manual. We have the evidence that there is no failure during the deployment.

Specifics: We have created a small solution containing only custom connectors and was deployed via git in target org. That time it reflected expected actions. Next time, when we deployed actual solution keeping custom connector actions it got overwritten to prior state (expected custom actions are not reflected). Then we again deployed that small solution via git with a newer version to the target org and it worked.

Concern: If we have to perform the same each time whenever we deploy actual solution, will be a big task. Kindly suggest any better way.

We have some checkboxes on readonly mode basic form in Power Pages portal. However, they do not accept focus when pressing tab key

The ILogger Interface provided to log into Application Insights lacks many logs like the customMetrics, dependencies and customEvents log. For the frontend (JavaScript) a similar mechanism to ILogger is missing entirely.

Current translation process is prone to errors, the standard translation export lacks context information, which form, section tab this translation is for; additionally you can only import translations into the environment where it came from; and there is no good approach how to use translations together with managed solutions, especially when the customer translates over many entities a hundreds of standard and custom columns.

It should be possible to use the Power Platform portal to run benchmark of forms loading and record creation/update as well as to expose API calls to utilize this functionalities in the automation pipelines.

Furthermore, Microsoft should provide standard benchmarks for comparison (of course considering local network speed etc.).

We received a message from Message Center (ID: MC942823) informed that starting in March 2025, the tenant isolation feature will be enabled by default for tenants that have not been configured with a tenant isolation policy

We understand that this will affect apps and flows using cross-tenant connections. However, there is currently no method to identify which apps and flows are using these connections or to list all the impacted apps and flows. If we have multiple apps or flows, we will have to check each one individually, which is a frustrating and time-consuming process.

It would be beneficial to have a feature in the future, such as a dashboard or a list, that helps summarize which apps and flows are using cross-tenant connections.

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!

Developers currently need to register plugins in a development environment before they can add the steps to a solution for export/unpack and further ALM steps. This is unnecessary overhead and bears huge effort savings at a global scale of Dataverse.

A solution would be to allow the definition of plugin steps at build time (e.g. via class attributes/annotations), so that the .cdsprj file automatically produces the solution XML with the proper steps.

I was advised to go this route, for a ticket that was placed on 10/28 regarding the release of the power platform catalog.

When a Catalog is created, a solution alongside it is installed in the target environment (either created from the wizard or selected from your current environments)

If for any reason this catalog needs to be marked active/inactive after install, it will not accept your change. If the catalog needs to be uninstalled and reinstalled, either for testing purposes, et al. you are no longer allowed to install the catalog in an environment where a catalog previously existed. Deleting the appropriate solution, components, tables, etc will still not allow you to select an environment to create a catalog in.

Upon bringing this to microsoft, intent that this must be a bug, i was advised to create a new environment which based on capacity is not a viable solution for most companies, as it is inferred that with a catalog in your environment, you are utilizing an amount of dataverse capacity that is not returned. When voicing the concern for what appears to be a broken process, i was advised that catalog uninstalls are not supported which is a extremely detrimental when trying to grow the platforms user-base!

While the rep i worked with was kind and understanding, and i dont believe this is the place to submit something that is clearly a bug, to an ideas page, I will still champion this!