Start from the real task
Copilot Studio treats where computer use runs as a configuration concern, which changes credentials, logging, network access, and recovery.
The same agent action behaves differently when it runs locally, in a hosted environment, or behind a managed network boundary.
A case is not yet a market
The signal matters when it clarifies a real service task, deliverable, and acceptance rule, not when it only shows a demo.
Check the delivery boundary
- Record runtime environment, credential storage, network range, and retry rules for every automated flow
- Keep the test narrow: one service scenario with clear inputs, deliverables, acceptance rules, and human review
What still needs proof
A shared runtime can let one automation inherit credentials or network access meant for another workflow. Keep the original source open so the announcement, the evidence, and this site's interpretation stay separate.