Create Employee Recognition Cards with Power Automate and Teams

A useful recognition flow starts with approval, not artwork. Store the nomination in SharePoint, have the right person approve it, generate a card from a controlled Word template, save the result, then post a link in Teams.

That sequence prevents spelling mistakes, private comments and unapproved praise from being broadcast automatically.

Fact-checked against current Microsoft Learn connector documentation on 24 August 2026.

Choose the output before building

The Microsoft route is best for a document-style card or certificate:

SharePoint holds the nomination and its status.
Word Online (Business) fills a controlled template.
SharePoint stores the generated file.
Teams receives a message and link.

If you need a designed PNG image rather than a Word or PDF file, you will need an approved image-rendering service or a custom component. Do not pretend Word's document connector is an image generator.

Microsoft currently labels the Word Online (Business) connector as Premium. Check licensing and data-loss-prevention policy in the target environment before promising this route.

1. Create the recognition list

Create a SharePoint list with fields such as:

Recipient name
Recipient email
Recognition text
Submitted by
Approval status
Generated file URL
Teams announcement sent
Processing key

Use a multi-line plain-text field for the recognition message. Restrict who can approve and edit the final text.

The processing key can combine the list item ID and approved version. It stops a later edit from sending the same announcement twice.

2. Build the Word template

Create the template in Word for Windows and add supported content controls from the Developer tab. Plain text, image, combo box, drop-down and repeating-section controls are among the types Microsoft documents as supported.

Give every control a clear, unique title. Store the template in OneDrive for Business, SharePoint or an Office 365 Group document library so the connector can select it.

Do not use unsupported controls such as rich text, date picker, check box, building-block gallery or legacy form controls. Microsoft also documents a 10 MB input-file limit for the connector actions.

3. Trigger only after approval

Use a SharePoint trigger, then add trigger conditions or an early Condition so processing continues only when:

Approval status is Approved;
Generated file URL is blank; and
Teams announcement sent is No.

This makes the flow restartable. A failed Teams post does not require another card, and an already-generated card is not recreated accidentally.

4. Populate and save the card

Add Populate a Microsoft Word template and map the approved list fields to the controls.

Then:

Create the .docx file in a controlled SharePoint library.
If a PDF is required, use Convert Word Document to PDF.
Create the PDF in its final library.
Update the list item with the generated file URL before posting to Teams.

Microsoft says PDF conversion does not support documents carrying certain Confidential or Highly Confidential sensitivity-label values. Test the template with the labels your organisation actually uses.

5. Post a link in Teams

Use Post message in a chat or channel and include:

the recipient's approved display name;
the approved recognition text;
a link to the generated file.

The Teams connector documents an approximate 28 KB message limit for message-posting actions. A short announcement and link is more reliable than embedding a large document or elaborate HTML.

The Teams audience must also have permission to open the SharePoint file. A successful post does not prove the link works for ordinary members.

6. Mark the announcement complete

Only after Teams confirms success, update Teams announcement sent to Yes and store the message or run reference you need for support.

Put failure handling in a separate Scope. Record the error against the SharePoint item and notify an owner without exposing the recognition text to a broad support channel.

Tests worth running

Test:

apostrophes, ampersands and long names;
an empty optional field;
a rejected nomination;
a duplicate trigger;
a card using your real sensitivity label;
a Teams member who is not a site owner;
a failure after file creation but before the Teams post.

The process is successful only when the approved content, generated file, permissions and announcement all agree.

Microsoft sources

Build the approval and recovery path properly

Bring the list fields, template controls and a failed run to the Power Automate Builders Space. The campaign identifies readers arriving from this guide.