Experimental preview / active fixes

Review the source.
Keep the evidence.

A standard Copilot Studio agent for small, trusted Power Platform exports. Native Microsoft flows collect bounded source evidence. The agent turns it into practical advice—with the gaps left visible.

Not a checker. Not a certification. Submitted packages are never imported or executed.

Standard harnessCopilot Studio, not GitHub Copilot
Native Microsoft flowsNo hosted Python or Azure worker
GPT-5 ReasoningPreview · not for production

Evidence snapshot

A public walkthrough, not production approval.

Current review acceptance remains partial. Preview-model and missing Studio-evaluation advisories are unresolved. Public-preview approval is not production/runtime acceptance.

01 / Two intake paths

The topic is not the tool.

One agent, two carefully separated routes. The diagrams below describe the architecture; they are not captured runs.

Upload the original .zip or .msapp to storage—not this site or native chat. Manual review uses the operator’s own OneDrive Inbox. Automatic review uses an approved private SharePoint Incoming library. Keep the original extension.
Manual / caller-owned

A conversation with consent

Identity: the caller’s selected OneDrive Invoker connection. No maker fallback.

  1. 1 / MESSAGE

    Ask for a review

    “Review my solution export” in the authenticated agent.

  2. 2 / TOPIC

    ReviewTrustedExport

    Private Inbox instructions → filename validation → explicit trusted-export consent.

  3. 3 / ACTUAL TOOL

    CollectReviewEvidence

    InvokeFlowTaskAction → native OneDrive collection flow, in Invoker mode.

  4. 4 / ANSWER

    Source-backed advice

    Numbered excerpts, locations, observations and verification steps. Coverage is explicit.

Storage prerequisite: a private physical PowerPlatformSolutionReviewInbox in the caller’s own default OneDrive. Filename only; no sharing URL, path or shared-drive shortcut. Manual/multi-user runtime acceptance is not established.

Automatic / owner-scoped PoC

A file event with guarded delivery

Identity: declared automation owner/service connections. Not uploader impersonation.

  1. 1 / TRIGGER

    SharePoint Incoming

    GetOnNewFileItems admits a new direct-child file in the approved scope.

  2. 2 / NATIVE FLOW

    Authorize & acquire

    Uploader/owner, version, unique job key and privacy guards. OneDrive ExtractFolderV2 and bounded reads.

  3. 3 / ACTUAL CONNECTOR

    ExecuteCopilotAsyncV2

    The same published agentReviewSuppliedAutomationEvidence. Component JSON, then MAIN.

  4. 4 / PRIVATE OUTPUT

    Protected report bundle

    Accepted source assessments + MAIN + retained inventory and coverage. Rejected assessments stay unavailable.

  5. 5 / GUARDED CAPABILITY

    SendEmailV2

    Optional Outlook email only after recipient, source version, report privacy and delivery-reservation checks.

Email belongs to the flow, not the model’s tool menu. The model cannot choose To/Cc/Bcc, grant access or retry a send. Delivery state is separate from review outcome; EmailSent never means “complete review.”

Source text is evidence, not authority.

Package instructions cannot change permissions, recipients, tools or storage. Reserved message prefixes route the review contract; they are not authentication.

Static review ≠ running the app.

No import, execution, resave or dependency installation of submitted packages. Installing the reviewer itself is a separate, normal Power Platform solution import.

02 / The experience, honestly shown

From an original export
to inspectable evidence.

Real UI, using synthetic test content. Historical captures remain historical—even when later fixes improve the implementation. No private genuine-solution report is published here.

01

Put the file in the right place.

The automated route watches the designated private Incoming folder. This capture shows an existing synthetic file, not a new upload or processing receipt.

Actual test capture Read-only SharePoint view, 13 September 2026. Account/runtime identifiers and unrelated navigation masked or cropped.

Actual SharePoint Incoming view showing one existing synthetic MSAPP export, with owner and deployment details redacted.
A location example, not evidence of a fresh upload. The original upload-completion and transient processing states were not captured.
02

Read the detailed source assessment.

The report records what was actually visible, its supplied lines and concrete checks still needed. An empty findings list is valid when no defect is supported.

