Forum Discussion
Calendar button missing - On Prem 2016 Exchange
I had exactly the same issue as you and have solved it by following OAUTH manual setup to the letter via this doc https://docs.microsoft.com/en-us/exchange/configure-oauth-authentication-between-exchange-and-exchange-online-organizations-exchange-2013-help?redirectedfrom=MSDN
Get-IntraOrganizationConnector |fl Name,TargetAddressDomains,DiscoveryEndpoint,Enabled
brought no errors but no data. I had previously ran HCW and this completed with no errors (I assumed the hybrid process was fully complete). Exchange 2016 on premises, premium office 365 with licenses applied for exchange online plan. No mailboxes have been migrated, all are on premises. On premises existing Mail contacts and groups WERE visible in exchange online admin. AD Azure connect was already run with optional hybrid exchange enabled. Calendar button did not appear in teams. Teams worked otherwise.
So I ran the manual configuration of OAUTH from that link and calendar button started to appear after 30 mins. Again, these are ALL on premises mailboxes, we have not migrated any mailboxes yet.
One caveat, at the end of the process you need to create an AD object - this object had already been created so it looked like HCW had at least tried to make the OAUTH link but hadnt fully completed it.
Nice it works well - only one small thing is missing - adding the channel to a meeting will give an error since the mail boxes for the "channel team" has not been recognized by Exchange as a valid mail-address.
Rest is so far I can see now working well - Thank you Spiros
PS: I am a user - so got our IT-guys to follow your instruction - they first replied that there was an error in the set-up from MS
Microsoftholmj Can you check if the group's email address has a special character in it? Get-UnifiedGroup -Identity "Group name" cmdlet will show email address of the group.
If there is then it needs to changed to something that does not contain special character for channel meeting scheduling to work.
Tushar Pathak Hi Tushar,
here is an example of the e-mail adress (auto-generated from Teams)
General - sales <b576444f.xxxxx.xx@emea.teams.ms> (I have left out company name in first block and put in some x instead - otherwise it is identical with the channel email-adress.
Meeting is added nicely in channel
Invitation is sent to all in the channel with "team" as organizer -
only the "accept" on meeting give an error since the reply goes to Team adress - mentioned above and this is not present in On Prem 2016 Exchange
Work Around could be "edit before reply - delete group adress and insert organizer e-mail insted"
Understand that alternative would be to go "on Line" or make a real Hybrid with both On prem and On line - which we do not want to do right now at least.
Have a nice day out there
holmj
holmj if I understand your issue properly, your "issue" is not an issue and your on-premises Exchange server won't need any special configuration to be able to "find" the MS Teams e-mail address as those are using generic e-mail addresses with a Microsoft domain that it is already properly registered and publicized.
Your issue should be all the way around, meaning, the invitation of the MS Teams services are not able to "reach" the on-premises users because of not properly configured mail flow between Office 365 and Exchange on-premises infrastructure.Please check your mail flow and make sure that a cloud user is able to exchange e-mails with on-premises users before we proceed further with the troubleshooting
Have a nice day
Spikar
