Repository navigation
Add privacy-preserving agent, action, and workflow usage reporting - #1943
Merged
Paul Lizer (paullizer) merged 1 commit intoNov 17, 2026
Conversation
Track actual agent, action and workflow attempts and expose metadata-only reporting in Classic and V2 Activity Logs. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Paul Lizer (paullizer)
merged commit Nov 17, 2026
0015082
into
microsoft:Development
12 of 13 checks passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Linked issue
N/A. The user chose not to create an issue for this work.
Release Notes & Latest Features
Is this visible to end users?
Available to authorized Control Center Activity Logs readers, not ordinary chat users.
Is this admin-facing (Admin Settings, governance, deployment, config)?
Should this become a Latest Feature card?
Screenshot needed for the card?
Version bump
application/single_app/config.pyVERSIONthird segment bumped, or not needed because this is docs-onlydeployers/version.txtbumped, or not needed becausedeployers/was not changedApplication version:
0.261.446->0.261.447. No deployer changes.Testing / validation
Run from the repository root; the offline functional suite used
$env:PYTHONPATH="$PWD\application\single_app;$PWD\functional_tests".python -m pytest -p test_support.cosmos_network_guard functional_tests\test_runtime_usage_reporting_owner.py functional_tests\test_agent_workflow_runtime_usage.py functional_tests\test_action_runtime_usage.py functional_tests\test_control_center_usage.py -q --disable-warnings --tb=short --maxfail=1- 68 passed, with network blocked and real initialized owners/installed SDK point responses.python -m pytest ui_tests\test_control_center_runtime_usage.py ui_tests\test_v2_control_center_activity_logs.py -q --disable-warnings- 18 passed, including Classic/V2 desktop/mobile usage interactions.npm --prefix application\v2_ui run build- passed; existing large-bundle warning remains.node --check application\single_app\static\js\control-center-usage.jsandnode --check application\single_app\static\js\control-center.js- passed.python functional_tests\route_tests\test_route_blueprint_policy_inventory.py- 15/15 passed.python functional_tests\route_tests\test_route_unauthenticated_policy_contract.py- 10/10 passed.python functional_tests\route_tests\test_route_policy_test_coverage.py- 5/5 passed.python functional_tests\test_docs_app_surface_coverage.py- 7/7 passed;python functional_tests\test_docs_site_quality.py- 6/6 passed.git diff --check- passed. Repository XSS/access-control inspectors also passed against the actual changed/new lines.Known validation limitations:
python scripts\check_cosmos_response_boundaries.py --run-contracts- blocked by 18 pre-existing fingerprint gaps in unchangedroute_backend_orchestration.py. Confirmed that file matches the starting HEAD while HEAD's committed inventory already differs. Changed usage owners have zero review gaps; unrelated owner reviews were preserved rather than silently approved. A broader independent contract run was stopped after a failure; no full-suite pass is claimed.python functional_tests\test_logging_tag_standardization.py- fails on existing nonstandard tags. The change introduces no new logging tags.requests.getseam rather thanguarded_request; the agent's broader outcome selection reported 9 passed, 2 failed. Focused new action telemetry coverage passes.Documentation
Added runtime usage feature documentation and updated the administrator/V2 guides, including privacy boundaries, metric interpretation, legacy coverage, retention/storage gaps, and query limits. Separate fix documentation is not applicable. Release-note changes were offered but deferred while the user was unavailable; they are not included here.
Security checklist
@swagger_route(security=get_auth_security())sanitize_settings_for_user()Both API aliases retain Activity Logs authorization; dashboard-reader access alone is insufficient. No settings payload was added. Usage events, report output, and CSV use explicit metadata allowlists; UI values use text-safe rendering and CSV cells receive formula-injection protection.