Microsoft Teams Licensing for Financial Institutions (2026 Guide)

If your institution is approaching its Microsoft 365 renewal, Microsoft Teams is no longer the line item it used to be. The simple math that said Teams was free with E3 or E5 was rewritten on April 1, 2024, when Microsoft unbundled Teams from the worldwide Enterprise commercial SKUs. New customers can no longer buy Microsoft 365 E3, Microsoft 365 E5, or Office 365 E1, E3, or E5 with Teams included. Existing customers can keep renewing the bundled versions, but the renewal math is no longer obvious. The same is true on the small business side, where Microsoft 365 Business Basic, Standard, and Premium now ship in two flavors, one with Teams and one without.

For banks, credit unions, and mortgage companies, this is not a cosmetic change. Teams sits in the middle of three regulated workflows: loan officer client communication, deposit account servicing, and any examiner interaction that touches video, chat, or call recording. Every dollar a financial institution spends on Teams above the floor price is paying for an add-on with a defined regulatory or productivity payoff, and every dollar of bundled Teams pricing that no longer fits the institution's actual usage is overhead the CFO can claw back at the next renewal.

This article walks through what Microsoft actually charges for Teams in May 2026, where the bundled-vs-unbundled break-even sits for a financial institution at 50, 100, or 250 seats, what Teams Phone really costs once Public Switched Telephone Network connectivity is included, what changed inside Teams Premium versus Teams Enterprise on April 1, 2026, and how Microsoft Purview retention policies satisfy the Federal Financial Institutions Examination Council Information Security Booklet expectation for electronic communications retention. The numbers are all sourced from Microsoft's own published commercial pricing pages as of May 2026.

The licensing decision is straightforward once each line item is on the table. The hard part is that Microsoft's commercial pricing pages, the Microsoft Teams add-on licensing documentation, and the Microsoft Learn Audio Conferencing guidance all live on different pages. None of them are written specifically for a $1 billion community bank, a 60,000-member credit union, or a 200-loan-officer mortgage company. The point of this article is to assemble those pieces into a single sizing model an IT director can take to a renewal meeting.

What Microsoft changed about Teams licensing on April 1, 2024

Before April 2024, Microsoft 365 E3 and E5 came with Teams included, and the only customers who saw a "with Teams" versus "no Teams" choice were European Economic Area and Switzerland customers, who had been offered the unbundled SKUs since October 1, 2023 under European Commission antitrust pressure. On April 1, 2024, Microsoft extended the same change to the rest of the world. The Microsoft Teams add-on licensing documentation on Microsoft Learn states the policy explicitly:

Starting April 1, 2024, all new Enterprise customers who wish to provide workers with both Microsoft Teams and the value in existing Microsoft 365 or Office 365 Enterprise suites (E1, E3, E5) will need to purchase two SKUs: one E1, E3, or E5 (no Teams) suite and one Teams standalone (Microsoft Teams Enterprise or Microsoft Teams EEA).

Four facts inside that paragraph matter for any financial institution renewing in 2026.

First, the change only applies to new Enterprise customers. Existing customers who already had bundled E1, E3, or E5 with Teams before April 1, 2024 can continue to renew, upgrade, or otherwise adjust those subscriptions just like before. The bundled SKU price still appears on Microsoft's published pricing pages, and ABT's renewal team can confirm in writing whether an institution's current tenant qualifies as a legacy bundled customer.

Second, the change applies only to the Enterprise tier. Microsoft 365 Business Basic, Business Standard, and Business Premium (up to 300 users) and the Microsoft 365 Frontline F1 and F3 worker suites are still sold in both flavors, with and without Teams. A 250-seat community bank that runs Microsoft 365 Business Premium can choose either path at any renewal, with no legacy-customer exception required.

Third, the unbundling does not affect Microsoft 365 admin licensing for Teams meeting attendees. Anyone with an Office 365 or Microsoft 365 license that includes Teams (legacy bundled) or with a separate Teams Enterprise add-on can host and attend Teams meetings. External attendees joining from outside the tenant do not need any Microsoft license at all.

