Collab365

Help with Licensing and/or permissions for adding tables to Dataverse through Power Apps

Q: Does a Microsoft 365 E3 licence allow creation of full Dataverse tables?

No. M365 E3 is restricted to Dataverse for Teams (2 GB limit). Power Apps Premium licence is required for unrestricted tables at make.powerapps.com.

Q: What is the difference between Environment Maker and System Customizer roles?

Environment Maker allows canvas apps and flows but no Dataverse schema changes. System Customizer grants full rights to create/edit tables.

Q: How to check if my environment has a Dataverse database?

In Power Platform admin center, select environment. If 'Add Dataverse' button shows, no database exists; provision it first.

C

Collab365 TeamAuthorPublished Apr 23, 2026

2

At a Glance

Target Audience: Power Platform Admins, Citizen Developers, Power Apps Makers
Problem Solved: Greyed-out 'New Table' button in Power Apps due to missing Dataverse database, inadequate licensing (e.g., M365 E3), or lacking System Customizer role.
Use Case: Migrating from SharePoint lists to relational Dataverse tables for complex apps like engineering asset tracking.

The "New Table" button greys out in Power Apps if your environment lacks a Dataverse database, you miss System Customizer/Admin roles, or your licence (like E3) doesn't include full Dataverse write access.1 Here is the fix. To resolve this immediately, three prerequisites must align: you need a premium Power Apps licence, explicit environment-level security roles, and an actively provisioned Dataverse backend.3 We see this snag constantly in the community, and front-loading these three checks will save you hours of frustration.

Key Takeaway: Resolving a greyed-out "New Table" button requires a synchronised approach. You must check your licensing limits, your environment's database status, and your granular security role assignments.

> TL;DR / Quick Fix Checklist:

Licence Check: Ensure your user account holds a Power Apps Premium licence ($20/user/month). Standard M365 E3 plans limit Dataverse strictly to Teams environments.5
Environment Selection: Verify the active environment in the top-right corner of make.powerapps.com. Avoid the Default environment, which increasingly restricts custom table creation.8
Database Provisioning: Navigate to admin.powerplatform.microsoft.com > Environments. Confirm a Dataverse database is actively added to your selected environment.3
Role Assignment: Assign the user the System Customizer or System Administrator role via Settings > Users + Permissions > Security roles.11
Test Creation: Refresh the Power Apps studio, select the Tables tab, and confirm the "+ New Table" button is fully active and clickable.10

Who Is This Guide For? ## Prerequisites

This post is a direct replacement for an older 2023 Collab365 forum thread. We have completely updated it to reflect the 2026 realities of the Power Platform. We wrote this specifically for power users, citizen developers, and engineers who find themselves unexpectedly blocked by IT governance policies.

Consider Bill, a Collab365 member and senior electrical engineer. Bill has about two years of basic M365 and Power Apps experience. In 2023, he needed to build an application to track complex lifecycles for high-voltage transformers and substations. He initially used SharePoint lists, but quickly realised that SharePoint drops data when handling complex relational hierarchies.

Key Takeaway: SharePoint lists are flat files masquerading as databases. For complex, relational engineering data, you must migrate to Dataverse.

Bill decided to migrate his data to Dataverse to use proper relational tables. He logged into Power Apps, clicked on the Tables tab, and hit a brick wall. The "+ New Table" button was entirely greyed out. When he hovered over it, a privilege error appeared. Bill had an M365 E3 licence and a Power BI Pro licence, so he assumed he had full access to the Microsoft ecosystem. He was wrong.1

By 2026, here is the update. If you are in Bill's shoes—needing custom tables for critical apps but facing greyed-out buttons because IT hasn't set the correct licences or environment roles—this guide is your roadmap.

Essential Prerequisites

Before we dive into the exact menu clicks, you must secure a few foundational elements.

A Premium Power Apps Licence: You cannot build full Dataverse tables on a standard Office 365 or M365 E3 licence. You must secure a Power Apps Premium licence, a Dynamics 365 enterprise licence, or work in an environment covered by Pay-as-you-go Azure meters.6
Environment-Level Administrator Access: You need IT to grant you access to the Power Platform admin center, or you need an active administrator willing to follow this guide and perform the role assignments for you.3
Available Tenant Capacity: Your organisation must have at least 1 GB of available Dataverse Database capacity. If your tenant is out of storage, the system blocks the creation of new databases entirely.14

