How Many Users Can Use Microsoft 365 Business? (w/Examples) + FAQs

Microsoft 365 Business plans allow a maximum of 300 users per tenant, a hard cap set by Microsoft across Business Basic, Business Standard, Business Premium, and Apps for Business. Once your organization hits user number 301, you cannot buy another Business seat, and you must move some or all of your workforce to an Enterprise plan like Microsoft 365 E3 or E5 to keep licensing new people.

This ceiling is not a soft guideline. It is a licensing rule tied to the Microsoft Product Terms and the Microsoft Online Subscription Agreement, and ignoring it creates real consequences: blocked purchases, a forced mid-year migration, and, in regulated fields like healthcare or defense, compliance gaps that can expose you to HIPAA fines or DFARS contract loss. Before you pick a plan, you need to understand how the cap works, how it interacts with federal rules like the FTC Safeguards Rule, and what happens in the hundreds of small edge cases that trip up growing companies.

A recent Microsoft earnings release reports more than 400 million paid Microsoft 365 commercial seats worldwide, and small-to-midsize businesses make up the fastest-growing slice of that base, which means the 300-user wall is hit by tens of thousands of firms every year.

• 🎯 The exact 300-seat cap, where it comes from, and what counts as a “user”
• 🛡️ How federal laws like HIPAA, GLBA, and DFARS interact with your license choice
• 🧮 Real named examples of companies hitting the cap and how they solved it
• ⚠️ The most common mistakes buyers make when they outgrow Business plans
• 🚀 A step-by-step path from Business Premium to Enterprise E3 or E5

The 300-User Cap Explained

The 300-user limit applies at the tenant level, meaning one Microsoft 365 tenant can hold a combined total of 300 active Business SKU licenses. This rule is published directly in the Microsoft 365 Business plan comparison page and repeated in the Microsoft 365 service description. The cap counts every person assigned any Business license, not just paid active users, and it cannot be raised by calling support.

The reason the cap exists is that Microsoft designed the Business family for small and medium companies that do not need features like advanced eDiscovery, large-scale information barriers, or unlimited email archiving. Enterprise plans carry those heavier features and are priced and scoped for bigger workforces. If you try to buy a 301st Business license, the Microsoft 365 admin center will block the purchase and show an error.

The consequence of ignoring the cap is simple but painful. You will not be able to onboard the new hire on time, and your HR onboarding workflow will stall. A common misconception is that you can “stack” two Business tenants to get 600 seats. You cannot share a single email domain across two tenants without complex cross-tenant configuration, which defeats the purpose.

What Counts as a “User”

A “user” under Microsoft 365 Business licensing is any identity in Microsoft Entra ID that is assigned a paid Business license. Guest accounts invited through Entra B2B collaboration do not count against the 300-seat cap because they do not consume a Business SKU. Shared mailboxes also do not count, provided they are under the 50 GB limit and are not assigned a license.

The consequence of miscounting is that you may budget for 300 licenses and discover your admin accidentally licensed service accounts, printers, or meeting rooms, eating into your real headcount. A real-world mini-scenario: a 270-employee marketing agency licensed 25 conference-room resource accounts, which pushed them to 295 used seats and left only 5 slots for new hires that quarter.

A common misconception is that unlicensed accounts still count. They do not. Only assigned Business licenses count, which means unlicensed admin accounts, break-glass accounts, and service principals are free in terms of the 300 cap, though they still have security implications under the NIST Cybersecurity Framework.

Tenant vs. Subscription Scope

The 300-user cap is per tenant, not per subscription. You can buy three separate Business subscriptions (say, Basic, Standard, and Premium) inside the same tenant, but the combined assigned seats across all three still cannot exceed 300. Microsoft documents this in the licensing restrictions section of the commerce docs.

The consequence of misunderstanding this is real. Owners often think they can buy “100 Basic plus 250 Standard” and reach 350 users. The system will reject the 301st total assignment, regardless of which Business SKU it belongs to. A named example: Priya Shah, operations lead at a 290-person logistics firm, tried to add 30 Business Basic licenses for warehouse staff on top of 285 Business Standard seats and was blocked at checkout.

A common misconception is that buying a second tenant solves the problem cheaply. It does not, because cross-tenant mail flow, SharePoint search, and Microsoft Teams collaboration all break across tenant lines, creating an IT headache that usually costs more than upgrading to Enterprise.

