How Enterprise is set up
Your own region, and the three choices that shape it.
3 min read
Your own region
Every Enterprise customer gets a OneTaskList region of their own, in the Azure location you choose. It holds your boards, tasks, connections, tool tokens, attachments and logs, and nothing in it is shared with another customer. Your people still open OneTaskList at the usual address: the shared front door signs them in and sends them to your region, so there is no separate URL to hand out.
Three choices
| Choice | Option A | Option B |
|---|---|---|
| Where the region runs | Our Azure subscription. We run it and the Azure cost is part of your price. | Your Azure subscription. You pay Azure directly and see every resource. |
| Whose app keys connect your tools | Ours. People connect their tools straight away. | Yours. You register the apps and we hold the secrets in your Key Vault. |
| How people sign in | Work accounts, limited to your allow-list. | Single sign-on through your identity provider. |
What is in your region
- Container Apps: the web app and the background sync.
- SQL Database: boards, people and connections.
- Cosmos DB: tasks.
- Storage: attachments and queues.
- Key Vault: app secrets and encryption keys.
- Redis: cache and live board updates.
- Application Insights: logs and telemetry.
What stays shared
Sign-in, your organisation record (members, seats and the audit log) and billing run as shared OneTaskList services, so names, email addresses, sign-in settings and invoices sit outside your region. The front door keeps no customer data. See Where your data lives.
Getting started
- Scope: seats, Azure location, and the three choices above.
- Sign-in: send your allow-list, or set up single sign-on.
- App keys: use ours, or send us your own client IDs and secrets.
- Your region: we deploy it and connect it to the front door.
- Pilot, then everyone: a pilot group first, then open sign-in to your domains.