Microsoft Contacts

MICROSOFT 365 · PEOPLE

Directory lookups under that user’s own permissions.

Acts as the person, not as itself

Each user connects their own account. Every call carries both identities — the agent and the person it is acting for — so the agent can never reach past what that individual can already do.

Credentials never touch the agent

Tokens live in the vault and attach server-side at call time. The agent holds a session, not a secret, and revoking access does not mean rotating a key.

Every call on the record

Who asked, which agent acted, which action ran, and the verdict that let it through — one audit trail across every integration, not one per vendor.

What an agent can do

Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.

microsoft_contacts_create_contactWRITE

Create a new contact.

Contacts.ReadWrite

microsoft_contacts_create_contact_folderWRITE

Create a new contact folder.

Contacts.ReadWrite

microsoft_contacts_create_shared_contactWRITE

Create a contact in another user's shared mailbox.

Contacts.ReadWrite.Shared

microsoft_contacts_delete_contactWRITE

Delete a contact.

Contacts.ReadWrite