Prevent the script from creating the SO in DAuth scenarios#2399
Merged
Conversation
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
dpaulson45
approved these changes
Aug 21, 2025
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.
Issue:
We noticed that some customers ran the script in DAuth (no OAuth configured). Creating the Setting Override (SO) in this scenarios, might break workflows like Free/Busy, Profile Picture and MailTips.
Reason:
In pure DAuth scenarios, the dedicated hybrid app is not being used. It's therefore not necessary to create the SO to enable the feature.
Fix:
Exchange Onlineexists and is enabledIntraOrganizationConnectorwhich is enabled (we can't do deeper validation here since this command can be executed in disconnected mode in case that theCustomAppIdwas provided)Validation:
Lab