Plan-by-Plan User Limits

Every SKU in the Microsoft 365 Business family shares the same 300-user cap, but the features, price, and target buyer differ in ways that matter for compliance and cost. You can see the full matrix on the Microsoft 365 for business plans page. Choosing the wrong SKU means paying for features you never use or missing features you legally need.

The consequence of picking the wrong tier is that you may violate industry rules without knowing it. For example, a healthcare practice on Business Basic has email but lacks the Defender for Office 365 controls that help meet HIPAA Security Rule safeguards. A real scenario: Marcus Lee, IT manager at a 150-seat dental group, kept the group on Business Basic for two years before realizing the plan did not cover the encryption features his HIPAA Business Associate Agreement required.

A common misconception is that “Business Premium is just a nicer Business Standard.” It is not. Premium adds Intune device management, Defender for Business, and Azure Information Protection plan 1, which are often required by contract or regulation.

Business Basic, Standard, and Premium

Business Basic gives web and mobile versions of Word, Excel, PowerPoint, and Outlook, plus 1 TB of OneDrive per user and hosted Exchange mail. Business Standard adds the desktop versions of the Office apps and the premium version of Outlook. Business Premium bundles Basic, Standard, plus the security stack above, which is the main reason regulated small firms buy it.

The consequence of underbuying is contract or regulatory exposure. A GLBA-covered accountant without Intune device compliance policies cannot enforce the FTC Safeguards Rule requirement to control access on mobile devices. A named example: Dana Ortiz, managing partner at a 40-person CPA firm, upgraded 40 seats from Standard to Premium after her cyber insurance carrier required MFA enforcement and device encryption as conditions of renewal.

A common misconception is that Business Premium is “too much” for a 10-person firm. In practice, the per-user cost difference pays for itself the first time Defender blocks a credential-theft phishing email or the first time Intune wipes a lost phone containing client tax returns.

Apps for Business and Frontline Plans

Apps for Business is the desktop-app-only SKU and still counts against the 300 cap. It does not include Exchange, Teams, or SharePoint, which surprises buyers who assume “Microsoft 365” always includes email. You can read the exact scope on the Apps for Business plan page.

Frontline plans, labeled F1 and F3, sit in the Enterprise family, not the Business family, which is an important licensing nuance. Frontline workers can be mixed into a tenant that also holds Business licenses, but Frontline licenses follow the Microsoft 365 F licensing rules and have their own caps and feature limits. The consequence of confusing these is overspend: a retail chain with 800 cashiers does not need 800 Business Premium seats; it can license them as F3 at a fraction of the price.

A named example: Jordan Park, CIO at a 1,200-employee regional restaurant group, licensed 80 back-office staff on Business Premium and 1,120 kitchen and floor workers on Frontline F3, staying inside Microsoft rules while cutting licensing costs by roughly half compared to an all-Enterprise deployment.

What Happens When You Hit 300 Users

When the 301st hire lands, the admin center blocks you from assigning another Business license, and you have exactly three legitimate paths forward. You can move to an Enterprise plan, mix Business and Enterprise inside the same tenant, or split the company into multiple tenants. Each path has tradeoffs described in the Microsoft 365 licensing guidance.

The consequence of doing nothing is that your HR, payroll, and access-provisioning pipelines break. New hires cannot get email, cannot join Teams meetings, and cannot access company SharePoint. Under the FTC Safeguards Rule, unapproved workarounds such as shared logins create a reportable security incident if discovered.

A common misconception is that Microsoft gives a grace period above 300. It does not. The cap is enforced at purchase, not at audit, which means the block happens in real time the moment you try to assign seat 301.

Mixed Licensing: Business and Enterprise in One Tenant

Microsoft allows Business and Enterprise SKUs to coexist in the same tenant, but with a caveat: Microsoft 365 Apps for Business and Microsoft 365 Apps for Enterprise cannot be mixed on the same machine without careful configuration. The rules are documented in the mixed-license scenarios article.

The consequence of mixing poorly is broken Office installs, failed activations, and help-desk tickets. A real mini-scenario: Rachel Kim, IT lead at a 310-person software firm, upgraded her 10 newest hires to Microsoft 365 E3 and left her original 300 on Business Premium. Because both SKUs ship desktop Office, she had to rebuild deployment policies in the Office Deployment Tool to keep activations clean.

