Every concept across the three guides, alphabetical. Filter by guide, shuffle, or flip them all at once.
Showing 15 cards · 0 flipped
02 · Applied
72K Row Demo
tap to reveal →
A worked example: 12 CSV files, 35 columns, ~72,000 rows, 30 MB. AI in SharePoint reads, analyzes, and produces an interactive HTML report in about seven minutes.
← tap to flip back
01 · Foundations
AI in SharePoint
tap to reveal →
A worker agent that writes and runs code in a sandbox against SharePoint files. Different from Copilot, which is a chat/RAG experience grounded in search.
← tap to flip back
02 · Applied
content_return: false
tap to reveal →
The read-tool flag that tells SharePoint to keep file content in tool storage instead of returning it to the model. The mechanism that prevents context overflow.
← tap to flip back
02 · Applied
Context Window
tap to reveal →
The token budget the LLM can see at once. Even modern windows cannot fit 30 MB of data — and even if they could, the model still gets confused.
← tap to flip back
03 · Advanced
create_file
tap to reveal →
Final tool call in the pipeline. Writes the sandbox-generated artifact into the SharePoint document library where the user can open it.
← tap to flip back
03 · Advanced
find_files
tap to reveal →
First tool call in a typical run. Returns file metadata matching the prompt — names, sizes, columns — without transferring content.
← tap to flip back
01 · Foundations
RAG
tap to reveal →
Retrieval-Augmented Generation. The LLM searches a corpus, retrieves chunks, and reasons over them. Powers Copilot; cannot do precise math at large scale.
← tap to flip back
03 · Advanced
run_in_sandbox
tap to reveal →
Executes the JavaScript the model has generated against data in tool storage. Produces a new artifact — JSON analytics, an image, or an HTML file.
← tap to flip back
01 · Foundations
Sandbox
tap to reveal →
A secure execution boundary where agent-generated code runs against data the user supplied. Cannot call external services or mutate other content.
← tap to flip back
03 · Advanced
Self-Contained Report
tap to reveal →
An HTML file that includes all CSS, JS, and data inline. No CDN dependencies, no live data source. Portable, shareable, snapshot in time.
← tap to flip back
02 · Applied
Strawberry Problem
tap to reveal →
The classic "how many Rs in strawberry" failure. Demonstrates why letting the LLM write code, not the answer, produces reliable results for any countable task.
← tap to flip back
01 · Foundations
Tool Call
tap to reveal →
A single step the agent invokes — find files, read files, run code, create file. The model chains tool calls to build a workflow.
← tap to flip back
02 · Applied
Tool Storage
tap to reveal →
Server-side storage that holds file content during an agent run. The model references the data by handle; the bytes never enter the context window.
← tap to flip back
03 · Advanced
Trust Boundary
tap to reveal →
The strict edge around the sandbox. Data and code-execution stay inside. No outbound network, no mutation of other content, no escape — only the produced artifact crosses out.
← tap to flip back
01 · Foundations
Worker Agent
tap to reveal →
An AI agent that delivers work artifacts — files, reports — by writing and executing code, rather than predicting answers from a trained model.