microsoft
microsoft.
List the linked Microsoft 365 accounts and the services each one has authorised.
setup & usage
this connector is the account: the Microsoft address, its token, the directory it signs in to, the default account. each Microsoft service — SharePoint & OneDrive, Outlook, Outlook Calendar, Teams — is a connector in its own right, with its own consent (its permissions only): authorise it from its card, on the same account. Microsoft adds each new consent to the ones already given: one account, one connection, several services.
_account=<name>, otherwise the one the project pins — on the service's card, otherwise on this one —, otherwise the only one, otherwise the default. an unknown name is refused, never replaced by anotherwhen a client has invited you into THEIR Microsoft 365 (you are a guest of their directory, with a personal Microsoft account or another company's account), the ordinary sign-in lands in your own directory, or fails. In the Client directory field of the connection, give the client's directory: its Microsoft domain (contoso.onmicrosoft.com, or a domain of theirs like contoso.com), its directory ID, or simply the address of one of its SharePoint sites (https://contoso.sharepoint.com/sites/...).
contoso.onmicrosoft.com: a convention that almost always holds. If Microsoft says the directory does not exist, ask the client's administrator for the exact domain or the directory ID (Entra admin center, Overview)many organizations forbid a person to authorise an application alone: Microsoft then says "admin approval required", and the card comes back with that reason. A Microsoft 365 administrator of the organization must approve oto once, for everyone:
microsoft_admin_consent() returns the approval link (url, valid seven days) to send to that administrator — services to approve (default: all the Microsoft services), tenant the organization's domain or a SharePoint address of theirs (default: the administrator's own directory)microsoft_accounts — the linked accounts and, for each, the services it has authorised and the client's directory it signs in to. This is the question to ask when a service tool refuses: the account exists but has not yet authorised THIS service — connect it from the service's card.
oto_identity(op='set', connector='microsoft', identity_id='<account>')this connector accepts multiple comptes: connecting with another compte adds it alongside the others, named by its address; reconnecting with the same one replaces its own.
_account="<name>" on the tool; list them: oto_identity(op='list', connector='microsoft')oto_identity(op='set', connector='microsoft', identity_id='<name>')_account) and adding upoutils
utilisation
claude plugin marketplace add otomata-tech/oto-plugin — mcp + skill configurés.pipx install oto-cli puis oto microsoft …