A common misconception is that mixing is a permanent answer. For most firms, it is a bridge. Once you cross 300 meaningfully, the simpler, cheaper long-term answer is to consolidate on Enterprise E3 or E5.

Migrating to Enterprise E3 or E5

Enterprise plans have no user cap, include richer compliance tools, and unlock features like unlimited archive, Purview Data Loss Prevention, and advanced eDiscovery. The migration itself is mostly a license swap inside the same tenant, not a data move, which keeps downtime near zero when done right.

The consequence of rushing the migration is data loss or feature regression. For example, moving from Business Premium to E3 drops Defender for Business, and you must replace it with Defender for Endpoint Plan 1 or add Defender as an add-on, or users lose endpoint protection on day one.

A common misconception is that E5 is always the right Enterprise target. E5 adds Phone System, Defender for Office 365 Plan 2, and Purview premium features. If you do not use those, E3 plus targeted add-ons is usually cheaper and still removes the 300-user cap.

Federal Compliance Considerations

Your license choice has direct federal-law consequences because several U.S. statutes require specific technical safeguards that map to Microsoft 365 features. The big four are HIPAA, GLBA’s Safeguards Rule, SOX, and DFARS / CMMC for defense contractors.

The consequence of a license-compliance mismatch is enforcement action. HHS HIPAA fines can run to millions per violation category, and DoD contractors without CMMC Level 2 attestation are barred from bidding on covered contracts. A named example: Elena Ramirez, compliance officer at a 220-person medical billing company, moved the firm from Business Standard to Business Premium after her auditor flagged the absence of Intune-enforced device encryption as a HIPAA Security Rule gap.

A common misconception is that Microsoft “is HIPAA compliant out of the box.” Microsoft signs a HIPAA Business Associate Agreement, but you remain responsible for configuring the service, training staff, and producing evidence under the HIPAA Security Rule at 45 C.F.R. § 164.308.

HIPAA and Healthcare Tenants

A covered entity or business associate using Microsoft 365 must execute the Microsoft BAA, which is included by default for most commercial Microsoft 365 subscriptions. The scope of the BAA is described in the Microsoft HIPAA/HITECH compliance offering. Business Premium is the practical entry tier for healthcare because it includes device management, DLP, and message encryption.

The consequence of falling short is an Office for Civil Rights investigation, mandatory corrective action plans, and civil monetary penalties. A named example: Dr. Samuel Greene, founder of a 60-provider telehealth group, standardized every clinician on Business Premium to enable enforced MFA, Intune compliance, and Purview sensitivity labels on PHI before the group’s first OCR audit.

A common misconception is that a BAA alone equals compliance. It does not. The BAA is a contract; compliance requires the administrative, physical, and technical safeguards that the HIPAA Security Rule lists, most of which are customer-configured inside the tenant.

GLBA, SOX, and State Privacy Laws

The FTC Safeguards Rule under GLBA requires financial institutions, including many non-bank firms like CPAs and mortgage brokers, to implement written information security programs, access controls, and MFA. SOX Section 404 requires public companies to maintain internal controls over financial reporting, including IT general controls on email and file systems. State laws like CCPA/CPRA in California add data-subject rights that your tenant must be able to honor.

The consequence of non-compliance is regulatory action and private lawsuits. Tomás Ribeiro, CFO at a 275-person fintech, upgraded the company from Business Standard to Business Premium to enable conditional access and Intune, because his SOX auditor flagged unmanaged BYOD laptops as a material weakness.

A common misconception is that “small” companies are exempt. Under the 2023 FTC Safeguards Rule amendments, the MFA and access-control requirements apply at 5,000 consumer records, which most small CPA and lender firms cross quickly.

CMMC and Defense Contractors

Defense contractors handling Controlled Unclassified Information (CUI) must meet CMMC Level 2 by the DoD phased schedule that began rolling out under the final CMMC rule at 32 C.F.R. Part 170. Commercial Microsoft 365 does not meet these requirements for CUI; contractors must use Microsoft 365 GCC High, which is an Enterprise-only offering.

The consequence of staying on commercial Business plans while handling CUI is contract loss and potential False Claims Act exposure, as DOJ’s Civil Cyber-Fraud Initiative actively pursues contractors that misrepresent cybersecurity posture.

