Skip to content
PERINGER Data Solutions, back to home

Back

Solution

Mail and collaboration tenant

A tenant grows by accretion: one more administrator, a forgotten external share, licences nobody reviews. I compare the operator, the contract, the processing locations and the support access before choosing, then design or take over the tenant with separated roles, a protected domain, a tested migration and licences reconciled to people.

The claims you can finally make

In practice

  • A decision matrix that also tests keeping the current service: operator, contract, processing locations, support access, subprocessors, retention, export and deletion
  • Tenant design: separated admin roles, conditional access, external sharing rules, retention and logs
  • SPF, DKIM and DMARC introduced in stages and monitored, for Exchange, Google Workspace, kSuite, Infomaniak or Proton mail
  • A piloted migration with coexistence; history, calendars, contacts, aliases and shared mailboxes reconciled before the old service closes
  • Licence reconciliation: assignment, use, contract, renewal and owner, with every removal approved before application
  • A decision record for the applicable processing: operator, contracts, access, locations, subprocessors, retention and exit, with legal review where interpretation is required

Systems involved

  • Microsoft 365 and Exchange Online, Google Workspace, Infomaniak kSuite
  • Proton Mail and Proton Drive where the extra confidentiality justifies its constraints
  • The domain registrar and the DNS records
  • The directory of record and the secrets manager
  • Vendor and reseller portals for licences

Service lineServers and hosting →

How it runs

  1. Scoping

    Confidentiality, contract, access, location, retention and exit each get named first. The service comes after that decision.

  2. Design

    Admin roles, sharing and retention rules and the domain records are drawn, then the tenant is prepared while the current service keeps running.

  3. Migration

    History imported, then the MX records switched inside an announced window. The old mailbox stays readable until the final reconciliation.

  4. Verification

    Inbound and outbound mail, delegation, sharing and a mailbox restore are tested. DMARC reports show the real senders; I reconcile them before tightening the policy, and hand over the reconciled licence list.

Test the fit: Mail and collaboration tenant

Describe the context, constraints and decision you need to make. The first conversation qualifies scope, boundaries and the next useful step.

Describe the situation