☁️
Microsoft
  • Readme
  • Virtual Internship Program
    • InsideSherpa & Background
    • Goal Tracking
    • Engineering Internship
      • 1. Research on Microsoft
      • 2. Preparing for the Virtual Experience
        • Preparing for my virtual internship with Microsoft
        • SMART goal setting
      • 3. Campus: Business Foundation Skills
        • Respect, Integrity and Accountability
          • Situational based questions
        • Commitment and approach to values into action
        • Microsoft's cultural transformation
        • Microsoft's solutions for digital transformation
      • 4. Campus: Work Ready Skills
        • My professional voice (be confident)
          • Confidence in meetings
          • Confidence in business
          • Confidence in communication
          • The task
        • A professional approach to meetings
        • The importance of your personal brand
      • 5. Work Ready Skills
      • 6. Technical Engineer Skills
    • Go-To-Market Internship
      • 1. Research on Microsoft
      • 2. Preparing for the Virtual Experience
        • Asia Pacific Internship Experience
        • SMART Goals
  • Microsoft Student Accelerator (MSA)
    • Workshop 1: AI & Machine Learning
    • Project 1: Machine Learning
    • MSLearn 1
    • Workshop 2: Cloud Fundamentals
    • MSLearn 2
    • Project 2: Web Application
      • My idea
      • Exploring msa.ms (old website)
        • For Schools
        • For Employers
        • Events
      • Finding a theme
      • Collecting assets
      • Designing the Header
      • A custom domain using Azure DNS
        • Azure DNS Learn Path
        • Introduction
        • What is DNS?
        • Azure DNS
        • Configuring Azure DNS
        • Buying a custom domain on GoDaddy
      • Plugins
        • Contact Form
        • Implementing SEO
        • Anti-spam
        • SSL
      • Transfering to a new domain
      • Improving site Health
      • Adding custom CSS
      • Interactivity with JS
      • Managing Wordpress from the terminal
      • Next steps: Editing content
      • The front page
        • Global elements
        • Layouts are good sometimes
        • Customising the front page
      • Revisiting the contact form
      • RYTE SEO Analysis
      • Cache Management
      • Traffic Monitoring and Analytics
      • FAQ
      • Documentation
    • Workshop 3: Web App & APIs
    • Project 3: Building an app
      • Target Persona
      • Idea
    • MSLearn 3
      • Create a Canvas App
        • Get started with Power Apps
          • Introducing Power Apps
          • Untitled
      • Use UI and controls
  • Interview Preparation
    • Azure (Cloud) Application & Infrastructure Specialist Roles
      • Revisiting my assessment
      • The technical assessment
      • Using LinkedIn
    • Technology Strategist Roles
      • Partner Technical Architect
  • Power Platform
    • Power Platform Fundamentals
      • The Power Platform
        • A Data-driven World
        • What is the Power Platform?
        • Features of the Power Platform
        • Data Connectors
        • Data Delegation
        • Creating Custom Connectors
        • Putting it all together
      • Power Apps
        • What is Power Apps?
        • Power Apps & what it can do
        • The 3 Types of Power Apps
        • AI Builder in your Power Apps
        • The 4 Models of AI Builder
        • The business value of Power Apps
        • Case study: Heathrow Airport
      • Common Data Service
        • What is the Common Data Service?
        • Entities in Common Data Service
        • Scalability
        • The Common Data Model
        • Types of Entities and Fields in CDS
        • Understanding relationships using Entities
        • Environments in Common Data Service
        • Business Rules
        • Administer (Administration)
      • Building an app solution
        • Basic elements
        • Untitled
      • Power Automate
        • What is Power Automate?
          • Types of flows
      • Building an automated solution
      • Power BI
        • Parts of Power BI
      • Building a simple dashboard
    • PL-900
  • Microsoft Azure
    • Cloud Concepts
      • Principles of cloud computing
        • An analogy
    • Core Cloud Services
    • AZ-900
      • Virtual Training Day
        • 1.
        • 2.
        • 3.
        • 4.
  • Microsoft 365
    • Microsoft 365 Fundamentals
      • What is Microsoft 365?
  • UNSW Cloud Society
    • Microsoft Azure
      • Workshop 1
      • Workshop 2
      • Workshop 3
    • Power Platform
      • Building a Helmet Detection App
  • Microsoft Reactor
    • PowerApps workshop
  • News
    • Microsoft exams $15 down from $100
    • Microsoft's cultural transformation
Powered by GitBook
On this page
  • Overview of the Common Data Service
  • What does the Common Data Service provide?
  • Security
  • Logic
  • Data
  • Storage
  • Integration
  • What you can do with the CDS

