問題文
Why does the documentation recommend using the Copilot usage metrics API for new integrations rather than the user management API?
選択肢
- The two APIs return identical data through different endpoints, so either may be used and the recommendation is only about which one is more convenient.
- The usage metrics API provides unified telemetry across completions, chat, and agent modes and is the resource being actively developed; the user management API is the source of truth for license and seat information instead.
- The usage metrics API already includes license assignments and seat data, which makes the other API redundant for any new integration.
- The user management API has been deprecated, so new integrations must move off it before it is removed and the usage metrics API is its replacement.