web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / Power Automate Generat...
Power Apps
Suggested Answer

Power Automate Generated Worddoc Content Controls Is Not Editable

(1) ShareShare
ReportReport
Posted on by

Product Area

 

  • Power Apps

  • Power Automate

  • Word Online (Business)

  • AI Builder

  • Word Content Controls


  •  
 

Issue Summary

 

We are using a Power Apps and Power Automate solution to generate Microsoft Word documents from a predefined Word template containing Content Controls.

 

The flow receives data from AI Builder and populates the Content Controls within the Word template to generate a formatted Word document.

 

The document is successfully generated; however, end users are unable to directly edit the populated content in the generated document. Users must manually open Microsoft Word settings and disable Content Control restrictions before they can modify the content.

 

We are looking for a configuration or solution that allows the generated document to be editable immediately after creation without requiring every user to manually disable Content Control settings.

 
 

Current Process

 

  1. User submits information through Power Apps.

  2. Power Automate flow is triggered.

  3. AI Builder generates the response/content.

  4. Power Automate populates a Word template containing Content Controls.

  5. A Word document is generated and shared with the user.

  6. User opens the document and attempts to edit the generated content.


  7.  
 
 

Actual Behavior

 

  • Generated document content appears within Content Controls.

  • User cannot directly modify the content.

  • To edit the content, the user must:

    • Open Word Options/Developer settings.

    • Manually disable Content Control restrictions.

    • Then edit the document.


    •  


  •  
 

This must be repeated by each user experiencing the issue.

 
 

Expected Behavior

 

  • Generated Word document should be editable immediately after creation.

  • Users should not be required to manually disable Content Control settings.

  • Ideally, the flow should generate:

    • An editable Word document, OR

    • A document where Content Controls are automatically unlocked/removed after population.


    •  


  •  
 
 

Business Impact

 

  • Poor user experience.

  • Additional manual steps for all users.

  • Increased support requests and training effort.

  • Generated document cannot be easily reviewed and updated by business users.


  •  
 
 

Questions for Microsoft

 

  1. Is this behavior expected when Power Automate populates Word Content Controls?

  2. Is there a supported configuration to automatically make populated Content Controls editable?

  3. Can Content Controls be unlocked or converted to regular text through Power Automate after document generation?

  4. Is there a recommended approach for generating editable Word documents from AI Builder output while retaining the initial document formatting?

  5. Are there any limitations or licensing considerations related to editable Word templates generated from Power Automate?

Additional Information

 

  • Source: Power Apps

  • Automation: Power Automate Cloud Flow

  • Content Generation: AI Builder

  • Output Format: Microsoft Word (.docx)

  • Document Template: Word Template containing Content Controls
I have the same question (0)
  • Suggested answer
    Valantis Profile Picture
    6,967 on at
     
    This is a Word template design issue, not a Power Automate limitation. The content controls in your Word template have their Locking properties set incorrectly.
     
    Fix in the Word template:
    1. Open the template in Word with Developer tab enabled
    2. Select each content control
    3. Click Properties (Developer tab)
    4. In the Locking section, uncheck both:
     - Content control cannot be deleted
     - Contents cannot be edited
    5. Save the template
     
    This is the cause of the read-only behavior. When Power Automate populates the control, it inherits whatever locking was set on the control in the template. If "Contents cannot be edited" was checked, the populated document has that lock enforced.
     
    For the recommended approach to generate fully editable documents: after populating, the content controls remain as controls in the output.
     
    If you want plain editable text with no content control wrapper at all, the only supported path in Power Automate is to convert the document via a post-processing step. A common approach is to use an Office Script after generation to programmatically remove content controls while preserving the text, then save the cleaned document. There is no Power Automate action that strips content controls natively.
     
      Best regards,

    Valantis   ✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

    ❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

    🏷️ For follow-ups  @Valantis.

    📝 https://valantisond365.com/ 💼 LinkedIn ▶️ YouTube
  • Suggested answer
    WarrenBelz Profile Picture
    156,229 Most Valuable Professional on at
    I cannot speak to AI Builder - I use HI (Human Intelligence) Builder, however a Word document generated from a merged template, when you use Create file in SharePoint or OneDrive in your Flow should be editable. I have a number of these in prod Flows and this is the case in them. You can lock the merged fields by checking the second box below in the Developer Tab > Properties of Word.
    but the rest of the document content should be editable unless it was saved read-only or the user only has this permisson on the location.
     
     So to your questions
    1. Is this behavior expected when Power Automate populates Word Content Controls?
      No - unless they have been configured as described above
       
    2. Is there a supported configuration to automatically make populated Content Controls editable?
      Yes - they are by default - although the bounding box will still be visible to the user

    3. Can Content Controls be unlocked or converted to regular text through Power Automate after document generation?
      Unlocked - Yes. Converted - No

    4. Is there a recommended approach for generating editable Word documents from AI Builder output while retaining the initial document formatting?
      Try writing the Flow and Template "the old way" - happy to help if requiired.

    5. Are there any limitations or licensing considerations related to editable Word templates generated from Power Automate?
      Other than Multiplexing (the link is a PDF download of the MS guide on the subject), probably not. I will leave it to you to interpret whether the guide applies, although the concept is more about accessing premium data sources.
     
     
    Please Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider answering Yes to Was this reply helpful? or give it a Like
    Visit my blog
    Practical Power Apps    LinkedIn  
  • WarrenBelz Profile Picture
    156,229 Most Valuable Professional on at
    A quick follow-up to see if you received the answer you were looking for. Happy to assist further if not.
     
    Please Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider answering Yes to Was this reply helpful? or give it a Like ♥
    Visit my blog
    Practical Power Apps    LinkedIn   
  • WarrenBelz Profile Picture
    156,229 Most Valuable Professional on at
    A quick follow-up to see if you received the answer you were looking for. Happy to assist further if not.
     
    Please Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider answering Yes to Was this reply helpful? or give it a Like ♥
    Visit my blog
    Practical Power Apps    LinkedIn   

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the June Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Apps

#1
WarrenBelz Profile Picture

WarrenBelz 353 Most Valuable Professional

#2
11manish Profile Picture

11manish 150

#3
MS.Ragavendar Profile Picture

MS.Ragavendar 68 Super User 2026 Season 1

Last 30 days Overall leaderboard