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.
rvt20s glad that the solution worked.
Regarding the additional domains yes further steps are necessary.
To open your calendar in MS Teams, MS Teams backend services will run an autodiscover process for the domain fo the user. If you have configured everything only for your main domain, step 5 should be repeated for the additional domains. Keep in mind that you also need an autodiscover.DOMAIN.com entry in your Public DNS that points to your Exchange server. If your Exchange server doesn't include the other domains in the certificate with the entry autodiscover.DOMAIN.com then you should create SRV records for each domain and remove the A record that points to autodiscover. With SRV record you will redirect the connection to your public domain that is included in the certificate of the exchange server without issue.
Please let me know if everything worked as excepted.
Kind regards
Spikar
Spiros Karampinis - Thank you very much! Working now since adding the dns SRV records (due to mismatch on domain name)
kcmoun glad that I could help you.
Please don't forget to "like" the reply that helped you to solve your issue,
so you identify the right solution for your case and also reward the corresponding colleague for his contribution.
Kind regards
Spikar