AI · MICROSOFT · SHARED KNOWLEDGE

AI, in your work.

Understand what’s changing.
Discover what you can do with it.

IN FOCUS / AI & industry

Copilot Chat limits: preparing support teams and user expectations

Microsoft extends usage limits to additional Copilot Chat features for users without a Microsoft 365 Copilot license in commercial organizations. The notifications call for support preparation and a review of license requests, without turning every limit into a recommendation to buy.

Read the story 3 min

TRY IT IN NEXO

A useful answer starts before the question.

Choose a task. Compare two requests. Take away a prompt with context.

Open the prompt workshop Interactive example · Fictional data · No signup
FROM IDEA TO NEXT STEP

“Summarise this meeting.”

ContextGoalFormat

“Extract decisions, actions and what still needs confirming.”

The difference is in what you ask.

EXPLORE NEXO

The latest, with perspective.

59 articles

Topic: All

Business Central and SharePoint: a fix addresses REST upload 404 errors

BCApps includes a path adjustment for the SharePoint connector. We review the backports and the requirements for evaluating Microsoft Graph while delivery is confirmed.

Microsoft · Announcement: · Editorial review

Laptop with a code editor open on a desk, with a monitor behind it.
Archive photo: Christopher Gower / Unsplash.
nNexo CommunityEditorial review · 2026-11-08

ANNOUNCEMENT & AVAILABILITY

Public sources checked on November 7, 2026. Integration into a branch does not establish that the patch is installed in customer environments. The sources consulted do not provide a complete list of affected and fixed builds.

Fix SharePoint REST upload 404 caused by trailing slash in parent folder

A trailing slash in the parent folder

The BCApps commit links legacy REST upload 404 errors to a trailing slash in the parent folder path. The change normalizes that path while preserving `/` for the root.

The described scope includes Storage Browser uploads, external attachments, copying, and moving files. Graph mode is unchanged.

What is merged and what remains unconfirmed

The main PR was merged on November 5. Its backports had the following status when checked:

The target branches help track maintenance work, but they do not constitute a list of releases already delivered. For a particular installation, the build must be identified and checked for inclusion of the change.

BranchReferenceVerified status
29.xPR #13693Open
29.1PR #13694Merged on November 6
29.0PR #13695Merged on November 6
28.xPR #13696Merged on November 6
28.5PR #13697Merged on November 6
28.4PR #13698Merged on November 6

Technical scope and validation limits

The 29.x backport description also covers directory paths ending in a slash, doubled separators before filenames, and existence checks. It preserves the original parent paths returned in listings.

The main PR states that AL compilation, tests, and validation against real SharePoint were not run locally. Adding tests to the code does not, by itself, demonstrate that the scenario works in a customer environment.

Nexo's proposed diagnostic approach

Our editorial interpretation is that operations should be investigated separately. A 404 alone is insufficient to attribute an incident to this defect. We suggest gathering a minimal reproduction before changing configuration:

  • Record the Business Central build, connector version, and configured API mode.
  • Record the exact operation, failure time, and submitted path without including credentials.
  • Test navigation, upload, and existence checks separately in a test environment.
  • Compare results before and after the change, keeping the file and destination folder the same.

Synthetic example: three different questions

Consider a test folder named `Ensayo` and a file named `muestra.txt`. This example is Nexo's diagnostic proposal; it neither reproduces an incident nor presents measured results.

OperationQuestion to answer
Navigate to EnsayoCan the folder be opened and its contents listed?
Upload muestra.txtIs the file created at the intended destination?
Check its existenceDoes the subsequent query find that same file?

Microsoft Graph: an alternative that needs preparation

The 29.0 backport PR proposes disabling `Use legacy REST API` as a temporary workaround.

Microsoft's documentation distinguishes permissions by API and authentication method. For Graph with a client secret or certificate, it specifies the `Sites.Selected` application permission and a per-site `write` grant as the minimum for full connector functionality.

Nexo's recommendation: review the app registration and grants before testing the switch. Existing REST permissions should not be assumed sufficient for Graph, nor should changing modes be expected to resolve every upload error.

Created with AI assistance and reviewed by Nexo Community. Practical proposals and editorial interpretation are distinguished from documented facts.

Read the source ↗

CONNECT THIS IDEA

A useful next step.

AI & industry · 4 minExpense Agent adds per diem lines on travel approval in development codeAI & industry · 3 minExpense Agent adds pre-submission approver assignment to its code

Copilot Business in CSP: preparing for usage-based billing planned for 2027

Microsoft postpones the change for new CSP purchases to January–March 2027. Certain eligible experiences may incur charges beyond license fees, subject to an adjustable monthly limit.

Microsoft · Announcement: · Editorial review

Copilot panel in Microsoft Word with a prompt to draft a proposal from meeting notes.
Microsoft 365 Copilot in Microsoft Word (archive). Image: Microsoft. Used with permission from Microsoft.

More articles appear as you continue scrolling.