A common misconception is that a commercial Business Premium plan plus good hygiene is “close enough” for CUI. It is not. GCC High is required specifically because commercial tenants do not guarantee U.S. data residency or U.S.-person support staff, both of which DFARS 252.204-7012 requires.

Three Real-World Scenarios

Scenario planning helps you see the 300-user cap the way an experienced admin sees it: not as a number, but as a trigger event that forces a strategic choice. The three scenarios below cover the most common patterns observed across Microsoft Partner deployments.

Scenario Table 1: Fast-Growing Startup

Scenario Table 2: Healthcare Practice Expansion

Scenario Table 3: Defense Contractor CUI Handling

Named Examples You Can Learn From

Priya Shah, operations lead at a 290-person logistics firm in Ohio, solved her 300-cap problem by auditing the tenant and deactivating 28 licenses assigned to former employees who were never offboarded. That recovery bought her six months before a real Enterprise migration was needed, and it illustrates the value of a quarterly license audit under the Microsoft 365 admin center reporting tools.

Dr. Samuel Greene, a telehealth founder, chose Business Premium for his 60 providers specifically to meet the HIPAA Security Rule’s technical safeguards at 45 C.F.R. § 164.312. His deployment used Intune compliance policies, Conditional Access, and Purview sensitivity labels, which together created the documented technical safeguards his annual risk analysis required.

Jordan Park, CIO of a restaurant group, mixed 80 Business Premium seats with 1,120 Frontline F3 seats to license a 1,200-person workforce without overpaying. That blend used the Frontline licensing rules documented in the Microsoft 365 Frontline comparison. His approach cut projected licensing spend by roughly half versus an all-E3 deployment.

Elena Ramirez, compliance officer at a medical billing company, standardized on Business Premium to close HIPAA gaps flagged by her external auditor, then built a three-year roadmap to move to E5 once the firm crossed 300 employees. Tomás Ribeiro, a fintech CFO, made a similar call for SOX reasons, choosing Premium today with a planned jump to E3 plus Defender add-ons next fiscal year.

Mistakes to Avoid

• Assuming the cap is soft: Microsoft enforces 300 at purchase time, and there is no appeal, which means waiting until hire day to notice the limit will break onboarding.
• Licensing shared mailboxes: A shared mailbox under 50 GB does not need a license, and assigning one wastes a seat and pushes you toward the cap faster.
• Mixing Apps for Business and Apps for Enterprise on the same device: The two desktop SKUs do not coexist cleanly, and users will hit activation errors documented in the Office deployment troubleshooting guide.
• Forgetting to offboard ex-employees: Stale licenses count against the cap and cost money, and under the FTC Safeguards Rule they also create orphaned access risks.
• Treating Microsoft’s BAA as a compliance finish line: The BAA is a contract, not a configuration, and HHS OCR will still inspect your Security Rule safeguards during an audit.
• Buying E5 when E3 plus add-ons would do: E5 is powerful, but most midsize firms use under 30 percent of the premium features and overpay as a result.
• Handling CUI on a commercial tenant: DFARS 252.204-7012 requires controls and residency that commercial Microsoft 365 cannot guarantee, so you must use GCC High for CUI.
• Ignoring Conditional Access: Business Premium includes Entra ID P1 and Conditional Access, and skipping it leaves MFA enforcement weaker than the FTC Safeguards Rule expects.
• Skipping a quarterly license audit: Most tenants carry 5 to 15 percent waste in stale or misassigned licenses, and that waste often hides the room you need to stay under 300.
• Relying on a second tenant as a long-term fix: Cross-tenant collaboration breaks Teams, SharePoint, and Exchange shared calendaring in subtle ways that burn IT hours.

Do’s and Don’ts

• Do run a quarterly license audit in the admin center, because stale assignments are the single biggest cause of surprise cap hits.
• Do buy Business Premium if you are in a regulated field, because the security stack usually pays for itself in one avoided incident.
• Do plan an Enterprise migration at 250 users, because buying time at 299 is stressful and error-prone.
• Do use Microsoft Entra B2B guests for contractors, because guest accounts do not consume Business seats.

• Do document your license-to-control mapping, because auditors under HIPAA, SOX, and GLBA expect to see it.