Key Takeaway: Do not attempt to fix a greyed-out button without first verifying your tenant has at least 1 GB of pooled Dataverse database capacity remaining.

Why Is My "New Table" Button Greyed Out in Power Apps 2026?

When you navigate to make.powerapps.com, select the Tables tab on the left navigation pane, you expect to start building. (Screenshot shows grey button under Tables tab in make.powerapps.com, with a yellow warning banner stating 'One or more commands are unavailable due to your current privileges'.1)

If that button is inactive, the system is actively enforcing one of four distinct governance or architectural constraints. Let us break them down.

1. The Environment Lacks a Dataverse Database

Environments in the Power Platform act as security and data boundaries. However, creating a new environment does not automatically create a Dataverse database inside it.17 An administrator might create an environment purely to host simple canvas apps that connect to external data sources like SQL Server or SharePoint.

If the environment lacks that foundational Dataverse backend, there is nowhere to store the tables. The platform recognises this and completely disables the table creation interface.10 We see this snag in dozens of setups where IT provisions the shell of an environment but forgets to initialise the SQL backend.

Key Takeaway: An environment without an explicitly added Dataverse database cannot host custom tables. The UI will lock you out to prevent data orphans.

2. Missing Security Roles (System Customizer or Administrator)

Dataverse uses a highly granular, role-based access control (RBAC) system. When IT adds you to an environment, they typically assign you the default Environment Maker role.

This role sounds powerful, but it is intentionally restricted. It permits you to create canvas apps, Power Pages, and Power Automate flows, but it explicitly denies the privileges required to modify the database schema.4 To create a new table, you are attempting to alter the database architecture. Only users assigned the System Customizer or System Administrator roles possess these architectural permissions.11

3. Licensing Restrictions (The M365 E3 Limitation)

This is where 70% of users hit a wall. Many enterprises operate on Microsoft 365 E3 or E5 licences. Users assume these expensive licences encompass complete Power Platform capabilities. They do not.

Standard M365 licences include restricted usage rights tailored purely for personal productivity. They allow you to use Dataverse for Teams, which is a lightweight version of the database restricted entirely within the Microsoft Teams interface, bound by a strict 2 GB storage limit per team.2 If you try to build a full model-driven app or standalone Dataverse table at make.powerapps.com using an E3 licence, the system blocks you with a privilege error.2

Key Takeaway: E3 limits you to Teams Dataverse. If you need enterprise-grade relational tables accessible outside of a Teams channel, you must upgrade to a full Power Apps Premium licence.

4. Entra ID Synchronisation Delays

Sometimes, your IT department does everything correctly. They assign the Power Apps Premium licence. They assign the System Customizer role. Yet, the button remains greyed out.

This happens due to synchronisation latency between Microsoft Entra ID (formerly Azure AD) and the local Dataverse security tables. When IT updates your profile, that token claim must propagate through the Microsoft cloud. This delay can take anywhere from five minutes to a few hours. Users often need to clear their browser cache, sign out entirely, or have an admin run a forced diagnostic sync to resolve the latency.18

Dataverse Licensing Requirements for Creating Tables

The licensing landscape for Dataverse underwent massive changes leading up to 2026. A clear understanding of these tiers is mandatory if you want to explain to your IT department exactly what you need.

According to Collab365 research, licensing confusion is the number one reason IT departments hesitate to unlock table creation capabilities. They fear hidden costs. Let us clarify the exact 2026 pricing and capabilities.

The End of Sale for the Power Apps Per App Plan

Historically, if an engineer like Bill needed to build one specific app with Dataverse, IT would purchase the "Power Apps per app" plan. It was highly affordable at $5 per user/app/month.19

However, effective January 14, 2026, Microsoft officially removed the Power Apps per app SKU from the licensing guide for new purchases.20 Microsoft made this decision because tracking individual app usage became an administrative nightmare for tenant managers. While existing enterprise customers locked into an Enterprise Agreement can continue to use and renew this licence, new deployments must pivot to alternative models.20

