Microsoft Dataverse for Teams
At Microsoft Inspire 2020, Microsoft Partner focused conference, Microsoft introduced A low code / No code app building planform for Microsoft Teams build on top of Power Platforms Common Data service now named Microsoft Dataverse.
This post provides quick “up to speed” info found scattered around in different sources on some of the key capabilities in the no-code app building platform called Microsoft Dataverse for Teams called. I will also cover some of the differences between Microsoft Dataverse for Teams and Common Data Service, now named Microsoft Dataverse.
For full details, check the Sources in the end of this post ⇓
The new Microsoft Dataverse for Teams delivers a built-in, low-code data platform for Teams and enables everyone to easily build and deploy apps and intelligent chatbots in Teams with Microsoft Power Apps and Microsoft Power Virtual Agents.. all included in Microsoft Teams Licensing.
It-is a light version of Common Data Service (CDS) now named Microsoft Dataverse.
What is Microsoft Dataverse?
- As it always has been, it is a Secure, smart, and scalable data platform that powers the Power Platform and Dynamics 365 CE.
What is “Project Oakdale” for Teams?
- Microsoft Dataverse for Teams is NEW. (General Available 16. nov. 2020).
- Microsoft Dataverse for Teams comprises a subset of Power platforms Common Data service capabilities (CDS) specifically for Microsoft Teams.
- Teams users have an embedded App Studio with easy-to-use no code editable grid to build data models
- Access to the environment is restricted just to the Teams owners, members and guests. Teams-centric role-based access (Owners, Members, Guests) with governance tool and security for admins. In General Management will not be the same as for Common Data Service but will be Microsoft Teams centered.
- Teams-only client (Desktop + Mobile)
- 1 Project Oakdale environment per Team
- Relational, image and file data support
When would you upgrade from Microsoft Dataverse for Teams to full version of Microsoft Dataverse?
- When I need
- Application lifecycle Management
- Greater access control, auditing, Security and Compliance
- Relevance search, mobile offline data
- Native integration with Azure, SQL, and Azure Datalake
- Support for clients like web, desktop Microsoft Outlook and Microsoft Excel
- When I want to use
- Premium Connectors
- Business Process Flows
- Model Driven apps
- Non-relational data, managed lake
- Code plugins
- When I reached the boundaries of Microsoft Dataverse for Teams capacity
- Each Microsoft Dataverse for Teams environment uniquely maps (1:1) to a Teams team and can store up to 1,000,000 records based on typical usage (enforced as 2GB relational database storage per Project Oakdale environment; up to 1TB per tenant).
Why not just use Microsoft List / SharePoint lists?
Lists is great for quickly tracking data in Teams. All your lists are instantly usable inside of Teams. Additionally, you can build canvas apps and flows on top of your Lists just like you can today in SharePoint.
Microsoft Dataverse for Teams is great for building Power Platform solutions in Teams. The key difference is in type of storage, for e.g. relational table storage and support for file and image data, with find, filter and sort.
Why I am excited
I am no longer the kid that was not allowed by the grownups (aka IT) to play with Microsoft Dataverse but where left to finding a workaround to do my job working with SharePoint list and excel.
Finally a low-code custom development platform with super easy interface to use directly in Microsoft Teams. The right place for citizens users to easy build their first take on a citizen developed app that fits their way of working. All build on a proper Enterprise grade low-code datastore with super easy option to transition to professional development if needed.
Sources for above info
Twitter post like this: https://twitter.com/rc_says/status/1285598557014306818