Mar 23 2018
- last edited on
Jan 14 2022
Hi We are looking at a scenario where we want to create an additional Office 365 tenancy for staff and customers to collaborate in primarily using SharePoint . The users of this tenancy will already exist in separate azure ad directories. So we will have to add all users as Azure B2b guests in the new tenancy.
Can somebody give me an overview of the limitations of what Azure B2b guests can and cant do and what the roadmap is?
Mar 23 2018 06:35 AM
If you already have an Office tenant, why do you want another one? they will be totally disconnected and you will have to do duplicate admin tasks. It would be much easier to just enable external sharing on dedicated sharepoint sites in your existing Office 365 tenant.
You state that users of the new tenancy already exist in separate Azure AD directories. How can you know that for all of your customers? are these directories that you manage or that your customers manage?
B2B is good if you know who you are going to work with and want to preload a bunch of accounts.
In general B2B Guests can do whatever they are authorized to do by the person who invites them,with some restrictions of course. In SharePoint, they can be granted edit or read permissions
Mar 23 2018 07:24 AM
Hi dean in office 365 sharepoint there are scenarios where you do not want people to be able to see other people - for example the people picker.
In sharepoint online the people picker shows everyone in the azure ad that is mapped to it. There is no way to lock it down to say organisational units like in sp on premise.
This is one of the drivers for looking at another tenancy.
I hope I have explained the issue.
Mar 23 2018 07:27 AM