Key Takeaway: The affordable $5 per app plan is dead for new customers in 2026. You must plan your architecture around Premium licences or pay-as-you-go Azure meters.

2026 Microsoft Power Apps Pricing Comparison

To fully enable the creation and management of Dataverse tables across unrestricted environments today, users must secure the Power Apps Premium licence.5

Here is how the current landscape breaks down:

Licence Type	Table Creation Rights	Access Scope	2026 Pricing (per user/month)
M365 E3 / E5	Limited	Only within Dataverse for Teams (2 GB limit).7	Included in M365 subscription.
Power Apps Per App	Full	One specific custom app.19	$5 (End of Sale Jan 2026 for new customers).20
Power Apps Premium	Full	Unlimited apps, premium connectors, full Dataverse.5	$20.5
Pay-As-You-Go	Full	Billed via linked Azure subscription based on active use.3	Varies by active usage.

(Prices cited from official Microsoft Power Apps pricing documentation).

Many E3 users hit this wall. They attempt to stretch standard Office 365 entitlements into enterprise-grade relational database design, which the platform actively prevents. You must make the business case for the $20 Premium licence if you want to build serious data structures.

2026 Dataverse Capacity Units and Storage Increases

Licensing also dictates the storage capacity allocated to your entire organisation. This is a critical point. A user attempting to provision a database to fix their greyed-out button will fail entirely if the tenant lacks at least 1 GB of pooled Dataverse database capacity.14

In late 2025 and early 2026, Microsoft significantly increased default storage entitlements. They did this to support the massive rise of AI-driven applications and metadata storage requirements.22

Key Takeaway: Microsoft doubled the default Dataverse database capacity for Premium tenants in 2026, giving you more headroom to provision new environments without immediately buying storage add-ons.

According to the official Licensing documentation, the Power Apps Premium tenant-level default Dataverse capacity increased from 10 GB to 20 GB for the database, and from 20 GB to 40 GB for file storage.21

This means if your IT department claims they cannot give you an environment because "Dataverse storage is too expensive," you can gently remind them that their baseline entitlements just doubled at no extra cost.24

Step-by-Step: Provision Dataverse Database & Assign Permissions

If your tenant possesses the correct licensing and capacity, you must systematically configure the environment. Here is what we recommend. We wrote these steps so you can literally copy and paste them into an email to your IT admin if you lack the access to do it yourself.

Step 1: Provision the Dataverse Database

If the environment lacks a data store, the interface remains completely locked. You must use the Power Platform admin center to attach a database to the environment.10

Sign in to admin.powerplatform.microsoft.com using an account with Dynamics 365 or Power Platform admin rights.3
In the left navigation pane, select Environments.
Select the specific environment where you intend to build the application.
Look at the central overview pane. If the environment lacks a database, a prompt will explicitly state "Add Dataverse web part." Click the + Add Dataverse button.10
A configuration panel will slide out. Select the default language and currency for the database.3
Click Save. The provisioning process will begin.

Key Takeaway: Provisioning the database is an irreversible action. The currency and language you select will permanently dictate the base formatting for all financial rollup columns in that environment. Choose carefully.

It typically takes several minutes for the Microsoft cloud to initialise the Azure SQL backend, deploy the core system tables, and report an "Active" status. Do not rush this process.

Step 2: Assign the System Customizer Role

Once the database confirms an "Active" status, providing basic access to the environment is insufficient. The user needs explicit schema modification rights. IT must map your account to the correct security role.4

While still inside the Power Platform admin center, ensure your target environment is selected.
Navigate to Settings > Users + permissions > Users.13
Locate the specific user (e.g., our senior electrical engineer, Bill) from the list. If the user is absent, select Add users and search Microsoft Entra ID to invite them into the environment.
With the user selected, click Manage security roles in the top command bar.16
A side panel will appear with an extensive list of roles. Scroll down and check the box next to System Customizer.11
Click Save to commit the assignment.

Understanding the Role Duties Matrix

