Forum Discussion
Calendar button missing - On Prem 2016 Exchange
Hi,
We have a on-prem 2016 exchange with the lastest updates, but we still doesn't get the Calendar button in teams.
Is this even possible when we only have an onpremise exchange and not hybrid?
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.
39 Replies
you must have an Oauth configuration for the calendar to appear. To do this either enable a Full Hybrid solution which will configure Oauth for you, or exchange minimal hybrid +
https://docs.microsoft.com/en-us/exchange/configure-oauth-authentication-between-exchange-and-exchange-online-organizations-exchange-2013-help
David Bargna please allow me to add my 2 cents.
You don't really need Exchange full or minimal to get the calendar button in Microsoft Teams.
It is enough if you have
- Azure AD Connect, active Exchange Hybrid under sync options
- Autodiscover entry in Public DNS and Exchange Server accessible from MS Teams IP addresses
- OAUTH configured as described in the following article, steps 1-5 should be enough
- https://docs.microsoft.com/exchange/configure-oauth-authentication-between-exchange-and-exchange-online-organizations-exchange-2013-help
Please let me know if your issue is solved and mark also the reply that helped you as correct.
Thank you
Spikar
- Hello Sir,
Any idea why I'm getting this error when I try to export auth cert from step 3?
You cannot call a method on a null-valued expression.
At C:\ExportAuthCert.ps1:9 char:1
+ $certBytes = $oAuthCert.Export($certType)
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [], RuntimeException
+ FullyQualifiedErrorId : InvokeMethodOnNull
Exception calling "WriteAllBytes" with "2" argument(s): "Value cannot be null.
Parameter name: bytes"
At C:\ExportAuthCert.ps1:11 char:1
+ [System.IO.File]::WriteAllBytes($CertFile, $certBytes)
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : ArgumentNullException
David Bargna thanks! It's finally working after enabling Oauth 🙂
- EdsonSerrano
Microsoft
has-dbk Enable "Exchange Hybrid Deployment" option in Azure AD Connect and re-run HCW (new version released yesterday - http://aka.ms/hybridwizard). The key is OAuth configuration.
EdsonSerrano Thanks for your answer. We have now done the steps with configuring the hybrid environment, and moved a couple of mailboxes to the cloud, even then they wont get the calendar button.
If we move new mailboxes from on-premise to O365, they get the calendar button.Could Oauth still be the problem?
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.
EdsonSerrano as far as I know, the Exchange Hybrid option in Azure AD Connect should be enough. Exchange Hybrid configuration is something different and not needed for the calendar functionality in Teams when the mailbox resides on-premises as far as OAuth Authentication between Exchange and Office 365 is working.
Please correct me if I am wrong
Hey,
I have the same problem/question and I'm new to exchange and O365 authentication methods.
Can you tell how I can check if OAuth is functioning after configuring Azure AD Sync and if not, what need I to do to get OAuth working?
Kind Regards
- Afaik, no
To me it looks like this should be working based on what MS says online, but its not. Maybe it's possible to start connecting the exchange and O365 without moving all the mailboxes into O365?
We haven't done anything with the "Hybrid" setting in our ECP.- https://docs.microsoft.com/en-us/microsoftteams/exchange-teams-interact
With Exchange 2016 SP3 or later I should work, but you need to sync exchange properties with AADSync. Exchange EWS have to be published for your on-premises environment.
