MS Teams 'calendar' tab missing

[ITGURU]

Hi,

I currently have Exchange 2016 local install and starting to use teams. Users do not have the 'calendar' icon resulting in unable to schedule meetings or meet now.

I believe this has something to do with oAuth.

Has anyone else with Local exchange only set this up and able to assist with what steps they took, without setting up a hybrid configuration?

I am using the MS sync tool to sync users from AD to 365.

Thanks.

[3s-gtech]

I *think* you’ll need a fairly recent Exchange 2016 CU, alongside a Hybrid configuration, for that to become available. The mailboxes themselves can stay on-prem, but you’ll need to have the O365 mail side configured at a basic level.

[ITGURU]

I *think* you’ll need a fairly recent Exchange 2016 CU, alongside a Hybrid configuration, for that to become available. The mailboxes themselves can stay on-prem, but you’ll need to have the O365 mail side configured at a basic level.

 

I have read several articles online...

 

I am on exchange 2016 CU 8 so should be ok.

 

Just wondered what the next steps would be. Once I've enabled hybrid from Exchange, will i also need to amend the Azure AD Sync tool to include hybrid settings?

[Jonah]

We've recently done this (after resolving a bizarre issue that wouldn't let the Hybrid Configuration Wizard identify the logged in user!).

 

You'll need Hybrid configured (via the HCW), and "Exchange Hybrid Deployment" set in your Azure AD Connect. Users will also need an EOL license assigned.

 

You may need to update your Exchange servers to a more recent CU, as from the HCW log file, the minimum supported versions of Exchange are:

 

Supported Releases:

Exchange Server 2019 "E19" RTM Version 15.2 (Build 221.12)

Exchange Server 2016 "E16" CU11 Version 15.1 (Build 1591.1)

Exchange Server 2016 "E16" CU10 Version 15.1 (Build 1531.3)

Exchange Server 2013 "E15" CU21 Version 15.0 (Build 1395.4)

Exchange Server 2013 "E15" CU20 Version 15.0 (Build 1367.3)

Exchange Server 2010 "E14" SP3/RU25 Version 14.3 (Build 435.0)

Exchange Server 2010 "E14" SP3/RU24 Version 14.3 (Build 419.0)

[ITGURU]

We've recently done this (after resolving a bizarre issue that wouldn't let the Hybrid Configuration Wizard identify the logged in user!).

 

You'll need Hybrid configured (via the HCW), and "Exchange Hybrid Deployment" set in your Azure AD Connect. Users will also need an EOL license assigned.

 

You may need to update your Exchange servers to a more recent CU, as from the HCW log file, the minimum supported versions of Exchange are:

 

Supported Releases:

Exchange Server 2019 "E19" RTM Version 15.2 (Build 221.12)

Exchange Server 2016 "E16" CU11 Version 15.1 (Build 1591.1)

Exchange Server 2016 "E16" CU10 Version 15.1 (Build 1531.3)

Exchange Server 2013 "E15" CU21 Version 15.0 (Build 1395.4)

Exchange Server 2013 "E15" CU20 Version 15.0 (Build 1367.3)

Exchange Server 2010 "E14" SP3/RU25 Version 14.3 (Build 435.0)

Exchange Server 2010 "E14" SP3/RU24 Version 14.3 (Build 419.0)

 

I thought that an EOL license wasn't required otherwise it kind defeats the purpose....users will login to 'mail' and send emails, but any incoming emails will go back to local exchange server. trying to prevent them using exchange online (365)

[Jonah]

I could be wrong, but I'm fairly sure even with the Hybrid stuff configured, our staff didn't get the Calendar tab until we assigned an EOL license.

 

If you have Hybrid set up and your Azure AD Connect configured for Hybrid Exchange (so the various exchange GUIDs get sync'd), when you assign an EOL license it will only pre-provision a mailbox, etc. in preparation for any future migration. All our staff are currently still on-prem, but have an EOL license assigned - in the Admin portal it'll show "This user's on-premises mailbox hasn't been migrated to ‎Exchange Online‎. The ‎Exchange Online‎ mailbox will be available after migration is completed.", and if they open Outlook on the web, they'll be presented with a link to your on-prem OWA:

 

 

EDIT: I've had a brief scan online - you could be right, the EOL may not be necessary for the calendar function in teams - we assigned them anyway as we'll be migrating to EOL in the future.

Edited June 8, 2020 by Jonah

[ITGURU]

It appears that when I followed the guide as soon as i enabled the hybrid option in AD azure sync tool the user did change to This user's on-premises mailbox hasn't been migrated to ‎Exchange Online‎. The ‎Exchange Online‎ mailbox will be available after migration is completed

under the 'mail tab'

I attempted the oauth powershell but the test still came back failed, so might just leave it.

Tested with a user and they can now see calendar and schedule meetings.

[Domino]

I followed this: https://jaapwesselius.com/2020/04/06/configure-oauth-authentication-in-exchange-2016/

 

No Hybrid, No Exchange Online Licenses for users. Your EWS needs to be externally accessible.

[ITGURU]

Followed same article but when run Test-OAuthConnectivity -Service EWS -TargetUri https://outlook.office365.com/ews/exchange.asmx -Mailbox [email protected] -Verbose | Format-List

it comes back as FAILED (even when i replace with a valid email address)

 

Some authentication failed error message.

 

Once OAuth is configured should it pull calendar from exchange users calendar?

[ITGURU]

Even though the test fails, it does appear that when i create a teams meeting it is saving the calendar entry to local exchange, so i'm happy

[KK20]

run this

Get-IntraOrganizationConnector |fl Name,TargetAddressDomains,DiscoveryEndpoint,Enabled

if you get no error but also no response then your OATH is borked and the cause (this was our cause). To fix, run through this:

https://docs.microsoft.com/en-us/exchange/configure-oauth-authentication-between-exchange-and-exchange-online-organizations-exchange-2013-help?redirectedfrom=MSDN run through it all and don't be tempted to cut corners....

 

we use hybrid 2016, ran through hybrid wizard without issue. No mailboxes have been migrated.

[CAWJames]

Just to add to this, Autodiscover has to work properly and point back to your on-prem, and not O365 when in hybrid anyway, as the DNS setup when you setup email wants you to point AutoDiscover to Cloud, which removes the calendar icon as Teams can't find on-prem calendaring!