MC1508992: Power Platform Removes Temporary Authentication URLs from Word Online (Business) Connector for Secure File Access

MWPRO IMPACT SCORE
OPERATIONAL IMPACT
68
0 25 50 75 100
HIGH IMPACT • REVIEW RECOMMENDED
Recommended Action:
Review the update and plan any required actions before rollout.
▶ What is MWPro Impact Score? Watch our 60‑second explainer

Primary Audience

Power Platform AdminsMicrosoft 365 AdminsSharePoint AdminsIT ManagersDevelopersService Owners
Why this score?
AI Confidence
HIGH
Enough detail is available to trust this assessment.
Assessment Reasoning
This is a confirmed deprecation and behavioural change for the Word Online (Business) connector in Power Platform, effective 14 October 2026. It replaces temporary unauthenticated URLs with secure authenticated access, requiring updates to flows and integrations relying on old patterns. Admins must review and modify automation, sharing or downstream integrations while coordinating with developers and workflow owners; user impact is indirect through any broken flows or revised processes.
78
🛡️ Admin Impact
40
👥 User Impact
72
⚡ Urgency
68
🔧 Effort
ℹ️ WHAT YOU NEED TO KNOW
📌

AT A GLANCE

The Word Online (Business) connector now requires authenticated access instead of temporary unauthenticated URLs. This change improves file access security across SharePoint and OneDrive integrations.
👥

END USERS

No major end-user change expected.
🛡️

IT ADMINS

Review and update any flows or integrations that use unauthenticated download URLs to ensure continued file access.
📅

ROLLOUT TIMELINE

Available:
Now

📢 Official Microsoft Message Center Announcement


Power Platform – Deprecation of temporary authentication URLs for the Word Online (Business) connector
Message ID: MC1508992
On October 14, 2026, the Word Online (Business) connector will remove its dependency on temporary, pre-authorized download URLs. This change improves the security for file access in SharePoint and OneDrive scenarios by requiring authenticated access for generated document content.

How does this affect me?
After this change, connector actions will use authenticated access to retrieve files instead of unauthenticated download URLs. This will affect organizations using the Word Online (Business) connector in Power Automate, Power Apps, or related SharePoint and OneDrive scenarios. Additionally, makers and admins with flows or integrations that depend on unauthenticated temporary or pre-authorized download URLs returned by connector actions will also be affected by this.

With this change:
  • The connector will remove its dependency on temporary or pre-authorized download URLs.
  • Flows relying on the CreateWordFileWithContent returned URL as an unauthenticated direct download link may be impacted. It is recommended that customers should review any flows that depend on the returned URL for unauthenticated file access.
The following actions are not expected to introduce any breaking changes as these operations already retrieve content using authenticated access:
  • GetSchema
  • GetFile: The connector will retrieve content using authenticated access.
  • ConvertFile / GetFilePDF: The connector will use authenticated streaming instead of a pre-authorized download URL.
What action do I need to take?
To prepare for this change, admins, users, and makers need to perform the following actions:
  • Use authenticated file content retrieval or appropriate SharePoint sharing links instead of unauthenticated download URLs.
  • Review flows and integrations that use Word Online (Business) connector to output URLs for unauthenticated file access.
  • For file-content scenarios, use SharePoint or OneDrive Get file content and pass the file content or bytes downstream.
  • For email attachment scenarios, use Get file content and then send the email with the file attached.
  • For sharing-link scenarios, use file metadata and create an appropriate SharePoint sharing link that matches your tenant and site sharing policies.
  • For HTTP, custom connector, Azure Function, or external service scenarios, ensure the downstream caller authenticates to SharePoint or Microsoft Graph and has permission to access the file.

Source: Microsoft Message Center • Analysed by MWPro

Share This Update