Keep values in the right boundary

What you'll do

Map four information boundaries for a synthetic BI workflow: local evidence, customer Fabric execution, external agent provider and Hosted metadata. Decide where five example artifacts belong. Your output is a disclosure worksheet; this lesson requires no uploads, credentials or client evidence.

Draw the actual movement

The supportable promise is that Hosted qualification uploads exclude raw business values and evidence. It is not a claim that nothing ever crosses a network. Approved source and Fabric operations move information within the customer's chosen environment. Information supplied to an external assistant follows that provider's separate controls.

Local evidence can include source extracts, oracle numbers, SQL/DAX, report renders and receipts. The Hosted ledger receives a closed value-free signed attestation. It also handles account and organisation information under separate controls; value-free qualification does not mean the whole service contains no personal or administrative data.

Treat the assistant as its own boundary

A local file path does not mean its content stays local once pasted into an assistant. Before asking for analysis, select the minimum approved material. A value-free source index can help with structural reasoning, but names and relationships may still reveal business context.

Use a synthetic exercise when practising prompts. Do not paste a client's ledger graph into chat merely because the task is read-only. Reading and disclosure are different questions. A read-only tool may prevent mutation while still returning information that needs the correct authorisation.

Disclosure worksheet
Question: explain why a qualification is stale
Minimum teaching input: synthetic scope and changed dependency
Excluded: actual values, SQL/DAX, client identities and report images
Output: bounded next-evidence recommendation

Understand the Hosted projection

The exporter verifies a selected signed local subject and supporting chain, then emits bounded verdicts, times, signer information and keyed commitments. Raw values, queries and local receipts are excluded. Hosted verifies the envelope and authority; it does not receive enough information to recompute business totals.

Do not add private supporting files to the envelope as an informal attachment. The closed projection is deliberate. An auditor who needs raw evidence requires a separately approved local review route; a Hosted status question is not that route.

Keep credentials out of learning artifacts

The documented repository practice uses Azure Key Vault, names-only manifests and private human entry. Names of environment variables can be documented; actual secret values do not belong in prompts, commands copied into a worksheet, logs or screenshots. Follow the approved project's credential workflow rather than improvising a course-specific secret file.

This is a handling principle, not a claim that every customer must use one secret platform or that production custody has independent certification. Do not infer HSM-only custody, completed compliance assurance or production recovery guarantees from a local implementation description.

Finish by classifying five synthetic artifacts and stating the reason for each boundary. Your expected output includes one safe summary for an external assistant and one explicit item withheld for approved local review. No raw evidence should be submitted to the academy. This exercise establishes your understanding of disclosure limits, not a production security assessment or client reporting award.

Check your understanding

1. Why is the narrower Hosted no-values statement more accurate than saying nothing leaves the network?
2. How can a read-only assistant request still cross a disclosure boundary?
3. Why does signing a local receipt not make it suitable for Hosted upload?