Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The following documentation shares answers to frequently asked questions about use case classification in Microsoft 365, Copilot, Copilot agents, Cowork, and other Microsoft AI experiences.
What is use case classification?
Use case classification is an AI-powered capability that identifies and classifies the use cases people commonly work on (for example, go-to-market planning, project scheduling, or executive summary writing) based on their activity in Microsoft 365, Copilot, Copilot agents, Cowork, and other Microsoft AI experiences.
By understanding and classifying the use cases, Microsoft 365 Copilot, Cowork and other AI experiences can deliver more relevant prompts, learning content, and workflow recommendations that fit the work people do.
At the organizational level, aggregated use case classification insights may be surfaced to business leaders, to help them understand AI spend and usage patterns across their organization.
Use case classification uses signals from a user's work activity to classify that activity against a built-in taxonomy of use cases. The predefined taxonomy provides a consistent framework for grouping use cases across supported environments. To learn more about the taxonomy, see Understand business use case taxonomy.
Microsoft does not see the underlying content used to classify use cases or the use cases that AI identifies for a user. A user's individual use case classifications are not visible to other people; organization leaders see use case data only as aggregated insights. Use case classification is not designed for behavioral monitoring, performance management, or employment decisions. It classifies only work-related use cases from a standardized use case taxonomy.
What metrics are used to measure performance?
Microsoft evaluates the accuracy and quality of use case classification using approaches such as LLM-as-a-judge, with human review when needed. These measurements guide ongoing improvements to the system over time.
To support personalized experiences and aggregated insights, Copilot creates and stores metadata for each use case classification.
What are the limitations of use case classification?
Review the following limitations:
- Use case classifications depend on the signals available to Microsoft, such as Microsoft 365 profile data (role, job title) and activity data from Microsoft 365, Copilot, Cowork, Microsoft agents and other Microsoft AI experiences. These signals may not fully reflect all use case classifications an individual performs.
- Use case classifications are mapped to a pre-built standardized use case classification taxonomy. This taxonomy may not capture every possible use case classification variation, which may affect the granularity of the use case classification inferences provided to users and administrators.
- Even within the signals available, AI models cannot be guaranteed to infer use case classifications accurately and may make errors based on a misinterpretation of a user's role or activity. While we aim for the system to be accurate in aggregate, there may be individual use case classification inferences that are significantly inaccurate.
- Users, business leaders and administrators should treat use case classification and aggregate use case classification insights as one source of information among others and apply their own judgment when acting on the data.
- Users can minimize the impact of these limitations by turning off use case classification if they do not wish their activity to be used for this purpose (see the controls described below).
What operational factors and settings allow for effective and responsible use of use case classification?
- Administrators are responsible for understanding their organization's local legal and business requirements, including applicable data protection obligations and Works Council guidelines and for using the available controls to configure use case classification in a manner consistent with those requirements and their business practices.
- Users can turn off use case classification at any time in the Microsoft 365 profile editor, on the Data and privacy tab. When use case classification is turned off for a user, AI will not identify their use case classifications for personalization. Add Link to user controls page.
- Using Feature Access Management, administrators can set default privacy controls for specific users or groups including restricting use case classification or controlling whether inferred use case classifications can be shared with Copilot and agents. Add Link to admin controls section.
- Aggregated insights derived from use case classification are AI-generated and are labeled as such, so that leaders and administrators understand the data is produced by AI.
- Unlike some other AI inference systems, use case classification does not require users to confirm or dismiss individual use case classification inferences. The system operates transparently in the background, and users retain control through the opt-out and administrator controls described above.