Force Send External Invite Email

%3CLINGO-SUB%20id%3D%22lingo-sub-1200833%22%20slang%3D%22en-US%22%3EForce%20Send%20External%20Invite%20Email%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1200833%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20several%20accounts%20in%20AD%20that%20are%20assigned%20to%20outside%20contractors%2C%20all%20of%20which%20have%20an%20assigned%20email%20address%20in%20the%20Email%20field%20(for%20example%2C%20let's%20say%20one%20of%20the%20problematic%20individuals%20is%20%3CA%20href%3D%22mailto%3Auser%40domain.xyz)%3A%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Euser%40domain.xyz)%3A%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CPRE%3EEmailAddress%20%3A%20user%40domain.xyz%3CBR%20%2F%3EEnabled%20%3A%20True%3CBR%20%2F%3EUserPrincipalName%20%3A%20user%40anotherdomain.xyz%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20causes%20an%20issue%20in%20SharePoint%20Online%20when%20we%20try%20to%20send%20an%20external%20site%20invite%20to%20the%20%3CA%20href%3D%22mailto%3Auser%40domain.xyz%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Euser%40domain.xyz%20%3C%2FA%3Eemail%20address%2C%20as%20the%20people%20picker-like%20control%20resolves%20the%20email%20address%20to%20the%20%22internal%22%20account%2C%20no%20matter%20what%3A%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22jnlce_0-1582903384642.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F174062i8F0E0242DEFAB129%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20title%3D%22jnlce_0-1582903384642.png%22%20alt%3D%22jnlce_0-1582903384642.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20question%3A%20Is%20there%20anyway%20to%20force%20an%20external%20invite%20email%20to%20go%20to%20the%20email%20address%2C%20instead%20of%20it%20resolving%20to%20the%20%22internal%22%20account%3F%26nbsp%3B%20We%20can't%20change%20the%20current%20setup%20in%20AD%20as%20other%20applications%2C%20unfortunately%2C%20rely%20on%20it.%3CBR%20%2F%3E%3CBR%20%2F%3ESteps%20I%20have%20tried%3A%3C%2FP%3E%3CUL%3E%3CLI%3EPOST'ing%20ShareObject%20via%20%2F_api%2FSP.Web.ShareObject%20(sends%20to%20%22internal%22%20account)%3C%2FLI%3E%3CLI%3EPOST'ing%20a%20ShareObject%20via%20%2F_vti_bin%2Fclient.svc%2FProcessQuery%20(sends%20to%20%22internal%22%20account)%3C%2FLI%3E%3C%2FUL%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1200833%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1206775%22%20slang%3D%22en-US%22%3ERe%3A%20Force%20Send%20External%20Invite%20Email%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1206775%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F570638%22%20target%3D%22_blank%22%3E%40jnlce%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHave%20you%20tried%20adding%20them%20as%20a%20%22New%20Guest%20User%22%20in%20azure%20AD%3F%20Call%20the%20account%20something%20like%20External%20Joe%20Bloggs%20so%20you%20can%20resolve%20them%20correctly%20in%20SharePoint.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Visitor

We have several accounts in AD that are assigned to outside contractors, all of which have an assigned email address in the Email field (for example, let's say one of the problematic individuals is user@domain.xyz):

EmailAddress : user@domain.xyz
Enabled : True
UserPrincipalName : user@anotherdomain.xyz

 

This causes an issue in SharePoint Online when we try to send an external site invite to the user@domain.xyz email address, as the people picker-like control resolves the email address to the "internal" account, no matter what:

jnlce_0-1582903384642.png

 

My question: Is there anyway to force an external invite email to go to the email address, instead of it resolving to the "internal" account?  We can't change the current setup in AD as other applications, unfortunately, rely on it.

Steps I have tried:

  • POST'ing ShareObject via /_api/SP.Web.ShareObject (sends to "internal" account)
  • POST'ing a ShareObject via /_vti_bin/client.svc/ProcessQuery (sends to "internal" account)
1 Reply
Highlighted

@jnlce 

 

Have you tried adding them as a "New Guest User" in azure AD? Call the account something like External Joe Bloggs so you can resolve them correctly in SharePoint.