{"resourceId":"ubc-m365-copilot-premium-paid-faculty-staff-agents-studio-withheld-20261015","versions":[{"version":"external-3551c80abad0275f21ff667a905d60c34d5e42b90f727093970df855f75523f6","resource":{"id":"ubc-m365-copilot-premium-paid-faculty-staff-agents-studio-withheld-20261015","title":"UBC offers paid Microsoft 365 Copilot (Premium) to faculty and staff from Oct. 15, keeps students on Copilot Chat, and withholds Copilot Studio and agents pending privacy, security and governance review","organization":"University of British Columbia (UBC IT)","sector":"Higher education","geography":"British Columbia, Canada","publishedAt":"Undated service page; availability from 2026-10-15","publicationDate":null,"eventDate":"2026-10-15","sourceName":"UBC Information Technology","sourceLabel":"University IT service page","sourceUrl":"https://it.ubc.ca/services/artificial-intelligence/microsoft-copilot-ubc","evidenceClass":"standards-guidance","outcomeClass":"emerging","topics":["knowledge-work","developers-agents","governance-procurement"],"finding":"UBC IT's Copilot service page says Copilot Chat (Basic) is available to eligible students, faculty and staff through UBC's Microsoft 365 licensing, while M365 Copilot (Premium) is available to eligible faculty and staff as of Oct. 15, 2026, as a paid annual subscription charged to a Workday worktag after a manager discussion and self-service request. Students keep Copilot Chat only. The page says Premium currently includes Anthropic Claude Opus and Sonnet models and OpenAI models. Copilot Studio and Copilot Agents will not be available at launch while UBC reviews privacy, security, governance, support, licensing and data-access questions and plans testing and pilots. Users must follow UBC's information-security classification standard and validate AI output.","sledRelevance":"A large research university is using departmental chargeback for premium Copilot and explicitly holding back agents and Copilot Studio, decisions many US universities face. Available from Oct. 15, inside the freshness window.","evidence":"University-authored service documentation. No adoption counts, prices in the text read, or outcomes.","architectureImplications":"Premium grounds Copilot in Microsoft Graph data the user can access, so existing permissions define exposure; agents and Studio are deferred.","governanceImplications":"Tiered access (Basic for all, Premium for funded faculty and staff), chargeback approval and a formal review before agents are allowed.","securityPrivacyImplications":"Use must follow UBC's security classification standard; Premium's reach into email, files and meetings makes oversharing a key risk.","caveats":"Canadian institution; BC privacy law differs from US FERPA context. Page is undated and the price is on a linked page not reviewed. Multi-model availability (Claude, OpenAI) is as stated by UBC.","streamIds":["microsoft"],"roles":{"sales":"UBC frames premium Copilot as a funded, opt-in service for faculty and staff, with students on the included Chat tier and agents held back. In university conversations, ask who pays (central or departmental), which roles have high-value Microsoft 365 work, and what review is required before agents. Do not imply UBC reported results or that agents are approved. A sensible offer is help with chargeback design and the agent governance review UBC describes.","engineering":"Premium Copilot reasons over email, files, meetings and chats the user can access, so permissions hygiene is the core engineering concern. Engineers should assess oversharing in SharePoint and OneDrive, map data classifications to Copilot use, and design how departmental licences are assigned and revoked. For agents and Copilot Studio, prepare a test environment and criteria covering data access, connectors and support before any pilot, matching the review areas UBC lists.","delivery":"Delivery should run the request-and-approval workflow, chargeback, onboarding and user guidance on validating output. For the deferred agents and Studio, plan the testing and pilot phase UBC describes: select a few use cases, define data-access rules, and set success and support criteria. Track Premium uptake by unit to see where value is perceived. Communicate clearly to students why their tier differs."},"roleDetails":{"sales":{"customerProblem":"A university wants to offer premium Copilot without central funding for everyone and is unsure about agents.","stakeholders":["CIO","Finance/chargeback","Privacy office","Information security","Faculty and staff unit heads"],"discoveryQuestions":["Who funds premium Copilot licences?","Which roles benefit most from deeper Microsoft 365 integration?","What review must agents and Copilot Studio pass?","How will student access differ?"],"valueHypothesis":"A chargeback model plus staged agent review may let a university scale where value is perceived while containing risk.","potentialEngagement":"Chargeback design and agent/Copilot Studio governance review for a university Copilot service.","unsupportedClaims":["UBC adoption or productivity results","Agents are approved at UBC","Prices (not reviewed)"]},"engineering":{"fit":"Universities on Microsoft 365 with departmental budgets.","architectureIntegration":"M365 Copilot grounded in Graph data; Copilot Chat for all; agents deferred.","prerequisites":["Oversharing assessment","Licence assignment automation","Security classification guidance"],"constraints":["Agents and Studio unavailable at launch","Students limited to Basic"],"security":"Premium's access to mail and files requires permission cleanup and classification rules.","proofOfValue":["Oversharing scan for pilot units","Agent test environment with data-access criteria"]},"delivery":{"work":"Request/approval and chargeback operations; staged agent pilot planning.","dependencies":["Workday worktags","Self-service portal","Governance review"],"ownership":"UBC IT with finance and privacy office.","skillsAdoption":"User guidance on validating output and data classification.","governanceCheckpoints":["Approval before licence assignment","Agent review before pilot","Uptake review by unit"],"acceptanceCriteria":["Proposed: agent pilot only after privacy and security review","Proposed: quarterly uptake report"],"risks":["Oversharing through Graph grounding","Inequity between staff and students","Unmanaged agent sprawl later"]}},"retrievedAt":"2026-10-31T03:08:28Z","enrichedAt":"2026-10-31T03:21:01Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Premium is targeted at high-frequency Microsoft 365 work; students do not get Premium, creating a staff/student capability gap.","procurementImplications":"Departmental chargeback through Workday worktags makes premium Copilot a unit-level budget decision.","operatingModelImplications":"Central IT offers the service, departments fund it, and agent capability waits for a governance review.","sourceVerification":{"openedUrl":"https://it.ubc.ca/services/artificial-intelligence/microsoft-copilot-ubc","referenceExcerpt":"No. Copilot Agents will not be available at launch.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}