Before your first Copilot Managed Runtime pilot
The central operating question is who owns an app after it becomes useful. Use a small internal workflow to connect business ownership, access decisions, development and support.
Start by naming the intended users and data. Document environment membership, app access and data permissions separately. Make the release checkpoint visible: who accepts a version, and how does support identify the version in use?
Give finance a model with visible assumptions. A call-volume estimate is more useful than an unsupported monthly price. Record build consumption separately from runtime and list specialized services explicitly. Replace assumptions with actual usage when the pilot runs.
The downloadable pack provides a decision register and a simple illustrative credit calculation. It is a planning aid, not a tested tenant configuration. This episode examines Microsoft's preview documentation; it does not claim a deployment or measured bill.
When the pilot is complete, retain evidence of the ordinary-user path, a denied-user path and a controlled update. Decide whether expansion is justified by those results and the owner's support capacity.
