After Ignite: someone in your company can now build an agent on SharePoint
Microsoft Ignite ran from 19 to 22 November 2024. One announcement needs attention this week rather than next year.
At Ignite, held from 19 to 22 November 2024, Microsoft set out an ambition to put a copilot in every employee’s hands and an agent in every business process. Among the announcements: Copilot Actions for automating routine tasks, employee self-service agents for HR and IT, an interpreter in Teams, and SharePoint agents.
Most of that is preview or roadmap. SharePoint agents are the item that lands now.
Why that one is different
A SharePoint agent is scoped to a site, a library or a set of documents, and it answers questions about them. Creating one is a few clicks by whoever can already access those files.
That is a genuinely useful thing. A site holding your quality manual, your technical datasheets or your standard terms becomes answerable in plain language instead of searchable by filename. For a Swiss SME with a decade of accumulated PDFs, that is real value on day one.
It is also a change in how your existing permissions behave. A document that was technically accessible but practically buried is now one question away. Nothing was breached. Something that relied on obscurity stopped being obscure.
Three things to check this week
- Your SharePoint permissions, not your agent policy. The agent inherits access; it does not grant it. So the real audit is: which sites are open to « everyone in the organisation » and what is actually in them. Most companies find at least one surprise here, usually an HR or finance folder from a reorganisation.
- Who may publish an agent to others. Building one for yourself is low risk. Sharing one with a department changes who reads what, and should be a decision rather than a default.
- Document currency. An agent answering from a 2019 price list will answer confidently and wrongly. Retire superseded documents, or scope agents to sites you know are current.
The honest framing
This is not a security incident waiting to happen. It is a permissions audit that most companies have deferred for years and now have a concrete reason to do.
An afternoon spent on the second bullet above is the highest-value AI governance work available to a Microsoft-based SME this quarter. It requires no new licence and no project.