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!

You can see a list of projects and connection sets from the Data Integration section of the Power Plarform admin center.

However, you will not be able to check the environment ID from the list.

Therefore, it takes a significant amount of time to view the records one by one to verify the environment ID.

As a result, you will not be able to work efficiently.

To solve this problem, we would like to implement a function to search for the environment ID related to the project and connection settings.

Hello, I have developed a Power Page and embedded it into a Power Pages Site, but I require the page to be anonymous, as it is a survey.

It would be good if this could be achieved and the Power Page follows the site visibility settings.

Thanks.

Current Behavior: Users are unable to access the Power Apps portal using GDAP (Granular Delegated Admin Privileges) because this functionality is not supported at the moment. They can only access Dataverse environments.

Expected Behavior: Partners should be able to access the Power Apps portal using GDAP (Granular Delegated Admin Privileges).

Currently, there is a bug in the Power Platform where, if a user loses access to the environment or their account gets disabled in Microsoft Entra ID, their Azure AD Groups are no longer synced with the "teammemberships" table in the Dataverse. In such cases, manual removal of teams from the user’s profile in the Admin Center is required.

The user must be manually removed from the teams at the environment level.

We have separate Microsoft Entra ID groups created for segregation of access roles. Group(s) are assigned to a user, which provides specific access rights to our model-driven app. Once the user is added to a specific Entra ID Group, his "team memberships" updates in the model-driven app. However, if user's groups are removed from the Entra ID or he leaves the organization (meaning his Azure acc is disabled), "team memberships" in the model-driven app are not updated/synced with Entra ID. User must sign out and sign back in for the cache to be cleared. It goes without saying that the user is unable to sign out/sign in if his access rights are revoked, therefore his "team memberships" are never updated. 

Please find Microsoft's documentation below. The part in bold is not correct or does not work as intended:

Due to the team member's privileges being derived dynamically at run-time, the team member's Microsoft Entra group memberships are cached upon the team member's log-in. This means that any Microsoft Entra group membership maintenance done on the team member in Microsoft Entra ID will not be reflected until the next time the team member logs in or when the system refreshes the cache (after 8 hours of continuous log-in).

In our tenant, our admin accounts (with tenant admin roles) do not have mailboxes. This means we are not able to receive the Dataverse storage capacity alerts. It would be great if we could configure different email addresses to receive these alerts.