Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

No cookies to display.

Pages Menu
TwitterRssFacebook

Posted by on Jul 21, 2020 in Development, Microsoft Teams

Common Data Service is now Microsoft Dataflex, and it’s WAY more than just a name change. This changes everything.

Common Data Service is now Microsoft Dataflex, and it’s WAY more than just a name change. This changes everything.

A big announcement happened today. It might not seem like one right now, but I think we’ll look back on this in a year’s time and wonder how we ever made do without this part of the Teams Development puzzle.

The top-line is that the Common Data Service (CDS) is being renamed, but is also coming to Microsoft Teams. This means that developers will have access to a relational data-store right within Microsoft Teams.

“Inside #MicrosoftTeams, there’s going to be a place for applications to keep data in a persistent store. Tables, columns, rows, relationships. No need to create a database. No extra license, no cost, no setup. Just the data, accessible in Teams for apps to use. ?”

Let’s say that again. Inside #MicrosoftTeams, there’s going to be a place for applications to keep data in a persistent store. Tables, columns, rows, relationships. No need to create a database. No extra license, no cost, no setup. Just the data, accessible in Teams for apps to use. ?

This instantly makes it easier to build applications that need complex state, need to store objects, want to collect and work with data. It’s possible to build all these things today, but it requires a knowledge of using a database, or Azure Storage Tables or similar.

Having Microsoft Dataflex be something that “comes with Teams” and that developers can rely on as being there will also help the low/no code development process and enable more complex applications to be built in this way, using technologies such as PowerApps and Power Virtual Agents.

It’s a decision that sounds kinda crazy, but also makes complete sense.

Teams as a Platform

Teams is becoming more than just a collaboration tool – this change means that it’s also going to become the storage location for numerous low/no code applications. This will likely have implications for adoption, information governance and security that we will have to work through in the coming weeks and months. Even understanding where this data resides could be a multi-layered answer.

I think Microsoft know these questions are coming – Dataflex already comes will built-in full audit logs and DLP policies.

I’m a Teams developer, should I delete my database now?

Good question. This is a new announcement, so you shouldn’t rush to anything, but for new projects starting now – if you’re building a Teams application and you need to store data, I’m not sure why you would use an “external” data source, unless you’re storing vast amounts of data or doing something computationally intensive. By using Dataflex your solution will be simpler to deploy, and have a lower cost to run. It’s a bit of a no-brainer.

It’s early days, but I’m pretty excited about what this will do for enabling more applications to come to Microsoft Teams. The great thing about technology is that it’s always changing!

Written by Tom Morgan

Tom is a Microsoft Teams Platform developer and Microsoft MVP who has been blogging for over a decade. Find out more.
Buy the book: Building and Developing Apps & Bots for Microsoft Teams. Now available to purchase online with free updates.

Post a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Share to Microsoft Teams