cancel
Showing results for 
Search instead for 
Did you mean: 

Licensing - Project Oakdale

I've been experimenting with Project Oakdale - PowerApps created in Teams. I'd read so much about Project Oakdale in various articles plastered all over the internet and I was excited to read rumours that users would not need the per app or per user license. 

 

My investigations discovered that actually there are no changes to the licensing of PowerApps created in Teams. Premium Connectors still require the per app or per user license. I was hoping that Microsoft would have at least allowed a Standard Connector to CDS or to Azure SQL.

 

I'm frustrated. Everytime I wow my customers with PowerApps and then explain the licensing the project dies a death. The licensing cost is prohibitive for my customers. 

 

Can I suggest that a positive way for customers to move from PowerApps Portal to PowerApps created in Teams is to include CDS or Azure SQL as a Standard Connector. We need a relational database Standard Connector. Microsoft make money from CDS capacity and from Azure SQL so surely making it a Standard Connector would increase usage and adoption?

 

Without these changes to the licensing I'm afraid I see no point in Project Oakdale. 

 

Please vote for a Standard Relational Database Connector in Project Oakdale so that we can increase adoption and usage.

 

Thanks!

Status: New
Comments
Advocate V

I whole heartily agree. Great suggestion. If CDS was a standard connector, we'd pump all our data into CDS, which would increase the storage size, which would require the purchasing of more storage. It's a win for everyone.

 

Project Oakdale will make a difference, as we'll no longer have to bend SharePoint to breaking point. But having it in Teams means the database is siloed, meaning the real benefit of having all company data in a single CDS environment is impossible.  

 

 

Super User

Without a sensible database option Power Apps is too limited to build anything truly useful - if your data is important, you shouldn't be storing it in SharePoint lists, if it is important and you have more than a handful of users, you are better off paying for development up front in more flexible (license-free) tools rather than paying the ongoing licenses to connect to real databases.

I've up-voted the idea even though I think CDS is a a much poorer option than Azure SQL. CDS it is not properly relational, not supporting joins across multiple entities within Canvas PowerApps or WorkFlows and so encouraging redundant relationships and duplicated/inconsistent data. It also incorporates non-relational 'additions' such as multi-value fields, option sets and polymorphic relationships which make it quicker to design build databases but store up all sorts of issues for the future.