Microsoft 365 Information Barriers: Licensing, Configuration, and What It Actually Costs

Information Barriers (IB) is one of the most misunderstood compliance features in Microsoft 365. Organizations in financial services, legal, pharmaceutical, and government sectors need it — regulators demand it — but the licensing requirements are frequently misstated by Microsoft account teams, and the gap between "included" and "required" licensing often costs six figures.

After 20 years advising enterprises on Microsoft licensing, the pattern is consistent: organizations discover they need Information Barriers during a compliance audit or regulatory examination, they get quotes from Microsoft without independent analysis, and they overbuy. This guide gives you the framework to license IB precisely, deploy it correctly, and avoid paying for E5 licensing when a targeted add-on will suffice.

What Information Barriers Actually Does (and Doesn't Do)

Information Barriers is a compliance feature in Microsoft Purview that prevents two-way communication and collaboration between defined groups of users. It operates at the policy level within Microsoft Teams, SharePoint Online, and OneDrive for Business. When IB policies are active, users in restricted segments cannot initiate chats, add each other to meetings, search each other's profiles, or co-edit SharePoint documents.

Understanding the scope is critical to understanding the licensing need:

• Teams: IB prevents direct messages, group chats, and meeting add — enforced in near real-time.
• SharePoint and OneDrive: IB restricts sharing and co-authoring between incompatible segments.
• Exchange Online: Information Barriers does NOT restrict email in most configurations. If you need email-level restrictions, you need a separate solution (transport rules, journal policies, or third-party DLP).
• Yammer / Viva Engage: Limited IB support — Microsoft's guidance on Viva Engage IB enforcement has evolved and the current state should be confirmed before deployment.

This is important for licensing decisions: if your regulatory requirement only applies to Teams and SharePoint collaboration (not email), you may not need the full E5 Compliance stack — though IB itself still requires E5 Compliance tier licensing.

The Licensing Requirements: Plans, Add-Ons, and Who Needs What

The licensing hierarchy for Information Barriers is as follows. Users must have one of these to be covered by IB policies:

IB Segments: Configuration Complexity and Licensing Scope

An Information Barrier "segment" is a defined group of users — typically mapped to an Azure AD group or attribute — that IB policies reference. The complexity of your segmentation model drives both deployment cost and licensing scope.

Common Segment Architectures

In financial services, the classic IB deployment separates investment banking from equity research (Chinese wall requirements). In legal, it separates matter teams to prevent conflicts of interest. In pharmaceutical, it separates early-stage R&D from regulatory affairs. Each of these creates two or more segments, all of which require IB licensing for every user within them.

The key question in any IB deployment is: how many users are "in scope" for IB policies? If only 30% of your organization needs to be in IB-managed segments, you only need to license that 30% — though Microsoft account teams often push for full tenant licensing, which is not required by the product.

Segment-Level vs. Tenant-Level Licensing

Microsoft's licensing documentation states that users must be licensed for the features they use. If a user is never placed in an IB segment and no IB policy applies to them, they do not need E5 Compliance for IB purposes. This is frequently the basis for significant cost reduction in IB deployments. A 10,000-user organization where only investment banking (1,200 users) and equity research (800 users) need IB can license 2,000 users for E5 Compliance rather than 10,000 — a cost difference of approximately $120,000–$150,000 per year at standard pricing.

Information Barriers v1 vs. v2: The Architecture Change That Affects Licensing Decisions

Microsoft introduced Information Barriers v2 with significant architectural changes that affect how organizations should plan deployments. Understanding the version difference matters for licensing because v2 changes the segment interaction model.

In IB v1, the default mode was "restrictive" — segments that were not explicitly permitted to communicate were blocked by default. In IB v2, Microsoft introduced a "compatibility" mode that changes the interaction logic: segments are interoperable unless explicitly blocked. This is a fundamental inversion of the trust model.

For organizations with strict regulatory requirements (e.g., FINRA Rule 17a-3, MiFID II information barrier requirements), the shift from v1 to v2 requires careful policy review. Moving to v2 without re-validating your IB policies may inadvertently allow communication that was previously blocked.

The licensing requirements for v1 and v2 are identical. What differs is the policy configuration effort and the compliance validation work required when migrating between versions — which typically requires external advisory support.

IB in the Broader Compliance Licensing Context

Organizations evaluating Information Barriers rarely need only IB. The same regulatory drivers that require IB — financial services conduct rules, legal conflict management, pharma data segregation — typically also require:

• Communication Compliance — supervisory review of Teams and email communications (requires E5 Compliance; see our Communication Compliance licensing guide)
• Insider Risk Management — behavioral analytics for data exfiltration and policy violations (see our Insider Risk Management licensing guide)
• Advanced eDiscovery — legal hold and content search across regulated segments (see our Advanced eDiscovery licensing guide)
• Microsoft Purview Information Protection — sensitivity labels and encryption for documents crossing segment boundaries

All of these capabilities are in the E5 Compliance add-on. If your organization needs three or more of these features, the E5 Compliance add-on (rather than individual feature add-ons) typically delivers the best per-feature cost — but this math requires careful analysis against your actual user population in scope for each feature.

For a broader view, see our Microsoft 365 Compliance Add-Ons guide and the E3 vs E5 comparison.

Negotiating IB Licensing in Your EA

Information Barriers licensing is nearly always purchased as part of an E5 Compliance add-on under an Enterprise Agreement. The negotiation principles that apply to E5 Compliance add-ons in your EA include:

Segment Scope Negotiation

Push back on any proposal to license IB at the full tenant level. Document your actual IB segment users precisely and negotiate licensing only for those users. This argument is supported by Microsoft's own licensing documentation — the question is whether your account team acknowledges it.

E5 Compliance Bundle Discount vs. Individual Add-Ons

If you need IB plus Communication Compliance plus Insider Risk, you'll be buying E5 Compliance regardless. In that scenario, negotiate the E5 Compliance add-on discount aggressively — the bundle should be significantly discounted off MSRP. The discount floor on E5 Compliance add-ons in competitive EA negotiations typically runs 15–25% depending on total contract value and competitive alternatives.

Pilot Licensing Before Full Deployment

IB deployments rarely go live on day one for all in-scope users. Negotiate a phased licensing model — license the pilot segment first, with committed expansion terms — to avoid paying for 2,000 user licenses while deploying to 200 during a 6-month pilot phase.

For full EA negotiation strategy, see our Microsoft EA Negotiation Complete Guide and the EA Negotiation service page.

The Hidden Cost: Deployment and Ongoing Management

IB licensing is only part of the cost. Information Barriers deployments have substantial professional services and ongoing management costs that organizations frequently underestimate:

• Policy design: Defining segments, mapping them to Azure AD attributes, and documenting the IB policy logic in regulatory terms requires compliance expertise.
• Azure AD attribute cleanup: IB relies on Azure AD user attributes (department, custom attributes) to define segments. If your Azure AD data is inconsistent — which it typically is after years of organic growth — you'll need an attribute remediation project before IB can be deployed.
• SharePoint site remediation: Existing SharePoint sites shared across segments will need to be audited and remediated before IB goes live. This is often the most time-consuming part of an IB deployment.
• Ongoing segment management: As employees change roles, IB segment assignments must be maintained. This requires an automated process connected to HR systems — a manual approach breaks down quickly at scale.

When IB Is Not the Right Answer

Information Barriers is a powerful tool but not the only tool for organizational separation requirements. Smaller organizations, or those with simpler segmentation needs, should evaluate alternatives before committing to E5 Compliance tier licensing:

• Separate tenants: For complete separation between business units (e.g., M&A firewall), separate Microsoft 365 tenants eliminate IB complexity entirely — at the cost of higher administrative overhead and lost collaboration capabilities.
• Teams private channels: For lightweight separation within Teams without regulatory requirements, private channels and team membership controls may be sufficient.
• SharePoint permission controls: Native SharePoint permissions and site-level security can achieve content separation without IB licensing.
• Third-party DLP and communication surveillance tools: For organizations already using Bloomberg, Symphony, or similar compliance tools, evaluate whether IB duplication is necessary or whether those tools cover the regulatory requirement.

The question to ask: what specific regulatory requirement are you satisfying with IB, and can it be satisfied with a lower-cost control? This is precisely the analysis an independent licensing advisor performs before engaging Microsoft on E5 Compliance pricing.

Conclusion: License IB Precisely, Deploy It Correctly

Information Barriers is a legitimate and often mandatory compliance control — but it is expensive, complex to deploy, and frequently over-licensed. The core framework for managing IB licensing costs: license only in-scope segment users (not the full tenant), negotiate E5 Compliance add-on pricing at discount levels appropriate to your total EA value, and invest in Azure AD attribute quality before purchasing licenses.

The organizations that manage IB costs effectively treat the licensing purchase and the deployment readiness as two separate workstreams — both requiring expert support. Purchasing before you're ready means paying for licenses you cannot use. Deploying without licensing precision means compliance gaps that surface in audits.