Fourth, the bundled "with Teams" SKU is more expensive than the unbundled "no Teams" SKU plus a separate Teams Enterprise license at every Enterprise tier. The math below shows why most financial institutions on legacy bundled subscriptions are still better off renewing the bundle than switching to the unbundled path, while new financial institution deployments have to start from the unbundled side regardless.

The real Teams price landscape for financial institutions in May 2026

Microsoft publishes commercial pricing on three separate web pages: the Microsoft 365 Business plan comparison, the Office 365 Enterprise plan comparison, and the Microsoft 365 Enterprise plans and pricing page. The Microsoft Teams page lists the standalone and add-on prices. Putting all four pages together gives the full picture for a bank, credit union, or mortgage company in May 2026, paid on annual commitment terms:

The Teams upcharge inside the bundled SKU is $8.55 per user per month at all four Enterprise tiers (Office 365 E3, Office 365 E5, Microsoft 365 E3, Microsoft 365 E5). On the small business side, the upcharge is smaller: $1.60 for Business Basic and $3.21 for Business Standard. Microsoft 365 Business Premium also publishes a "with Teams" and "no Teams" variant; the differential follows the same low-single-digit pattern as Business Standard.

Now compare those numbers against the cost of building the same configuration from the unbundled path. A new customer who wants a Microsoft 365 E3 license plus Teams has to buy two SKUs: Microsoft 365 E3 (no Teams) at $27.45 and Microsoft Teams Enterprise at a per-user list price that, at the published Microsoft commercial pricing on May 14, 2026, lands at roughly $5.25 per user per month for the worldwide standalone SKU. The combined unbundled cost is therefore approximately $32.70 per user per month, compared with the legacy bundled price of $36.00. The unbundled path is cheaper than the legacy bundle, which is the reason new customers were moved to it. Existing legacy bundled customers do not see this lower combined price on a like-for-like renewal, because the bundled SKU is renewed at its bundled list price.

The implication for a financial institution renewing in 2026 is that a switch from a legacy bundled E3 subscription to an unbundled "no Teams" E3 plus separate Teams Enterprise license can save between $3 and $4 per user per month, depending on the Microsoft Cloud Solution Provider's negotiated rate. For a 100-seat institution, that is $3,600 to $4,800 per year. For a 250-seat institution, $9,000 to $12,000 per year. The work involved is real, however, because the unbundled split requires reissuing every user a new pair of licenses, and Microsoft's tenant tooling does not automatically remap entitlements. A Tier-1 Microsoft Cloud Solution Provider can do the mapping and timing for the institution, but the institution should understand the cash-flow trade-off going in.

Bundled vs unbundled: when to renew Teams inside E3 or E5, and when to split

The bundled-versus-unbundled question is not actually a Teams question. It is a renewal-channel question, because the savings only exist if the institution can take advantage of the lower unbundled list price. Three scenarios cover almost every financial institution in 2026.

A 50-seat credit union typically licenses Microsoft 365 Business Premium because it is the only Business-tier plan that includes Microsoft Defender for Business and Microsoft Intune. Business Premium ships in both "with Teams" and "no Teams" variants, with a Teams upcharge that is small in absolute terms. At this size, the cost of the Microsoft Cloud Solution Provider's time to move every user to the unbundled split usually exceeds the annual savings. Stay bundled.

This is the segment where the unbundled split is most likely to be worth the work. At 100 seats, $8.55 per user per month is $10,260 per year. At 250 seats, $25,650. After subtracting the price of the standalone Microsoft Teams Enterprise license, the net annual savings is in the $3,000 to $12,000 range, which justifies a one-time provisioning effort at most institutions. The right question to ask the Microsoft Cloud Solution Provider is whether the institution can keep its existing bundled E3 subscription through the current renewal term and switch only at renewal time, so no mid-term enrollment amendment is required.

At Microsoft 365 E5 list price ($57.00 per user per month bundled, $48.45 unbundled, plus Teams Enterprise standalone), the $8.55 per user per month delta translates into roughly $30,800 of annual savings for a 300-seat institution. The complication is that Microsoft 365 E5 includes Audio Conferencing as part of the bundle. If the institution unbundles to no-Teams E5 plus standalone Teams Enterprise, the institution loses that bundled Audio Conferencing entitlement and must add it back as a separate add-on at standalone list price. A Tier-1 Microsoft Cloud Solution Provider can model the round-trip cost: in most E5 cases, the savings still exceed the Audio Conferencing add-back, but the margin is narrower than at the E3 tier, and the institution should walk through the actual usage profile before signing the change.

