%3CLINGO-SUB%20id%3D%22lingo-sub-1751711%22%20slang%3D%22en-US%22%3ECollaborate%20with%20anyone%20in%20any%20organization%20with%20any%20email%20address!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1751711%22%20slang%3D%22en-US%22%3E%3CP%3EHowdy%20folks%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%E2%80%99ve%20heard%20from%20you%20that%20interconnected%20supply%20and%20distribution%20chains%2C%20and%20vendor%20models%20are%20bringing%20B2B%20partners%20directly%20into%20your%20business%2C%20where%20secure%20and%20seamless%20collaboration%20is%20more%20important%20than%20ever.%20We%20also%20know%20how%20painful%20it%20can%20be%20for%20IT%20managers%20to%20keep%20track%20of%20guest%20user%20accounts%2C%20and%20for%20end%20users%20to%20remember%20multiple%20usernames%20and%20passwords.%20We%20are%20continually%20improving%20our%20Azure%20AD%20External%20Identities%20solution%20with%20more%20support%20for%20bring-your-own-identity%20(BYOI)%20options.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EToday%2C%20we%20are%20announcing%20another%20enhancement%20to%20our%20BYOI%20story%20with%20the%20general%20availability%20of%20email-based%20one-time%20passcode%20(email%20OTP)%20feature%20for%20collaboration.%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWith%20email%20OTP%2C%20org%20members%20can%20collaborate%20with%20anyone%20in%20the%20world%20by%20simply%20sharing%20a%20link%20or%20sending%20an%20invitation%20via%20email.%20Invited%20users%20prove%20their%20identity%20by%20using%20a%20verification%20code%20sent%20to%20their%20email%20account.%20Once%20authenticated%2C%20each%20session%20providing%20access%20to%20the%20shared%20resource%20lasts%2024%20hours.%20On%20subsequent%20sign%20ins%2C%20users%20receive%20a%20new%20one-time%20code%20via%20email%2C%20which%20they%20must%20enter%20to%20prove%20continued%20ownership%20of%20the%20email%20account%20and%20continue%20receiving%20access.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Email%20OTP%20end-user.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F236947iD84BEAE0E08CC9FC%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22Email%20OTP%20end-user.png%22%20alt%3D%22Nicole%2C%20a%20marketing%20consultant%20to%20Woodgrove%20Bank%2C%20accesses%20Woodgrove%20resources%20by%20verifying%20her%20email%20address.%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3ENicole%2C%20a%20marketing%20consultant%20to%20Woodgrove%20Bank%2C%20accesses%20Woodgrove%20resources%20by%20verifying%20her%20email%20address.%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAzure%20AD%20treats%20email%20OTP-based%20users%20like%20other%20B2B%20guests%2C%20making%20them%20subject%20to%20security%20policies%20set%20by%20your%20organization%20such%20as%20Conditional%20Access%2C%20Multi-Factor%20Authentication%20(MFA)%20and%20periodic%20access%20reviews.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CDIV%3EEmail%20OTP%20is%20also%20being%20rolled%20out%20%3CSPAN%3Eworldwide%20in%20Microsoft%20Teams%20preview%20mode.%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ETo%20get%20started%20with%20email%20OTP%2C%20check%20out%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Factive-directory%2Fexternal-identities%2Fone-time-passcode%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ethe%20documentation%20here%3C%2FA%3E.%20As%20always%2C%20we%20invite%20you%20to%20share%20any%20questions%20or%20feedback%20about%20the%20feature%20through%26nbsp%3Bthe%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ffeedback.azure.com%2Fforums%2F169401-azure-active-directory%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3EAzure%20forum%3C%2FA%3E%26nbsp%3Bor%20%3CA%20href%3D%22https%3A%2F%2Ftwitter.com%2Fazuread%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3E%40AzureAD%3C%2FA%3E%26nbsp%3Bon%20Twitter.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAlex%20Simons%20(%3CA%20href%3D%22http%3A%2F%2Ftwitter.com%2Falex_a_simons%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3E%40Alex_A_Simons%3C%2FA%3E)%3C%2FP%3E%0A%3CP%3ECorporate%20Vice%20President%20of%20Program%20Management%3C%2FP%3E%0A%3CP%3EMicrosoft%20Identity%20Division%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CEM%3ELearn%20more%20about%20Microsoft%20identity%3A%3C%2FEM%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CEM%3ERelated%20Articles%3A%20%3C%2FEM%3E%3CSPAN%3EPublic%20preview%20announcement%20of%20email%20one-time%20passcode%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EReturn%20to%20the%20%3C%2FEM%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fazure-active-directory-identity%2Fbg-p%2FIdentity%22%20target%3D%22_blank%22%3E%3CEM%3EAzure%20Active%20Directory%20Identity%20blog%20home%3C%2FEM%3E%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3E%3CEM%3EJoin%20the%20conversation%20on%20%3C%2FEM%3E%3CA%20href%3D%22https%3A%2F%2Ftwitter.com%2Fazuread%2Fstatus%2F1278418103903363074%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3E%3CEM%3ETwitter%3C%2FEM%3E%3C%2FA%3E%3CEM%3E%20and%20%3C%2FEM%3E%3CEM%3E%3CA%20href%3D%22https%3A%2F%2Fwww.linkedin.com%2Fshowcase%2Fmicrosoft-security%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3ELinkedIn%3C%2FA%3E%3C%2FEM%3E%3C%2FLI%3E%0A%3CLI%3E%3CEM%20style%3D%22font-family%3A%20inherit%3B%22%3EShare%20product%20suggestions%20on%20the%20%3C%2FEM%3E%3CA%20style%3D%22font-family%3A%20inherit%3B%20background-color%3A%20%23ffffff%3B%22%20href%3D%22https%3A%2F%2Ffeedback.azure.com%2Fforums%2F169401-azure-active-directory%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3E%3CEM%3EAzure%20Feedback%20Forum%3C%2FEM%3E%3C%2FA%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1751711%22%20slang%3D%22en-US%22%3E%3CP%3EB2B%20collaboration%20via%20email%20based%20one-time%20passcode%20is%20now%20generally%20available.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1751711%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EProduct%20Announcements%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2034256%22%20slang%3D%22en-US%22%3ERe%3A%20Collaborate%20with%20anyone%20in%20any%20organization%20with%20any%20email%20address!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2034256%22%20slang%3D%22en-US%22%3E%3CP%3EHow%20does%20this%20apply%20to%20Teams%2C%20SharePoint%2C%20and%20OneDrive%3F%20If%20I%20invite%20someone%20to%20a%20Team%2C%20or%20share%20a%20single%20file%20or%20folder%20in%20SharePoint%20with%20someone%2C%20how%20do%20they%20get%20back%20to%20that%20Team%20or%20item%20that%20was%20shared%20with%20them%3F%20Do%20they%20have%20to%20keep%20the%20email%20invitation%20forever%20and%20always%20start%20at%20that%20email%20to%20get%20back%20to%20the%20content%20that%20was%20shared%20with%20them%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2036561%22%20slang%3D%22en-US%22%3ERe%3A%20Collaborate%20with%20anyone%20in%20any%20organization%20with%20any%20email%20address!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2036561%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20this%20still%20restricted%2Fconstrained%20by%20the%20AzureAD%20External%20Collaboration%20settings%2C%20so%20if%20one%20is%20using%20the%20Allowed%20Domains%20list%2C%20invites%20can%20still%20only%20be%20sent%20to%20those%20domains%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20does%20the%20error%20look%20like%20if%20you%20attempt%20to%20send%20an%20invite%20to%20a%20domain%20not%20on%20the%20Allowed%20Domains%20list%2C%20or%20if%20you%20do%20not%20have%20Invite%20permissions%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2037599%22%20slang%3D%22en-US%22%3ERe%3A%20Collaborate%20with%20anyone%20in%20any%20organization%20with%20any%20email%20address!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2037599%22%20slang%3D%22en-US%22%3E%3CP%3EHow%20does%20this%20apply%20to%20Azure%20Government%20or%20GCC-High%20tenants%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2053819%22%20slang%3D%22en-US%22%3ERe%3A%20Collaborate%20with%20anyone%20in%20any%20organization%20with%20any%20email%20address!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2053819%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F62361%22%20target%3D%22_blank%22%3E%40Kevin%20McKeown%3C%2FA%3E%2C%26nbsp%3Bno%2C%20the%20invited%20user%20does%20not%20need%20to%20hold%20onto%20the%20email.%20They%20can%20request%20for%20a%20new%20code.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2053823%22%20slang%3D%22en-US%22%3ERe%3A%20Collaborate%20with%20anyone%20in%20any%20organization%20with%20any%20email%20address!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2053823%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F548028%22%20target%3D%22_blank%22%3E%40KeithBachmanTP%3C%2FA%3E%2C%26nbsp%3Byes%2C%20if%20you%20have%20Allowed%20Domains%20list%20configured%20in%20Azure%20AD%20External%20Collaboration%20settings%2C%20invitations%20can%20only%20be%20sent%20to%20and%20redeemed%20by%20those%20that%20are%20on%20the%20allowed%20list.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20the%20invitation%20is%20sent%20to%20a%20domain%20that%20is%20not%20allowed%2C%20then%20the%20error%20today%20will%20say%20%22You%20can't%20get%20there%20from%20here.%22%20We%20are%20working%20on%20improving%20the%20error%20message.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2056653%22%20slang%3D%22en-US%22%3ERe%3A%20Collaborate%20with%20anyone%20in%20any%20organization%20with%20any%20email%20address!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2056653%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F491078%22%20target%3D%22_blank%22%3E%40lipar7%3C%2FA%3E%26nbsp%3BYou%20are%20misunderstanding%20my%20question.%20I%20am%20not%20asking%20about%20the%20OTP%20code%20email.%20I%20am%20asking%20how%20external%20users%20get%20back%20to%20various%20content%20that%20was%20shared%20with%20them.%20Do%20they%20bookmark%20the%20URL%20once%20they%20have%20accessed%20the%20shared%20content%20the%20first%20time%3F%20Do%20they%20hold%20on%20to%20the%20initial%20invitation%20email%20that%20they%20received%2C%20which%20includes%20a%20link%20to%20the%20shared%20content%3F%20(This%20is%20what%20most%20people%20do.)%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20a%20better%20way%20for%20external%20users%20to%20get%20back%20to%20content%20that%20was%20shared%20with%20them%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2058716%22%20slang%3D%22en-US%22%3ERe%3A%20Collaborate%20with%20anyone%20in%20any%20organization%20with%20any%20email%20address!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2058716%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F772357%22%20target%3D%22_blank%22%3E%40gibsonProperties%3C%2FA%3E%2C%20Email%20OTP%20is%20not%20available%20in%20those%20clouds%20yet%2C%20but%20we%20are%20currently%20working%20on%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2058815%22%20slang%3D%22en-US%22%3ERe%3A%20Collaborate%20with%20anyone%20in%20any%20organization%20with%20any%20email%20address!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2058815%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F62361%22%20target%3D%22_blank%22%3E%40Kevin%20McKeown%3C%2FA%3E%26nbsp%3BThat%20is%20correct.%20The%20link%20in%20the%20email%20points%20to%20the%20organization%20in%20which%20the%20invited%20user%20is%20trying%20to%20sign%20in%20and%20access%20content%2C%20so%20the%20best%20way%20to%20revisit%20this%20later%20is%20to%20save%20or%20bookmark%20the%20link%20that%20was%20in%20the%20email.%20I%20am%20not%20aware%20of%20any%20other%20better%20way%20to%20get%20back%20to%20content.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2064748%22%20slang%3D%22en-US%22%3ERe%3A%20Collaborate%20with%20anyone%20in%20any%20organization%20with%20any%20email%20address!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2064748%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F491078%22%20target%3D%22_blank%22%3E%40lipar7%3C%2FA%3E%26nbsp%3BWill%20external%20sharing%20in%20Azure%20Government%20be%20the%20same%20as%20commercial%20Azure%3F%26nbsp%3B%20When%20is%20the%20estimated%20beta%20as%20I%20have%20not%20been%20able%20to%20find%20anything%20on%20blogs%20or%20roadmaps%20etc%3F%20Is%20there%20a%20specific%20team%20blog%20I%20should%20follow%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%3C%2FP%3E%3C%2FLINGO-BODY%3E

