10 posts tagged with "Microsoft 365"

You have an idea for an app that could make your team's work much easier. It would give everyone a clear view of tasks, responsibilities, and progress. You describe how it should work, and Copilot Code builds a first version. You can try it, refine it, and prepare it for your team.

I see Microsoft building an app platform inside Microsoft 365. Creating code through prompts, often called vibe coding, is becoming part of a broader process: build, publish, share, and maintain.

I recently wrote about a SharePoint resource center with dynamic filtering. I like that approach. It helps colleagues find documents and links, even if they do not know the right search term.

On October 14, 2026, Microsoft announced SharePoint Knowledge Base in Frontier Preview. Its pages use Markdown. I like that choice because M365Wizard also uses Markdown files. In SharePoint, you can use a visual editor, or edit the Markdown.

A resource center points readers to sources. In a knowledge base, you write the explanation on the page itself. You can link pages about related topics. Colleagues, Copilot, and agents can then use the same guidance. This makes SharePoint a shared knowledge platform.

On September 25, 2026, Microsoft announced the new Copilot with Home, Code, and Autopilot. Home brings Chat and Cowork together, Code helps you build your own solutions, and Autopilot is designed to keep working in the background.

Mike Tholfsen explains the announcement clearly in his short video, The NEW Microsoft Copilot Super App – Everything That's Changing. He connects the new app to four ways of working: getting help, delegating, building, and automating. I find that breakdown useful because it helps you decide which work you want Copilot to take on.

A document can be stored correctly and still be difficult to discover. Search and Copilot help when someone can describe what they need. They are less helpful when a colleague only knows the subject and wants to see what is available.

Dan Carroll of Academy 365 demonstrates a practical answer in his video, Why I don't build document libraries any more.... He turns a SharePoint document library into a visual resource center and uses dynamic filtering to guide visitors from a topic to the relevant resources.

A SharePoint library reaches 5,000 files, and then a view stops working or a flow misses records. The library still has room for far more content.

Microsoft's List View Threshold guidance says that a SharePoint list or library can contain up to 30 million items or files. The familiar 5,000 figure is the List View Threshold. It limits how much work certain database operations, such as a query, can do at once. Microsoft also notes that the exact threshold can vary.

Most users and many libraries will never run into the List View Threshold. But when a view, flow, migration, or permission change does hit a limit, the visible error rarely tells the complete story. You first need to understand which technical path is failing and why.

Do not split a library simply because it passes 5,000 files. First ask how people and systems find, show, synchronize, secure, and process those files.