Microsoft Dynamics 365 Business Central Team Members Annual Subscription (12 Months)
PRODUCT DESCRIPTION
Microsoft Dynamics 365 Business Central Team Members Annual Subscription (CFQ7TTC0LH39:0002) - Local Support
A Limited-Rights Licence for People Who Consume Rather Than Operate
Team Members is the low-cost licence for the majority of an organisation who need to see what is in the system, approve something occasionally and update the odd record — but who do not run finance, sales or operations from it. Microsoft's licensing guide describes it as: "Assigned to a named user, Business Central Team Members provides read-only access to certain data and limited functionality within Business Central deployments."
What Microsoft Publishes About the Rights — and What It No Longer Does
Being straight about this matters more than sounding authoritative. Microsoft's current customer-facing description of what a Team Members licence allows is a single line on its pricing page: "Get limited access to read data, approve workflows, and create or update select information." The itemised allow-and-deny list that the channel has quoted for years is no longer published. It used to live in a standalone Business Central licensing guide which Microsoft folded into the main Dynamics 365 guide. We will not reproduce a list Microsoft has withdrawn.
Do Not Rely on the Dynamics 365 Team Members Appendix — It Is a Different Product
A specific trap worth naming, because it produces mis-sold licences. The Dynamics 365 Licensing Guide contains an appendix titled "Dynamics 365 Team Members Use Rights Overview", and it is tempting to read it as authoritative here. It is not: that appendix describes the Customer Engagement Team Members licence — accounts, leads, opportunities, cases, activities — which is a different product with different rights. If somebody quotes you Team Members rights from that appendix for a Business Central deployment, they have the wrong licence.
What Is Published: the Permission Sets Attached to the Licence
Microsoft does document the default permission model. A Team Members user is assigned the permission sets D365 READ, D365 TEAM MEMBER, EDIT IN EXCEL - VIEW, EXPORT REPORT EXCEL and LOCAL, and Microsoft notes that "Other permission sets are added automatically based on the user groups assigned to the license." If you need certainty about a specific task, the reliable route is to test it against those permission sets in a sandbox before you commit — and we will help you set that up.
Dynamics 365 Business Central Team Members Annual Subscription Datasheet — Licensing and Specifications
What Microsoft States About the Rights
| Licensing guide wording | "Assigned to a named user, Business Central Team Members provides read-only access to certain data and limited functionality within Business Central deployments" |
| Pricing page wording | "Get limited access to read data, approve workflows, and create or update select information" |
| An itemised allow-and-deny list | No longer published on any live Microsoft page. The historical source was a standalone Business Central licensing guide that Microsoft has folded into the main guide |
| The appendix that is NOT about this product | The licensing guide's "Dynamics 365 Team Members Use Rights Overview" appendix describes the Customer Engagement Team Members licence, not Business Central |
Default Permission Sets Attached to the Licence
| D365 READ | Assigned by default |
| D365 TEAM MEMBER | Assigned by default |
| EDIT IN EXCEL - VIEW | Assigned by default |
| EXPORT REPORT EXCEL | Assigned by default |
| LOCAL | Assigned by default |
| Additional sets | "Other permission sets are added automatically based on the user groups assigned to the license" |
Licensing
| Licence type | Limited-rights licence, assigned to a named user |
| Does it require a full user? | Not published by Microsoft for Business Central. Product Terms lists no prerequisite for Business Central Team Members; prerequisite wording that exists for the separate Customer Engagement Team Members SKU does not transfer |
| Minimum purchase | Not published by Microsoft |
| Term | Twelve months as sold by SourceIT |
Data Residency for a Singapore Tenant
| Singapore availability | Listed by Microsoft as Available, localised by Partner, base app W1, environment abbreviation SG |
| Azure geography | Asia Pacific |
| What Microsoft commits to | "Microsoft stores customer data at rest in the selected Azure geographic location within the customer-selected macro region geography", and for Asia-Pacific "Your data resides within the Asia-Pacific region" |
| What Microsoft does NOT commit to | In-country storage in Singapore for a standard subscription. Microsoft ties datacentre-level pinning to Advanced Data Residency criteria: "If you're a customer who meets ADR criteria, your Dynamics 365 and Power Platform data is stored at rest within your selected datacenter region" |
| Finding your region | "Administrators can use the Dynamics 365 Business Central admin center to find the Azure region that their environments are in" |
What Microsoft Does Not Publish for This Product
The following are commonly asked about but are not stated on any current official Microsoft source for this product, so SourceIT does not quote them: an itemised list of what a Team Members licence may and may not do, whether a Team Members licence requires at least one full user, a minimum seat count, a per-version end of support date for Business Central online and a mapping between the commerce SKU identifier and this product. We would rather leave a field blank than print a figure we cannot substantiate.
Lifecycle, End of Support and Entitlement
SourceIT sells this as a twelve-month subscription with a GST invoice in Singapore. The subscription is a right to use the service for the term, not a perpetual licence: when the term ends the entitlement ends unless it is renewed.
Microsoft's lifecycle listing places Business Central under the Modern Lifecycle Policy, with a start date of 1 November 2016 and a retirement date shown as "In Support". The Modern Lifecycle Policy carries an obligation on the customer as well as on Microsoft: "Customers must stay current as per the servicing and system requirements published for the product or service", and Microsoft commits to "a minimum of 12 months' notification prior to ending support if no successor product or service is offered". In practice that means roughly six months on any given major version before the update is enforced. Note that Microsoft frames this as an update enforcement timeline rather than a support-ends date, and publishes no per-version end-of-support date for Business Central online. Separate Fixed-policy dates exist for Business Central on-premises and do not apply to this subscription.
Talk to our team before the renewal date rather than after it. Seat counts, mid-term changes and co-terming with the rest of your Microsoft estate are all easier to arrange in advance, and we can quote the alternatives if a bundle would work out better for you.
Published Lifecycle Dates
| Lifecycle policy | Modern Lifecycle Policy |
| Start date | 1 November 2016 |
| Retirement date | "In Support" — none published |
| Major updates | Two a year, released on the first workday of April and October (release waves 1 and 2) |
| Minor updates | Monthly, in every month except April and October |
| Update period | Five calendar months from general availability. April releases run to early September; October releases to early March |
| Grace period | One further month, after which the update cannot be rescheduled |
| Enforced update period | Begins after the grace period. Extensions that block the update may be automatically uninstalled |
| Restoring an older version | "It's not possible to restore an environment to a version that is in its Grace or Enforced update period after an update to a later version has succeeded" |
Support and Entitlement Position
This is a software subscription, not hardware. It carries no hardware warranty, and any warranty term you see on a hardware listing does not apply here. What you are buying is a twelve-month right to use the service, together with SourceIT's local support in Singapore. Microsoft's own condition is that technical and billing support for a subscription bought through a partner runs through that partner, so for this subscription that means us: raise the ticket with SourceIT and we escalate to Microsoft where it needs to go. Renewal, seat changes and co-terming are handled on your SourceIT account. Ask our team for the current entitlement position in writing with your quotation.
Compatibility, Deployment and System Requirements
The practical way to establish whether Team Members covers a given task is to test it rather than to read about it, because Microsoft has withdrawn the itemised rights list. A Team Members user gets the D365 READ, D365 TEAM MEMBER, EDIT IN EXCEL - VIEW, EXPORT REPORT EXCEL and LOCAL permission sets by default, with more added automatically according to the user groups assigned. Set up one Team Members user in a sandbox environment — every subscription includes three — and walk through the specific tasks that matter before you buy in volume. We will help you set that up.
Get the licence mix right before go-live rather than after. Under-licensing a user who turns out to need full rights is the most common and most disruptive Business Central licensing correction, because it usually surfaces in the middle of a month-end. Tell us what each group of users actually does and we will map it to tiers with you.
On data residency, Microsoft is more forthcoming for Business Central than for most of its security products, and the distinction is worth getting right. Singapore is listed as Available with an Azure geography of Asia Pacific, and Microsoft's commitment for that macro region is that "Your data resides within the Asia-Pacific region". What Microsoft does not promise on a standard subscription is storage in the Singapore datacentre specifically — that is tied to Advanced Data Residency criteria. If in-country storage is a regulatory requirement for you, raise it with us before you order and we will get the position confirmed.
Rights, Permissions and How to Verify Them
| Licence type | Limited rights, named user |
| Published rights | "read-only access to certain data and limited functionality"; "read data, approve workflows, and create or update select information" |
| Default permission sets | D365 READ, D365 TEAM MEMBER, EDIT IN EXCEL - VIEW, EXPORT REPORT EXCEL, LOCAL |
| Full user prerequisite | Not published for Business Central |
| How to verify a specific task | Test it in one of the three included sandbox environments |
Official Microsoft Sources & Downloads
- Dynamics 365 Business Central pricing
- Licensing in Business Central (Microsoft Learn)
- Create users according to licences in Business Central (Microsoft Learn)
- Managing capacity in Business Central (Microsoft Learn)
- Production and sandbox environments in Business Central (Microsoft Learn)
- Managing production and sandbox environments (Microsoft Learn)
- Operational limits for Business Central online (Microsoft Learn)
- Dynamics 365 Business Central lifecycle (Microsoft Learn)
- Business Central update rollout timeline (Microsoft Learn)
- Business Central country availability and Azure geography (Microsoft Learn)
- Dynamics 365 Licensing Guide, September 2026 (PDF)
- Microsoft Product Terms for Dynamics 365
- Business Central licensing documents (Microsoft Licensing)
- Modern Lifecycle Policy (Microsoft Learn)
Where a figure appears on this page it is quoted from one of these Microsoft pages; where Microsoft publishes nothing, this page says so rather than filling the gap. Supplied by SourceIT in Singapore with a GST invoice and local support. For a written quotation, current stock position or delivery lead time, contact our team.
Frequently Asked Questions — Dynamics 365 Business Central Team Members Annual Subscription
What can a Team Members user actually do?
Microsoft publishes two sentences and no more: the licensing guide says the licence "provides read-only access to certain data and limited functionality", and the pricing page says "Get limited access to read data, approve workflows, and create or update select information." The itemised list that used to exist is no longer on any live Microsoft page. For a specific task, test it in a sandbox against the default permission sets — we will help you set that up.
Someone showed us a detailed list of Team Members rights. Is it reliable?
Check where it came from. The Dynamics 365 Licensing Guide has an appendix called "Dynamics 365 Team Members Use Rights Overview", but it describes the Customer Engagement Team Members licence — accounts, leads, opportunities, cases — not Business Central. Lists drawn from that appendix, or from Microsoft's withdrawn standalone Business Central guide, are not a current Microsoft statement about this licence.
Do we need at least one full user licence as well?
Microsoft does not publish a prerequisite for Business Central Team Members, and Product Terms lists none. Prerequisite wording that exists for the separate Customer Engagement Team Members SKU does not transfer to this one. In practice an implementation needs full users to operate the system, but that is a design point rather than a published licence rule. Ask us and we will confirm the position on your purchasing route.
What permission sets does the licence give?
By default: D365 READ, D365 TEAM MEMBER, EDIT IN EXCEL - VIEW, EXPORT REPORT EXCEL and LOCAL. Microsoft adds that "Other permission sets are added automatically based on the user groups assigned to the license." Those five are the reliable starting point for testing what a Team Members user can reach.
Is there a minimum number of licences?
Microsoft publishes no minimum for Business Central Team Members. Practical minimums come from the purchasing programme rather than the product, so ask our team what applies on the route we would quote you.
