You don’t need to be a licensing expert to build on D365 CE, but enough projects get into trouble over licensing assumptions that it’s worth understanding the shape of it — especially since it directly affects what you’re allowed to design.

Base licenses

Each of the main apps — Sales, Customer Service, Marketing, Field Service — is licensed per user, per app, typically in Enterprise and Professional tiers. Enterprise unlocks the full customization surface (custom plugins, advanced business rules, more complex automation); Professional is a lighter, cheaper tier with some customization limits. This matters at the design stage: a client on Professional licenses may not be entitled to use a feature you’re planning to build around.

Attach licenses

If an organization already owns one qualifying D365 license, additional apps can often be added at a steep “attach” discount rather than full price — Microsoft’s way of encouraging multi-app adoption rather than penalizing it.

Power Apps per-app and per-user licensing

Custom apps built on Dataverse that aren’t one of the named CE apps (a canvas app, or a custom model-driven app) are typically licensed separately through Power Apps — either:

  • Per-app — a user is licensed to use one specific app.
  • Per-user — a user is licensed to use any number of apps in the tenant.

This is the license model you’ll run into most often when building custom internal tools on Dataverse rather than configuring the standard Sales/Service apps.

Dataverse storage and capacity

Licenses also entitle a tenant to a pool of Dataverse storage (database, file, and log capacity), tracked at the tenant level in the Power Platform admin center. Large attachment volumes or heavy plugin tracing can quietly eat into this — worth checking if an environment starts behaving oddly.

Why this is a developer concern, not just a sales one. Design decisions — “let’s build this as a separate canvas app,” “let’s give every employee access to this custom table” — have direct licensing cost implications. Flagging that early, even just by asking “do we know this is covered under the current licenses,” saves a very awkward conversation after you’ve already built it.

Licensing terms change fairly often, so for anything with real budget attached, always confirm current details against Microsoft’s official Dynamics 365 pricing page rather than relying on this (or any) summary.