---
title: Does Ashby support integrating with either multiple Google Workspaces or Microsoft 365 tenants?
slug: does-ashby-support-integrating-with-either-multiple-google-workspaces-or-microsoft-365-tenants
docTags: rl7p3XLQknqPB1UQ70cu_,7ciBZ_ksC9UuPdKWchuuv
createdAt: 2025-07-10T11:56:44.877Z
---

:::hint{type="warning"}
It is not possible to integrate with both Google Workspace and Microsoft 365 instances in the same Ashby account. For more on this, check out [Does Ashby support integrating with both Google and Microsoft at the same time?](https://docs.ashbyhq.com/does-ashby-support-integrating-with-both-google-and-microsoft-at-the-same-time)
:::

Below you can find a table listing what is and is not supported in a single Ashby account

| Scenario                                                                 | Is this supported?    | Relevant guide                                                                                                                                                                                                              |
| ------------------------------------------------------------------------ | --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Multiple domains within a single Google Workspace account                | Yes                   | [Updating the domain or adding a secondary domain to an Ashby account](https://docs.ashbyhq.com/updating-the-domain-or-adding-a-secondary-domain-to-an-ashby-account)                                                       |
| Multiple domains within a single Microsoft 365 tenant                    | Yes                   | [Updating the domain or adding a secondary domain to an Ashby account](https://docs.ashbyhq.com/updating-the-domain-or-adding-a-secondary-domain-to-an-ashby-account)                                                       |
| Multiple domains across more than one Google Workspace                   | Yes, with limitations | [Does Ashby support integrating with either multiple Google Workspaces or Microsoft 365 tenants?](https://docs.ashbyhq.com/does-ashby-support-integrating-with-either-multiple-google-workspaces-or-microsoft-365-tenants)  |
| Multiple domains across more than one Microsoft 365 tenant               | Yes, with limitations | [Does Ashby support integrating with either multiple Google Workspaces or Microsoft 365 tenants?](https://docs.ashbyhq.com/does-ashby-support-integrating-with-either-multiple-google-workspaces-or-microsoft-365-tenants)  |
| Multiple domains across both Google Workspaces and Microsoft 365 tenants | No                    | [Does Ashby support integrating with both Google and Microsoft at the same time?](https://docs.ashbyhq.com/does-ashby-support-integrating-with-both-google-and-microsoft-at-the-same-time)                                  |



Ashby does support connecting either multiple Google Workspaces within a single Ashby account or multiple Microsoft 365 tenants within a single Ashby account. However, these instances are treated independently and do not behave as a unified system. Users across different domains or tenants will face the same platform-level limitations when trying to schedule interviews or send emails to one another through Ashby.

## What does that mean?

You can configure more than one domain (e.g., @acme.com and @subsidiary.acme.com) or tenant, and users under each can connect their calendars and inboxes via Personal Settings.

However:

- Email and calendar features will only work within the same domain or tenant
- Users from one domain cannot schedule on behalf of or email as users from another
- Google Meet links can't be embedded in Microsoft Outlook events, and vice versa
- Free/busy availability can’t be shared between users on different platforms or domains

Ashby mirrors Google and Microsoft's native limitations. They don’t support seamless cross-domain scheduling or delegation unless complex enterprise trust relationships are configured, and even then, Ashby does not support those workarounds.

## What can users still do across instances?

Regardless of the integration setup, users from any domain or tenant can:

- Log in and access Ashby (if provisioned)
- Leave interview feedback
- Submit referrals
- Review applications\*
- Collaborate on candidate profiles and leave notes\*
- Create jobs and reports\*
- Subject to access permissions — see [User Permissions](https://docs.ashbyhq.com/user-permissions) for more.

## What are the limitations?

When users from different platforms or domains try to interact through Ashby, they’ll run into these constraints:

- Can’t schedule interviews for users outside their own domain or tenant
- Can’t send emails on behalf of users from other domains or tenants
- Calendar availability is only visible within the same domain/tenant
  - Users who have connected their calendar via personal settings in Ashby (through the personal OAuth integration) may be able to view calendar availability for users on a different domain or tenant. This access is view-only — it does not enable scheduling on behalf of those users or any other cross-domain calendar actions.
- Conferencing links cannot be embedded across platforms

These limitations are imposed by the native behaviors of Google and Microsoft APIs, which Ashby respects to maintain security and stability.

## Will Ashby support unified cross-domain or cross-platform scheduling in the future?

It’s unlikely. These limitations stem from how the underlying platforms work — Ashby reflects those constraints to avoid introducing data access issues or unreliable functionality.

If your organization operates across multiple domains or tenants, we recommend choosing a primary domain for recruiting or working with your IT team to centralize recruiting-related calendars and emails under a shared instance.



