Outlook add-in pointing to another tenant

%3CLINGO-SUB%20id%3D%22lingo-sub-1403881%22%20slang%3D%22en-US%22%3EOutlook%20add-in%20pointing%20to%20another%20tenant%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1403881%22%20slang%3D%22en-US%22%3EHi%20guys%2C%3CBR%20%2F%3EWe%E2%80%99ve%20recently%20moved%20from%20a%20proof%20of%20concept%20tenant%20to%20a%20new%20tenant%20that%20has%20launched%20across%20the%20business.%20I%E2%80%99ve%20got%20a%20couple%20of%20cases%20where%20users%20are%20logged%20into%20Teams%20in%20the%20new%20tenant%2C%20yet%20when%20they%20create%20a%20Teams%20meeting%20via%20the%20Outlook%20add-in%2C%20it%20still%20seems%20to%20create%20it%20to%20the%20old%20tenant%2C%20which%20is%20signed%20out%20of%20and%20no%20longer%20in%20use.%20It%E2%80%99s%20easy%20to%20tell%20based%20on%20whether%20you%E2%80%99re%20stuck%20in%20the%20lobby%20or%20admitted%20straight%20away%2C%20and%20also%20the%20rights%20you%20get%20when%20clicking%20on%20Meeting%20Options.%3CBR%20%2F%3E%3CBR%20%2F%3EAny%20suggestions%3F%20It%20becomes%20a%20little%20embarrassing%20when%20you%E2%80%99re%20an%20organiser%20and%20you%E2%80%99re%20stuck%20in%20the%20lobby!%20I%20just%20can%E2%80%99t%20understand%20how%20it%E2%80%99s%20still%20utilising%20the%20old%20tenant.%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1403881%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMeetings%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ETips%20%26amp%3B%20Tricks%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1408647%22%20slang%3D%22en-US%22%3ERe%3A%20Outlook%20add-in%20pointing%20to%20another%20tenant%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1408647%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20managed%20to%20find%20a%20resolution%20to%20this.%20The%20user%20needs%20to%20close%20Outlook%20(File%20%26gt%3B%20Exit)%20and%20then%20sign%20out%20of%20Teams%20and%20close%20the%20client.%20They%20then%20need%20to%20restart%20Teams%2C%20sign%20in%20and%20once%20signed%20in%2C%20re-open%20the%20Outlook%20client.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20it's%20done%20in%20that%20order%2C%20it%20seems%20to%20connect%20the%20Teams%20Outlook%20add-in%20to%20the%20account%20signed%20into%20the%20Teams%20client%20with%20and%20resolved%20the%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor
Hi guys,
We’ve recently moved from a proof of concept tenant to a new tenant that has launched across the business. I’ve got a couple of cases where users are logged into Teams in the new tenant, yet when they create a Teams meeting via the Outlook add-in, it still seems to create it to the old tenant, which is signed out of and no longer in use. It’s easy to tell based on whether you’re stuck in the lobby or admitted straight away, and also the rights you get when clicking on Meeting Options.

Any suggestions? It becomes a little embarrassing when you’re an organiser and you’re stuck in the lobby! I just can’t understand how it’s still utilising the old tenant.
1 Reply
Highlighted

Hi all,

 

I've managed to find a resolution to this. The user needs to close Outlook (File > Exit) and then sign out of Teams and close the client. They then need to restart Teams, sign in and once signed in, re-open the Outlook client. 

 

If it's done in that order, it seems to connect the Teams Outlook add-in to the account signed into the Teams client with and resolved the issue.