Multi-tenant Login

%3CLINGO-SUB%20id%3D%22lingo-sub-1432390%22%20slang%3D%22en-US%22%3EMulti-tenant%20Login%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1432390%22%20slang%3D%22en-US%22%3E%3CP%3ELooking%26nbsp%3Bforward%20to%20hearing%20from%20the%20folks%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F614645%22%20target%3D%22_blank%22%3E%40MicrosoftTeamsTeam%3C%2FA%3E!%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20would%20really%20like%20to%20know%20where%20we%20are%20on%20%3CSTRONG%3EMulti-tenant%20Login%3C%2FSTRONG%3E%3B%26nbsp%3B%20we%20have%20many%20customers%2C%20they%20all%20have%20their%20own%20tenants%2C%20we%20get%20added%20to%20all%20of%20them.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3ESMS%3C%2FSTRONG%3E%3B%20Will%20I%20be%20able%20to%20use%20it%20with%20Direct%20Routing%20numbers%3F%20Eg.%20All%20of%20the%20customers%20we%20deploy%20with%20Direct%20Routing%20all%20have%20SMS%20enabled%20numbers.%20It%20would%20be%20nice%20if%20we%20could%20forward%20messages%20from%20our%20platform%20to%20Teams%20Users%20and%20also%20allow%20them%20to%20respond.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20know%20these%20are%20both%20on%20Uservoice%2C%20just%20would%20be%20nice%20to%20hear%20an%20update%20on%20these%20features.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1432390%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1468258%22%20slang%3D%22en-US%22%3ERe%3A%20Multi-tenant%20Login%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1468258%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20there%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F685976%22%20target%3D%22_blank%22%3E%40elagerway%3C%2FA%3E%26nbsp%3B-%20MTMA%20(Multi%20Tenant%2C%20Multi%20Account)%20scenarios%20are%20definitely%20being%20worked%20on.%20A%20few%20things%20are%20being%20worked%20on%20specifically%20in%20the%20MT%20space%2C%20which%20mobile%20has%20a%20variance%20of%20this%20today.%20We'll%20see%20some%20future%20work%20on%20this%20area%20on%20desktop%2Fweb%20coming%20in%20the%20next%20few%20months!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAs%20for%20the%20latter%20question%20-%20can%20you%20describe%20this%20a%20bit%20further%3F%20When%20you%20state%20SMS%2C%20do%20you%20mean%20specifically%20around%20the%20CID%20functionality%20for%20DR%3F%20Anything%20additional%20will%20help!%20Thx!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESam%2C%20Teams%20Engineering%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1468419%22%20slang%3D%22en-US%22%3ERe%3A%20Multi-tenant%20Login%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1468419%22%20slang%3D%22en-US%22%3EThanks%20for%20the%20update%20on%20MTMA%2C%20good%20to%20hear%20the%20desktop%20isn't%20getting%20left%20behind.%3CBR%20%2F%3E%3CBR%20%2F%3ERe%20SMS%2C%20we%20want%20to%20be%20able%20to%20use%20the%20SMS%20functionality%20provided%20by%20other%20CPaaS%20providers%20and%20flow%20those%20SMS%20messages%20to%20the%20intended%20recipient%20in%20Teams.%20Eg.%20We%20associate%20an%20on-prem%20number%20(Direct%20Routing)%20with%20a%20user%20in%20Teams%2C%20so%20they%20can%20make%2Freceive%20calls.%20We%20should%20also%20be%20able%20to%20point%20the%20Webhook%20from%20the%20provider%20to%20a%20URI%20in%20365%2FTeams%20and%20have%20the%20messages%20show%20up%20in%20the%20user's%20personal%20chat%20UI.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1486987%22%20slang%3D%22en-US%22%3ERe%3A%20Multi-tenant%20Login%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1486987%22%20slang%3D%22en-US%22%3E%3CP%3EAs%20you%20correctly%20mentioned%2C%20You%20have%20to%20identify%20the%20Client%2FTenant%20ID%20while%20you%20allow%20the%20user%20to%20login%20to%20the%20multi-tenant%20application.%20There%20are%20basically%203%20ways%20to%20identify%20the%20Tenant%20ID.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3EUse%20the%20company%20code%20text%20field%20where%20your%20users%20can%20enter%20their%20tenant%20id%2C%20password%2Fusername%20to%20authenticate%20(Error-prone%2C%20users%20may%20not%20enter%20the%20id%20correctly).%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3Ecollect%20the%20username%20and%20password%20and%20identify%20the%20Tenant%20ID%20by%20yourself%2C%20but%20you%20have%20to%20enforce%20Unique%20identity%20(email)%20for%20all%20the%20users%20in%20the%20system.%20(Preferred)%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3EAssign%20a%20unique%20Sub-domain%20for%20each%20tenant%20(Preferred).%20Using%20a%20unique%20URL%20of%20the%20customers%2C%20you%20can%20identify%20the%20tenant%20id%20and%20you%20can%20connect%20to%20appropriate%20DBs%20of%20the%20customer.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3EWRT%20to%20Authentication%2C%20I%20personally%20don't%20recommend%20Basic%20Authentication%20because%20of%20the%20security%20vulnerability%2C%20So%20you%20could%20either%20go%20with%20Digest%20Authentication%2F%20Client%20Certificate%20Authentication.%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Looking forward to hearing from the folks @Microsoft_Teams_team

 

We would really like to know where we are on Multi-tenant Login;  we have many customers, they all have their own tenants, we get added to all of them.

 

SMS; Will I be able to use it with Direct Routing numbers? Eg. All of the customers we deploy with Direct Routing all have SMS enabled numbers. It would be nice if we could forward messages from our platform to Teams Users and also allow them to respond.

 

I know these are both on Uservoice, just would be nice to hear an update on these features.

3 Replies

Hi there @elagerway - MTMA (Multi Tenant, Multi Account) scenarios are definitely being worked on. A few things are being worked on specifically in the MT space, which mobile has a variance of this today. We'll see some future work on this area on desktop/web coming in the next few months!

 

As for the latter question - can you describe this a bit further? When you state SMS, do you mean specifically around the CID functionality for DR? Anything additional will help! Thx!

 

Sam, Teams Engineering

Thanks for the update on MTMA, good to hear the desktop isn't getting left behind.

Re SMS, we want to be able to use the SMS functionality provided by other CPaaS providers and flow those SMS messages to the intended recipient in Teams. Eg. We associate an on-prem number (Direct Routing) with a user in Teams, so they can make/receive calls. We should also be able to point the Webhook from the provider to a URI in 365/Teams and have the messages show up in the user's personal chat UI.

As you correctly mentioned, You have to identify the Client/Tenant ID while you allow the user to login to the multi-tenant application. There are basically 3 ways to identify the Tenant ID.

Use the company code text field where your users can enter their tenant id, password/username to authenticate (Error-prone, users may not enter the id correctly).

collect the username and password and identify the Tenant ID by yourself, but you have to enforce Unique identity (email) for all the users in the system. (Preferred)

Assign a unique Sub-domain for each tenant (Preferred). Using a unique URL of the customers, you can identify the tenant id and you can connect to appropriate DBs of the customer.

WRT to Authentication, I personally don't recommend Basic Authentication because of the security vulnerability, So you could either go with Digest Authentication/ Client Certificate Authentication.