We see administrators make a critical mistake here constantly. They get frustrated with permissions, give up, and assign the user the Global Administrator or System Administrator role just to make the greyed-out button disappear.

Assigning roles blindly introduces severe governance risks. Collab365 strongly recommends adhering to the principle of least privilege. You should only give users the exact permissions they need to do their job.

Here is the definitive role matrix for 2026:

Security Role	App Creation Rights	Dataverse Schema Rights (Tables)	Data Access Limitations
Environment Maker	Full (Canvas, Automate)	None (Button is greyed out)	Cannot access or view Dataverse data.4
System Customizer	Full	Full (Can create/edit tables)	Can view all custom tables, but only views rows in core tables (Accounts, Contacts) that they explicitly created.11
System Administrator	Full	Full (Can create/edit tables)	Has full, unrestricted permission to view all data and manage security policies across the environment.11

Key Takeaway: Never grant the System Administrator role to standard users simply to bypass the greyed-out button. The System Customizer role provides the exact privileges required for table creation while maintaining data boundaries.

Best Practice: Use Entra ID Group Teams

Instead of assigning the System Customizer role to individual users one by one, enterprise IT departments should use Microsoft Entra ID (formerly Azure AD) groups.13

You create an Entra security group called "Power Apps Table Designers." You map that group to a Dataverse Team in the admin center, and you assign the System Customizer role to that Team.13 From that point forward, IT simply adds or removes users from the Entra group. The Dataverse security model automatically inherits those changes, instantly enabling or disabling the "New Table" button for those users without requiring manual admin center clicks.

Restricting Environment Creation via PowerShell

If you give users too much power, they might try to circumvent your permission structures by spinning up their own unmanaged Developer environments where they are the automatic owner.

Administrators can prevent this by deploying PowerShell cmdlets to restrict environment creation. By executing $requestBody = [pscustomobject]@{ powerPlatform = [pscustomobject]@{ governance = [pscustomobject]@{ disableDeveloperEnvironmentCreationByNonAdminUsers = $True } } } followed by the Set-TenantSettings command, IT ensures that only global administrators dictate where databases reside.14 This keeps your tenant clean and governs where tables are built.

Default Environment vs Dedicated: Which to Use for Tables?

A very common pitfall observed by Collab365 involves users attempting to construct highly relational, mission-critical Dataverse tables inside the tenant's Default environment.

Every single Microsoft tenant comes with a Default environment. Every user in your organisation automatically has the Environment Maker role there.2 While the Default environment technically permits table creation if the user holds a premium licence and the Customizer role, architectural changes in 2024 and 2026 strongly discourage this practice.

The Shift Away from the Default Environment

Think of the Default environment like a crowded public whiteboard. It serves well as a shared personal productivity space. But as thousands of simple flows and canvas apps accumulate, it transforms into an unmanageable, chaotic repository.26

In October 2024, Microsoft started tightening the screws. They deprecated support for multitenant apps without a service principal in the Microsoft Entra ID target tenant, increasing the security stringency across all Dataverse platforms.27

Key Takeaway: Building complex Dataverse architectures in the Default environment exposes your organisation to governance failures and data leaks. Always provision dedicated sandbox or production environments for custom tables.

By 2026, Microsoft introduced specific features within Managed Environments to extract assets out of the Default environment. The "Move apps from the default environment" capability, released in general availability in April 2026, allows administrators to systematically migrate canvas apps and custom SharePoint forms to designated, governed environments.9

If Microsoft is actively building tools to help you evacuate the Default environment, you should absolutely not be building new Dataverse tables there.

Environment Strategy Comparison

Environment Type	Database Status	Governance Posture	Best Use Case
Default Environment	Pre-provisioned	Poor (Shared by all tenant users)	Personal productivity, basic SharePoint form modifications.2
Dataverse for Teams	Auto-provisioned	Rigid (Tied to Microsoft Teams roles)	Small, localized tools within a specific Team (2 GB limit).7
Dedicated Production	Manually provisioned	Excellent (Full RBAC and ALM control)	Enterprise-grade applications, complex relational databases, Managed Environments.8