Actual test capture Accepted App-source assessment from the synthetic owner-email run. The second selected assessment was unavailable; this is not 2/2 success.

Actual synthetic App-source report with grounded observations, no confirmed findings, and unrated verification-needed items; private identifiers are redacted.
Native SharePoint text-preview excerpt. Unknown runtime behavior stays VERIFICATION NEEDED, not an invented low-severity defect.
03

Keep the limitations in the report.

These user-selected excerpts show a previous partial review: an unavailable second assessment, omitted metadata, runtime checks NOT RUN and visible pre-fix text-decoding artifacts.

Actual user-provided images · historical Capture date and exact run/version are not independently established. The decoding artifacts have not been retouched.

Historical partial report with executive summary, methodology, inventory, one saved and one unavailable assessment, and visible legacy decoding artifacts. Address bar and identifiers are redacted.
Detail 01: earlier Partial report. Browser chrome cropped; job, filename and private-path identifiers redacted. Status, counts and issues retained.
User-provided report sections five to ten: no confirmed findings, unavailable C2, no acquired embedded SARIF, runtime checks not run, and explicit omissions, with historical decoding artifacts.
Detail 02: visually classified during this site’s curation. Sections 5–10 show no confirmed findings, unavailable C2, no acquired SARIF, and omissions. Not new runtime evidence.
The email is a notification—not the authoritative report. The hero features the user’s actual Outlook dark-mode image. A separately captured owner inbox run established received formatted email, honestly reporting one saved and one unavailable assessment. It did not establish full review acceptance or every email client’s rendering.
Image provenance & public-safety treatment

Every product image is actual UI: either supplied by the user or captured read-only by the test operator. All displayed report content is synthetic/demo-safe. These are not current genuine-solution report screenshots.

User-selected originals remain unchanged outside this public subtree. New derivatives strip image metadata and apply only declared privacy crops/masks. No status, counts, findings or known decoding problems are edited to imply success.

The parent approved these curated derivatives for public preview based on the site agent’s normal visual/privacy review and independent parent hash/private-identifier scans. Parent image-display capacity prevented independent visual reinspection; none is claimed.

Open any image for its full-size derivative. Exact source hashes, transforms and final asset hashes are recorded in the publication manifest. This approval does not upgrade runtime acceptance.

03 / The actual build reference

Topics. Tools. Instructions.

Readable contracts and sanitized source—not an independently deployable agent. These references describe the observed published agent rules; later runtime candidates do not inherit that acceptance.

HarnessStandard Copilot Studio
OrchestrationGenerative
Model selectionPreviewModels / GPT5Reasoning
AudienceIntegrated · Always sign-in · GroupMembership

General model knowledge, file analysis, semantic search, web browsing and code interpreter are disabled. Availability, licensing, preview terms, region and data movement must be verified in each target environment.

Review topics

topics\ReviewTrustedExport.mcs.yml

Review trusted export

Trigger
Recognized requests such as “Review my solution export”; reserved automation prefixes excluded.
Inputs
ASCII leaf filename ≤100 characters, original ZIP/MSAPP extension, and explicit affirmative consent. No repeated dots, paths or URLs.
Output
result: current collector evidence JSON → generated detailed interactive answer.
Guards
Always asks consent. Invalid input or cancellation accesses no source. Missing tool evidence is not a successful review.

topics\ReviewSuppliedAutomationEvidence.mcs.yml

Review supplied automation evidence

Trigger
Leading PSR_COMPONENT_INPUT_V3 or PSR_REVIEW_ONLY_V1.
Inputs
Supplied evidence text ≤60,100 characters. Prefixes route data; the external flow enforces identity.
Output
ResponseContract + result. COMPONENT → one PSR_COMPONENT_V3 JSON object. MAIN → ten-section synthesis.
Guards
Connector-free. No file lookup, consent loop, email or recipient selection. Reject unusable/oversized input.
Supporting topics and lifecycle
  • ConversationStart: welcome and intake explanation, not source acquisition.
  • Fallback: reserved review/repair prefixes return to the supplied-evidence topic; ordinary unknown intents take the normal fallback path.
  • Search / conversational boosting: excludes reserved prefixes; not the review collector or proof of external web search.
  • Signin, OnError, MultipleTopicsMatched: sign-in, error handling and disambiguation.
  • Greeting, Goodbye, ThankYou, StartOver, ResetConversation, EndofConversation, Escalate: ordinary conversation plumbing, not extra review tools or a staffed-support promise.

