Flowgrammer

Power Automate Document Processing

Orchestrate AI Builder confidence and Approvals before one draft write.

— Craig Major

Direct answer

Power Automate orchestrates. AI Builder or Azure Document Intelligence extracts. Do not collapse those layers with SharePoint Syntex. AI Builder returns field values and confidence as floats from 0 to 1. A Microsoft example sometimes uses 0.65. That number is an illustration, not a Flowgrammer default. Approvals must finish before a draft write. There is no native requestid. Labelled-text fixtures do not measure OCR.

Use this page for cloud-flow orchestration. Start with Intelligent Document Processing for extraction vocabulary, Document Processing Automation for the pillar, or SharePoint Document Processing Automation for library schema.

Who this is for

Microsoft-stack operations leads who already have Power Automate and a named Approvals owner. Prerequisites: one environment, one document family, and a policy that confidence never posts a draft by itself.

Layering

  • Power Automate: intake, routing, Approvals, destination
  • AI Builder document processing: prebuilt invoice or a custom model
  • Azure Document Intelligence: a separate extractor when you choose it
  • SharePoint or Outlook: storage and mail connectors, not the extractor

Do not treat Syntex, AI Builder, and Azure Document Intelligence as one product.

Confidence

Official Microsoft docs describe confidence as a float from 0 to 1 on extracted fields. High confidence is not accounting-ready truth. Microsoft examples sometimes flag values below 0.65. Flowgrammer leaves the buyer threshold blank in the checklist except for that official example note. Avery Chen still approves.

Worked example

Cedar and Quay Fabrication Ltd drops a labelled-text stand-in for INV-TP-2401 into a cloud flow. The flow records vendor, invoice number, date, total, and per-field confidence. Confidence is stored. It is not trusted. Avery Chen receives Start and wait for an approval. After Approve, one draft handoff is written. A later retry hashes vendor plus invoice number plus source bytes because Power Automate has no Intuit-style requestid.

If Approvals times out, no draft. If the file exceeds the cited prebuilt invoice limits, the flow stops. Those names are fictional. This draft did not sign in to a Microsoft tenant.

Workflow

  1. Intake. Email, SharePoint, or a manual trigger. Respect connector file-size notes.
  2. Extract. AI Builder Process documents or Extract information from invoices. Or Azure Document Intelligence through a connector. Not OCR accuracy theatre.
  3. Record confidence. Store 0 to 1 floats. Compare to the buyer policy, not to a Flowgrammer default.
  4. Duplicate check. Application hash of source plus vendor plus document number.
  5. Approvals. Start and wait. Every non-duplicate needs explicit Approve.
  6. Draft write. After Approve only. Never payment or bank connectors.
  7. Retry. Same application key. Prove one destination write.
  8. Limits. Prebuilt invoice notes include 20 MB, first 2000 PDF pages, and 360 calls per environment per 60 seconds across document processing models. Reconfirm on publish day.

Decision table

Condition Automatic Review Human-only
Fields plus confidence recorded Store values Approvals Set the threshold
Confidence below buyer policy Flag Person decides Do not auto-approve
Duplicate hash Stop None Override policy
Approval timeout No draft Restart Approvals Do not skip
File over connector or model limit Stop None Split or change source
Payment connector requested Block None Person pays elsewhere
Canada residency assumed Stop the claim None Paste tenant notes

Human gates

A person sets the confidence policy. A person completes Approvals. A person confirms connector limits. A person pastes tenant residency from the actual environment. A person never auto-approves on score alone.

Failure paths

  • Confidence treated as posting authority
  • Approval timeout with no long-running pattern
  • Attachment over Outlook, SharePoint, or model limits
  • Duplicate write because no application key
  • Payment connector added
  • Invented Canada residency or CAD credit prices
  • Mixing Syntex with AI Builder in one sentence as if they were one model

Test cases

Reuse the five labelled-text invoice cases as orchestration fixtures. They do not measure OCR.

Case Input Expected Acceptance
Clean Unique document Confidence recorded, Approve, one draft write_count=1
Duplicate Same hash Stop No Approvals write
Missing fields Required field blank Review No draft
Conflict Incompatible totals Review No draft
Timeout Destination or Approval lost Retry or restart One draft after Approve

Licensing and residency

AI Builder credits are moving toward Copilot Credits. Seeded credit end-of-life and per-page credit figures are publish-day sensitive. Do not invent CAD unit prices. Cloud flow run duration and retention themes of about 30 days appear in prior Microsoft limits docs. Pending Approvals can time out. Re-fetch limits and credit pages before publish.

Data residency is tenant-specific. Do not promise Canada residency as a Flowgrammer guarantee.

This research did not run a live tenant. Do not claim Microsoft partner status or measured OCR accuracy.

Cost and measurement

Cite the buyer's current Power Platform admin invoice. Outlook attachment themes of about 25 MB and SharePoint file themes of about 100 MB / list attachment about 90 MB come from connector docs and need a publish-day recheck. They are not a universal attachment limit.

Asset instructions

Download Power Automate and AI Builder Checklist. Open Cover, then ConfidencePolicy, Approvals, and Limits. Leave the buyer threshold blank except the official 0.65 example note. ZIP name: Flowgrammer-Power-Automate-AI-Builder-Checklist-v0.1.0.zip. The resources slug is power-automate-ai-builder-checklist so it does not collide with the article slug.

Next step

If environment, model, and Approvals owner are named, book a fit call for an AI Automation Systems Document Automation System. Otherwise start with an AI Success Audit. Use Book a fit call when you are ready.

Sources