> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tenantcore.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Agency Onboarding

> A repeatable workflow for agencies and operators managing multiple Microsoft 365 tenants, domains, and mailboxes.

# Agency Onboarding

TenantCore is designed to make repeated infrastructure setup predictable.

For an agency or operator managing multiple client environments, use the same resource workflow every time.

## Recommended onboarding sequence

For each client or business environment:

```text theme={null}
Confirm ownership/authorization
        ↓
Connect Microsoft 365 tenant
        ↓
Add domains
        ↓
Configure DNS
        ↓
Create mailboxes
        ↓
Configure credentials/MFA
        ↓
Configure Outlook access if needed
        ↓
Set sending limits
        ↓
Connect sending platforms
        ↓
Review monitoring and Reports
```

## Keep client resources separated

Use TenantCore's tenant/domain/mailbox hierarchy to keep infrastructure associated with the correct Microsoft tenant.

Do not mix domains or mailboxes across clients simply because one operator manages all of them.

## Tenant slots

Each connected BYOT Microsoft 365 tenant consumes one BYOT tenant slot.

Base, Plus, and Complete each include 3 BYOT tenant slots.

Add additional slots as your managed client count grows.

## Provider connections

DNS-provider and sending-platform connections are scoped to the TenantCore account that owns them.

Use clear integration names where multiple workspaces/accounts exist so operators can select the correct destination.

## Standardize mailbox policy

For repeatable operations, define internal standards for:

* mailbox naming
* maximum mailbox count per domain
* daily send limit
* whether TenantCore-managed MFA is used
* which licensed user is the Mailbox Access Account
* which sending platform is used
* when a domain is considered ready for production

## Use Reports during handoff/support

Reports helps an agency answer:

* what changed
* when it changed
* which resource was affected
* whether the issue recovered
* which TenantCore action occurred

Use resource-scoped Reports rather than recreating infrastructure history manually for each client.