Microsoft Copilot Studio Hardening Guide
Harden Copilot Studio agent identity, connectors, MCP, delegated agents, computer use, model providers and retained artifacts.
Overview
This is a product guide within the Microsoft platform. Apply the hub’s tenant MFA, privilege management, OAuth consent and audit requirements, plus Microsoft Entra ID policies. Those do not configure Copilot Studio’s separate Power Platform and agent control surfaces.
Intended Audience
Power Platform administrators, agent owners, security engineers and reviewers of third-party integrations.
How to Use This Guide
- L1 (Crawl): Minimum production controls.
- L2 (Walk): Enhanced controls for sensitive workflows.
- L3 (Run): Regulated deployments must additionally validate their specific edition, region and authorization boundary.
Scope
Microsoft Copilot Studio, principally its standard harness, Power Platform environments, Dataverse records and connected tools. New GitHub Copilot/Customer Conversation harnesses have different feature availability; validate applicability rather than assuming identical settings. This is not a complete Microsoft 365 Copilot or Foundry guide. No tenant was modified or live-validated.
This guide reconciles Pluto’s CopilotSec research with current Microsoft documentation. The research ledger records coverage, conflicting defaults and unresolved surfaces. Security recommendations below are HTH’s deployment choices, not claims that a model can enforce a policy by instructions alone.
Table of Contents
- Identity and production ownership
- Integration supply chain
- Execution and model boundaries
- Retention and monitoring
- Compliance Quick Reference
1. Identity and production ownership
1.1 Require authentication on every production channel
Profile Level: L1 (Crawl)
| Framework | Relevant controls |
|---|---|
| NIST SP 800-53 Rev. 5 | AC-3, IA-2 |
Description
Require an identity check before an internal agent exposes data or actions. Inventory every published channel; an authenticated Teams deployment does not prove that a second web channel is protected.
Rationale
Why This Matters:
- Anonymous callers must not inherit privileged integrations.
- Review permissions at each boundary, not just the sign-in screen.
Attack Prevented: Unauthenticated access to internal agents.
ClickOps Implementation
- Open the agent’s Settings > Security > Authentication. Select Authenticate with Microsoft, or configure Authenticate manually for a supported deployment.
- Save and Publish; an unsaved or unpublished authentication change does not protect the live agent.
- Review Channels and retire unused public/demo deployments. Apply the tenant policy in §2.1 to prevent makers restoring anonymous access.
Code Implementation
Code Pack: API Script
: "${DATAVERSE_URL:?Set the HTTPS Dataverse organization origin}"
: "${DATAVERSE_TOKEN:?Supply a short-lived token for that organization}"
export DATAVERSE_URL DATAVERSE_TOKEN
python3 - <<'CHECK'
import os, urllib.parse
if any(ord(c)<32 or ord(c)==127 for c in os.environ['DATAVERSE_URL']+os.environ['DATAVERSE_TOKEN']):
raise SystemExit('Control characters are not allowed in URL or token')
u=urllib.parse.urlsplit(os.environ['DATAVERSE_URL'])
if u.scheme!='https' or not u.hostname or u.username or u.password or u.query or u.fragment or u.path not in ('','/'):
raise SystemExit('DATAVERSE_URL must be an HTTPS origin, without credentials or a path')
CHECK
origin="${DATAVERSE_URL%/}"
# Do not place tokens in command arguments or follow redirects.
work=$(mktemp -d)
trap 'rm -rf "$work"' EXIT
chmod 700 "$work"
umask 077
printf 'Authorization: Bearer %s\n' "$DATAVERSE_TOKEN" > "$work/headers"
url="$origin/api/data/v9.2/bots?\$select=botid,name,authenticationmode,authenticationtrigger,accesscontrolpolicy,statecode"
: > "$work/rows"
: > "$work/seen"
while [[ -n "$url" ]]; do
# A foreign-origin nextLink must never receive the bearer token.
PAGE_URL="$url" python3 - <<'CHECK'
import os, urllib.parse
if any(ord(c)<32 or ord(c)==127 for c in os.environ['PAGE_URL']):
raise SystemExit('Control characters are not allowed in pagination')
b=urllib.parse.urlsplit(os.environ['DATAVERSE_URL'])
u=urllib.parse.urlsplit(os.environ['PAGE_URL'])
if (u.scheme,u.netloc)!=(b.scheme,b.netloc) or u.username or u.password or not u.path.startswith('/api/data/v9.2/') or u.fragment:
raise SystemExit('Rejected unsafe pagination URL')
CHECK
if grep -Fqx -- "$url" "$work/seen"; then echo 'Repeated pagination URL' >&2; exit 1; fi
printf '%s\n' "$url" >> "$work/seen"
status=$(curl -q --silent --show-error --fail --max-time 60 --connect-timeout 15 --max-redirs 0 --max-filesize 52428800 --proto '=https' \
--header @"$work/headers" --header 'Accept: application/json' \
--header 'OData-Version: 4.0' --header 'OData-MaxVersion: 4.0' \
--header 'Prefer: odata.maxpagesize=500' --output "$work/page" --write-out '%{http_code}' "$url")
[[ "$status" == 200 ]] || { echo "Unexpected HTTP status: $status" >&2; exit 1; }
jq -e '(.value | type == "array") and ((has("error")) | not) and all(.value[]; type == "object" and (.botid | type == "string" and length > 0))' "$work/page" >/dev/null
jq -c '.value[] | {botid,name,statecode,authenticationmode,authenticationtrigger,accesscontrolpolicy,review:(if .authenticationmode == 1 then "NO_AUTH" elif .authenticationmode == 0 then "UNSPECIFIED_REVIEW" elif .authenticationmode == 2 then "INTEGRATED_VERIFY_CHANNELS" elif .authenticationmode == 3 then "CUSTOM_ENTRA_VERIFY_CONFIG" elif .authenticationmode == 4 then "GENERIC_OAUTH_VERIFY_CONFIG" else "UNKNOWN_REVIEW" end)}' "$work/page" >> "$work/rows"
url=$(jq -er 'if .["@odata.nextLink"] == null then "" elif (.["@odata.nextLink"] | type) == "string" then .["@odata.nextLink"] else error("Invalid nextLink") end' "$work/page")
done
jq -e -s 'map(.botid) | length == (unique | length)' "$work/rows" >/dev/null
jq -s 'sort_by(.botid)' "$work/rows"
Validation & Testing
Test each published URL signed out and with an unauthorized account. Both must fail before sensitive tools or knowledge run. Re-test after publishing.
Sources: User authentication.
1.2 Separate production makers, operators, and readers
Profile Level: L1 (Crawl)
| Framework | Relevant controls |
|---|---|
| NIST SP 800-53 Rev. 5 | AC-6, CM-3 |
Description
Use dedicated production environments and narrowly assigned maker roles. A colleague allowed to chat should not automatically become an editor. Maintain an accountable owner and reviewed release record for each agent.
Rationale
Why This Matters:
- Editing an agent changes its effective supply chain.
- Review permissions at each boundary, not just the sign-in screen.
Attack Prevented: Unauthorized agent modification and privilege expansion.
ClickOps Implementation
- In the Power Platform admin center, restrict environment membership using approved Microsoft Entra security groups.
- Assign authoring roles only to approved makers through Dataverse group teams. Avoid routine System Administrator access.
- In the agent’s … > Share, distinguish collaboration from permission to chat; review recipients and role changes before saving.
- Require independent approval before promoting changes to production.
Code Implementation
Code Pack: CLI Script
: "${DATAVERSE_ENVIRONMENT:?Set an explicit environment GUID or HTTPS URL}"
command -v pac >/dev/null || { echo 'Install the official Power Platform CLI first' >&2; exit 1; }
pac copilot list --environment "$DATAVERSE_ENVIRONMENT"
Validation & Testing
A chat-only test user must not edit tools, instructions or sharing. Confirm production changes have a reviewer and compare the agent inventory with your approved register.
Sources: Secure projects; Sharing.
1.3 Prevent unintended use of maker credentials
Profile Level: L1 (Crawl)
| Framework | Relevant controls |
|---|---|
| NIST SP 800-53 Rev. 5 | AC-3, AC-6 |
Description
For user-driven internal agents, require end-user credentials rather than lending every caller the maker’s authority. Handle unattended workloads separately with explicitly reviewed least-privilege identities.
Rationale
Why This Matters:
- A valid caller is not necessarily entitled to the maker’s permissions.
- Review permissions at each boundary, not just the sign-in screen.
Attack Prevented: Confused-deputy access through shared credentials.
ClickOps Implementation
- In Power Platform admin center > Manage > Environments > [environment] > Settings > Product > Features > Copilot Studio agents, set Control maker credential options to End-user credentials for the user-driven environment.
- For grouped environments, configure the environment group instead.
- Pilot first: enforcement affects existing tools and can break scheduled/background agents that lack a live user. Do not quietly restore maker credentials to fix those failures.
Automation: Unverified for direct enforcement of this precise setting in this review. Use the documented console path; the surface census records known APIs and remaining schema gaps rather than asserting no automation exists.
Validation & Testing
Try an action with a user who lacks permission at the target service. It must remain denied. Test autonomous workloads separately before rollout.
Sources: Credential governance.
2. Integration supply chain
2.1 Enforce connector, channel, trigger, and HTTP data policies
Profile Level: L1 (Crawl)
| Framework | Relevant controls |
|---|---|
| NIST SP 800-53 Rev. 5 | AC-4 |
Description
Establish a scoped Power Platform data policy for production. Use Blocked for disallowed capabilities; Non-business is a segregation group, not an unconditional deny.
Rationale
Why This Matters:
- A prompt is not an egress policy.
- Review permissions at each boundary, not just the sign-in screen.
Attack Prevented: Exfiltration through unapproved connectors or channels.
ClickOps Implementation
- In the Power Platform admin center, create or edit a Data policy, classify connectors, select environments, and review before saving.
- Block Chat without Microsoft Entra ID authentication in Copilot Studio. Block unused Direct Line and other publication channels, HTTP, skills, and event triggers.
- Put approved business connectors together; explicitly block rejected connectors, including those underlying MCP. Use documented endpoint filtering where HTTP is necessary.
- Test effects on existing agents. Current Microsoft documentation specifies real-time enforcement, not merely a publish-time check.
Automation: Unverified for direct enforcement of this precise setting in this review. Use the documented console path; the surface census records known APIs and remaining schema gaps rather than asserting no automation exists.
Validation & Testing
Attempt a blocked connector in a test agent and in an already-published test deployment. Confirm a policy violation and preserve the approved exception list.
Sources: Copilot data policies; Policy configuration.
2.2 Constrain HTTP destinations and render structured output
Profile Level: L2 (Walk)
| Framework | Relevant controls |
|---|---|
| NIST SP 800-53 Rev. 5 | SI-10 |
Description
Do not echo an arbitrary upstream response as authoritative company guidance. Use fixed destinations, validate returned values and render only necessary fields through a maker-controlled template. Structured JSON alone does not make strings or URLs trustworthy.
Rationale
Why This Matters:
- A compromised endpoint can return convincing instructions.
- Review permissions at each boundary, not just the sign-in screen.
Attack Prevented: Upstream content injection and phishing through agent output.
ClickOps Implementation
- In the relevant Topic, inspect Advanced > Send HTTP request nodes. Replace user-controlled destination URLs with approved destinations and enforce §2.1 endpoint restrictions.
- Set Response data type > From Sample Data > Get schema from sample JSON for the expected response shape.
- Render approved fields, not the whole response body; reject unexpected URLs, values and errors. Keep external-source attribution outside upstream-controlled text.
Automation: Unverified for direct enforcement of this precise setting in this review. Use the documented console path; the surface census records known APIs and remaining schema gaps rather than asserting no automation exists.
Validation & Testing
Feed an unexpected URL, extra field, markup and error body from a test endpoint. None should become a trusted link or instruction; malformed responses should fail closed.
Sources: HTTP nodes.
2.3 Allowlist MCP tools and review upstream changes
Profile Level: L2 (Walk)
| Framework | Relevant controls |
|---|---|
| NIST SP 800-53 Rev. 5 | CM-3, AC-6 |
Description
Treat MCP servers as changing dependencies. Approving a server is not approval of every future tool or changed description.
Rationale
Why This Matters:
- Server updates can expand agent capabilities without a new integration.
- Review permissions at each boundary, not just the sign-in screen.
Attack Prevented: Tool poisoning and supply-chain capability expansion.
ClickOps Implementation
- Open Agent > Tools > [MCP server]. Turn Allow all off and enable only approved individual tools.
- Save and publish. With Allow all off, newly introduced tools remain disabled by default.
- Apply data policy to the underlying connector, review server identity and permissions, and compare tool names, descriptions and schemas with the approved baseline.
- Remove unused servers; do not trust a catalog risk score as authorization.
Automation: Unverified for direct enforcement of this precise setting in this review. Use the documented console path; the surface census records known APIs and remaining schema gaps rather than asserting no automation exists.
Validation & Testing
Add a harmless test tool on an owned test server and confirm it stays disabled. Change a description and verify your review process detects it. A tool inventory is not proof that runtime content is safe.
Sources: MCP selection; Dynamic MCP behavior.
2.4 Review child agents, routing, and completion boundaries
Profile Level: L2 (Walk)
| Framework | Relevant controls |
|---|---|
| NIST SP 800-53 Rev. 5 | CM-3, AC-6 |
Description
Inventory delegated agents and their instructions, tools and inputs alongside the parent. Choose explicit invocation for sensitive operations rather than broad description-based routing.
Rationale
Why This Matters:
- A parent can delegate authority to a less-reviewed dependency.
- Review permissions at each boundary, not just the sign-in screen.
Attack Prevented: Routing hijack and unreviewed delegated actions.
ClickOps Implementation
- Open the parent’s Agents page and inspect each child, its owner, instructions, tools and knowledge.
- In child details, review When will this be used? and Outputs > After running.
- Do not treat a fixed parent response or adaptive card as a child-output security filter: these choices govern the parent’s completion, not messages the child sends while executing.
- Review component changes before release; the hash pack flags changes for review, not maliciousness.
Code Implementation
Code Pack: API Script
: "${DATAVERSE_URL:?Set the HTTPS Dataverse organization origin}"
: "${DATAVERSE_TOKEN:?Supply a short-lived token for that organization}"
export DATAVERSE_URL DATAVERSE_TOKEN
python3 - <<'CHECK'
import os, urllib.parse
if any(ord(c)<32 or ord(c)==127 for c in os.environ['DATAVERSE_URL']+os.environ['DATAVERSE_TOKEN']):
raise SystemExit('Control characters are not allowed in URL or token')
u=urllib.parse.urlsplit(os.environ['DATAVERSE_URL'])
if u.scheme!='https' or not u.hostname or u.username or u.password or u.query or u.fragment or u.path not in ('','/'):
raise SystemExit('DATAVERSE_URL must be an HTTPS origin, without credentials or a path')
CHECK
origin="${DATAVERSE_URL%/}"
# Do not place tokens in command arguments or follow redirects.
work=$(mktemp -d)
trap 'rm -rf "$work"' EXIT
chmod 700 "$work"
umask 077
printf 'Authorization: Bearer %s\n' "$DATAVERSE_TOKEN" > "$work/headers"
url="$origin/api/data/v9.2/botcomponents?\$select=botcomponentid,name,schemaname,componenttype,data,content,modifiedon"
: > "$work/rows"
: > "$work/seen"
while [[ -n "$url" ]]; do
# A foreign-origin nextLink must never receive the bearer token.
PAGE_URL="$url" python3 - <<'CHECK'
import os, urllib.parse
if any(ord(c)<32 or ord(c)==127 for c in os.environ['PAGE_URL']):
raise SystemExit('Control characters are not allowed in pagination')
b=urllib.parse.urlsplit(os.environ['DATAVERSE_URL'])
u=urllib.parse.urlsplit(os.environ['PAGE_URL'])
if (u.scheme,u.netloc)!=(b.scheme,b.netloc) or u.username or u.password or not u.path.startswith('/api/data/v9.2/') or u.fragment:
raise SystemExit('Rejected unsafe pagination URL')
CHECK
if grep -Fqx -- "$url" "$work/seen"; then echo 'Repeated pagination URL' >&2; exit 1; fi
printf '%s\n' "$url" >> "$work/seen"
status=$(curl -q --silent --show-error --fail --max-time 60 --connect-timeout 15 --max-redirs 0 --max-filesize 52428800 --proto '=https' \
--header @"$work/headers" --header 'Accept: application/json' \
--header 'OData-Version: 4.0' --header 'OData-MaxVersion: 4.0' \
--header 'Prefer: odata.maxpagesize=500' --output "$work/page" --write-out '%{http_code}' "$url")
[[ "$status" == 200 ]] || { echo "Unexpected HTTP status: $status" >&2; exit 1; }
jq -e '(.value | type == "array") and ((has("error")) | not) and all(.value[]; type == "object" and (.botcomponentid | type == "string" and length > 0))' "$work/page" >/dev/null
python3 - "$work/page" >> "$work/rows" <<'HASH'
import json,sys,hashlib
for row in json.load(open(sys.argv[1]))['value']:
data=row.get('data')
content=row.get('content')
row={k:row.get(k) for k in ('botcomponentid','name','schemaname','componenttype','modifiedon')}
row['data_sha256']=hashlib.sha256(data.encode()).hexdigest() if isinstance(data,str) else None
row['content_sha256']=hashlib.sha256(content.encode()).hexdigest() if isinstance(content,str) else None
print(json.dumps(row,sort_keys=True))
HASH
url=$(jq -er 'if .["@odata.nextLink"] == null then "" elif (.["@odata.nextLink"] | type) == "string" then .["@odata.nextLink"] else error("Invalid nextLink") end' "$work/page")
done
jq -e -s 'map(.botcomponentid) | length == (unique | length)' "$work/rows" >/dev/null
jq -s 'sort_by(.botcomponentid)' "$work/rows"
Validation & Testing
Trigger sensitive and unrelated queries. Confirm only intended agents run, inspect every user-visible child message, and test tool permissions independently of wording.
Sources: Child-agent behavior.
3. Execution and model boundaries
3.1 Disable unnecessary computer use and constrain approved runs
Profile Level: L2 (Walk)
| Framework | Relevant controls |
|---|---|
| NIST SP 800-53 Rev. 5 | AC-6, SC-7 |
Description
Treat computer use as a separate execution and credential boundary. Disable the tool when unnecessary; approved runs require limited destinations and a managed machine.
Rationale
Why This Matters:
- A browser session may possess more authority than the chat user.
- Review permissions at each boundary, not just the sign-in screen.
Attack Prevented: Desktop-mediated data exfiltration and privileged actions.
ClickOps Implementation
- In Agent > Tools, disable unused computer-use tools. For approved tools, select the intended Machine, enable Access control with explicit websites/apps, and turn Enforce HTTPS on.
- Prefer per-user machine credentials for conversational workflows. Keep passwords out of instructions; review stored credential scope and run artifacts.
- Use a dedicated managed machine. The Microsoft-hosted browser is not tenant Entra-joined or Intune-managed; both hosted-browser and Cloud-PC-pool options are documented as preview.
- Test human supervision and approval requirements before enabling writes.
Automation: Unverified for direct enforcement of this precise setting in this review. Use the documented console path; the surface census records known APIs and remaining schema gaps rather than asserting no automation exists.
Validation & Testing
Attempt a harmless action outside the allowlist. Access control restricts interaction, not opening a site; it is not a network firewall. Check screenshots, logs and target permissions using synthetic data.
Sources: Computer use; Runtime choices.
3.2 Limit dynamic tool execution and require confirmation
Profile Level: L2 (Walk)
| Framework | Relevant controls |
|---|---|
| NIST SP 800-53 Rev. 5 | AC-3, SI-10 |
Description
For sensitive tools, use explicit topic invocation, fixed validated inputs and end-user confirmation. Treat these as complementary controls, not a substitute for target-system authorization.
Rationale
Why This Matters:
- Broad orchestration can select a powerful tool from untrusted context.
- Review permissions at each boundary, not just the sign-in screen.
Attack Prevented: Unintended consequential tool execution.
ClickOps Implementation
- Open Agent > Tools > [tool] > Details > Additional details. Clear Allow agent to decide dynamically when to use the tool where explicit invocation is required.
- Set Ask the end user before running to Yes for consequential user-driven actions.
- Under Inputs, validate values and use Custom value for destinations or other parameters that users/model inference must not choose.
Automation: Unverified for direct enforcement of this precise setting in this review. Use the documented console path; the surface census records known APIs and remaining schema gaps rather than asserting no automation exists.
Validation & Testing
Try to invoke the tool indirectly from retrieved content and use an out-of-range input. Confirm no action occurs without the intended topic, valid parameters and required approval.
Sources: Tool controls.
3.3 Approve model providers across every model-using component
Profile Level: L2 (Walk)
| Framework | Relevant controls |
|---|---|
| NIST SP 800-53 Rev. 5 | SA-9, CM-3 |
Description
Maintain a provider/model allowlist covering the agent, prompt tools and computer use. A primary-model selection alone does not describe the complete processing chain.
Rationale
Why This Matters:
- Different components can send data to different approved processors.
- Review permissions at each boundary, not just the sign-in screen.
Attack Prevented: Unreviewed processing and incompatible residency/compliance assumptions.
ClickOps Implementation
- Review each provider’s processing terms and deployment suitability before enabling it in Microsoft 365.
- In Power Platform admin center > Manage > Environments > [environment] > Settings > Product > Features, turn unapproved external provider settings off. Use group rules for managed environment groups.
- Review the agent’s model selection and every prompt/computer-use model. Exclude preview/experimental options from production unless separately approved; validate supported alternatives before disabling a used provider.
Automation: Unverified for direct enforcement of this precise setting in this review. Use the documented console path; the surface census records known APIs and remaining schema gaps rather than asserting no automation exists.
Validation & Testing
Verify unapproved providers are unavailable to makers and exercise existing agents after the change. Capture provider, model, region and component in the release record.
Sources: External model controls; Model lifecycle.
3.4 Restrict grounding and validate moderation behavior
Profile Level: L2 (Walk)
| Framework | Relevant controls |
|---|---|
| NIST SP 800-53 Rev. 5 | SI-10 |
Description
Use approved knowledge sources for policy-sensitive answers. Disable unnecessary web search and unsupported-answer paths, while recognizing that grounding and moderation do not eliminate prompt injection.
Rationale
Why This Matters:
- Open-ended sources widen what can influence an answer.
- Review permissions at each boundary, not just the sign-in screen.
Attack Prevented: Untrusted grounding and fabricated authoritative responses.
ClickOps Implementation
- Review both Knowledge sources and topic-level generative-answer nodes. Remove unapproved sources.
- In Generative AI > Knowledge, turn Allow ungrounded responses off and disable Use information from the web/Web Search unless required.
- Review content moderation for the agent and topic overrides. Choose the strictest level compatible with the approved use case and test it.
Automation: Unverified for direct enforcement of this precise setting in this review. Use the documented console path; the surface census records known APIs and remaining schema gaps rather than asserting no automation exists.
Validation & Testing
Ask questions outside the approved corpus, including malicious instructions in test documents. Confirm fallback behavior. Turning off ungrounded responses does not prevent general knowledge being combined with retrieved material.
Sources: Knowledge configuration; Prompt-model settings.
4. Retention and monitoring
4.1 Set transcript access and retention independently
Profile Level: L2 (Walk)
| Framework | Relevant controls |
|---|---|
| NIST SP 800-53 Rev. 5 | AU-9, AU-11 |
Description
Approve who can read conversation records and how long each copy persists. Distinguish Dataverse retention from temporary Copilot Studio storage and Purview records.
Rationale
Why This Matters:
- Conversation evidence can become a second sensitive-data repository.
- Review permissions at each boundary, not just the sign-in screen.
Attack Prevented: Unauthorized disclosure through retained conversation data.
ClickOps Implementation
- In Power Platform admin center > Manage > Environments > [environment] > Settings > Product > Features > Copilot Studio agents, configure transcript viewing/downloading and saving deliberately. Use group rules where required.
- In Power Apps, review ConversationTranscript retention and approved cleanup processes, preserving legal holds. Do not assume hiding downloads deletes stored data.
- Account for temporary Copilot Studio storage (up to 28 days) and separate Purview retention. Turning Dataverse saving off can take up to 24 hours and affects reporting.
Automation: Unverified for direct enforcement of this precise setting in this review. Use the documented console path; the surface census records known APIs and remaining schema gaps rather than asserting no automation exists.
Validation & Testing
With synthetic conversations, verify allowed/denied viewers, saved records, and expiration in each store. Test the incident-response workflow before shortening retention.
Sources: Transcript controls; Power Apps transcripts.
4.2 Audit access to run artifacts without exporting secrets
Profile Level: L2 (Walk)
| Framework | Relevant controls |
|---|---|
| NIST SP 800-53 Rev. 5 | AC-6, AU-9 |
Description
Review Dataverse privileges and retention for computer-use artifacts separately from normal transcripts. Screenshots and detailed logs can reveal sensitive material.
Rationale
Why This Matters:
- A workflow’s data exposure can outlive its execution.
- Review permissions at each boundary, not just the sign-in screen.
Attack Prevented: Overbroad access to stored execution artifacts.
ClickOps Implementation
- Review environment security roles and effective table permissions, including custom roles and application users; do not rely on role names alone.
- Use Power Apps > Tables > All to inspect the relevant artifact tables with an approved administrator. Inventory metadata before opening content.
- Define approved retention/cleanup for artifacts and document legal-hold exceptions. The supplied inventory is read-only and never deletes records or downloads binary contents.
Code Implementation
Code Pack: API Script
: "${DATAVERSE_URL:?Set the HTTPS Dataverse organization origin}"
: "${DATAVERSE_TOKEN:?Supply a short-lived token for that organization}"
export DATAVERSE_URL DATAVERSE_TOKEN
python3 - <<'CHECK'
import os, urllib.parse
if any(ord(c)<32 or ord(c)==127 for c in os.environ['DATAVERSE_URL']+os.environ['DATAVERSE_TOKEN']):
raise SystemExit('Control characters are not allowed in URL or token')
u=urllib.parse.urlsplit(os.environ['DATAVERSE_URL'])
if u.scheme!='https' or not u.hostname or u.username or u.password or u.query or u.fragment or u.path not in ('','/'):
raise SystemExit('DATAVERSE_URL must be an HTTPS origin, without credentials or a path')
CHECK
origin="${DATAVERSE_URL%/}"
# Do not place tokens in command arguments or follow redirects.
work=$(mktemp -d)
trap 'rm -rf "$work"' EXIT
chmod 700 "$work"
umask 077
printf 'Authorization: Bearer %s\n' "$DATAVERSE_TOKEN" > "$work/headers"
url="$origin/api/data/v9.2/flowsessionbinaries?\$select=flowsessionbinaryid,createdon,modifiedon,statecode,mimetype"
: > "$work/rows"
: > "$work/seen"
while [[ -n "$url" ]]; do
# A foreign-origin nextLink must never receive the bearer token.
PAGE_URL="$url" python3 - <<'CHECK'
import os, urllib.parse
if any(ord(c)<32 or ord(c)==127 for c in os.environ['PAGE_URL']):
raise SystemExit('Control characters are not allowed in pagination')
b=urllib.parse.urlsplit(os.environ['DATAVERSE_URL'])
u=urllib.parse.urlsplit(os.environ['PAGE_URL'])
if (u.scheme,u.netloc)!=(b.scheme,b.netloc) or u.username or u.password or not u.path.startswith('/api/data/v9.2/') or u.fragment:
raise SystemExit('Rejected unsafe pagination URL')
CHECK
if grep -Fqx -- "$url" "$work/seen"; then echo 'Repeated pagination URL' >&2; exit 1; fi
printf '%s\n' "$url" >> "$work/seen"
status=$(curl -q --silent --show-error --fail --max-time 60 --connect-timeout 15 --max-redirs 0 --max-filesize 52428800 --proto '=https' \
--header @"$work/headers" --header 'Accept: application/json' \
--header 'OData-Version: 4.0' --header 'OData-MaxVersion: 4.0' \
--header 'Prefer: odata.maxpagesize=500' --output "$work/page" --write-out '%{http_code}' "$url")
[[ "$status" == 200 ]] || { echo "Unexpected HTTP status: $status" >&2; exit 1; }
jq -e '(.value | type == "array") and ((has("error")) | not) and all(.value[]; type == "object" and (.flowsessionbinaryid | type == "string" and length > 0))' "$work/page" >/dev/null
jq -c '.value[] | {flowsessionbinaryid,createdon,modifiedon,statecode,mimetype}' "$work/page" >> "$work/rows"
url=$(jq -er 'if .["@odata.nextLink"] == null then "" elif (.["@odata.nextLink"] | type) == "string" then .["@odata.nextLink"] else error("Invalid nextLink") end' "$work/page")
done
jq -e -s 'map(.flowsessionbinaryid) | length == (unique | length)' "$work/rows" >/dev/null
jq -s 'sort_by(.createdon, .flowsessionbinaryid)' "$work/rows"
Validation & Testing
Check access using a low-privilege test identity. Review the inventory’s timestamps and types against synthetic computer-use runs; do not assume every flow-session binary is a screenshot.
Sources: Flow-session binary schema; Run monitoring.
4.3 Verify audit coverage and deployment drift
Profile Level: L1 (Crawl)
| Framework | Relevant controls |
|---|---|
| NIST SP 800-53 Rev. 5 | AU-6, CM-3 |
Description
Maintain evidence of approved configuration, deployment changes and runtime events. Test the logging pipeline for every enabled channel instead of assuming one dashboard captures everything.
Rationale
Why This Matters:
- An unobserved configuration change can remove a preventive control.
- Review permissions at each boundary, not just the sign-in screen.
Attack Prevented: Undetected agent modification and delayed incident response.
ClickOps Implementation
- Use Microsoft Purview > Audit and the applicable DSPM activity views to verify Copilot Studio events and access restrictions.
- Compare the read-only agent inventory and component hashes with each approved release. Investigate differences before republishing.
- Check channel-specific licensing prerequisites; non-Microsoft-channel Purview support requires pay-as-you-go billing. Retain raw evidence only in an approved restricted repository.
Automation: Unverified for direct enforcement of this precise setting in this review. Use the documented console path; the surface census records known APIs and remaining schema gaps rather than asserting no automation exists.
Validation & Testing
Make a harmless change in a test agent, run a test conversation, and find corresponding evidence. Record missing events and retention limits rather than claiming full prompt/tool visibility.
Sources: Purview coverage.
5. Compliance Quick Reference
These are thematic mappings, not product certification or a claim of benchmark equivalence.
| Control family | NIST SP 800-53 Rev. 5 | Guide sections |
|---|---|---|
| Access enforcement / least privilege | AC-3, AC-6 | 1, 2, 3 |
| Configuration change control | CM-3 | 1.2, 2.3, 2.4, 4.3 |
| Audit review / retention | AU-6, AU-11 | 4 |
No Copilot Studio-specific CIS/STIG/SCuBA prescription was verified in this review. Microsoft 365/Entra baselines remain complementary, not substitutes for agent-specific controls.
Appendix A: Automation and applicability
The Code Packs are read-only audits, not enforcement or tenant-compliance certification. They enumerate all returned pages, fail on errors, restrict pagination to the selected HTTPS origin, and avoid transcript bodies/binary downloads. Run under a scoped identity in every relevant environment. Empty or permission-limited output does not prove a clean tenant.
Power Platform CLI, Dataverse Web API, Terraform Power Platform provider and Dataverse .NET SDK are real surfaces. Direct setting writes and complete Terraform-resource coverage remain explicitly scoped research gaps; no speculative endpoint is supplied. Two pack types are provided (API and CLI), rather than cosmetic placeholders for unsupported operations.
Appendix B: References
- Microsoft security and governance
- Microsoft secure-project guidance
- Pluto: Securing Copilot Studio
- Pluto: Inside Copilot Studio
Changelog
| Date | Version | Maturity | Changes | Author |
|---|---|---|---|---|
| 2026-11-12 | 0.1.0 | ai-drafted | Initial Pluto-to-Microsoft reconciliation: identity, DLP, MCP, HTTP, child agents, computer use, model governance, retention and read-only audits; current primary-source corrections and evidence gaps documented | Jai |
Contributing
Submit corrections and verified implementation evidence through GitHub. Do not include tenant data or credentials.