What is Dataverse?

What is Dataverse?

Why not just use a regular database?

You might wonder: why would Coastal Logistics use Dataverse instead of just setting up a SQL Server database? After all, SQL Server is powerful and well-known.

The answer is speed, security, and integration — all without needing a database administrator.

Aisha’s scenario

Aisha is the IT admin at Coastal Logistics (800 staff). Her operations team wants an app to track equipment inspections. In the old world, Aisha would need to:

1. Provision a SQL Server or request one from the infrastructure team
2. Design the schema — tables, columns, data types, relationships, constraints
3. Write stored procedures for validation logic
4. Build an API layer so apps can connect
5. Configure security — database roles, row-level permissions, encryption
6. Set up backups and disaster recovery
7. Maintain it forever — patching, scaling, monitoring

With Dataverse, her operations team creates the table directly inside Power Apps, adds columns through a visual interface, and security inherits from the environment settings. Aisha reviews the security roles, and the app is live by lunchtime.

Dataverse vs traditional databases

Traditional databases vs Microsoft Dataverse

Feature	Traditional Database	Dataverse
Setup	Install, configure, and maintain a server	Already running — create tables in the browser
Schema design	Write SQL CREATE TABLE statements	Visual table designer — click to add columns
Security	Configure database roles, connection strings, firewall rules	Built-in security roles, row-level and column-level security, Entra ID integration
Business logic	Write stored procedures, triggers, application code	Business rules, calculated columns, Power Automate flows — no code
API access	Build and maintain your own REST API	Automatic REST API for every table (OData endpoints)
Backups	You configure backup schedules and storage	Automatic daily backups with point-in-time restore
Scaling	You plan capacity, add servers, configure replication	Managed by Microsoft — scales automatically
Standard tables	Start from scratch every time	400+ pre-built tables (Accounts, Contacts, etc.)
File/image storage	Separate blob storage service needed	Built-in file and image columns
Integration	Custom connectors for each app	Native to Power Apps, Power Automate, Dynamics 365, and Copilot Studio

Standard tables — the head start

Dataverse comes with over 400 standard tables. These are pre-built, well-structured tables designed around common business scenarios:

Standard Table	What It Stores	Used By
Account	Companies, organisations	Sales, service, custom apps
Contact	Individual people	CRM, communication, forms
Activity	Emails, calls, tasks, appointments	Relationship tracking
User	System users and their security roles	Security, assignment, audit
Team	Groups of users	Security, ownership
Note	Attachments and text notes	Any record with notes
Email Message	Tracked emails	Dynamics 365, Outlook integration

You never need to build these from scratch. If you deploy Dynamics 365 Sales, the Account and Contact tables are already populated with the right columns and relationships.

💡 Can I modify standard tables?

Yes. You can add custom columns to standard tables, but you cannot delete the built-in columns. This protects the data model that Microsoft applications depend on.

For example, you could add a “Preferred Shipping Method” column to the standard Account table without breaking anything that already uses it.

Custom columns you add are prefixed with your publisher prefix (e.g., cr4e2_preferredshipping) to avoid naming conflicts.

Dataverse environments

Every Dataverse instance lives inside a Power Platform environment. Think of it as a container — each environment has its own Dataverse database, its own security settings, and its own apps.

Aisha manages several environments at Coastal Logistics:

• Default — where everyone lands, used for personal productivity apps
• Production — the live equipment tracking app
• Dev — where makers build and test before promoting to production

We will cover environments in detail in Module 9. For now, the key point is: Dataverse data is always scoped to an environment. Data in the Dev environment is completely separate from Production.

ℹ️ Does every environment get Dataverse?

Not automatically. Dataverse is provisioned per environment. Some environments (like the default) may not have a Dataverse database until someone creates one.

Creating a Dataverse database in an environment requires either Power Apps, Power Automate, or Dynamics 365 licensing — or an admin to provision it manually from the Power Platform admin center.

🎬 Video walkthrough

🎬 Video coming soon

What is Dataverse? — PL-900 Domain 2

What is Dataverse? — PL-900 Domain 2

~10 min

Flashcards

Question

What is Microsoft Dataverse?

Click or press Enter to reveal answer

Answer

A cloud-based, low-code data platform built into the Power Platform. It provides a secure, scalable relational data store with built-in business logic, security, automatic APIs, and 400+ standard tables.

Click to flip back

💡 Show hint

Question

How many standard tables does Dataverse include?

Click or press Enter to reveal answer

Answer

Over 400 standard tables — including Account, Contact, Activity, User, Team, and Note. These align with the Common Data Model and are used by Dynamics 365 applications.

Click to flip back

💡 Show hint

Question

What does Dataverse provide automatically that a traditional DB requires you to build?

Click or press Enter to reveal answer

Answer

Automatic REST APIs (OData), built-in security roles, row/column-level security, daily backups, business rules, calculated columns, file/image columns, and Entra ID integration.

Click to flip back

Question

Where does Dataverse data live?

Click or press Enter to reveal answer

Answer

Inside a Power Platform environment. Each environment has its own Dataverse database, security settings, and apps. Data in one environment is completely separate from another.

Click to flip back

💡 Show hint

Knowledge Check

Knowledge Check

Aisha needs a data store for a Power Apps application that will track equipment inspections. She wants built-in security, automatic APIs, and no server maintenance. Which option is best?

AAzure SQL Database — full relational database with T-SQL supportBSharePoint list — already available in Microsoft 365CMicrosoft Dataverse — cloud data platform native to Power PlatformDExcel workbook stored in OneDrive — simple and familiar

Check Answer

Knowledge CheckSelect all that apply

Which of the following are advantages of Dataverse over a traditional SQL Server database? (Select TWO)

ADataverse uses a proprietary query language instead of SQLBDataverse provides 400+ standard tables out of the boxCDataverse automatically generates REST API endpoints for every tableDDataverse does not support relational data

Check Answer

Knowledge Check

In Dataverse, what is a standard table?

AA table you create from scratch for your specific business needsBA pre-built table included with Dataverse that follows the Common Data ModelCA virtual table that connects to an external data sourceDA temporary table used only during data imports

Check Answer

---

Next up: We will dive into how tables, columns, and relationships work inside Dataverse — including business logic options that bring your data to life.