Use a controlled Word template, an approved attendee record and the Word Online (Business) connector to create a certificate. Save the generated document first, convert it to PDF if required, then send it and record the result.
Do not trigger certificate generation merely because somebody registered. Attendance or completion should be a separate confirmed state.
Fact-checked against the current Microsoft Word, SharePoint and Outlook connector documentation on 24 August 2026.
Licensing and template limits
Microsoft currently labels Word Online (Business) as a Premium connector. Check the maker, owner and runtime licensing in the target environment.
Microsoft documents these template boundaries:
- supported controls include plain text, combo box, drop-down, image and repeating section;
- rich text, date picker, check box, building-block gallery and legacy controls are not supported;
- the input file limit for the connector actions is 10 MB;
- PDF conversion does not support documents with certain Confidential or Highly Confidential sensitivity-label values.
Test your actual template and label policy before committing to PDF delivery.
1. Create the attendee record
Use a SharePoint list or another governed data source with:
- attendee name;
- attendee email;
- event name;
- event date;
- attendance confirmed;
- certificate approved;
- certificate file URL;
- certificate sent at;
- processing key.
Keep confirmation and approval separate. The person who imports registrations should not automatically be able to assert attendance.
2. Build the Word template
In Word for Windows:
- enable the Developer tab;
- insert supported content controls;
- give every control a unique title;
- avoid placing unsupported controls in the document;
- store the template in SharePoint, OneDrive for Business or an Office 365 Group library.
Use a version-controlled master template. The flow should not select whichever document happens to have the same filename in a user's folder.
3. Trigger on confirmed approval
Use trigger conditions or an early Condition so the flow proceeds only when:
- Attendance confirmed is Yes;
- Certificate approved is Yes;
- Certificate file URL is blank; and
- Certificate sent at is blank.
This reduces accidental and duplicate generation.
4. Populate and create the certificate
Add Populate a Microsoft Word template and map the approved fields.
Then use SharePoint Create file to save the .docx output. Give files a collision-safe name based on an internal attendee or event ID, not only the person's name.
Do not include more personal data in the filename than the business needs.
5. Convert to PDF
If PDF is required, pass the generated Word document to Convert Word Document to PDF, then create the PDF in the final library.
Open the PDF during testing. A successful connector action does not prove fonts, images, page breaks and labels rendered as expected.
6. Send the certificate once
Use Send an email (V2) with either a secure SharePoint link or the retrieved PDF content as an attachment.
After the send action succeeds:
- update Certificate file URL;
- write Certificate sent at;
- store the processing key or run reference.
If the email fails after the file is created, the next run should reuse the existing approved file rather than create a new one.
Failure and privacy checks
- Reject blank or invalid email addresses.
- Restrict the certificate library appropriately.
- Do not expose the complete attendee list through a shared folder.
- Log safe identifiers, not the certificate content.
- Decide what happens when a name is corrected after issue.
- Define whether certificates can be revoked or regenerated.
Microsoft sources
- Word Online (Business) connector
- SharePoint connector reference
- Office 365 Outlook connector reference
- Power Automate error handling
Check the duplicate and failure paths
Bring the template controls, attendee states and a redacted test output to the Power Automate Builders Space.