# Google and Microsoft

Connect OAuth accounts and understand shared calendars, scopes and tenant restrictions.

Source: https://docs.getridian.com/integrations/google-microsoft/
Language: en
Reviewed: 2026-09-20

## Calendar access

Connect from Ridian using the provider's sign-in page. Read the consent screen and select the intended provider account. Existing shared access depends on permissions at Google or Microsoft; Ridian cannot manufacture rights the provider has not granted.

For assistant workflows, reading, availability, supported standalone writes and bounded weekly-series creation use the shared permission path. Not every event is editable: organized meetings, series and provider-specific restrictions require their supported operation.

## Microsoft partial consent

A Microsoft connection can succeed while an optional permission is missing. Check the specific account capability when tasks, contacts, mail or shared calendar access fails. Reconnect or request the appropriate scope upgrade through Ridian. A tenant administrator's restrictions may require their involvement.

Tenant binding is a separate boundary from signing in successfully. Do not connect a different organization's account as a workaround for a denied work-account policy.

## Google organizational resources

Google Workspace room discovery requires organizational setup in addition to an ordinary connected calendar account. Personal Google accounts are not a substitute for a Workspace resource configuration. See [rooms](https://docs.getridian.com/guides/rooms/).

## Additional domains

Tasks, personal contacts and sending mail require their own scopes and client permissions. Calendar permission is not a blanket authorization for these domains. Gmail support here is sending mail, not reading an inbox. Check [tasks, contacts and mail](https://docs.getridian.com/guides/additional-tools/) before enabling a workflow.