Agents beside people
Find the right agent, or the right person, by task
More of the help people need now comes from AI agents. DirectoryPoint lists them beside your colleagues, so one search for a task shows both: the agent that can do it and the people who know it.
How it works
- A site owner turns agents on. In Settings, Agents. Until then nothing about agents appears.
- Add the agents you use. By hand, or many at once from a CSV file. Each agent has a name, a description, the tasks it helps with, a launch link and a status.
- Tag them by task. Agents use the same list of tasks and skills as people, so a task like "book leave" or "expenses" connects both.
- People search as usual. Searching a task lists the matching agents first with an Agent badge, then the people who can help, each with their contact actions.
- Open agent. The button opens the stored link and says which website it opens, for example m365.cloud.microsoft. In Microsoft Teams it opens through Teams.
What "may need a licence" means
Many agents only work for people with the right licence or access. An agent built for Microsoft 365 Copilot, for example, may need a Microsoft 365 Copilot licence, and an agent from another company may need that company's own subscription.
DirectoryPoint cannot see who holds which licence for each agent, so it never promises that an agent will open for everyone. When a site owner marks an agent as needing a licence, its card says "May need a licence". The agent's description is the place to say which licence and how to ask for it.
A DirectoryPoint licence covers DirectoryPoint only. It does not include, sell or replace any licence an agent needs.
On every agent card
- An Agent badge, so nobody mistakes an agent for a person
- The tasks it helps with
- "May need a licence", where the site owner says so
- The website Open agent goes to
Agent accounts in Microsoft Entra ID
Some organisations give agents their own accounts in Microsoft Entra ID. With the Standard tier, DirectoryPoint recognises them, so the people directory stays about people.
Badged
Agent accounts show an Agent badge wherever they appear.
Not counted
They are left out of headcount, so they never count towards your plan.
Kept apart
They are left out of the org chart and celebrations by default; an admin can change that.
Questions about agents
Does DirectoryPoint include any AI agents?
No. DirectoryPoint is a directory: it lists agents your organisation already has, so people can find them by task. It does not build, host or run agents.
Does listing an agent give people access to it?
No. Open agent only opens the link you stored. Whether someone can use the agent is decided where the agent lives (for example by Microsoft 365 Copilot licences, Copilot Studio sharing or the agent maker's own sign-in), not by DirectoryPoint.
Can DirectoryPoint see what people ask an agent?
No. DirectoryPoint never sees conversations with agents. It stores only the details a site owner enters about each agent.
Who can add agents?
Site owners of the DirectoryPoint site, or, when a site owner names a shared registry, the owners of that registry site. Everyone who can open the site that holds the agents list can read it, so do not put anything private in an agent's description.
Can several sites share one agents list?
Yes. In Settings, Shared registry location, a site owner can name one other site on the same SharePoint host to hold the agents list and its task terms, shared with other Apps 365 Point apps there. DirectoryPoint never reads or writes a registry on another host, and says plainly when the site cannot be read.
Why is the agents list off at first?
So that each organisation decides when agents appear beside people. A site owner turns it on in Settings, Agents, and can turn it off again at any time.
Agents are added by hand or from a CSV file. What is in each release is on the changelog.
Try every feature for 14 days
Every feature is free for 14 days from the moment a site owner sets DirectoryPoint up, with no key and no card. No Microsoft Graph permission is needed to start.