[BUG]: CRITICAL : Dataverse Legacy dependency for the Code Components of Creator Kit

[dineshary]

Describe the bug
When i add creator kit components to the canvas app (Icon, DetailsList), there is a dependency on Dataverse Legacy is also created. But i am not using anything related to Dataverse or Dataverse legacy. This issue occurs with the Code components like icon, details list etc

This looks very critical as the Dataverse Legacy connector is getting depreciated very soon.

To Reproduce
Steps to reproduce the behavior:

1. Create a canvas app
2. Add DetailsList, Icon creator kit components to the app
3. Save and try Sharing the app. Data permissions section in the Share Dialog shows Dataverse now even though there are no Dataverse involved in the app
4. Try moving the solution to another environment where dataverse legacy connector is blocked, app will not open due to DLP

Expected behavior
Dataverse legacy must not be a dependency for the app

Screenshots
App: (If the Dataverse legacy is not blocked as per the DLP policy)

App: (If the Dataverse legacy is Blocked as per the DLP policy)
I tried adding the Details list component with datasource from Office365 users. Also, there is only one Connector used in the canvas app which is Office365Users

Additional context

AB#969

[schngupta]

This bug is a significant obstacle for my PowerApp because several external users depend on the app to submit critical business information. Unfortunately, the app's integration with Dataverse requires a premium license, which I do not believe external users can obtain.

[denise-msft]

@dineshary in the share panel you showed, which tables are displayed? At some point in the studio, did you attempt to add a Dataverse table and then remove it? What happens if you just hook it up to a non-premium data source like SharePoint or to list Office365 Users, can you try that in an app from scratch?

[dineshary]

@denise-msft When i click Show tables, it doesnt show any tables. The screenshots provided are from the app built from scratch with the steps described.

We have multiple canvas apps in our organization with creator kit and sharepoint as data source, they all have the same issue even though dataverse or dataverse legacy are not used in the apps

[RiccoHippDev]

Hello people
I'm here briefly because I can also have to say something on the subject.

I have spent the last two days with Microsoft support because of exactly the same issue.

In my case, the code component "Command Bar" was to blame for the generation of a dataverse connection.

The reason is, according to Microsoft the Following Licence(change):

Code Components that connect to external services or data directly via the user's browser client and not throught connectors are conisdered as premium. When these components are used in an app, the app becomes premium, and the end-users are required to have PowerApps Licences.

[dineshary]

@RiccoHippDev Thanks a lot for sharing!! How did you manage to solve this reference to Dataverse Legacy?

In my case, i am not using Dataverse in the app and sharepoint is the only datasource connected to it.

[RiccoHippDev]

I'm sorry to dissapoint you but the only solution is to remove the code component from the App.

After that you stil have the Dataverse Conenction in the Sharing Menu but you can share it without assigning a security roles.
Users have then access to the app without a PowerApps Licence

[dineshary]

@RiccoHippDev Thanks for the reply!

I am fine with the issue since it is not impacting anything at the moment. BUT it still has the dependency on Dataverse Legacy connector in the DLP policy. If i remove that, app does not work.

Microsoft is slowly depreciating the Dataverse legacy connector in different parts of power platform, i am worried about that. One day, many of my apps will not work suddenly

[denise-msft]

Thank you for continuing to provide information. We are looking into this and will provide a resolution as soon as possible.

Microsoft is slowly depreciating the Dataverse legacy connector in different parts of power platform, i am worried about that. One day, many of my apps will not work suddenly

Where are you seeing the legacy connector being added? I am able to reproduce this issue but it looks like the modern connector is being added as a dependency. In that sense the deprecation of the legacy connector should not affect you, but we still want to figure out the issue with the controls being marked as premium if they're not using those features.

[dineshary]

When i move the solution to a different environment and open the app. It shows the error that the App is not compliant to the DLP policy.

Business connector: shared_office365users cannot be used with non-business connector: /providers/Microsoft.PowerApps/apis/shared_commondataservice.

The Target environment has Dataverse connector enabled as a Business Connector but not the Dataverse legacy connector.

If i enable Dataverse legacy connector as a business connector in the target environment, then everything works well

[denise-msft]

Thank you for sharing the additional details. We're currently working with the engineering team to investigate and will try to provide an update soon.

[denise-msft]

Just an update - this was escalated to the product team who has acknowledged the incident and is working on this. We'll share a timeline once available.

[denise-msft]

Update - Power Apps team is still actively looking into the issue. They're investigating by looking at any changes recently made related to DLP. We will provide more details when available.

[Hankanman]

This is still an issue, I have secure clients that want to disable the legacy connector per its deprecation announcement and are unable to due to this issue

[aleeland]

Hello everyone, it looks like this is still an open issue. I am a member of the MSFT Power Platform DLP team and we are trying to block the legacy Dataverse connector also within DLP policies, but this would break users' apps that have the Creator Kit in their environment (mine included). Is there a timeline for resolution for this?

[denise-msft]

This is being tracked by the product team and will hopefully be able to provide a timeline for a fix soon. Thank you for your patience.