{"resourceId":"uthsc-oneit-department-paid-claude-code-microsoft-cowork-20261002","versions":[{"version":"external-ccdeacb33177e04c8f389770a95ef89dee983bca85b675f7b8e8e35bfac8bed9","resource":{"id":"uthsc-oneit-department-paid-claude-code-microsoft-cowork-20261002","title":"UTHSC opens department-purchased Claude Code and Microsoft Cowork licenses, with departments paying licensing fees and Azure usage","organization":"University of Tennessee Health Science Center (UTHSC); UT OneIT","sector":"Public health-sciences university: enterprise IT, software licensing and cloud cost management","geography":"Memphis, Tennessee, United States","publishedAt":"2 October 2026 (UTHSC News announcement by ITS Communications)","publicationDate":"2026-10-02","eventDate":"2026-10-01","sourceName":"UTHSC News","sourceLabel":"Institutional IT announcement","sourceUrl":"https://news.uthsc.edu/announcements/ut-is-now-providing-claude-code-and-microsoft-cowork/","evidenceClass":"vendor-claim","outcomeClass":"emerging","topics":["developers-agents","knowledge-work","governance-procurement","operating-model"],"finding":"Responding to requests, OneIT now offers Microsoft Cowork and premium Claude features, including Claude Code, Claude desktop and GitHub integrations, within the university's enterprise environment, available for purchase from 1 October. Claude for Higher Education licenses cost $20 per month (Standard) or $50 per month (Premium, five times the usage), and staff on personal accounts are steered to buy through OneIT. Cowork, which sends emails, schedules meetings, creates documents and posts in Teams on a user's behalf, requires a subscription connected to the department's Azure subscription, with departments responsible for licensing fees and Azure usage. Why now: not previously archived; it shows the cost-recovery model behind the same agentic-tool expansion UMB announced on 13 October.","sledRelevance":"Makes explicit that agentic AI on campus is arriving as departmental spend with metered cloud consumption, so finance and IT need chargeback, usage monitoring and agent-action controls, not just license approvals.","evidence":"Short institutional announcement with prices; no usage, cost or control details beyond licensing.","architectureImplications":"Cowork runs against the department's Azure subscription; Claude Code and GitHub integrations bring developer workflows into the enterprise tenant.","governanceImplications":"Approval flows through OneIT purchasing; agent actions such as sending email or posting in Teams on users' behalf call for action-level policies (interpretation).","securityPrivacyImplications":"Agents acting in mail, calendar and Teams can expose or send data at scale; the announcement does not describe guardrails.","caveats":"Prices and features as announced; no data-class rules are stated in this item (UT's separate guidance matrix covers that). Published before the last completed run and included as paired evidence.","streamIds":["campus-operations"],"roles":{"sales":"Sales framing: UTHSC shows agentic tools arriving as department-paid seats plus metered Azure consumption. Finance and IT leaders will need cost visibility and agent-action rules before usage grows. A bounded offer is a chargeback and usage-monitoring design for agentic AI. Avoid promising savings; the announcement reports none, and departments are taking on variable costs they may not yet be able to forecast.","engineering":"Engineering framing: Cowork acting in email, calendar and Teams, and Claude Code with GitHub integrations, raise action-level risks. Pre-sales should ask which actions agents may take without confirmation, how Azure consumption is capped per department, and how GitHub integrations are scoped. Proof of value should include a spending-alert test and a review of agent actions logged in Microsoft 365 audit records.","delivery":"Delivery framing: departmental purchasing needs a request workflow, a cost owner per subscription and usage reports. OneIT owns the environment; department business officers own spend. Proposed acceptance: every Cowork subscription has a named budget owner and a monthly usage report, and agent actions in mail and Teams are logged and reviewable by security staff."},"roleDetails":{"sales":{"customerProblem":"Departments want agentic AI tools now, and central IT needs a way to fund and control them.","stakeholders":["CIO and OneIT","Department business officers","Finance and budget office","Information security"],"discoveryQuestions":["How will you cap and report Azure consumption per department?","Which agent actions need user confirmation?","How many staff moved from personal Claude accounts?"],"valueHypothesis":"Interpretation: chargeback and usage reporting could keep variable agent costs predictable.","potentialEngagement":"Chargeback, budget-alert and agent-action policy design for one campus's agentic AI offerings.","unsupportedClaims":["Any productivity result","Total cost or adoption numbers","That agent actions are controlled"]},"engineering":{"fit":"Relevant to campuses offering agentic tools in Microsoft 365 and developer environments.","architectureIntegration":"Cowork connected to department Azure subscriptions; Claude Code with GitHub integrations in the enterprise tenant.","prerequisites":["Azure cost management per subscription","Microsoft 365 audit logging","GitHub organisation controls"],"constraints":["Variable consumption costs","No stated data-class rules in this announcement"],"security":"Define which agent actions require confirmation; scope GitHub integrations; log agent activity.","proofOfValue":["Trigger and verify a departmental budget alert","Review a sample of logged agent actions"]},"delivery":{"work":"Stand up purchase workflow, cost ownership and usage reporting for agentic tools.","dependencies":["Azure billing setup","Licensing workflow","Security policy for agent actions"],"ownership":"OneIT owns the environment; department business officers own spend.","skillsAdoption":"Users need guidance on reviewing agent actions before they send or post.","governanceCheckpoints":["Budget owner named before activation","Agent-action policy reviewed by security"],"acceptanceCriteria":["Proposed: 100% of subscriptions have a named budget owner","Proposed: monthly usage report per department"],"risks":["Unexpected Azure bills","Agents sending or posting incorrect content","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 budgets.","procurementImplications":"Per-seat monthly pricing plus variable Azure consumption billed to departments.","operatingModelImplications":"Central IT provides the enterprise environment; departments carry license and consumption costs.","sourceVerification":{"openedUrl":"https://news.uthsc.edu/announcements/ut-is-now-providing-claude-code-and-microsoft-cowork/","referenceExcerpt":"Because this is a premium AI resource, departments will be responsible for licensing fees and Azure usage.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}