Content reviewed: 12 October 2026

Before buying Dynamics 365, record what each person reads, creates, changes and approves, including custom apps and integrations. Assigned licences and technical roles are different. You need product use rights and an access configuration that respects their scope.

Base and Attach belong to the same user

The verified October 2026 Dynamics 365 licensing guide uses Base and Attach for multiple eligible applications of one named user. Generally, the highest-priced application must be the Base and additional apps must form an allowed combination. The guide documents a Business Central Premium exception. Do not choose the order merely by calling an app the business’s primary system.

Attach is not a standalone cheaper licence for a colleague. The recipient needs their own qualifying Base. Recheck combinations, editions and ordering when duties change. The guide explains licensing; applicable Product Terms and the contract establish binding rights.

Four different decisions
RequirementAssessInsufficient evidence
Full use of one applicationAppropriate full licenceGeneric job title
Several full apps for one personEligible Base + AttachBase assigned to another person
Limited personal tasksSpecific Team Members rightsLow frequency of use
Custom app or integrationOperations, tables and access methodOne licensed service account

Team Members is not a universal reader or support agent

Microsoft Learn describes designated customer-engagement apps: Sales Team Member, Customer Service Team Member and Project Resource Hub. Team Members does not grant unrestricted access to Sales Hub, Customer Service Hub or custom apps. The task must fit the app’s rights and current guide.

The October guide also distinguishes Business Central Team Members from Dynamics 365 Team Members. Similar names do not make rights transferable. Relevant customer-engagement rights are for personal use, not automatically the same tasks on behalf of others. Finance and HR have specifically defined additional options; assess the actual activity.

When tailoring a Team Member app, check the supported module, customisation scope and approved scenario. The October 2026 guide describes a limit on additional tables, while general Learn wording describes an app table limit differently. Confirm the current interpretation for your module before designing at the limit. Table count alone never grants unrestricted operations.

Technical roles can increase licence requirements

Roles determine available actions, not job titles. For Finance and Operations, the guide relates the required licence to accessible securable-object classifications. Adding a higher-tier operation to a shared role can change requirements for every assigned user. Assess granted access as well as actions performed last month.

Learn states that Team Members enforcement does not check every individual operation. Successfully saving a record therefore does not prove licensing. Reconcile entitlements, roles and actual work; use conformance reports as evidence rather than a substitute for assessment.

Power Apps: reading and changing have different boundaries

Restricted-table documentation says a custom app or flow that only reads a table can use suitable Power Apps or Power Automate rights without the corresponding Dynamics app licence. Creating, updating or deleting restricted rows generally requires the relevant Dynamics rights. This is distinct from directly using the Dynamics application.

Explicit exceptions exist. For Case, supported self-service creation and work with self-created cases can use suitable Power Platform licences. That does not permit acting as a support agent managing others’ cases. The limited Work Order exception covers self-reporting a problem, not completing a service job. Both operation and context matter.

The broad table and indirect-reading explanation in the general multiplexing overview are not worded consistently. Assess a specific custom app using current restricted-table documentation, the guide and contractual rules together. The discrepancy does not justify either full Dynamics licensing for every reader or unrestricted access without verification.

Integration and manual entry are different cases

Multiplexing does not reduce licensing by pooling many people through one technical account. Record the end user, app, automation, table and operation. The guide also permits a licensed person to manually enter information received from an unlicensed person; it does not regard that specific process as multiplexing.

Paths to assess
Data pathCheck
A person manually rekeys a colleague’s informationGenuine manual step and entering person’s licence
Custom app only displays Dataverse dataSuitable Power Platform rights, read-only operation and tables
User changes restricted data through a flowDynamics rights or a documented specific exception
Many people use one shared integrationEnd users and actions, not merely the connection account

A hypothetical business has an issue-reporting form and a separate technician app. People only reporting problems may fit a supported self-service scenario. A technician scheduling and closing others’ jobs performs different work. Sharing a database does not necessarily mean every group needs the same licence.

Before purchasing or changing roles

  1. 01

    List operations

    Read, create, change, delete, approve and act on behalf of others

  2. 02

    Map the data path

    Dynamics app, custom app, flow, API, manual entry and end users

  3. 03

    Verify specific rights

    Apps, editions, tables, documented exceptions and customer contract

  4. 04

    Assign eligible licences

    Base and Attach to the same person; limited licences for matching scenarios

  5. 05

    Reconcile roles with the design

    Access, conformance evidence, pilot and reassessment when operations change

Keep a record grouped by actual work, rather than merely purchased SKUs. Review current guidance before renewal and after integration changes. Retain the date and sources supporting the conclusion.

Frequently asked questions

Can one person hold Base and another only Attach?

Not as a Base/Attach combination. Attach needs a qualifying Base for the same named user.

Does Team Members cover occasional full case management?

Frequency does not change rights. Assess the task under the actual app and Team Members scenario.

Does every read through a custom Power App need a full Dynamics licence?

Not automatically. Restricted-table guidance distinguishes reading from changes. Verify the qualifying Power Platform rights and actual design.

Does a service account remove other users’ licence requirements?

No. Pooling connections alone does not reduce required licences. Identify end users and operations.