Update TeamsClientConfiguration and TeamsUpdateManagementPolicy with OCDIRedirect/UseUnifiedDomain attributes #13197
Conversation
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
|
Learn Build status updates of commit 3e8f797: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Learn Build status updates of commit a77f5d8: ✅ Validation status: passed
For more details, please refer to the build report. |
kevintan250
changed the title
SerdarSoysal
added
the
Sign off
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 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.
The OCDIRedirect attribute in Teams Update Management Policy has been moved and reconfigured as the UseUnfiedDomain attribute in Teams Client Configuration. This PR removes the documentation added in anticipation of the OCDIRedirect attribute being published and moves it to describe the UseUnifiedDomain attribute instead.