• Do not buy a second tenant just to dodge the cap, because cross-tenant collaboration costs more than Enterprise licensing.

• Do not license resource mailboxes or printers, because they do not need a Business seat under the Exchange Online limits.
• Do not assume Business Premium meets CMMC Level 2, because CUI work requires GCC High.
• Do not mix Apps for Business and Apps for Enterprise on the same PC without deployment planning, because activation errors will follow.
• Do not wait until hire day to check your seat count, because the admin center block is instant and cannot be overridden.

Pros and Cons of Staying on Business Plans

• Pro: Lower per-user cost than Enterprise, which protects margins for firms under 300 people.
• Pro: Business Premium bundles Intune, Defender, and AIP at a bundled discount that is hard to beat in Enterprise a la carte.
• Pro: Simpler admin surface than E3 or E5, which suits lean IT teams.
• Pro: HIPAA BAA coverage is included, which matters for small healthcare and allied-health firms.

• Pro: Fast onboarding because the Business admin center is designed for non-specialist admins.

• Con: Hard 300-user cap that forces a migration event at the worst possible time if you did not plan for it.

• Con: No advanced compliance features like Insider Risk Management or Customer Lockbox, which show up in E5.
• Con: No GCC High option, which rules out CUI and certain state and local government work.
• Con: Limited retention and archive ceilings compared to E3 and E5 unlimited archive.
• Con: No Phone System included, which pushes growing firms to add Teams Phone separately.

The Migration Process From Business to Enterprise

A Business-to-Enterprise migration is mostly a license swap inside a single tenant, but the sequence matters. Microsoft documents the recommended steps in the change plan or subscription guide. Doing the steps out of order can drop features users rely on, which is why a test group is non-negotiable.

Step 1: Inventory and Plan

Start by exporting a full license report from the Microsoft 365 admin center and mapping every current feature each user depends on. The consequence of skipping this step is post-migration complaints about missing Defender protections or Intune policies, which happen because E3 does not include Defender for Business and Intune device compliance requires specific add-ons.

A named example: Rachel Kim, IT lead at a 310-person software firm, exported her Business Premium feature list first, then mapped each to an E3 equivalent before buying a single Enterprise seat. That mapping caught the Defender for Business gap before migration, not after.

A common misconception is that “E3 is a superset of Business Premium.” It is not. E3 lacks Defender for Business and Intune compliance patterns that Premium ships by default; those must be added separately or replaced with Defender for Endpoint P1.

Step 2: Pilot with a Test Group

Pilot the E3 or E5 swap on 5 to 10 users covering each major role, run Office activation checks, Teams, SharePoint, and Intune policy enrollment for at least two weeks. The consequence of skipping pilot is discovering at the organization-wide cutover that Conditional Access policies scoped to Business Premium licenses now exclude Enterprise users, which creates access outages.

A real scenario: a 400-person firm rolled out E3 without piloting and found that their Purview sensitivity label policy targeted only Business Premium licenses, leaving Enterprise users without labels for three weeks. That lapse created a DLP gap that their cyber insurance carrier later noted during renewal underwriting.

A common misconception is that pilots delay the project. In practice, a two-week pilot saves weeks of post-cutover help-desk tickets and audit exceptions.

Step 3: Swap Licenses and Decommission

Assign Enterprise licenses, remove Business licenses, and watch the admin center for activation errors during the following 48 hours. The consequence of leaving both licenses assigned is double-billing, because Microsoft bills each assigned license until it is explicitly unassigned or the subscription is canceled under the Microsoft billing rules.

A named example: Tomás Ribeiro ran his fintech migration over a three-day weekend, reassigning licenses in PowerShell batches of 25 users, verifying Office activation and Teams login after each batch. That cadence made rollback easy for any batch that failed, and kept billing clean under Microsoft’s prorated cancellation rules.

A common misconception is that Microsoft automatically refunds the remaining Business term when you move to Enterprise. Microsoft prorates under the new commerce experience rules, and prorated refunds depend on your commitment term, so read the contract before canceling mid-term.

Key Entities You Should Know