Microsoft Teams Phone for banks, credit unions, and mortgage companies

Microsoft 365 plans, with or without Teams, do not include Teams Phone. Teams Phone is a separate add-on license that turns Teams into the institution's hosted Private Branch Exchange (PBX), with cloud voicemail, call forwarding, call transfer, auto attendants, call queues, caller ID, and the ability to make and receive calls to and from external phone numbers. Most banks, credit unions, and mortgage companies that adopt Teams Phone are replacing an aging on-premises PBX or migrating off a third-party hosted Voice over Internet Protocol provider.

Microsoft sells Teams Phone in two architectures: with Microsoft as the Public Switched Telephone Network carrier (the Microsoft Calling Plans path), or with the institution's existing carrier handling the Public Switched Telephone Network leg (the Operator Connect, Direct Routing, Teams Phone Mobile, or Shared Calling paths). Both architectures require a Teams Phone Standard license at the user level.

For most financial institutions, the practical question is whether to stay with the incumbent carrier through Operator Connect or Direct Routing, or to consolidate on Microsoft Calling Plans. The Microsoft Cloud Solution Provider can quote both paths. The Operator Connect path keeps the institution's existing phone numbers, billing relationship, and emergency-services configuration in place; the Microsoft Calling Plan path consolidates onto a single Microsoft monthly invoice and simplifies provisioning. Neither path is universally better; the trade-off depends on the institution's existing carrier contract, the geographic spread of branches, and whether the institution wants Microsoft to be the responsible party for 911 routing.

The other Teams Phone surface that frequently surprises financial institutions is the Queues app. Microsoft's Queues app provides call queue and auto attendant management inside Teams, with real-time and historical reporting for inbound call traffic. For a community bank's loan servicing desk or a credit union's member services queue, Queues is genuinely useful. The Queues app requires both a Teams Phone license and a Teams Premium license, however. Institutions that run inbound call queues should plan to license both at the Teams Phone user level.

Teams Premium and Teams Enterprise: what the April 2026 feature shift changed

Effective April 1, 2026, Microsoft moved a set of features that had previously been exclusive to Teams Premium into the base Teams Enterprise license. The Microsoft Teams Premium licensing page on Microsoft Learn states the change clearly:

Translating that update into practical guidance for a financial institution: the base Teams license inside an existing Microsoft 365 or Office 365 subscription now does more than it did six months ago, and the question of whether a particular user needs the $10.00-per-user-per-month Teams Premium add-on has narrowed to four real categories.

For users outside those four categories, Teams Enterprise (the base license) now covers enough functionality that Teams Premium is hard to justify. The institution can run a Teams Premium trial license for 25 users for 30 days from the Microsoft 365 admin center to confirm whether any of the four use cases applies before paying for production licenses.

Teams Rooms Pro is a separate $40.00 per room per month license that applies to conference-room hardware, not to user accounts. Banks and credit unions with managed conference rooms (typically branch boardrooms or executive meeting spaces) license Teams Rooms Pro per room. The Teams Premium and Teams Rooms Pro licenses do not overlap, do not conflict, and are not dependent on each other.

The Microsoft 365 retention and audit controls examiners expect

Federal banking regulators have not published a Microsoft Teams retention rule. The Federal Financial Institutions Examination Council Information Technology Examination Handbook, the Office of the Comptroller of the Currency's Interagency Guidelines Establishing Standards for Safeguarding Customer Information (12 CFR Part 30, Appendix B), and the National Credit Union Administration's parallel guidelines (12 CFR Part 748, Appendix A) all require risk-based retention of electronic records and audit trails, but none of them name Teams specifically.

That gap puts the burden on the institution to make a defensible retention decision and configure Microsoft 365 to enforce it. Microsoft Purview retention policies are the canonical control. A Purview policy applied to the Teams workload sets per-message retention windows for chats, channel messages, and meeting recordings, overriding the default Teams chat retention period and surviving the user-side delete action.

