microsoft / microsoft/CSS-Exchange

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

Open
#2,346 1 comment 0 reactions 1 assignee View on GitHub

@lusassl-msft is already working on this.

Since Jun 3, 2025.

Enhancement Health Checker Need Investigation Triage
Dominant language
PowerShell
Stars
1.3k
Forks
395
Avg merge
14h 7m
Merged PRs (30d)
5

Description

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.