SharePoint Updates

Introduction

We’ve shipped a focused set of improvements to Unifize’s Microsoft 365 SharePoint integration to deliver smoother file handling, more deterministic link generation, and stronger tenant-scoped security.

What this release covers

1) File picker authentication (token handling)

What you’ll notice:

The latest release makes it reliable to pick a file from SharePoint in the File Upload Checklist. This means no more random “can’t load site” errors, fewer retries, and faster selection.

What changed under the hood:

Unifize now sends a single, correct SharePoint sign-in token to the picker (with better diagnostics), removing the ambiguity that occasionally caused the picker to break.

---

2) Reliable file redirection (createLink scope)

What you’ll notice:

In the File Upload Checklist, when you click the Edit button in the attached SharePoint files, you’re taken straight to the exact file, not to a parent folder. This prevents the creation of anonymous edit links and limits them only to people inside your Microsoft 365 organization.

What changed under the hood:

In scenarios with inherited permissions, users could occasionally be routed to a folder URL instead of the file URL. Now, Unifize uses /graph-api/drive/{drive-id}/item/{item-id}/createLink to generate a file-specific edit link every time, with a restricted scope of the createLink API to within the M365 organization.

---

Before vs After

1. File picker authentication (token handling)

Before	After
The API server returned two tokens in its response to the file-picker request; the filepicker then attempted a key lookup (command.resource) via the Channel Messaging Web API.	The response now sends only the SharePoint token, and the client uses it exclusively for the file picker.
In some cases that lookup returned undefined, leaving the filepicker without a valid token and causing errors when picking files from sites.	This removes the command.resource lookup issue and adds log messages in the same namespace for better tracing.

1. Reliable file redirection (createLink scope)

Before	After
In scenarios with inherited permissions, clicking the Edit button in the File Upload Checklist on the platform may redirect you to a folder URL rather than the file URL.	Unifize calls /graph-api/drive/{drive-id}/item/{item-id}/createLink to generate a file-specific edit link every time, with a restricted scope of the createLink API to within the M365 organization.
Links were not always restricted to your tenant so that anonymous edit links could be created.	Edit always opens the exact file, and anonymous links are not created.

Uses cases

• Better team collaboration: Anyone opening an attached SharePoint file from the File Upload Checklist by clicking the Edit button is taken directly to the file without detours to a parent folder. This avoids confusion, saves time, and keeps everyone working on the same document.

• Faster file selection: The SharePoint file picker is more reliable, so files attach quickly with fewer “site can’t load” errors or retries.

• Safer internal editing: Edit links work only for people in your Microsoft 365 organization, reducing accidental exposure and keeping edits inside your tenant.