- last edited on
Will the implementation of tenant restrictions via proxy header injection prevent users in our directory who were invited as B2B guest users to another tenant from accessing that partner tenant from our network where tenant restrictions are in place? I posed this question at a MS tech summit and was told no - the answer given was that as the authentication takes place in in the invitee's (our) tenant (as the identity directory). But isn't the access security token given by the resource tenant with their tenant ID? My own testing with Fiddler has confirmed that indeed I cannot access a resource tenant as a guest user that isn't included in 'Restrict-Access-To-Tenants' in our proxy header.
This would mean updating on the proxy a list of organizations that we could partner with as invitees, which makes the feature not as practical or useful as we originally thought.
Is there any thought of whitelisting companies for outgoing and incoming B2B relationships that can be maintained at the tenant level?
07-06-2017 09:29 AM
We have a allow / deny list coming up for managing outgoing relationships, but what is your scenario for restricting incoming relationships?
07-06-2017 09:55 AM - edited 07-06-2017 09:59 AM
With tenant restrictions in place via our proxy (allowing only our tenant/domain), is there a way that the access token can be granted to our users as guests of allowed partners we identify within our tenant? Tenant restrictions is great for preventing users to access tenants where they may have accounts, but how can we make this work for user accounts which exist in our own directory when invited as guest?
And either way, it would be useful to have a whitelist of organizations that our users are allowed to be invited as guests to. Or auditing of such?