{"resourceId":"umb-managed-claude-for-education-baa-level1-20261013","versions":[{"version":"external-ccdeacb33177e04c8f389770a95ef89dee983bca85b675f7b8e8e35bfac8bed9","resource":{"id":"umb-managed-claude-for-education-baa-level1-20261013","title":"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","organization":"University of Maryland, Baltimore (UMB) Center for Information Technology Services (CITS)","sector":"Public health, law and human-services university: enterprise IT and software licensing","geography":"Baltimore, Maryland, United States","publishedAt":"13 October 2026 (The Elm announcement)","publicationDate":"2026-10-13","eventDate":"2026-10-13","sourceName":"The Elm (University of Maryland, Baltimore)","sourceLabel":"Institutional IT announcement","sourceUrl":"https://elm.umaryland.edu/announcements/2026/Claude-for-Education-is-Now-Available-at-UMB-.php","evidenceClass":"vendor-claim","outcomeClass":"emerging","topics":["knowledge-work","developers-agents","data-security","governance-procurement"],"finding":"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.","sledRelevance":"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":"Institutional announcement; no usage, cost-recovery or security-review results are reported. The BAA covers eligible services only.","architectureImplications":"SSO with Duo, a central tenant and account migration from personal accounts; connectors and Cowork extend the tool into other systems, which needs scoping.","governanceImplications":"Per-user purchase through the software licensing office; managed use replaces individually managed accounts.","securityPrivacyImplications":"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.","caveats":"Pricing and features as stated by UMB at publication; the BAA's scope by feature is not detailed. No adoption figures.","streamIds":["campus-operations"],"roles":{"sales":"Sales framing: UMB shows the managed-tenant pattern reaching health-sciences campuses, with a BAA and a narrow data approval. The likely need is helping such campuses decide which data classes and connectors to allow next, and how to migrate personal accounts. Avoid implying the BAA clears protected health data for every feature; UMB itself limits approval to Level 1 internal information, and no outcomes are reported.","engineering":"Engineering framing: Claude Code, Cowork and connectors in a tenant approved only for Level 1 internal data mean the controls that matter are connector allow-lists, code-execution policy and SSO-based account lifecycle. Pre-sales should ask which connectors are enabled, how feature-level BAA eligibility is tracked, and how personal accounts are found and migrated. Proof should test that restricted data cannot flow through enabled connectors.","delivery":"Delivery framing: migrating personal Claude accounts into a managed tenant needs an inventory of existing users, a cut-over date and support capacity. CITS owns the tenant; data stewards own classification rules. Proposed acceptance: all known personal-account users migrated or notified by a set date, and a documented connector allow-list reviewed against data classes each term."},"roleDetails":{"sales":{"customerProblem":"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"],"discoveryQuestions":["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?"],"valueHypothesis":"Interpretation: a data-class and connector review could let a campus widen approved use safely; no outcomes are reported here.","potentialEngagement":"A connector and data-class review plus personal-account migration plan for one managed AI tenant.","unsupportedClaims":["That the BAA covers every feature","Any productivity or cost result","Adoption levels"]},"engineering":{"fit":"Relevant to campuses running managed agentic AI tenants with regulated data nearby.","architectureIntegration":"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.","proofOfValue":["Test that restricted data cannot be reached through enabled connectors","Confirm deprovisioning removes tenant access"]},"delivery":{"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.","skillsAdoption":"Users need guidance on what Level 1 internal data means in practice and on agentic features.","governanceCheckpoints":["Connector review before enablement","Data-class approval changes logged"],"acceptanceCriteria":["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"]}},"retrievedAt":"2026-10-18T21:51:50-05:00","enrichedAt":"2026-10-18T22:00:09-05:00","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Access depends on departmental or personal purchase, which may create uneven access across units.","procurementImplications":"Per-seat annual pricing through central licensing; buyers pay.","operatingModelImplications":"Central IT runs the tenant and support mailbox; units fund seats.","sourceVerification":{"openedUrl":"https://elm.umaryland.edu/announcements/2026/Claude-for-Education-is-Now-Available-at-UMB-.php","referenceExcerpt":"agreement with Anthropic includes a Business Associate Agreement (BAA), providing additional contractual protections for eligible services.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}