[Improvement] - Health Checker: Dedicated Exchange Hybrid Application is recommended in no rich coexistence hybrid configuration

[kadmos36]

Provide Version Number
25.05.28.1447

Describe the issue
The Healthchecker says the we should create the dedicated hybrid application, because the script checks only with Get-SettingOverride.

Expected behavior
The Script should only output the recommendation for dedicated hybrid app if Get-HybridConfiguration returns one or more Features that are part of the rich coexistence.

Script Output
Feature(s) enabled for Hybrid use: SecureMail Dedicated Exchange Hybrid Application: Configure the dedicated hybrid app to ensure hybrid features continue working in the future More information: https://aka.ms/HC-ExchangeHybridApplication

Additional context

• Following the Exchange Blog Article: https://techcommunity.microsoft.com/blog/exchange/exchange-server-security-changes-for-hybrid-deployments/4396833 we removed with ConfigureExchangeHybridApplication.ps1 -ResetFirstPartyServicePrincipalKeyCredentials the keycredentials as recommended in the blog article.
• We have manually set the Hybrid Configuration to non rich coexistence with Set-HybridConfiguration -Features SecureMail
• I'm not sure, but rich coexistence features should be: FreeBusy, MailTips and Photos
• The Healthchecker script was run from server with only the Management tools.
• We use on premise Exchange only for routing E-Mails from local applications to Exchange Online, or external recipients, and for recipients management

[lusassl-msft]

@kadmos36 thanks for reaching out. Unfortunately, we can't rely on the values returned by Get-HybridConfiguration (except SecureMail). since these settings are no longer used by Exchange Server to determine the hybrid configuration state. We would therefore need to check for the different configurations instead (for example, IntraOrganizationConnector). Let me add this work item to the backlog for triage.