• Microsoft Corporation is the licensor, publisher of the Product Terms, and data processor under the BAA and DPA.
• Microsoft Entra ID is the identity directory that stores each user and enforces MFA and Conditional Access.
• HHS Office for Civil Rights is the federal agency that enforces HIPAA against covered entities and business associates.
• Federal Trade Commission is the agency that enforces the GLBA Safeguards Rule and unfair-practices cases against financial institutions.
• Department of Defense CIO publishes the CMMC rule and oversees contractor cybersecurity attestation.
• Securities and Exchange Commission enforces SOX and its IT general control expectations for public issuers.
• California Privacy Protection Agency enforces CCPA and CPRA data subject rights against covered businesses.
• C3PAOs are third-party assessors certified to perform CMMC Level 2 assessments for DoD contractors.
• Microsoft Partner Center is the portal where CSPs manage customer licensing under the new commerce experience.
• NIST publishes SP 800-171 and the Cybersecurity Framework that many of the rules above reference directly.

Tenant Design Choices That Affect the Cap

Tenant design affects how close you run to the 300-user cap because every identity you create, license, or sync from on-premises Active Directory potentially consumes a seat. Use Microsoft Entra Connect scoping filters to prevent sync of accounts that do not need Microsoft 365, like service accounts and disabled users.

The consequence of over-syncing is that the admin center shows hundreds of synced objects, most of which are noise, and license automation tools sometimes assign licenses to all of them. A named example: Priya Shah tightened her Entra Connect OU filters to exclude a stale “Former Employees” OU, which removed 40 ghost accounts and freed seats without a single real person losing access.

A common misconception is that synced-but-unlicensed accounts are harmless. They are harmless for the 300-user cap, but they inflate your directory and increase the phishing attack surface, which raises FTC Safeguards Rule and HIPAA Security Rule risk.

FAQs

Can I have more than 300 users on Microsoft 365 Business?

No. The Business family caps assigned licenses at 300 per tenant. You must use an Enterprise plan like E3 or E5, or a Frontline F1 or F3, to license any user beyond that number.

Does the 300 cap apply per subscription or per tenant?

No, not per subscription. The cap is per tenant across the combined total of Business Basic, Business Standard, Business Premium, and Apps for Business licenses assigned inside that single Microsoft 365 tenant.

Can I mix Business and Enterprise licenses in the same tenant?

Yes. Microsoft permits Business and Enterprise SKUs in one tenant, but you must watch for desktop Office coexistence rules and feature overlaps when users hold both Apps for Business and Apps for Enterprise entitlements.

Do shared mailboxes count against the 300-user limit?

No. A shared mailbox under 50 GB does not require a license and does not count against the cap, provided you do not assign a Business license to that mailbox’s underlying account.

Do guest users count toward the 300 cap?

No. Microsoft Entra B2B guests do not consume Business licenses and therefore do not count, though you should monitor guest activity for security and FTC Safeguards Rule access-control purposes.

Is Microsoft 365 Business Premium HIPAA compliant?

Yes, with proper configuration. Microsoft signs a HIPAA BAA for covered services, but you must configure Intune, Conditional Access, Purview labels, and staff training to meet the HIPAA Security Rule safeguards.

Can defense contractors use Business Premium for CUI?

No. Controlled Unclassified Information requires Microsoft 365 GCC High, which is an Enterprise-only offering that provides the U.S. data residency and personnel controls DFARS 252.204-7012 demands.

Do I need Business Premium for the FTC Safeguards Rule?

Yes, practically speaking. Premium’s MFA, device management, and access controls align to the Safeguards Rule technical requirements, while Business Basic and Standard leave meaningful gaps that your written information security program must otherwise close.

Can I downgrade from Enterprise back to Business?

Yes, if you are under 300 users and willing to lose Enterprise-only features like unlimited archive and advanced eDiscovery. Downgrades must be executed inside your subscription term following Microsoft’s new commerce experience cancellation and change rules.

Will Microsoft raise the 300-user cap in the future?

No indication exists that Microsoft plans to raise it. The cap has stood since the product family’s launch, and Microsoft positions Enterprise as the path forward for anyone crossing the line.

Does buying Microsoft 365 Copilot affect my user cap?

No. Copilot is an add-on to existing base licenses and does not change the 300-user Business cap, though Copilot availability and prerequisites are documented in the Microsoft 365 Copilot licensing guide.

Can nonprofits get higher user limits under Business plans?

No. Nonprofit pricing and grants are generous, but the 300-user technical cap applies identically to nonprofit Business tenants as documented in the Microsoft nonprofit offers.