MC1508992 Low
Power Platform – Deprecation of temporary authentication URLs for the Word Online (Business) connector
Summary AI-generated
Word Online (Business) connector will require authenticated access for file retrieval, removing dependency on unauthenticated download URLs as of October 14, 2026, improving SharePoint and OneDrive security.
Suggested actions AI-generated
- Review flows and integrations for unauthenticated file access.
- Use authenticated file content retrieval or SharePoint sharing links.
- Update email attachment flows to use authenticated file content.
- Create appropriate SharePoint sharing links matching tenant policies.
- Ensure external services authenticate and have file access permissions.
Written by Azure OpenAI (gpt-4.1) from the text of the post below. It can be incomplete or wrong; the original post is authoritative.
Similar posts
Search for more like this- MC1392593 Power Platform - Information regarding the retirement of the OneDrive (Consumer) Connector
- MC1184649 Microsoft SharePoint: Retirement of IDCRL authentication protocol and enforcement of OpenID Connect and OAuth protocols
- MC1454816 [Updated Date] Power Platform - Information about SharePoint file thumbnail changes
- MC1492958 Microsoft Graph: New tenant controls for retirement of non-standard file API tokens
- MC1189663 (Updated) Retirement of external access token for actionable messages – moving to Microsoft Entra authentication
- MC1527468 Microsoft Dataverse - Custom connector definition access update
Original post from Microsoft
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:
To prepare for this change, admins, users, and makers need to perform the following actions:
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.
- 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.
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.