Prevent B2B invites for 'personal' accounts

%3CLINGO-SUB%20id%3D%22lingo-sub-2734882%22%20slang%3D%22en-US%22%3EPrevent%20B2B%20invites%20for%20'personal'%20accounts%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2734882%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3CBR%20%2F%3E%26nbsp%3B%20%26nbsp%3B%20We%20are%20looking%20to%20enable%20B2B%20in%20our%20tenant.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEssentially%20-%20we%20only%20want%20to%20be%20able%20to%20invite%20B2B%20identities%20if%20they%20are%20'Work%20or%20School%20Accounts'%20%26amp%3B%20create%20them%20as%20cloud%20IDs%20(and%20manage%20the%20identity%20lifecycle)%20if%20they%20are%20not.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20read%20(all%3F)%20the%20documentation%20and%20I%20am%20unable%20to%20see%20how%20we%20are%20able%20to%20accomplish%20this.%3CBR%20%2F%3E%26nbsp%3B-%20The%20best%20solution%20that%20I%20could%20find%20would%20involve%20whitelisting%2Fblacklisting%20specific%20fqdns%3F%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fexternal-identities%2Fallow-deny-list%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fexternal-identities%2Fallow-deny-list%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20it%20as%20simple%20as%20removing%20'Microsoft%20Account'%20from%20the%20configured%20identity%20providers%3F%3CBR%20%2F%3E%26nbsp%3B-%20Is%20this%20possible%20(seems%20not%20to%20be%3F)%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fexternal-identities%2Fmicrosoft-account%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fexternal-identities%2Fmicrosoft-account%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThoughts%2Fexperiences%20most%20appreciated.%3CBR%20%2F%3E%26nbsp%3B-%20If%20this%20is%20not%20an%20out%20of%20the%20box%20feature%20-%20is%20there%20an%20API%20that%20we%20can%20query%20to%20validate%20the%20account%20type%3F%20(we%20are%20looking%20to%20build%20an%20automation%20process%20for%20this%20so%20an%20API%20call%20would%20work%20well)%3C%2FP%3E%3CP%3ECheers%2C%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2734882%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EIdentity%20and%20Access%20Management%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2759339%22%20slang%3D%22en-US%22%3ERe%3A%20Prevent%20B2B%20invites%20for%20'personal'%20accounts%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2759339%22%20slang%3D%22en-US%22%3E*bump*%20-%20Anyone%20at%20Microsoft%20that%20could%20please%20comment%20here%3F%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F79817%22%20target%3D%22_blank%22%3E%40microsoft%3C%2FA%3E%20%40micrsoftbot%3CBR%20%2F%3ECheers%2C%3C%2FLINGO-BODY%3E
New Contributor

Hi,
    We are looking to enable B2B in our tenant.

 

Essentially - we only want to be able to invite B2B identities if they are 'Work or School Accounts' & create them as cloud IDs (and manage the identity lifecycle) if they are not.

 

I've read (all?) the documentation and I am unable to see how we are able to accomplish this.
 - The best solution that I could find would involve whitelisting/blacklisting specific fqdns?
https://docs.microsoft.com/en-us/azure/active-directory/external-identities/allow-deny-list 

 

Is it as simple as removing 'Microsoft Account' from the configured identity providers?
 - Is this possible (seems not to be?) https://docs.microsoft.com/en-us/azure/active-directory/external-identities/microsoft-account 

 

Thoughts/experiences most appreciated.
 - If this is not an out of the box feature - is there an API that we can query to validate the account type? (we are looking to build an automation process for this so an API call would work well)

Cheers,

1 Reply
*bump* - Anyone at Microsoft that could please comment here? @microsoft @micrsoftbot
Cheers,