Basic O365 Organization email structure
You can follow this structure example to organize your email accounts based on your company’s needs. First let’s clear some basic concepts of office 365 mail service.
O365 can handle different types of email addresses and it is powered by active directory. So it gives the option to create an email structure similar to your organization’s levels.
O365 account
Name: John Doe
Type: Person
Email: john.doe@yourdomain.com
- Is physical person
- Logs in with username / password
- Accessing all services available in his plan using the same credentials
- Accessing all groups / teams he is an active member using the same credentials
- Accessing all shared emails he has active access using the same credentials
- Requires license
O365 Group
Name: Project 1 / Team 1 / Group 1
Type: Group of people
Email: project1@yourdomain.com / team1@yourdomain.com / group@yourdomain.com
- Is a group of members sharing resources to accomplish certain tasks or projects
- Each group is assigned with a shared email address
- One drive shared folders
- One Note shared notepads
- Shared calendars
- Shared contacts lists
- and more
- Members are granted access by admins and log in using their own credentials
- Does not require license
O365 shared email account
Type: Email address
Email: info@yourdomain.com / sales@yourdomain.com / marketing@yourdomain.com
- Is only an email account
- Handled / Used by individual members with active accounts
- Associated members gain access to use it with their own credentials
- Does not access services and apps
- Does not require license
O365 Distribution lists
Type: Email address
Email: allcompany@yourdomain.com / alleurope@yourdomain.com / allmarketing@yourdomain.com
- Is a contact list of email accounts grouped together
- Used to allow someone to send an email to a premade group of people without knowing their personal emails.
- Does not require license
Lets see some common structural examples
Let’s imagine that we have the following organizational structure and we need to transfer that into our email server structure.
Organization > 3 Departments > 8 People.
MyCompany
info@mycompany.com
Marketing Dept
marketing@mycompany.com
(Can be either a shared email or a group email)
Sales Dept
sales@mycompany.com
(Can be either a shared email or a group email)
Accounting Dept
accounting@mycompany.com
(Can be either a shared email or a group email)
O365 account
Name: John
Type: Person
Dept: Marketing
Personal Email: john@yourdomain.com
Shared Email: marketing@yourdomain.com
O365 account
Name: Jane
Type: Person
Dept: Sales / Marketing
Personal Email: jane@yourdomain.com
Shared Email: sales@yourdomain.com / marketing@yourdomain.com
O365 account
Name: George
Type: Person
Dept: Sales
Personal Email: george@yourdomain.com
Shared Email: sales@yourdomain.com
O365 account
Name: Jasmin
Type: Person
Dept: Accounting
Personal Email: jasmin@yourdomain.com
Shared Email: accounting@yourdomain.com
O365 account
Name: Nick
Type: Person
Dept: Marketing
Personal Email: nick@yourdomain.com
Shared Email: marketing@yourdomain.com
O365 account
Name: Chris
Type: Person
Dept: Sales / Accounting
Personal Email: chris@yourdomain.com
Shared Email: sales@yourdomain.com / accounting@yourdomain.com
O365 account
Name: Jacob
Type: Person
Dept: Sales
Personal Email: jacob@yourdomain.com
Shared Email: sales@yourdomain.com
O365 account
Name: Helen
Type: Person
Dept: Accounting / Marketing
Personal Email: helen@yourdomain.com
Shared Email: accounting@yourdomain.com / marketing@yourdomain.com
Now let’s see some common scenarios
Ler’s say that we need a department based structure. Our above example would look like this:
Shared Email / Department |
Members with access |
Sales |
Jane George Chris Jacob |
Marketing |
John Jane Nick Helen |
Accounting |
Jasmin Chris Helen |
Or if we see it by User
User | Can Access and receive or send on account of |
John | Marketing |
Jane |
Sales Marketing |
George | Sales |
Jasmin | Accounting |
Nick | Marketing |
Chris |
Sales Accounting |
Jacob | Sales |
Helen |
Marketing Accounting |
Now let’s mix it up a bit
Let’s imagine that our company gets a couple of projects and our members need to work in custom groups regardless the department they’re in.
Project 1: New Product launch "Test Product"
testproduct@mycompany.com
(A group email)
O365 account
Name: John
Type: Person
Dept: Marketing
Personal Email: john@yourdomain.com
O365 account
Name: George
Type: Person
Dept: Sales
Personal Email: george@yourdomain.com
O365 account
Name: Chris
Type: Person
Dept: Sales / Accounting
Personal Email: chris@yourdomain.com
Project 2: Corporate new years eve party
happynewyear@mycompany.com
(A group email)
O365 account
Name: Jane
Type: Person
Dept: Sales / Marketing
Personal Email: jane@yourdomain.com
O365 account
Name: Jasmin
Type: Person
Dept: Accounting
Personal Email: jasmin@yourdomain.com
Project 3: New headquarters in Paris / France
paristeam@mycompany.com
(A group email)
O365 account
Name: Nick
Type: Person
Dept: Marketing
Personal Email: nick@yourdomain.com
O365 account
Name: Jacob
Type: Person
Dept: Sales
Personal Email: jacob@yourdomain.com
O365 account
Name: Helen
Type: Person
Dept: Accounting / Marketing
Personal Email: helen@yourdomain.com
So now our structure would look like this
Project 1 | Project 2 | Project 3 |
|
Sales |
George Chris |
Jane |
Jacob |
Marketing |
John |
Jane |
Nick Helen |
Accounting |
Chris |
Jasmin |
Helen |
So to sum up
O365 is built for teams. And teams are an essential piece in the structure of an organization. So before you start building accounts, buying licenses and creating email addresses you should take a look at your company’s structure and figure out the one that suits you and your needs.