Howdy folks,

 

We’ve heard from you that interconnected supply and distribution chains, and vendor models are bringing B2B partners directly into your business, where secure and seamless collaboration is more important than ever. We also know how painful it can be for IT managers to keep track of guest user accounts, and for end users to remember multiple usernames and passwords. We are continually improving our Azure AD External Identities solution with more support for bring-your-own-identity (BYOI) options.

 

Today, we are announcing another enhancement to our BYOI story with the general availability of email-based one-time passcode (email OTP) feature for collaboration.

 

With email OTP, org members can collaborate with anyone in the world by simply sharing a link or sending an invitation via email. Invited users prove their identity by using a verification code sent to their email account. Once authenticated, each session providing access to the shared resource lasts 24 hours. On subsequent sign ins, users receive a new one-time code via email, which they must enter to prove continued ownership of the email account and continue receiving access.

 

Nicole, a marketing consultant to Woodgrove Bank, accesses Woodgrove resources by verifying her email address.Nicole, a marketing consultant to Woodgrove Bank, accesses Woodgrove resources by verifying her email address.

 

Azure AD treats email OTP-based users like other B2B guests, making them subject to security policies set by your organization such as Conditional Access, Multi-Factor Authentication (MFA) and periodic access reviews.

 

Email OTP is also being rolled out worldwide in Microsoft Teams preview mode.

 

