How BC’s licensing model works, which user type Finance should specify for each Finance role, what the license cost implications are of common Finance configuration decisions, the external accountant access option Finance often overlooks, and the five licensing decisions that generate unexpected Microsoft invoices Finance did not budget for.
The BC License Types Finance Must Understand
BC Essentials
The standard full-access license for most BC users. Includes the core Finance modules (GL, AP, AR, bank, fixed assets, budgeting), Supply Chain (purchasing, inventory, sales), and Project Management. Does not include Manufacturing (production orders, capacity planning) or Service Management.
Appropriate for: Controllers, Finance managers, AP coordinators, AR coordinators, purchasing managers, warehouse supervisors, and any user who needs full posting and transaction access in the covered modules.
Finance implication: Every user who needs to post transactions, run financial reports, or approve invoices in BC requires an Essentials or Premium license. Team Members cannot post transactions.
BC Premium
Includes everything in Essentials plus Manufacturing (production orders, BOMs, routing, capacity planning) and Service Management (service contracts, service orders, service items). Required for any user who must work with production orders or service module features.
Appropriate for: Production planners, shop floor supervisors, service managers, and any Finance user who must post production output journals, review WIP, or access manufacturing reports. If Finance needs to review production cost variances in BC, Finance requires a Premium license (or access through a named Premium user).
Finance implication: In manufacturing companies, the Controller typically needs Premium to access the full production accounting picture. Finance must confirm whether the management reports Finance uses require Premium module access or whether they are available under Essentials.
Team Members
A significantly lower-cost license designed for users who need limited, read-oriented access to BC. Team Members can: read any BC data, enter timesheets, submit expense reports, create and edit basic documents (quotes, orders) up to a limited scope, and approve workflow requests.
Appropriate for: Managers who need to approve purchase invoices (through the approval workflow) but do not post transactions themselves, employees who submit expense reports, executives who view reports but do not post.
Finance implication: Approval workflow approvers who do not need to post transactions can often use Team Members licenses, significantly reducing license cost for users who exist solely to approve Finance workflow steps. Finance must confirm with the Microsoft partner that the specific approval actions required by the workflow are within Team Members scope.
Device License
A per-device license rather than a per-user license. Designed for shared workstations in warehouses, shop floors, or retail environments where multiple people use the same device to perform specific, limited BC actions. One device license covers all users of that device.
Appropriate for: Warehouse scanner stations, shop floor terminals, reception desks where multiple staff use BC for specific narrow tasks (receiving goods, recording timesheets, looking up order status).
Finance implication: Rarely relevant for Finance workflows, but Finance teams in warehouse-heavy businesses should be aware that shared warehouse device licenses do not provide Finance-level access and cannot be used for transaction posting that requires individual user accountability.
External Accountant (Free)
Microsoft provides up to three free External Accountant user accounts per BC tenant. External Accountant users have similar access to Essentials users and can view and review transactions, run reports, and access the full BC environment. They cannot create users or access certain system administration areas.
Appropriate for: External auditors who need BC access for audit procedures, the external bookkeeper or accountant who reviews the books monthly, the tax advisor who accesses BC during tax return preparation. These are the three free licenses Finance most often pays for unnecessarily when they are not aware of the External Accountant option.
Finance implication: Every external Finance professional who regularly accesses the organization’s BC environment should be assigned an External Accountant license rather than a paid Essentials license. Finance confirms with the Microsoft partner that the external user’s access requirements are within External Accountant scope.
Finance Role-to-License Mapping—What Finance Should Specify for Each Role
Finance Role License Guide—Verify Current Scope With Your Microsoft Partner
Where Finance Configuration Decisions Create Licensing Costs
Finance teams are occasionally surprised to find that configuration choices they made for operational reasons have licensing cost consequences that were not in the implementation budget. The four most common:
Power Automate Premium Connectors
BC’s standard connector for Power Automate is included in most Microsoft 365 license tiers. However, flows that connect BC to third-party systems (non-Microsoft services, custom API endpoints, certain database connectors) use “premium connectors” that require a Power Automate Premium per-user license for each user whose flows use them. Finance that builds an invoice approval flow connecting BC to a third-party accounts payable platform may inadvertently require Power Automate Premium licenses for all Finance users who trigger or are notified by the flow.
Power BI Premium Per User for BC Reports
Power BI reports built on BC data can be shared in Power BI Service (the web-based report sharing platform). The sharing model determines the license cost: reports shared in a Power BI Premium workspace do not require viewers to have a Power BI Premium Per User license. Reports shared in a standard workspace require every viewer to have Power BI Pro or Premium Per User. Finance teams that build management dashboards in Power BI and share them widely through a non-Premium workspace may trigger a license requirement for every manager who views the dashboard.
Additional Environments
BC subscriptions typically include one production environment and one sandbox environment. Additional environments (a second sandbox for release wave testing, a training environment, a separate legal entity in its own environment) require additional environment licenses. Finance teams that want to test release waves in a dedicated environment separate from the primary sandbox may need to budget for the additional environment cost before requesting it.
Exceeding User Count Mid-Year
BC licenses are named user licenses—each active BC user requires their own license. When the organization adds users beyond the contracted count (new Finance hire, new approval workflow participant, temporary seasonal staff), the additional users are billed at the per-user rate in the current subscription. Finance should include BC user license cost in the annual HR/Finance headcount budget—not just the implementation cost—so that license additions from planned headcount changes are budgeted in advance.
Five Licensing Decisions That Generate Unexpected Microsoft Invoices
⚠️ External Accountant Seats Paid As Essentials—Paying for Licenses Microsoft Provides Free
The organization’s external bookkeeper, external auditor, and tax advisor each have Essentials licenses in BC. Nobody mentioned the External Accountant license option during the implementation. The three paid Essentials licenses cost approximately £2,400 per year (at typical Essentials pricing). The three External Accountant licenses that would cover the same access are provided free by Microsoft. The organization has been paying £2,400 per year for three years for licenses that were available at no cost. Finance discovers the External Accountant option when reviewing the BC license structure with the implementation partner during a system optimization engagement.
Fix: Before finalizing the license count for any BC implementation or renewal, Finance identifies every external user who needs BC access—auditors, external accountants, tax advisors, external consultants who need periodic read access. For each, Finance confirms whether External Accountant access covers their requirements (most external Finance professional use cases are within scope). Any external user whose access requirements are within External Accountant scope should be moved from a paid license to the free External Accountant slot before the next renewal. The three free External Accountant licenses are intended for exactly this use case. Using paid licenses for external Finance professionals when the free option covers the requirement is a consistent and avoidable cost.
⚠️ All Approval Workflow Participants Licensed as Essentials When Team Members Would Suffice
Finance configured a purchase invoice approval workflow with three approval levels: the AP Coordinator’s line manager (Business Unit Manager), the Finance Director, and the CFO. All three approvers were assigned Essentials licenses because the implementation partner recommended Essentials for “all active BC users.” The three approvers have no other BC activity—they log into BC only to approve or reject workflow requests. At typical Essentials pricing, three users who exclusively approve workflow requests cost approximately £2,400 per year in license fees. Team Members licenses, which typically include approval workflow actions, would cost approximately £600 per year for the same three users. The organisation overpays £1,800 per year for approval-only users because nobody evaluated whether Team Members scope covered the approval workflow action.
Fix: For each BC user whose activities are limited to approval workflow participation, Finance evaluates whether Team Members scope covers the required approval actions. The evaluation takes five minutes: review the current Microsoft documentation for Team Members included capabilities, confirm that the specific workflow approval action (approve purchase invoice, approve expense report) is in the included list, and if it is, assign Team Members rather than Essentials. Finance verifies this with the Microsoft partner before the license switch, because Team Members scope has evolved across BC releases and the current version’s scope must be confirmed against the version in production. If Team Members covers the approval use case, the license switch reduces cost without reducing the workflow’s functionality.
⚠️ Power Automate Premium Connector Required—Not in the Implementation Budget
Finance builds a Power Automate flow that routes BC purchase invoice approvals through Microsoft Teams and then connects to the organization’s third-party expense management platform to synchronize approval status. The Teams connector is a standard connector (included in most Microsoft 365 licenses). The third-party expense platform connector is a premium connector. Every BC user who is part of the flow—the AP coordinator who triggers it, the three approvers who receive Teams messages, the Finance manager who receives the summary—requires a Power Automate Premium per-user license. The Finance team discovers this when the flow runs in production and Microsoft surfaces the premium connector license requirement. The Power Automate Premium licenses add £4,200 per year to the Finance team’s technology cost—an amount that was not in the implementation budget because nobody evaluated the connector type during flow design.
Fix: Before building any Power Automate flow that connects BC to a non-Microsoft system, Finance confirms whether the external system’s connector is a standard connector or a premium connector. This information is visible in Power Automate’s connector catalog—premium connectors are marked with a “Premium” tag. If the required connector is premium, Finance includes the per-user Power Automate Premium license cost in the project budget before building the flow. Finance also considers whether the external system integration can be accomplished through a standard connector (such as HTTP webhook, which is standard) rather than the native premium connector, which would avoid the per-user license requirement.
⚠️ Seasonal Headcount Added Without Budgeting License Costs
The organization adds six temporary staff during peak season to handle increased order volume. Three of the six need BC access for order entry and inventory management. The HR team creates BC user accounts for the three temporary staff. The BC subscription automatically adjusts to the new user count and the additional three Essentials licenses are billed at the monthly per-user rate for the duration of the temporary engagement. The additional license cost is £720 for the three-month peak season. Finance did not budget for the additional licenses because the headcount budget covered temporary staff salaries but did not include the incremental BC license cost. When the Microsoft invoice arrives with the additional license charge, Finance has to find the £720 from a budget that does not include a line for it.
Fix: BC license cost is a per-headcount expense that Finance must include in the annual and project-level budget, not just at implementation. Finance includes BC license cost as a line item in the annual budget: the base license count for permanent staff, plus an estimate for planned headcount additions (from the HR headcount plan), plus a contingency for unplanned additions. For seasonal operations, Finance budgets the incremental BC licenses as part of the seasonal cost model. When HR plans a seasonal headcount addition that will require BC access, HR flags the BC license cost in the seasonal staffing budget—not as a surprise post-addition charge. The per-user monthly rate is predictable from the current subscription terms; Finance can calculate the cost of any planned addition in advance.
⚠️ Premium License Required for Finance Manufacturing Access—Controller Discovers She Cannot See Production Reports
The organization implements BC for a manufacturing operation. The Controller is assigned an Essentials license. During the implementation, nobody identified that the production cost reports Finance needs—specifically the WIP report and the production order cost variance analysis—require access to Manufacturing module features that are only available under the Premium license. In the first month of live operation, the Controller attempts to run the Production Order Statistics report and receives an access error. Investigation reveals that Essentials does not include Manufacturing module access. Upgrading the Controller to Premium requires a mid-month license change and an additional cost that was not in the implementation budget. The Controller goes three weeks without the production cost visibility she needs for the first month-end close.
Fix: Finance identifies, before the implementation begins, which BC reports and features each Finance role needs to do their job—and confirms which license tier provides those features. For manufacturing companies specifically, Finance confirms which production reports are visible under Essentials and which require Premium. The Controller in a manufacturing company almost always requires Premium: the WIP report, production order cost analysis, capacity variance reports, and BOM cost rollup are Manufacturing module features. This identification happens during the fit-gap workshop, where the implementation partner walks Finance through the module coverage for each license tier. Finance writes the license requirement for each Finance role into the project scope before licensing is purchased, not after go-live when upgrading requires a budget adjustment and a Microsoft license change request.
Do This / Don’t Do This
Do This
- Assign External Accountant licenses (free, up to three) to external auditors, bookkeepers, and tax advisors before purchasing paid licenses for the same users
- Evaluate whether approval-only workflow participants need Essentials or whether Team Members scope covers their actual BC activities
- Check connector type (standard vs. premium) before building any Power Automate flow that connects to a non-Microsoft system
- Include BC license cost as a headcount-linked line item in the annual budget, including estimates for planned additions
- Confirm which BC reports Finance needs require Premium access in manufacturing environments before purchasing Essentials for Finance roles
- Verify current license terms with the Microsoft partner before making any licensing decision—terms change with BC releases
Don’t Do This
- Pay for Essentials licenses for external accountants, auditors, or tax advisors when External Accountant licenses are free
- Assign Essentials to all users without evaluating whether their actual BC activities are within Team Members scope
- Build Power Automate flows connecting BC to third-party systems without checking whether the connector is standard or premium
- Omit BC license cost from the annual budget and discover additional license charges on the Microsoft invoice as surprises
- Accept the implementation partner’s default license recommendation without evaluating the role-level access requirements against each license tier
- Treat BC licensing as an IT-only decision—Finance uses BC daily and Finance must understand the license implications of the Finance configuration it builds
Up Next:
Licensing clarity prevents budget surprises. The series continues with a topic that comes up in every BC engagement where Finance has been operating on the platform for more than a year: Building a BC Finance Health Check—How Finance Reviews Its Own Implementation—the self-assessment Finance runs to identify configuration gaps that have accumulated since go-live, the reconciliation evidence that reveals whether BC’s subledgers are reliable, the governance cadences that reveal whether Finance owns BC or BC owns Finance, and a scoring framework for prioritizing the improvements that will have the most impact on the quality of Finance’s output from BC.
— Bobbi
D365 Functional Architect · Recovering Controller
Thank you for reading!
If this post helped you solve a real problem, share it with a Finance colleague who is in the middle of an ERP implementation or a post-go-live optimization. If you have a topic that I haven’t covered, please reach out. There is always one more post worth writing.
If you are interested in learning more, below are some of my recent posts:
Leave a Reply