2 365 accounts sharing calendar issue

%3CLINGO-SUB%20id%3D%22lingo-sub-2818239%22%20slang%3D%22en-US%22%3E2%20365%20accounts%20sharing%20calendar%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2818239%22%20slang%3D%22en-US%22%3E%3CP%3EOur%20tenant%20has%202%20domains%20that%20we%20use.%26nbsp%3B%20Call%20them%20domain1%20and%20domain2.%26nbsp%3B%20Everybody%20has%20an%20account%20in%20domain1.%26nbsp%3B%20A%20subset%20of%20these%20same%20people%20have%20an%20account%20in%20domain2.%26nbsp%3B%20I%20have%20a%20user%20that%20belongs%20to%20this%20subset%20with%20a%20calendar%20issue.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20this%20user%20opens%20his%20calendar%20and%20creates%20an%20invite%2C%20he%20must%20send%20that%20invite%20from%20his%20domain1%20account.%26nbsp%3B%20That%20is%2C%20if%20he%20clicks%20the%20%22From%22%20button%20on%20the%20invite%20he%20only%20has%20his%20domian1%20account%20available.%26nbsp%3B%20This%20means%20that%20the%20meeting%20he%20is%20sending%20the%20invite%20from%20only%20shows%20up%20on%20his%20domain1%20calendar.%26nbsp%3B%20Now%2C%20if%20he%20goes%20into%20his%20email%20(this%20is%20all%20being%20done%20in%20the%20Outlook%20client%2C%20not%20the%20web%20interface)%2C%20he%20can%20in%20fact%20create%20an%20email%20and%20click%20the%20%22From%22%20button%20and%20select%20that%20email%20either%20come%20from%20his%20account%20in%20domain1%20or%20domain2.%26nbsp%3B%20Now%20the%20problem%20is%20he%20ends%20up%20having%20to%20manage%202%20calendars.%26nbsp%3B%20Also%2C%20people%20he%20has%20shared%20his%20calendar%20with%20are%20not%20seeing%20meetings%20as%20they%20may%20only%20look%20at%20one%20calendar%20or%20the%20other.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHe%20only%20has%20a%20basic%20license%20attached%20to%20his%20domain2%20account%2C%20and%20a%20standard%20license%20attached%20to%20his%20domain1%20account%2C%20if%20that%20means%20anything.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20considering%20just%20deleting%20his%20domain1%20account%20as%20he%20doesn't%20use%20it%20much%2C%20but%20that%20brings%20up%20other%20issues.%26nbsp%3B%20Is%20that%20my%20only%20recourse%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Contributor

Our tenant has 2 domains that we use.  Call them domain1 and domain2.  Everybody has an account in domain1.  A subset of these same people have an account in domain2.  I have a user that belongs to this subset with a calendar issue.

 

If this user opens his calendar and creates an invite, he must send that invite from his domain1 account.  That is, if he clicks the "From" button on the invite he only has his domian1 account available.  This means that the meeting he is sending the invite from only shows up on his domain1 calendar.  Now, if he goes into his email (this is all being done in the Outlook client, not the web interface), he can in fact create an email and click the "From" button and select that email either come from his account in domain1 or domain2.  Now the problem is he ends up having to manage 2 calendars.  Also, people he has shared his calendar with are not seeing meetings as they may only look at one calendar or the other.

 

He only has a basic license attached to his domain2 account, and a standard license attached to his domain1 account, if that means anything.

 

I'm considering just deleting his domain1 account as he doesn't use it much, but that brings up other issues.  Is that my only recourse?

0 Replies