Was this helpful?

  1. Power Platform
  2. Power Platform Fundamentals
  3. Common Data Service

What is the Common Data Service?

PreviousCommon Data ServiceNextEntities in Common Data Service

Last updated 4 years ago

Was this helpful?

The Common Data Service (CDS) is a cloud-based, low-code Data Service AND App Platform. The advantage of this ecosystem that Microsoft has built up is that through the Common Data service, you can leverage the security and connectivity that is embedded in all Microsoft services.

What makes the Common Data Service unique is that it connects to all products and aspects within the Power Platform. This allows you to easily manage your business, automate processes and improve various aspects using the platform. As a data service, CDS supports not only the standard entities and fields that popular data services have, but also provide a simple way to define relationships with your data. So CDS is a rather practical and scalable solution - built to interface multiple products and applications with a strong foundation in data management and relationship building.

Overview of the Common Data Service

The Common Data Service is a cloud-based solution that sorts data from various sources and aligns business logic from different applications. You can imagine CDS as the middle child - the mediator - the shared node that brings together different systems under a common data pool.

The Common Data Service is managed by Microsoft and available for use globally. This means anyone around the world can utilise the Common Data Service in their systems, in conjunction with the Power Platform.

Even more, what is unique is that the CDS is deployed GEOGRAPHICALLY / locally. This is so that the CDS always complies to the local regulations of the user. If you were to use CDS in Germany for example, then the Common Data Service would follow the data policy guidelines that Germany provides (like GDPR or something).

One nuance however, is that the Common Data Service cannot be embedded in your application as a standalone. In other words, to access and utilise CDS, you require an Internet connection to link up with the service and manage your data.

The Common Data Service should serve as the Central Data Repository for all the data within the business - pooling data from different sources and keeping it in one secure location. This powerful tool is already intrinsicly embedded in a lot of Microsoft solutions - including Dynamics 365, Power Apps, Power Automate and AI Builder natively utilising the CDS.

What does the Common Data Service provide?

Security

The Common Data Service is in charge of managing Authentication for Azure's Active Directory (Azure AAD). This is the Identity Management for Azure that defines the conditions of accessing Azure products as well as rules for multi-factor authentication.

Logic

For Logic, the Common Data Service enforces a consistent logic across your various sets of data. This implies things like applying your business logic on the data such that regardless of how the data is used, the same rules always apply. The benefits of doing so is that the CDS helps to improve your data management regarding things like detecting duplication in data, promoting workflows that utilise this data and more.

Data

For data, the Common Data Service is in responsible for how you can interact with your data. CDS provides you with complete control over your data, helping you to do things like discover, catalogue, report, validate and model your data all under a common data thread. Again, this is to ensure that wherever the data is used and how it is interacted with there is always a level of consistency.

Storage

For storing your data, the Common Data Service utilises the Azure Infrastructure to store your data on the Azure Cloud. This ensures that your data will be kept secure and backed up - such that you need not worry about how to access your data and how you might scale your database. With all this taken care of, you even have the added ability to take advantage of Azure's features when interacting with data. Things like creating relational databases to form relationships with your data, or utilise different modes of storage like blob storage is all brought to the table with the Common Data Service

Integration

Extending upon different data sources, the Common Data Service connects your data in various ways to meet the needs of your business. For example, with external data, you may require an API compared to internal data on your storage which you may need to import or export. Having this selection of options makes it extremely easy to bring data into your database (CDS) and also extract your data.

What you can do with the CDS

Since you can connect your Common Data Service as a shared database to different sources, you can connect your Common Data Service to different cloud-based versions of a standard database. What this standard database provides are things like pre-defined tables and fields filled with things that are common across almost all organisations and businesses. This means that when you create your CDS, a level of work is already automated to set-up the CDS such that you are ready to go from the start. Having this can accelerate you into customising the CDS for your specific use case.

As such, you are free to extend upon the base database and add new tables and fields (or adding ENTITIES as they are referred to in CDS). So making new data entries is essentially creating new entities in CDS. By doing a level of work ahead of time, you can then concentrate on creating a better solution wihout needing to worry about your infrastructure, data storage or integration as that is all covered by CDS.

Once your data is connected using CDS, you can access it different depending on what services you are using CDS with. For Power Apps and Power Automate, it is natively supported such that you can instantly connect and set-up Common Data Service to manage your data. On the other hand, for external business solutions, you can utilise Connectors and APIs to manage and access your data, allowing you to connect to any business solution.

What the Common Data Service offers natively