Supported platforms & regions

MeetCrew supports Microsoft Teams, Zoom, Webex, and Google Meet. Its availability is scoped by region, and a teammate will refuse to join a meeting that falls outside that scope.

Platforms

Four meeting platforms are supported: Microsoft Teams, Zoom, Webex, and Google Meet. A teammate joins any of them as a named, disclosed participant.

Regions

v1 availability covers the United States and Canada. MeetCrew is hosted today in one Microsoft Azure region, US East, and every tenant is placed there. Self-service signup is open to organizations established in the United States; an organization established in Canada onboards by contacting us. Each tenant is assigned its region at onboarding, and that region is the value the join-time check compares against. The check is an allow-list of three regions — US East, US West, and Canada Central — so any geography without one of them is refused. The European Union and the United Kingdom are out of scope in v1. An organization established outside the supported jurisdictions cannot onboard: eligibility is attested and checked at onboarding, before any resources are created.

How geo-fencing behaves

Geo-fencing is enforced at three points: your tenant’s assigned region at onboarding, each deployment’s assigned region at configuration, and — on Microsoft Teams only — the meeting organizer’s assigned tenant region at join time. The join-time check is the subtle one, and it is narrower than it sounds. On Teams, a teammate invited to a meeting whose organizer tenant holds no supported assigned region refuses to join and notifies your administrator. A Teams short link does not name its organizer, so when you launch a teammate with one, you attest that the meeting is organized inside your own organization; MeetCrew then checks your own tenant’s region and does not verify the attestation. Zoom, Google Meet and WebEx carry no organizer signal, so the dispatching deployment’s own assigned region stands in instead — and because that region is in scope by construction, the join-time check never refuses on those three platforms. There the limit rests on your onboarding attestation and on the region assigned to each deployment.