For banks, credit unions, and mortgage companies that have broker-dealer subsidiaries (a common pattern for credit union holding companies with credit union service organizations, or for community banks with affiliated investment advisers), the SEC Rule 17a-4(b)(4) requirement for write-once-read-many storage of business communications applies. Microsoft Purview's preservation lock feature converts a Purview retention policy into a write-once-read-many control that satisfies the regulatory requirement without requiring third-party archiving software.

For institutions that license Microsoft Defender for Office 365 (included in Microsoft 365 E5 and as a standalone add-on), the Teams safe links and safe attachments features layer on top of the retention controls. Defender for Office 365 inspects every link and file shared in Teams chat, blocking phishing payloads at the moment of click. This is the same Defender for Office 365 anti-phishing engine that protects Exchange Online mailboxes, configured to scan the Teams workload. The two controls combine: Purview retains and Defender protects.

A practical sizing model for a 100-seat financial institution

The mental model an IT director needs at the renewal meeting is straightforward. Start with the seat count. Identify which users actually need Teams (almost all of them, in 2026). Identify which users need Teams Phone (typically loan officers, branch managers, member service representatives, and executive leadership; usually 50 to 70 percent of total seats). Identify which users need Teams Premium (typically the same set as Teams Phone plus board administrators and senior management). Then map those numbers to Microsoft's published list prices.

The same 100-seat institution running Microsoft 365 E5 (legacy bundled with Teams, Audio Conferencing included, Defender for Office 365 included, Microsoft Purview Audit Premium included) lands at roughly $79,200 per year for the E5 base plus the same Teams Phone, Teams Premium, and Teams Rooms Pro add-ons. The E5 differential of about $21,000 per year is the price of consolidating onto Microsoft's complete security and compliance stack inside the same renewal.

Most financial institutions in the 50-to-250-seat range land on one of two configurations. The first is Microsoft 365 E3 plus Teams Phone Standard for the 50-to-70 percent of seats that need a phone number, plus Teams Premium for the 25-to-30 percent of users who need the Queues app, intelligent recap, or multilingual translation, plus a sprinkling of Teams Rooms Pro licenses for managed conference rooms. The second is Microsoft 365 E5 with the same Teams Phone and Teams Premium overlay, justified by the institution's need for Microsoft Defender for Office 365, Microsoft Defender for Endpoint Plan 2, Microsoft Defender for Identity, Microsoft Defender for Cloud Apps, Microsoft Entra ID Plan 2, and the four Microsoft Purview Premium services that are bundled into the E5 SKU.

If the institution's renewal arrives in 2026, the right path depends on what regulators are asking about and what the institution actually uses today. ABT's licensing team can model the institution's current Microsoft 365 tenant entitlements against the renewal options before the renewal is signed. A bank or credit union that already has E5 with most security features dormant is a different licensing decision than a mortgage company moving from a third-party email platform onto Microsoft 365 for the first time.

For institutions weighing whether to keep Microsoft 365 E5 once the renewal arrives, the companion article on the nine Microsoft 365 E5 security features banks pay for but don't use walks through the verification steps for each E5 security add-on, with screenshots of the relevant Microsoft 365 admin portals. For institutions still in the Microsoft 365 E3 versus E5 decision, the Microsoft 365 E3 vs E5 vs Business Premium decision guide compares the three SKUs on price, security feature inclusion, and FFIEC examiner expectations. For institutions implementing Microsoft Defender for Office 365 (the engine that protects the Teams workload from phishing payloads), the Microsoft Defender for Office 365 anti-phishing configuration guide covers the policy stack examiners look for. Institutions deploying Microsoft 365 Copilot inside Teams should see the Microsoft 365 Copilot Business buyer's guide for financial institutions for the Copilot-specific licensing trade-offs.

Frequently Asked Questions

Justin Kirsch

CEO, Access Business Technologies

Justin Kirsch has been licensing Microsoft 365 for regulated financial institutions since 1999. As CEO of Access Business Technologies, the largest Tier-1 Microsoft Cloud Solution Provider dedicated to financial services, he helps more than 750 banks, credit unions, and mortgage companies match their Microsoft Teams licensing to the way their loan officers, branch staff, and executive teams actually work, and configures Microsoft Purview retention so examiners see the same answers the institution sees.