Accepting invitation as a Gmail User - Password does not work

%3CLINGO-SUB%20id%3D%22lingo-sub-116852%22%20slang%3D%22en-US%22%3ERe%3A%20Accepting%20invitation%20as%20a%20Gmail%20User%20-%20Password%20does%20not%20work%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-116852%22%20slang%3D%22en-US%22%3E%3CP%3EIn%20our%20case%2C%20previous%20external%20users%20invited%20from%20SharePoint%20show%20up%20with%20the%20%23EXT%23%20after%20their%20external%20mail%2C%20with%20the%20%22%20%40%20%22%20replaced%20with%20underline%20as%20bobafett_live.com%23EXT%23%40constoso.com.%3C%2FP%3E%3CP%3ENow%20Guest%20users%20invited%20from%20Azure%20show%20up%20as%20bobafett_live.com%40onmicrosoft.contoso.com%20.%3C%2FP%3E%3CP%3EWhich%20in%20my%20opinion%20looks%20awful%20and%20their%20is%20no%20way%20to%20change%20the%20invitations%20with%20the%20free%20(O365)%20version%20of%20Azure.%26nbsp%3B%20I%20even%20created%20a%20Support%20request%20to%20investigate.%3C%2FP%3E%3CP%3E%26nbsp%3B%20BUT%20what%20an%20Admin%20can%20do%20is%20change%20the%20username%20in%20the%20O365%20portal%20to%20use%20a%20semi-normal%20style%20of%20bobafett_live.com%40contoso.com%20but%20the%20change%20has%20to%20be%20communicated%20to%20the%20external%20party%20outside%20of%20the%20Azure%2FO365%20workflows%20because%20they%20cannot%20login%20after%20the%20change%20in%20the%20username%20until%20they%20are%20given%20the%20new%20one.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-112946%22%20slang%3D%22en-US%22%3EAccepting%20invitation%20as%20a%20Gmail%20User%20-%20Password%20does%20not%20work%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-112946%22%20slang%3D%22en-US%22%3E%3CP%3EWhen%20accepting%20an%20invite%20as%20a%20gmail%20user%20I%20get%20redirected%20to%20sign-in.%20But%20shouldnt%20I%20be%20redirected%20to%20the%20page%20where%20I%20%22Create%20Password%22%20first%3F%3C%2FP%3E%3CP%3EIt%20asks%20me%20for%20a%20password%20and%20the%20one%20attached%20to%20my%20Gmail%20obviously%20does%20not%20work.%20Can%20only%20add%20emails%20from%20microsoft-accounts%20or%20my%20organization.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20also%20wonder%20why%20Guest%20Users%20are%20stored%20as%20%22user%40live.com%22%20if%20I%20invite%20%22user%40live.com%22%2C%20should%20they%20not%20be%20stored%20as%20%22ext-user-live%40mycompany.com%22%3F%20As%20in%20the%20video%20here%3A%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Factive-directory-b2b-what-is-azure-ad-b2b%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Factive-directory-b2b-what-is-azure-ad-b2b%3C%2FA%3E.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-112946%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EB2B%20collaboration%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Occasional Visitor

When accepting an invite as a gmail user I get redirected to sign-in. But shouldnt I be redirected to the page where I "Create Password" first?

It asks me for a password and the one attached to my Gmail obviously does not work. Can only add emails from microsoft-accounts or my organization.

I also wonder why Guest Users are stored as "user@live.com" if I invite "user@live.com", should they not be stored as "ext-user-live@mycompany.com"? As in the video here: https://docs.microsoft.com/en-us/azure/active-directory/active-directory-b2b-what-is-azure-ad-b2b.

 

1 Reply

In our case, previous external users invited from SharePoint show up with the #EXT# after their external mail, with the " @ " replaced with underline as bobafett_live.com#EXT#@constoso.com.

Now Guest users invited from Azure show up as bobafett_live.com@onmicrosoft.contoso.com .

Which in my opinion looks awful and their is no way to change the invitations with the free (O365) version of Azure.  I even created a Support request to investigate.

  BUT what an Admin can do is change the username in the O365 portal to use a semi-normal style of bobafett_live.com@contoso.com but the change has to be communicated to the external party outside of the Azure/O365 workflows because they cannot login after the change in the username until they are given the new one.