PL-900 Deep Dive

What is Microsoft Dataverse? Complete PL-900 Guide

Dataverse is the data backbone of the Microsoft Power Platform. Understanding it is essential for PL-900 — and for building serious Power Platform solutions.

By MSCertQuiz Team•Updated March 2026•16 min read

PL-900 Exam Coverage

Dataverse is tested throughout Domain 2 (Identify core components of Power Platform, 25%) and appears in Power Apps and Power Automate questions. The exam tests: what Dataverse is, its components (tables, columns, relationships), how it compares to SharePoint, and when to use it. You'll likely see 5–8 Dataverse-related questions.

What is Microsoft Dataverse?

Microsoft Dataverse (formerly Common Data Service) is a cloud-based data storage and management platform that sits at the heart of the Microsoft Power Platform. It's a secure, scalable database-as-a-service designed specifically for business applications.

Think of Dataverse as a managed relational database with built-in features that traditional databases lack: business rules, security roles, audit logging, relationship tracking, and native integration with all Power Platform tools.

Dataverse powers:

• Dynamics 365 applications — CRM, ERP, Field Service, Customer Service are all built on Dataverse
• Model-driven Power Apps — require Dataverse as their data source
• Canvas Power Apps — can connect to Dataverse (among other sources)
• Power Automate flows — trigger on Dataverse changes, read and write Dataverse data
• Power Virtual Agents / Copilot Studio — store bot conversations and topics

Dataverse Core Components

Tables

The fundamental data container in Dataverse. Tables are similar to database tables — they store data in rows and columns. Dataverse includes both standard tables (provided by Microsoft for common entities like Account, Contact, Activity) and custom tables (created by your organization for specific data).

Exam tip: Tables replaced "Entities" in older CDS/Dataverse terminology. If you see "entity" in an exam question, it refers to what is now called a "table."

Columns (Fields)

Each table has columns that define the attributes of data stored. Dataverse supports many column types: Text, Number, Date/Time, Choice (dropdown), Lookup (relationship to another table), File, Image, and more.

Standard columns exist on all tables (CreatedOn, ModifiedOn, Owner). Custom columns are added by administrators to meet business needs.

Relationships

Dataverse supports structured relationships between tables:

One-to-many (1:N): One record in table A can relate to many records in table B. Example: One Account can have many Contacts.

Many-to-many (N:N): Many records in table A can relate to many records in table B. Implemented via a relationship table.

Many-to-one (N:1): Many records in table B relate to one record in table A (same as 1:N viewed from the other side).

Business Rules

No-code logic applied to Dataverse data that runs regardless of which Power Platform tool is used to access the data. Business rules can:

• Show or hide fields based on conditions
• Set field values automatically
• Validate data before saving
• Display error messages to users
• Mark fields as required based on other field values

Key point: Business rules run on the server side — they apply even when data is modified via the API, not just through Power Apps.

Security Roles

Dataverse has a granular security model that goes far beyond simple sharing. Security roles define what operations (Create, Read, Write, Delete, Append, Assign) users can perform on each table — and at what scope (User, Business Unit, Organization).

Exam tip: Dataverse's row-level security (who can see which records) is a major differentiator from SharePoint, which has list-level permissions but limited row-level control.

Choices (Option Sets)

Choices (formerly Option Sets) are dropdown fields with predefined values. They come in two types:

Global choices: Defined once at the environment level, reused across multiple tables (e.g., a status list shared by multiple tables).

Local choices: Defined for a specific column on one table only.

Dataverse vs SharePoint Lists: When to Use Each

This is one of the most tested PL-900 comparisons. Both can store data used by Power Apps and Power Automate — but they serve different scenarios:

Factor	Microsoft Dataverse	SharePoint Lists
Data Capacity	Large — suitable for millions of rows	Limited — best under 30 million items per library
Relationships	Native table relationships (1:N, N:N)	Lookup columns only, limited relationship support
Business Rules	Built-in, server-side business rules	Limited validation via calculated columns
Security	Row-level, field-level, role-based security	List/item-level only, no field-level
Offline Support	Supported in model-driven apps	Not natively supported for offline
Dynamics 365 Integration	Native — Dynamics 365 runs on Dataverse	No native integration
Licensing Cost	Requires Power Apps or Dynamics 365 license	Included in Microsoft 365 licenses
Complexity	Higher — admin required for setup	Lower — any user can create a list
Audit Logging	Built-in column and record auditing	SharePoint audit logs (less granular)
Best For	Complex business apps, Dynamics 365, enterprise data	Simple team data, document-adjacent data, M365 orgs

Exam Decision Rule

Use Dataverse when the scenario mentions: complex relationships, business rules, row-level security, Dynamics 365 integration, or large data volumes. Use SharePoint when the scenario mentions: simple team data, existing SharePoint investment, cost-conscious (M365 included), or document management alongside data.

Power Platform Environments

Every Dataverse database lives inside a Power Platform environment. Environments are containers for apps, flows, and data — they provide isolation between development and production, between different business units, or between different regions.

Default Environment

Automatically created for every Microsoft 365 tenant. All users in the tenant have access. Not recommended for enterprise apps — limited control over who can create apps.

Sandbox Environment

For development, testing, and training. Can be reset or copied. Ideal for building and testing Power Platform solutions before deploying to production.

Production Environment

Live business applications. More controlled access. Apps and flows running for business operations should live here.

Developer Environment

Individual environments created by developers using a Developer Plan (free). For personal development and testing — not for team collaboration.

Dataverse for Teams Environment

Created when Power Apps is used inside Microsoft Teams. Has a simplified Dataverse (not the full feature set). Limited capacity.

Practice PL-900 Dataverse Questions

Our PL-900 question bank covers Dataverse deeply — tables, relationships, business rules, security, and environments. Start with 40 questions free.

Start Free PL-900 Practice →