Furthermore, when deploying solutions across dedicated environments, developers can now utilise the 2026 Git integration pipelines natively within the Power Platform. This allows engineers to push Dataverse schema changes through Azure DevOps pipelines, ensuring that only code-reviewed and approved tables reach the production database.28 You cannot do this cleanly in the Default environment.

Troubleshooting: Still Can't Create Tables After Setup?

Even after configuring licences, provisioning databases, and assigning the System Customizer role, you may encounter persistent errors. The system can be notoriously stubborn.

When the platform blocks an action, it frequently displays a yellow banner at the top of the screen stating: "One or more commands are unavailable due to your current privileges for this environment".1

Running User Diagnostics

Do not panic and start randomly changing settings. The most effective troubleshooting method is the built-in diagnostic utility.

Administrators should navigate to the(https://learn.microsoft.com/en-us/power-platform/admin/database-security) configurations in the Power Platform admin center, locate the user, and click Run diagnostics.4

This tool performs a deep system check. It assesses group memberships, forces a hard sync with Entra ID, and verifies recognised service plans.18 Often, just running the diagnostic forces the cached tokens to refresh, and the "New Table" button magically turns blue.

Key Takeaway: If roles and licences are correctly configured but the button remains greyed out, running the User Access Diagnostics tool forces a synchronization with Entra ID to resolve the caching latency.

Common Dataverse Privilege Error Codes

When interacting with the Dataverse Web API or attempting table manipulations, the system generates specific hexadecimal error codes.30 Identifying these codes expedites resolution. Do not ignore the gibberish error codes; they tell you exactly what is broken.

Error Code	Error Name	Underlying Cause	Resolution
0x80048370	AccessCheckOrganizationMismatch	The user's OrganizationId does not match the environment's OrganizationId.31	Ensure the user is authenticated in the correct tenant and environment context. Clear browser cache.
0x80048350	AadGroupTeamsCanOnlyAssignInheritableRoles	Attempted to assign a "Team Privileges only" role to an Entra group.31	Modify the security role inheritance settings to support group-based assignment.
0x80048405	AccessDenied	The user lacks the fundamental CreateAccess right for the specific entity metadata.30	Verify the System Customizer role is actively applied and Entra ID has synchronised.
0x80048d2f	AccessModeChangeNeedSystemAdmin	User lacks administrative rights to alter access modes.31	Escalate to a Global or Power Platform Administrator to perform the operation.

The "Append To" vs "Append" Privilege Trap

Here is a highly specific issue that trips up even experienced makers. Let us say you finally fix the "New Table" button. You build a Transformers table and a Maintenance Logs table. You create a Lookup column on the Maintenance Logs table that points to Transformers.

When your users try to add a new maintenance log via a SubmitForm function in a canvas app, they get a privilege error.32

Why? Because Dataverse requires distinct privileges for relationships. To link a child record to a parent record, the user needs the Append privilege on the child table (Maintenance Logs) AND the Append To privilege on the parent table (Transformers).32 If your custom security role misses either of these granular permissions, the system blocks the table operation entirely. Always cross-reference the user's specific table privileges within their assigned security role.32

Power Apps Table Designer: Build Your First Table in 2026

Once the greyed-out button is resolved and turns a vibrant blue, you are ready to build. The modern Power Apps Table Designer offers capabilities that far surpass the legacy classic interfaces from a few years ago.

The 2026 release waves introduced deep integrations with artificial intelligence and external protocol standards. This fundamentally altered how data architectures are deployed in the Microsoft ecosystem.

AI-Assisted Schema Generation with Copilot

You no longer need to manually construct every single column. Makers can now build applications and underlying tables through natural language conversation with Copilot.34

By describing the business requirement in plain English (e.g., "Create a relational system to track electrical components, their maintenance schedules, and associated supplier contracts"), Copilot autonomously suggests the required Dataverse tables. It selects the optimal column data types, suggests choice values, and even establishes the necessary one-to-many or many-to-many relationships.35 This drastically reduces the time required to build a normalised database.

Furthermore, note that the 2026 modern look mandate is now fully enforced. It provides a refreshed, consistent user experience across all model-driven apps, officially deprecating the legacy classic theming mechanisms you might be used to.34

Key Takeaway: Copilot can generate your entire Dataverse schema in seconds, but you still need the System Customizer role to save that schema into the environment.

Integrating the Dataverse Model Context Protocol (MCP) Server

The most significant architectural leap for Dataverse in 2026 is the introduction of the Model Context Protocol (MCP) server. If you are an engineer, you need to pay attention to this.

MCP is a new open standard that permits large language model (LLM) applications to interact seamlessly with real, live business data.36 Microsoft shipped the MCP server integration natively inside Power Apps in April 2026.37

This integration exposes your newly created Dataverse tables as a full MCP server. It provides intelligent, schema-aware access to records for external AI agents, such as those built in Microsoft Copilot Studio or Claude Desktop.36

It is vital to distinguish between the two layers of MCP functionality:

Dataverse MCP: This exposes Dataverse data outward to AI agents. Developers use this when building an agent that needs to query historical records, analyse metadata, and securely execute read/write operations against the custom tables you just built.39
Power Apps MCP: This allows your application UI to call external AI models inward. App makers use this to embed AI reasoning directly inside the application interface to assist users.39

Resolving the "New Table" button not only allows for manual data entry but unlocks the ability to expose that data to advanced AI agents via the 2026 Dataverse MCP server framework. This turns your static database into a dynamic AI brain.

Optimizing Offline Capabilities with FetchXML

If you are like Bill, deploying applications to field workers operating in remote substations without internet connectivity, offline resilience is paramount.35

In March 2026, Microsoft introduced the FetchXML editor for offline profiles in the Power Apps mobile client.34 This allows advanced makers to write raw FetchXML queries directly into the studio to define custom synchronisation filters. It supports advanced features like unrelated tables and latematerialize="true".

This precise control over the synchronisation payload prevents timeouts on large tables and ensures your field applications remain highly performant even when downloading thousands of maintenance logs over a weak 3G connection.34

Frequently Asked Questions (FAQ)

To wrap this up, let us address the top five questions we see on the Collab365 forums regarding this specific issue.

1. Does a Microsoft 365 E3 licence allow the creation of full Dataverse tables? No. M365 E3 licences are fundamentally restricted to Dataverse for Teams. This permits the creation of tables strictly within the context of a specific Microsoft Teams environment, bound by a hard 2 GB storage limit. To create unrestricted tables at make.powerapps.com, a Power Apps Premium licence is absolutely required.2

2. What is the difference between an Environment Maker and a System Customizer? An Environment Maker can build canvas apps and Power Automate flows, but they possess zero privileges to access, create, or modify Dataverse data tables. The System Customizer role elevates those permissions, granting the necessary rights to define new schema elements and interact with the database directly.4

3. How do I check if my environment actually has a Dataverse database? Administrators must sign in to the Power Platform admin center, select the specific environment, and view the central summary pane. If the pane displays a prominent "Add Dataverse" button, the database does not exist. It must be provisioned before table creation is allowed.3

4. Can I still purchase the Power Apps per app licence to save costs? No. Effective January 14, 2026, Microsoft officially removed the $5 Power Apps per app SKU from sale for new customers. Organisations must utilise Power Apps Premium ($20/user/month) or Azure pay-as-you-go meters for new deployments, though existing Enterprise Agreements may allow temporary renewals until the contract ends.5

5. How much Dataverse capacity is included by default in 2026? Following the December 2025 capacity increases designed to support AI workloads, a tenant with Power Apps Premium licensing receives a default baseline of 20 GB for the Dataverse Database and 40 GB for Dataverse File storage. This provides substantial room for enterprise table deployment without immediate overage fees.21

Next Steps

Restoring the "New Table" button is merely the first step in architecting robust, scalable enterprise solutions on the Power Platform. By ensuring the correct alignment of Premium licensing, database provisioning, and precise RBAC role assignments, administrators safeguard their tenant against governance sprawl while empowering developers to build securely.

Test in your tenant now. Verify your licences, check your environment's database status, and ensure you have the System Customizer role.

We recommend starting with Collab365 Spaces' dedicated to Power Apps for insights, research and more.