Power Platform Governance and Administration

Currently the only documented place where Power Platform administrators can discover the status of Dataverse for Teams environments scheduled for automatic deletion is the Power Platform admin center Environment page. On that page the deletion status of affected environments is indicated in the State column by the words "(Ready __ days until disabled)". Unfortunately, because there is no way to export the contents of that page, responsible admins are left with the labor-intensive task of manually copying and pasting the relevant information into Notepad, Excel or another app. Power Platform Admin Powershell and Power Platform CoE Kit queries are also unable to capture this information.

I would like to suggest either (a) the addition of export capability to the Environments page; or (b) an exportable report that provides detailed status information on each inactive dataverse such as the environment name, contacted owner, state, inactive date, warning date, disabled date, and deletion date.

Activate the download option for SharePoint documents in the model-driven app. This option used to exist but has been deactivated.

It is great to allow customers to select preferred data center in each region on signup because data center alignment is mandatory for some services such as Synapse, Key Vault,...

Power Pages does not allow a site to be created with en-GB as a site language.

Please add.

Opening the admin portal, you can see the space consumption of each table. But you can't break down to the size of the data and the size of the index.

Therefore it's difficult to optimize the table, as at some tables, the index is the same size like the data.

It would be great, if during exporting the storage consumption to the excel, the used spaces is displayed as data and index in two columns.

Fail scenario:

Customer is using AAD as IDP and authenticate user accessing to Dynamics CRM on-premises.

When Edge profile signed in, CRM will use below wauth parameter "urn:federation:authentication:windows" to login with ADFS. It will generate a device token, which will override the original wauth paremeters, replace it with "urn:oasis:names:tc:SAML:2.0:ac:classes:Password", then you will get a ADFS error: "“Error details: Exception of type 'Microsoft.IdentityServer.Service.Policy.PolicyServer.Engine. InvalidAuthenticationTypePolicyException"

Authentication flow on Edge:

1. The user connects to the app, redirects to ADFS, and selects AAD authentication.
2. During AAD authentication, the user directly completes the first-stage verification through PRT (Primary Refresh Token) and enabling the immediate initiation of Multi-Factor Authentication (MFA).
3. After the completion of MFA, the token is sent back to ADFS. However, since there was no validation through Windows Integrated Authentication (WIA) during this process, it does not align with the app's requirements.

Successful scenario:

In InPrivate mode, Edge and Chrome (without installed extensions) will not use PRT, so you won't encounter this issue.

Authentication flow on In-Private Edge:

1.         The user connects to the app, redirects to ADFS, and selects AAD authentication.

2.         During AAD authentication, the user enters their account information. After entering the account, due to being in a Federated domain, they are redirected back to ADFS for validation.

3.         Upon returning to ADFS, since the User Agent supports WIA (Windows Integrated Authentication), the Windows Integrated Authentication process is completed.

4.         After the completion of MFA, the token is sent back to ADFS. Because the ADFS authentication process utilizes WIA, it aligns with the app's requirements, resulting in a successful authentication.

Root cause:

Edge utilizes PRT for authentication by default because device is registered on AAD it will use a device token which will override the crm's wauth parameters.

Expectation:

Edge browser as Microsoft supported browser should work with CRM application in this scenario when device is registered on AAD for example make PRT consistently include the WIA by default.

PROBLEM

The Dataverse does not record milliseconds in its date/time columns.

We have various jobs in our source systems (not all under our own control) that produce changes in short periods of time.

In Dynamics we have plugins that attempt to locate and set the "current state" of various entities based on the LAST action taken.

IMPACT

Without milliseconds being available, some entities are set to the wrong "current state" because the code randomly selects one record from the set of records falling in the last second of activity as the entity's "last action".

This can have potentially legal ramifications.

SOLUTION

ALL columns in Dataverse need to support milliseconds.

This includes built-in columns (e.g.: createdon, modifiedon) as well as custom columns.

Excluding a user from a security group leaves the user as an invalid user in the environment.

The security role will also remain assigned to the user at that time.

In that case, a manual operation to unassign the security role is required, but it would be very convenient for the user if the security role is unassigned when the user is excluded from the security group.

I've been using Power Automate and encountered a bug in the "When a new email arrives (V3)" trigger. After applying a "For Each" action following the trigger, retrieving dynamic information like "ReceivedDateTime" doesn't yield the expected value. The issue lies in the trigger not automatically incorporating the "For Each" action, requiring manual updates to function correctly.

For sandbox environments, backups are retained for up to seven days. However, for production environments that have been created with a database and Dynamics 365 applications enabled, manual backups are retained for up to 28 days. 

Currently,we need Admin access, but unfortunately, we are not authorized to obtain Admin access as it is managed by a different team.

Consequently, we are looking for alternative options or solutions to monitor the daily backup without relying on Admin access.