To get started with email OTP, check out the documentation here. As always, we invite you to share any questions or feedback about the feature through the Azure forum or @AzureAD on Twitter.

 

Alex Simons (@Alex_A_Simons)

Corporate Vice President of Program Management

Microsoft Identity Division

 

 

Learn more about Microsoft identity:

 

9 Comments
Contributor

How does this apply to Teams, SharePoint, and OneDrive? If I invite someone to a Team, or share a single file or folder in SharePoint with someone, how do they get back to that Team or item that was shared with them? Do they have to keep the email invitation forever and always start at that email to get back to the content that was shared with them?

Senior Member

Is this still restricted/constrained by the AzureAD External Collaboration settings, so if one is using the Allowed Domains list, invites can still only be sent to those domains?

 

What does the error look like if you attempt to send an invite to a domain not on the Allowed Domains list, or if you do not have Invite permissions?

New Contributor

How does this apply to Azure Government or GCC-High tenants?

Microsoft

Hi @Kevin McKeown, no, the invited user does not need to hold onto the email. They can request for a new code.

Microsoft

Hi @KeithBachmanTP, yes, if you have Allowed Domains list configured in Azure AD External Collaboration settings, invitations can only be sent to and redeemed by those that are on the allowed list. 

 

If the invitation is sent to a domain that is not allowed, then the error today will say "You can't get there from here." We are working on improving the error message.

Contributor

@lipar7 You are misunderstanding my question. I am not asking about the OTP code email. I am asking how external users get back to various content that was shared with them. Do they bookmark the URL once they have accessed the shared content the first time? Do they hold on to the initial invitation email that they received, which includes a link to the shared content? (This is what most people do.) 

Is there a better way for external users to get back to content that was shared with them?

Microsoft

Hi @gibsonProperties, Email OTP is not available in those clouds yet, but we are currently working on it.

Microsoft

@Kevin McKeown That is correct. The link in the email points to the organization in which the invited user is trying to sign in and access content, so the best way to revisit this later is to save or bookmark the link that was in the email. I am not aware of any other better way to get back to content.

New Contributor

@lipar7 Will external sharing in Azure Government be the same as commercial Azure?  When is the estimated beta as I have not been able to find anything on blogs or roadmaps etc? Is there a specific team blog I should follow?

 

Regards