Office365 Guest Access

%3CLINGO-SUB%20id%3D%22lingo-sub-742592%22%20slang%3D%22en-US%22%3EOffice365%20Guest%20Access%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-742592%22%20slang%3D%22en-US%22%3E%3CP%3EHi%3C%2FP%3E%3CP%3EWe%20have%20added%20users%20account%20from%20a%20external%20Office365%20tenant%20into%20our%20Azure%20AD%20Office365%20tenant.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20works%20fine%20and%20the%20Guest%20users%20can%20logon%20ok.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%20were%20were%20expecting%20that%20setting%20like%20ther%20external%20guest%20users%20%22Job%20title%22%2C%20%22Department%22%20etc..%20would%20be%20pulled%20accross%20from%20the%20other%20Office365%20tenant.%20However%20they%20don't%20seam%20to%20have%20been...%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F122558i7E7E1214701C2A46%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22tmp.png%22%20title%3D%22tmp.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnyone%20any%20ideas%20how%20to%20pull%20these%20details%20over%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-743624%22%20slang%3D%22en-US%22%3ERe%3A%20Office365%20Guest%20Access%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-743624%22%20slang%3D%22en-US%22%3EHi!%20This%20is%20not%20a%20feature%20as%20of%20now.%20It%20is%20however%20in%20the%20backlog%20according%20to%20%3CA%20href%3D%22https%3A%2F%2Ffeedback.azure.com%2Fforums%2F169401-azure-active-directory%2Fsuggestions%2F18836155-bring-through-external-user-profile-fields-when-us%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Ffeedback.azure.com%2Fforums%2F169401-azure-active-directory%2Fsuggestions%2F18836155-bring-through-external-user-profile-fields-when-us%3C%2FA%3Eso%20vote%20it%20into%20existence!%20%3A)%3C%2Fimg%3E%3CBR%20%2F%3E%3CBR%20%2F%3ERegards%2C%3CBR%20%2F%3E%3CBR%20%2F%3EViktor%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-757008%22%20slang%3D%22en-US%22%3ERe%3A%20Office365%20Guest%20Access%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-757008%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F272339%22%20target%3D%22_blank%22%3E%40Pn1995%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20had%20a%20client%20that%20needed%20to%20provision%20B2B%20users%20from%20a%20partner%20tenant%20that%20existed%20as%20AD%20objects%20in%20their%20local%20tenant%20-%20but%20needed%20to%20access%20resources%20and%20appear%20in%20gal%20as%20B2B%20users%20instead%20of%20local%20users%20-%20I%20populated%20these%20attributes%20via%20a%20call%20to%20the%20Graph%20API%20and%20used%20a%20patch%20call.%20This%20was%20done%20through%20a%20custom%20MIM%20connector.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-763184%22%20slang%3D%22en-US%22%3ERe%3A%20Office365%20Guest%20Access%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-763184%22%20slang%3D%22en-US%22%3EIn%20my%20opinion%2C%20I%20don't%20believe%20that%20this%20feature%20will%20ever%20be%20released.%20What%20you%20are%20asking%20is%20to%20collect%20sensitive%20information%20that's%20in%20another%20tenant.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-763187%22%20slang%3D%22en-US%22%3ERe%3A%20Office365%20Guest%20Access%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-763187%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F267638%22%20target%3D%22_blank%22%3E%40Corsino%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20true%20-%20in%20my%20situation%20there%20was%20tight%20integration%20required%20between%20the%20two%20tenants%2C%20since%20they%20were%20essentially%20part%20of%20the%20same%20org%2C%20in%20the%20process%20of%20eventual%20migration.%20I%20also%20have%20another%20client%20that%20needs%20to%20have%20ad-hoc%20B2B%20collaboration%20using%20a%20B2C%20application%2C%20in%20which%20case%20the%20B2B%20data%20utilized%20is%20that%20provided%20by%20the%20B2C%20application%20using%20self%20asserted%20info%20as%20well%20as%20data%20derived%20from%20an%20API%20internally.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Pn1995
Contributor

Hi

We have added users account from a external Office365 tenant into our Azure AD Office365 tenant.

 

The works fine and the Guest users can logon ok.

 

However were were expecting that setting like ther external guest users "Job title", "Department" etc.. would be pulled accross from the other Office365 tenant. However they don't seam to have been...

tmp.png

 

Anyone any ideas how to pull these details over?

 

Thanks

4 Replies
Hi! This is not a feature as of now. It is however in the backlog according to https://feedback.azure.com/forums/169401-azure-active-directory/suggestions/18836155-bring-through-e... so vote it into existence! :)

Regards,

Viktor

@Pn1995 

We had a client that needed to provision B2B users from a partner tenant that existed as AD objects in their local tenant - but needed to access resources and appear in gal as B2B users instead of local users - I populated these attributes via a call to the Graph API and used a patch call. This was done through a custom MIM connector.  

In my opinion, I don't believe that this feature will ever be released. What you are asking is to collect sensitive information that's in another tenant.

@Corsino 

This is true - in my situation there was tight integration required between the two tenants, since they were essentially part of the same org, in the process of eventual migration. I also have another client that needs to have ad-hoc B2B collaboration using a B2C application, in which case the B2B data utilized is that provided by the B2C application using self asserted info as well as data derived from an API internally.