Let's talk about users versus contacts.
A user is someone that can log on to Office 365, your log on name to 365 is actually your e-mail address.
So even if you have a 365 subscription that doesn't include e-mail services, you still are creating
a log in added domain name that will be there, log into everything.
And again, it's usually their e-mail address.
So a user can log into 365.
They have an email address depending on the license.
You have them.
They can install Microsoft Office again, depending on the license that you give them.
And you can also use the online apps once again, license dependent.
A contact is very similar really just to an address book.
But it's global.
So if we know that, let's say we have outsourced I.T. in our organization.
But I want people to be able to e-mail supported Xandra network dot com and have everyone have that
address.
I'm actually can create a contact card globally so that users will have that preloaded in their address
book.
So if they're reaching out for help, they all have it.
Now, that doesn't mean there's support.
E-mail has a license in 365.
It just basically means it's a contact record and it'll help the users forward email accordingly.
So user think about it this way, something you pay for contacts or something external to the organization
that you're just preloading for the global address book.