HC-EXOconnector doesn't cover all scenarios for routing mail from Onprem to EXO.#2261
Merged
Conversation
…rem to External domains in this check. Updated documentation
dpaulson45
approved these changes
Dec 17, 2024
Member
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
HC-EXOconnector doesn't cover all scenarios for routing mail from Onprem to EXO.
Issue:
Display for HCEXOConnecoter can't cover all scenarios for routing mail from Onprem to EXO.
Reason:
Reduce confusion.
Fix:
Updated output to be Yellow instead of Red and documentation in https://aka.ms/hc-exoconnectorissue
Validation: