Merge pull request #9790 from CarlosFarrica/docs-editor/teams-exchange-interaction-iss-1759147180

Update teams-exchange-interaction-issue.md

Author: Cloud-Writer

Teams/exchange-integration/teams-exchange-interaction-issue.md

@@ -53,14 +53,15 @@ To integrate the Teams service with your installation of Exchange Server, make s
 - Validate the [version and environment compatibility](/MicrosoftTeams/exchange-teams-interact) of Microsoft Exchange Server and Microsoft Teams in your deployment.
 - Microsoft Teams must be aware whether the mailbox is hosted on Exchange Online, on-premises, or in a [hybrid Exchange server deployment](/exchange/exchange-hybrid). Teams services call the Exchange Online services through an Autodiscover V2 call, which is redirected to on-premises servers hosting the mailbox in a hybrid configuration.
 - Exchange Online integrates with the on-premises Exchange server environment, as described in [What is OAuth authentication](/exchange/using-oauth-authentication-to-support-ediscovery-in-an-exchange-hybrid-deployment-exchange-2013-help#what-is-oauth-authentication). It's preferable that you configure it by running the Exchange Hybrid Wizard, but the same result can be achieved manually as described in [Configure OAuth authentication between Exchange and Exchange Online organizations](/exchange/configure-oauth-authentication-between-exchange-and-exchange-online-organizations-exchange-2013-help). Exchange Online is represented by the application ID `00000002-0000-0ff1-ce00-000000000000`.
-- Additionally, Teams services need to authenticate on behalf of the user to access the mailbox hosted on-premises also using OAuth. In this case the application ID of Skype for Business Online `00000004-0000-0ff1-ce00-000000000000` is used by the Teams scheduling service, together with MailUser referenced at [Configure Integration and OAuth between Skype for Business Online and Exchange Server](/skypeforbusiness/deploy/integrate-with-exchange-server/oauth-with-online-and-on-premises):
-  - The account is hidden from the Exchange address book. It's a best practice to hide the account from the address book because it's a disabled account.
+- Additionally, Teams services need to use OAuth to authenticate on behalf of the user to access the mailbox hosted on-premises. The Teams scheduling service uses the 'TeamsScheduler' application that has '7557eb47-c689-4224-abcf-aef9bd7573df' as the app ID, together with TeamsIntegrationRole referenced at [Create a new Mail User account used by partner applications](/skypeforbusiness/deploy/integrate-with-exchange-server/oauth-with-online-and-on-premises#step-2-create-a-new-mail-user-account-used-by-partner-applications). 
+
+- The account is hidden from the Exchange address book. It's a best practice to hide the account from the address book because it's a disabled account.
   - The account has an Exchange management role assignment of [UserApplication](/exchange/userapplication-role-exchange-2013-help).
   - For retention and archiving, a role assignment of [ArchiveApplication](/exchange/archiveapplication-role-exchange-2013-help) is required.
   - All steps in the article are required for full Teams and Exchange server on-premises.
 
-  > [!NOTE]
-  > An example of Microsoft identity platform and OAuth 2.0 usage can be found [here](/azure/active-directory/develop/v2-oauth2-on-behalf-of-flow).
+[!NOTE]
+
 - You should configure your internet-facing firewall or reverse proxy server to allow Microsoft Teams to access the servers that are running Exchange Server by adding the URLs and IP address ranges for Skype for Business Online and Microsoft Teams into the allowlist. For more information, see [Microsoft 365 URLs and IP address ranges - Microsoft Teams](/microsoft-365/enterprise/urls-and-ip-address-ranges?view=o365-worldwide#microsoft-teams&preserve-view=true).
 - Exchange Autodiscover V2 is required to allow the Teams service to perform an unauthenticated discovery against the user's mailbox that's located in Exchange Server. Autodiscover V2 is fully supported in Exchange Server 2013 Cumulative Update 19 or later. This is enough to enable Teams delegation to work correctly. However, the Teams Calendar app requires Exchange Server 2016 Cumulative Update 3 or later to be installed. Therefore, for full feature support, Exchange Server 2016 Cumulative Update 3 or later is required.