The tool in Studio—and the flow capabilities outside it

Actual Copilot Studio Tools list with one Flow tool, Collect bounded review evidence; owner identity redacted.
Actual read-only Studio configuration capture. The native row truncates the name. A listed tool is not proof of invocation or Invoker connection validation.
Native operations and configuration boundariesOn small screens, scroll sideways—or focus this table and use the arrow keys.
Capability / connectorActual operation & contractBinding and guard
Agent evidence toolCollectReviewEvidence / InvokeFlowTaskAction
Filename + trustedExportresult.
triggerCondition: false; called through the consent topic. Consent default is false; OneDrive connection mode is Invoker.
OneDrive for BusinessGetFileMetadataByPath, CreateFile, ExtractFolderV2, ExtractFolderV2_Continue, GetFileContent, DeleteFile.Own-drive isolated staging, bounded reads/continuation. Embedded owner connection in automation; caller connection in manual collection. No arbitrary shared URLs.
SharePointGetOnNewFileItems, GetFileContentByPath, HttpRequest.Direct Incoming children, source snapshot and private ACL checks; unique job/control records and protected Results files. Rebind actual target resources, not just the connector.
Office 365 UsersUserProfile_V2.Resolve and validate uploader’s directory identity and mailbox against the permitted owner. Fail closed on mismatch or unresolved identity.
Microsoft Copilot StudioExecuteCopilotAsyncV2.
ListCopilots is used during target setup to discover the published agent.
Same published agent and model. COMPONENT passes then MAIN. Final response is distinct from unvalidated conversation history. Bounded same-source retry/repair; no arbitrary execution.
Office 365 OutlookSendEmailV2 / SendReviewEmail.
Verified recipient + canonical outcome + protected links.
Not a freely selectable agent tool. Explicit email enablement, source recheck, private report verification and delivery reservation. Automatic send retries: none.
Delivery ambiguity stays visible. A failure after reservation can become EmailAmbiguous / DELIVERY_UNKNOWN. Do not replay it to force delivery. The ledger reduces duplicates but does not promise exactly-once email or guaranteed receipt. Links do not grant access.

Inspect the actual project instructions

Rules 3.3.1 instruction text, pinned to its recorded publication. No private connections, owner details or credentials. This is the reviewer agent’s project source—not GitHub Copilot’s instructions.

Full agent instruction text Copyable · source reference
Download instruction text

Sanitized topic and tool definitions JSON reference · not importable

Flow binding and private OneDrive/owner values are explicit placeholders. Sanitizing a reference does not transfer native deployment verification to it. Do not paste placeholders into a live connected definition.

Download sanitized reference

04 / Installation and reconnection

Configure first.
Enable deliberately.

A solution ZIP does not carry your SharePoint library, lists, permissions or working target connections. This is a nonproduction installation outline—not authorization to operate a tenant.

