ConveRact · integrations
Microsoft 365 API and OAuth Integration
Use your organization�s application registration to configure selected Microsoft 365 API actions. The connector builder stores credentials on the server and provides explicit read execution and write approval.
Discuss your integration requirementsFree integration. No installation charge or one-time ConveRact fee. Plan, usage, third-party, and custom development costs may apply.
Reviewed · ConveRact team
Match the application to your tenant
Supply the documented authorization and token endpoints, client ID, scopes and callback URL. Complete any required administrator consent in your organization. The hub implements Authorization Code with PKCE; unattended client-credentials grants are outside this builder.
Define resource-specific actions
Configure the exact API paths for the resources your application is allowed to access. Graph API usage is configured as REST JSON here; the name Microsoft Graph does not imply GraphQL. Automatic mailbox ingestion, event subscriptions and directory synchronization require their own workflows.