From the Campus Operations edition of October 18, 2026
University of Maryland, Baltimore launches a university-managed Claude for Education environment with a BAA, approved for Level 1 internal data, at $200 or $600 per user per year
University of Maryland, Baltimore (UMB) Center for Information Technology Services (CITS) · Public health, law and human-services university: enterprise IT and software licensing · Baltimore, Maryland, United States
- Publisher
- The Elm (University of Maryland, Baltimore)
- Original publication
- 13 October 2026 (The Elm announcement)
- Source retrieved
- 2026-10-19
- Event date
- 2026-10-13
What happened
UMB made a university-managed Claude for Education environment available to faculty, staff and students who buy a license, for teaching, research and administrative work. Access uses UMB credentials and Duo. UMB's agreement with Anthropic includes a Business Associate Agreement, and the service is approved for UMB Level 1 Internal Information, subject to policy and feature limits. Licenses are $200 per year (Standard) or $600 per year (Premium, about five times the usage), and both include web search, code execution, Claude Code, Cowork and connectors. Existing Claude users will be migrated. Why now: not previously archived, and part of a run of campuses moving premium agentic AI into managed, paid tenants this month.
Why it matters
Shows a health-sciences campus pairing a BAA with a narrow data approval (Level 1 internal only) while still exposing agentic features such as Claude Code, Cowork and connectors to buyers, which shifts risk management onto connector and data-class controls.
Evidence and measured results
Institutional announcement; no usage, cost-recovery or security-review results are reported. The BAA covers eligible services only.
Limitations and uncertainty
Pricing and features as stated by UMB at publication; the BAA's scope by feature is not detailed. No adoption figures.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-18; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Health-sciences campuses want premium AI under contract while keeping regulated data out until controls are proven.
- Stakeholders
- CIO and CITS
- Privacy and HIPAA officers
- Software licensing office
- Deans and department administrators
- Discovery questions
- Which data classes will you approve next, and what evidence would you need?
- Which connectors are enabled in your tenant?
- How many staff still use personal AI accounts for university work?
- Value hypothesis
- Interpretation: a data-class and connector review could let a campus widen approved use safely; no outcomes are reported here.
- Potential engagement
- A connector and data-class review plus personal-account migration plan for one managed AI tenant.
- Unsupported claims
- That the BAA covers every feature
- Any productivity or cost result
- Adoption levels
Pre-sales engineering
Role takeaway
- Fit
- Relevant to campuses running managed agentic AI tenants with regulated data nearby.
- Architecture and integration
- SSO with Duo, central tenant, connectors and code execution, account migration from personal plans.
- Prerequisites
- Data classification scheme
- Feature-level BAA eligibility list
- Identity lifecycle via SSO
- Constraints
- Approval limited to Level 1 internal data
- Feature limits on BAA coverage
- Per-seat cost
- Security
- Restrict connectors and code execution to approved data; track which features are BAA-eligible.
- Proof of value
- Test that restricted data cannot be reached through enabled connectors
- Confirm deprovisioning removes tenant access
Delivery
Role takeaway
- Work
- Migrate personal accounts, publish data-class rules and maintain a connector allow-list.
- Dependencies
- Tenant administration with the vendor
- Data steward input
- Licensing office workflow
- Ownership
- CITS owns the tenant; data stewards own classification rules.
- Skills and adoption
- Users need guidance on what Level 1 internal data means in practice and on agentic features.
- Governance checkpoints
- Connector review before enablement
- Data-class approval changes logged
- Acceptance criteria
- Proposed: known personal-account users migrated or notified by a set date
- Proposed: connector allow-list reviewed each term
- Risks
- Users assume the BAA means any PHI is allowed
- Connectors expose restricted systems
- Uneven access by budget
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
SSO with Duo, a central tenant and account migration from personal accounts; connectors and Cowork extend the tool into other systems, which needs scoping.
Governance
Who approves, reviews and stays accountable for outcomes?
Per-user purchase through the software licensing office; managed use replaces individually managed accounts.
Security and privacy
What data, permissions and controls need testing?
A BAA is in place, but approved data is limited to Level 1 internal information and features may carry further limits. Connectors and code execution widen the attack surface.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Access depends on departmental or personal purchase, which may create uneven access across units.
Procurement
What should contracts, pricing and exit terms secure?
Per-seat annual pricing through central licensing; buyers pay.
Operating model
Which teams own the service once it runs?
Central IT runs the tenant and support mailbox; units fund seats.
Publication history
- 2026-10-18Campus Operations · Issue 417 resources
Stable resource ID: umb-managed-claude-for-education-baa-level1-20261013