An experimental public-preview starter is available—not a production-approved or ready-to-import solution. Configure before import. Defaults remain disabled/no-email, known review limitations remain, and no target-tenant import/runtime proof is claimed. Never import a connected *.remote.zip or an unconfigured template. Public-preview approval does not authorize target installation or activation.
  1. Approve the target and its identity

    Use an authorized nonproduction Dataverse environment, a dedicated private SharePoint site and the intended owner/service user. Check model availability, Copilot Studio/Power Automate licensing and capacity, Exchange, OneDrive, regional/preview terms and DLP. Do not broaden tenant access to bypass a failing route.

  2. Prove the owner’s own default OneDrive

    Existing approved Graph metadata must establish self identity, default-drive ownership and the physical Inbox correspondence. An accessible foreign drive or shared shortcut is not sufficient—even with Full Control. Unavailable proof is a stop, not permission to request broad grants.

  3. Bind the five target connections

    SharePoint, OneDrive for Business, Office 365 Users, Microsoft Copilot Studio and Office 365 Outlook. Verify account, tenant, environment and connection state. Keep the manual tool’s separate reference in Invoker mode; automation connections use the declared owner.

  4. Configure and import the reviewer

    Use complete approved configuration helpers to build a *.target.zip plus connection-reference settings. Import the reviewer first, initially unpublished/disabled. Verify the actual imported bot, Integrated/Always/GroupMembership authentication, model and tool. Do not overwrite unrelated same-name components.

  5. Create and verify external resources

    Private versioned library: Incoming, Results, Working. Versioned ReviewJobs with indexed, unique PSRJobKey. A marked control row whose actual ID/type is discovered—not assumed. Private physical OneDrive Inbox with an installation marker. Existing unrelated resources are not adopted.

  6. Publish the actual imported agent; configure automation

    Review Studio’s native model/evaluation advisories and arrange appropriate authorized evaluations; none are claimed here. Deliberately enable the verified Invoker collector and publish the imported agent. Discover its actual target identity via ListCopilots, configure/repack automation, and import it disabled. Recheck all bindings, privacy and publication.

  7. Validate before explicit activation

    Run only an authorized owner-scoped synthetic no-email test. Approve the exact uploaded identity/version, observe the created-file trigger, and inspect MAIN, selected-source assessments, coverage, source integrity and private ACLs. A succeeded flow is insufficient. Enable ongoing automation only after acceptance; authorize email separately.

Flow defaultDisabled
Control defaultDisabled / no email
Activation latchpsrDeploymentReady = false
Credentials shippedNone

psrDeploymentReady is a Boolean WDL workflow parameter—not a Dataverse environment variable. Rebinding connections alone cannot enable the template. Local packaging helpers are installation tooling, not a hosted Python runtime.

05 / Limits & verification

A scoped pass is not a universal pass.

Evidence ledger · snapshot
What was checkedRecorded resultWhat it does not prove

Native Studio advisories remain.

GPT-5 Reasoning is Preview and not recommended for production. Performance, quality and response times may vary. Preview terms apply.

No in-product Studio evaluation has been run. Local tests and native pipeline probes do not clear Studio’s evaluation warning. Publication itself is not quality certification.

Actual read-only UI, 13 September 2026. Both Warning · Draft rows and the Loading indicator are retained; this is not an exhaustive zero-other-issues claim.

Actual Studio agent status: Models Risk warning that the preview model is not recommended for production, and Evaluation Quality warning that no evaluation has been run.
Actual configuration evidence. No model switch, evaluation or warning-clearing action is implied.

Deliberately bounded acquisition

Manual and automatic limits are differentOn small screens, scroll sideways—or focus this table and use the arrow keys.
BoundaryManual Invoker collectorAutomatic flow

Coverage is what was returned.

OneDrive can flatten archive paths. The original hierarchy, mappings and collision-free coverage are not established. Inventory records are not original control totals. complete=true describes the decoded excerpt, not the whole app.

First-N excerpts, legacy internals, binaries, unreadable files, metadata omissions and throttled reads stay explicitly unreviewed. Current bounds and service errors can force Partial or Failed.

Trusted exports only.

Not hardened against hostile archives. No guarantee of importability, runtime correctness, accessibility, security or compliance. No official Solution Checker, App Checker or Accessibility Checker execution.

Embedded SARIF, if acquired, is historical evidence—not a fresh checker run. Unverified runtime behavior is unrated VERIFICATION NEEDED; not a guessed defect.

06 / Take the starter, not a promise

An experimental starter.
With explicit limits.

Experimental starter — configure before import

    The download control requires the approved configuration and manifest to load. The download manifest is linked alongside.

    Public wrapper SHA-256

    Extract into a new private installation folder, then Set-Location .\starter and read .\README.md. The root PREVIEW-STATUS.md preserves the older c102 packaging snapshot, not newer private live fixes. All seventeen inner files remain unchanged; bare template ZIPs are not direct import inputs.

    Setup, provenance & references

    Read frozen c102 package status & setup Download SHA-256 & exact file manifest Actual project instruction text Sanitized topic & tool reference Target readiness checklist Publication manifest & image provenance

    Public-preview approval is not production/runtime acceptance. Reference files are not standalone installers. No connected exports, private original images or credentials are included.