Power Platform

Choose a connection

The OAuth connector exposes three maker-facing actions: Get account usage, Generate document from SharePoint, and Generate document from content. Picker, format, and template-schema lookups are internal designer operations.

Generate from SharePoint

1. Create an approved OAuth connector connection with your organizational account.
2. Choose Generate document from SharePoint.
3. Select a supported DOCX, XLSX, or PDF template using the site/library/folder picker.
4. Choose an offered output format and fill the template-driven fields, including repeating sections.
5. Optionally select an output folder, then run and validate the flow.

SharePoint lookups and saves run as the signed-in connection user through Microsoft Graph on-behalf-of, not tenant-wide application permissions. A separate Microsoft SharePoint connector connection is not required or reused.

Where the picker is unavailable, a SharePoint Online file/folder URL can be supplied. Arbitrary non-SharePoint URLs are not accepted. Designer picker behavior still requires live validation.

Generate from file content

Use Generate document from content with the file content from an earlier flow step. The action detects Word, Excel, or PDF from the bytes.

Both generation actions accept simple field objects and an advanced typed fieldsJson override for supported images, HTML, DOCX attachments, formatting, and removal:

{
  "CustomerName": "Cloudwell",
  "LineItems": [
    { "Product": "Widget", "Quantity": 2 }
  ]
}
                

This is a simple fields object, not the API’s typed field-array format. Build JSON with Compose/JSON operations rather than string concatenation.

Work with the result

Generation returns file content, filename, and content type. Selecting a SharePoint output folder also returns saved-file metadata and the normal SharePoint URL. Leaving it blank returns the file only.

Overwrite defaults to false. A naming conflict fails unless advanced overwrite is enabled. A generation failure writes no file; a save failure after generation returns an error but still consumes the admitted credit.

If you use Microsoft’s SharePoint connector separately, feed Get file content into generation and pass generated bytes to Create file. Use base64ToBinary() only for plain base64 that needs decoding; do not double-decode byte-formatted content. Verify the generated Power Apps signatures after import.

Availability, limits, and credits

• There is no standalone conversion-only action. Generation can output PDF when an enabled renderer is advertised.
• There is no temporary preview-link or Office-viewer action. Saved SharePoint URLs are ordinary file URLs, not anonymous sharing links.
• Templates are limited to 10 MiB decoded, output to 25 MiB, and replacement JSON to 1 MiB. Power Platform can impose lower practical file-size or timeout limits.
• An eligible tenant’s trial and credits are shared with the website and API keys. Generation consumes one credit; connection checks and internal picker/schema lookups do not.
• A new retry receives a new request ID and can consume another credit. Saving and generation are not an atomic transaction.
• Inactive entitlement returns 403, credit exhaustion 429, and unavailable licensing 503.

An ID token, Graph access token, API key, or application-only token cannot substitute for the OAuth connector’s dedicated delegated API token. Availability of connector source assets is not proof of rollout or certification.